From DM

Dear Careerlanders,

I have an MD who doesn't believe in taxes, I have informed him by sending mails of the implications of not remitting taxes.

He recently requested for TCC and I informed him it will be difficult to get because we have not been filing for VAT since 2019 plus their are penalities and fines attached to not filing.

He said, "any road side accountant can get TCC, why am I finding it difficult to get TCC".

The organization was incorporated in 2018 but started officially in 2019 they only did 2020 & 2021 audited financial statements (AFS) and it's not on tax promax and I informed him of the implications of our actions.

The auditor (to me is not an auditor because I haven't seen an auditor with earrings in my entire life) said tax pro max said tax pro max is the same as accounting software & it started in 2022 & I am supposed to know how to put it on tax Pro max but I informed him that from the (AFS) there's an annual turnover of 100m+ for 2020 and I asked if his aware of the implications given the fact that the company have not filed any VAT since 2019 he didn't respond.
I probed further, asking him since TPM came out in 2022 and the AFS of 2021 was done in 2022, why didn't he inform the organization about the news development and it's implications? He said, he was only contracted to do AFS.

It took serious fight to do the AFS for 2022 and it even the AFS is done half way (draft copy) and yet to be completed, the MD cited the fact that the current auditor (not the one with earrings) want to expose them to tax labilities because of the money he wants to collect, but I said no, his only informing us about the likelihood of our actions, if we go with 100m+ as turnover in the AFS 2020.

How best do you handle such boss because the auditor is telling my boss that I am supposed to know how to prepare audited financial statements and I said No, there's a difference between an auditor and an accountant.

Kindly help the best way to handle this lingering issue.

Hello fellow forum members,

Let's engage in a scenario-based discussion to enhance our problem-solving skills. Imagine you find yourself in the following situation at the workplace, and I'd love to hear your thoughts on how you would handle it:

Scenario: Balancing Tight Deadlines and Quality Assurance

You're leading a project team responsible for developing a critical software application. The project has tight deadlines due to market demands, and upper management is pushing for speedy delivery. However, your team is concerned that rushing might compromise the quality and functionality of the software.

What would you do in this situation? How would you strike a balance between meeting the deadlines and ensuring the highest possible quality of the software? Consider the perspectives of your team, stakeholders, and the organization's overall objectives.

Here's my take on it:

In this scenario, I would initiate a strategic approach to address the challenge:

Assess the Scope: First, I would thoroughly assess the project scope and identify essential features and functionalities. This would help prioritize tasks and ensure that we focus on delivering the core requirements.

Communicate with Stakeholders: I would have an open and transparent conversation with stakeholders, including upper management. I'd present the potential risks of compromising quality for speed and the potential consequences for the end-users and the organization's reputation.

Resource Allocation: I would evaluate the availability of resources and talent within the team. If possible, I'd explore the option of adding additional resources or adjusting team members' roles to ensure a balance between speed and quality.

Phased Approach: To meet tight deadlines without sacrificing quality, I would consider adopting a phased approach. We could prioritize and release essential features first, followed by subsequent updates that enhance functionality and quality.

Testing and Quality Assurance: Quality assurance is non-negotiable. I would allocate sufficient time for rigorous testing and quality checks. This might involve automated testing, thorough code reviews, and user acceptance testing.

Risk Management: I would proactively identify potential risks and mitigation strategies. This might involve having contingency plans in place and monitoring the project closely for any signs of deviation from the plan.

Feedback Loop: Throughout the process, I would maintain open lines of communication with the team. Regular feedback sessions would provide an avenue for addressing concerns, sharing progress updates, and making any necessary course corrections.

Remember, every workplace challenge presents an opportunity for growth and learning. By collectively sharing our strategies and insights, we can develop a diverse set of approaches to tackle complex scenarios like this one.

Now, over to you! How would you handle this situation? Let's brainstorm and learn from each other's perspectives.

Looking forward to your valuable input,
[PMO Global Institute]