5 Areas We Would Review Before Submitting MITRS

In our experience, most MITRS issues do not arise because a document is missing. They arise because two documents tell different stories.

Before MITRS, inconsistencies between the financial statements, tax computation, capital allowance schedule and incentive schedules might only surface when LHDN opened an audit and requested the full file. Now, all four documents are submitted together as part of the MITRS process. A cross-document review that previously happened at audit stage can happen much earlier.

We rarely find problems because a client forgot to upload a document. We usually find problems because different documents were prepared by different people at different times and nobody compared them side by side.

Before we allow a client’s MITRS submission to go in, we focus on five areas where inconsistencies most commonly occur.

Area 1 — Form C vs the Finalised Accounts

The most common version-control issue we encounter is this: Form C and the tax computation were prepared based on draft accounts, and the final audited financial statements came out slightly different.

Where audited financial statements are not finalised before the Form C filing deadline, companies should assess the implications early. Depending on the circumstances, an application for e-Lanjutan Masa may be required to avoid filing based on incomplete information. Our guide explains the application process and timelines:
e-Lanjutan Masa Guide 2026

Under MITRS, the final signed AFS and the tax computation are submitted together. If the profit before tax in the AFS does not agree to the opening figure in the computation, the inconsistency exists from the moment both documents are submitted together.

Area 2 — Fixed Asset Note vs Capital Allowance Schedule

This is the reconciliation we find most frequently produces unexplained gaps. The fixed asset note in the AFS and the capital allowance schedule are prepared independently — often by different people at different stages of the year-end process. By the time MITRS submission arrives, they may not have been compared against each other.

When the two documents are read side by side, additions, disposals, and closing balances should correspond. Where they do not, the gap needs an explanation before the submission goes in. A disposal that appears in the fixed asset note but is absent from the CA schedule raises the question of whether a balancing charge or allowance has been correctly computed. An asset addition in the CA schedule that does not appear in the fixed asset note raises its own set of questions.

Area 3 — Expense Disclosures vs Tax Add-Backs

This is the area most directly connected to the mindset we discussed in Part 2 of this series. The AFS discloses expenses by nature. The tax computation determines which of those expenses are fully deductible, partially deductible, or non-allowable. Where the two documents are inconsistent, the gap requires explanation.

A straightforward example: the AFS shows entertainment expenses of RM80,000. The tax computation shows an entertainment add-back of RM0. That is not automatically wrong — if the expenses are wholly client-related and supported by documentation, full deductibility may be justified. But it deserves review before submission rather than after a question arrives.

The same applies to maintenance and repairs, motor vehicle expenses, travel, professional fees, and director-related costs. In each case, the question is not whether the expense appears in the AFS — it is whether the tax treatment in the computation is consistent with the nature and purpose of the expense.

Area 4 — Related Party Transactions and Director-Related Balances

The related party note in the AFS discloses the nature and quantum of transactions between the company and its connected parties — directors, shareholders, related companies. Under MITRS, that note sits alongside the tax computation that determines how those transactions are treated. The two need to be consistent.

For related-party transactions, we focus on whether each transaction is properly documented, commercially supportable, and treated consistently in the tax computation. The transactions that most commonly require attention are management fees paid to related companies, rental paid to directors or shareholders, and loans or advances to and from directors.

Area 5 — Incentive Claims and Supporting Documentation

From our audit experience, incentive claims are often one of the first areas reviewed because the tax savings can be significant and the qualifying conditions are highly specific. Pioneer status, investment tax allowance, reinvestment allowance, and special deductions each carry their own eligibility requirements, approval conditions, and computation mechanics. Under MITRS, the incentive computation sits in LHDN’s system at the point of filing — not only when a CP700 is issued.

The checks here focus on two things: internal consistency, and consistency with the business activity disclosed in the AFS. An incentive claim must reconcile across the incentive computation schedule, Form C Part D, and the prior-year carry-forward position. And the qualifying activity described in the incentive schedule needs to be consistent with the nature of the business as disclosed in the AFS — revenue breakdown, segment information, and the directors’ report narrative.

Before the Submission Goes In

These five areas are not a comprehensive audit. They are the cross-document consistency checks that, in our experience, catch most of the issues before they become harder to explain.

The underlying question in each area is the same as the one we discussed in Part 2: not whether the position can be claimed, but whether it can be defended — with the financial statements, tax computation, capital allowance schedule and incentive computations all telling the same story.

Source: Section 82B, Section 33(1), Section 39, and Schedule 3, Income Tax Act 1967; LHDN MITRS official guidance; Finance Act (Amendment) 2024.