Willow Audit Willow Club Willow Academy
Articles

Correcting UAE Corporate Tax returns when an error does not change Due Tax. Interpreting amended Article 10(5) of the UAE Tax Proce-dures Law effective 1 January 2026

Federal Decree‑Law No. 28 of 2022 on Tax Procedures (the “Tax Procedures Law” or “TPL”), as amended with effect from 1 January 2026, revises the rule on “nil” corrections (errors that do not change the amount of Due Tax). The amended Article 10(5) introduces a split:

  • in cases specified by the Federal Tax Authority (“FTA”), such errors must be corrected by a Voluntary Disclosure;
  • in any other case, the error may be corrected “via a Tax Return”. This study explores the change, links it to the TPL Executive Regulation which already foreshadowed a dual route, and proposes a cautious, practi-tioner‑friendly approach for Corporate Tax items that are frequently “tax‑neu-tral” in the current period but decisive for future periods (e.g. Tax Losses, Free Zone de minimis calculations, substance‑related data points, and Transfer Pric-ing disclosures).

The 2026 amendment

1. Before 1 January 2026, Article 10(5) the Tax Procedures Law was commonly read as a blanket rule: if a taxpayer discovers an error or omission in a Tax Return and the amount of Due Tax does not change, the taxpayer “must” correct the return by submitting a Voluntary Disclosure.

2. From 1 January 2026, Article 10(5) adopts a split-route approach: such errors must be corrected by VD only “in the cases specified by the Authority”, and in “any other cases” must be corrected “via a Tax Return”.

Before 2026From 2026
If the Taxpayer discovers an error or omission in the Tax Return submitted to the Authority, where there is no difference in the amount of Due Tax, the Taxpayer must correct such return by submitting a Voluntary Disclosure.If the Taxpayer discovers an error or omission in the Tax Return submitted to the Authority, where there is no difference in the amount of Due Tax, the Taxpayer must correct such error by submitting a Voluntary Disclosure in the cases specified by the Authority, or correct such error via a Tax Return in any other case.

3. The amendment has two distinct effects:

  • Clarification of the VD hierarchy.

What the 2026 text makes explicit at primary-law level is that VD is not the universal response to nil-difference errors. Rather it is required only where the Authority has specified it.

That ordering was already foreshadowed in delegated legislation. Even before 2026, the Executive Regulation contemplated two paths for tax-neutral errors. Article 10(3) provides that where the taxpayer discovers an error or omission in a Tax Return “with no effect on the amount of Payable Tax”, the taxpayer must “correct the error or submit a Voluntary Disclosure … as may be specified by the Authority” This sits comfortably with earlier edition the Tax Procedures Law, which mandates that the Executive Regulation specify the provisions, procedures, and conditions for VDs in Article 10(6). The 2026 amendment therefore reduces the doctrinal tension by aligning the statute with the split logic already signaled in the Executive Regulation.

  • A positive duty to correct outside VD.

The more consequential novelty is the second half of the sentence: beyond the Authority-specified cases, nil-difference errors must be corrected “via a Tax Return.” In other words, the post-2026 regime does not merely narrow the scope of mandatory VD. It also closes the space for leaving purely informational inaccuracies uncorrected. Where the Authority has not required VD, the taxpayer must still cure the defect—through the Tax Return channel.

4. The following two examples show how the 2026 version of Article 10(5) shifts nil-difference errors from a VD-default approach to a Tax Return-default approach, even where the mistake is purely informational and does not change the tax outcome.

4.1. Example 1 (VAT): a nil-difference error not covered by the FTA’s VD-only decision.

Assume a VAT-registered business receives imported services subject to the reverse charge mechanism (RCM). In completing the VAT return, the business overstates the net value of those reverse-charge services in Box 3: “Supplies subject to the reverse charge provisions” in the Outputs section. The taxpayer also overstates the corresponding output VAT due in the VAT Amount column of that same box.

At the same time, the business makes an equal and corresponding overstatement in Box 10: “Supplies subject to the reverse charge provisions” in the Inputs section, claiming the same amount of VAT as recoverable input VAT. Box 10 is the recovery box specifically intended to recover VAT that the taxpayer accounted for as output tax under reverse charge (declared in the reverse charge output boxes), provided recovery is permitted.

As a result, the error does not change the net VAT payable for the period, because the VAT return computes Box 12 “Total value of due tax for the period” (driven up by the Box 3 overstatement) and Box 13 “Total value of recoverable tax for the period” (also driven up by the Box 10 overstatement), and then nets these in Box 14 “Payable tax for the period” (due tax less recoverable tax). If Box 12 and Box 13 move up by the same amount, Box 14 remains unchanged.

Before 2026, under Article 10(3) of the existing Executive Regulation, Voluntary Disclosure was only mandated for nil-difference errors that the FTA had explicitly specified. Since an error in RCM boxes, where equal amounts were overstated in both input and output tax, was not listed as requiring VD, it could remain uncorrected without breaching the rules.

However, after January 1, 2026, the amended Article 10(5) changes that. Now, if the FTA hasn’t specified VD for such a nil-difference error, it must be corrected “via the Tax Return”. In other words, what could have previously been left unadjusted now carries a default obligation to correct directly in the return.

4.2. Example 2 (Corporate Tax): reclassification between boxes with no impact on the tax base

Assume a taxpayer reports an item of income under the wrong disclosure line in the Corporate Tax return (e.g. one category of revenue is mistakenly entered under another revenue field), but the misclassification has no effect on (i) Taxable Income, (ii) Due Tax, or (iii) Corporate Tax Payable. The only defect is informational: the Authority’s record is inaccurate because the composition of revenue by category is misreported, even though the totals (and tax outcome) are correct.

Before 1 January 2026, this type of error could sit in the same “tax-neutral blind spot” as the RCM VAT example. While the pre-2026 wording of Article 10(5) was sometimes read broadly, the delegated framework had already moved toward specifying which nil-difference errors must be corrected by Voluntary Disclosure. A nil-difference Corporate Tax misclassification is not among Authority-specified VD cases. The return design does not offer a dedicated nil-difference correction mechanism. Therefore, the taxpayer could find that there is no clearly mandated and system-supported correction channel that updates the structured return record for a disclosure-only field. As a result, such misclassifications could, in practice, remain uncorrected (or be addressed only in internal working papers), precisely because the tax outcome is unchanged and the platform does not isolate or operationalize a correction route for nil-difference informational errors.

From 1 January 2026 onward, the situation changes. The change is that the nil-difference inaccuracy should no longer be left on file merely because it has no tax effect. Under the amended Article 10(5), where the error does not fall within Authority-specified VD cases, it must be corrected via a Tax Return by default.

The conceptual conclusion therefore mirrors the VAT RCM illustration: the taxpayer is expected to correct inaccurate return information even where Due Tax is unchanged.

5. The remaining constraint is operational, i.e. whether EmaraTax provides an amended-return workflow or a dedicated nil-difference correction schedule.

Entry into force and the practical timing of corrections

6. Federal Decree‑Law No. 17 of 2025 amended the Tax Procedures Law with effect from 1 January 2026, including the revised split‑route wording of Article 10(5).

7. Because Article 10(5) is triggered by the moment a taxpayer “discovers” the error or omission, the most defensible reading is that, from 1 January 2026 onwards, the taxpayer should be able to use the amended correction framework even where the underlying error relates to an earlier Corporate Tax Period. The compliance question is therefore not “which year did the error arise?”, but “when was it discovered and corrected?”.

The Federal Supreme Court’s doctrine of immediate and direct effect (الأثر الفوري المباشر) requires to apply the procedural amendments from their effective date to procedural steps taken thereafter and even to the ongoing effects of a pre-existing legal relationship. This is treated as “immediate application, not retroactive application”.[1]

8. In practice, however, the availability of the “Tax Return” route depends on how EmaraTax operationalizes correction. If the platform provides an amended‑return workflow for the relevant prior period, correction can occur immediately by resubmitting that period’s return via Voluntary Diclosure. If instead the platform follows a forward‑correction model, “via a Tax Return” will function as “through the next return that is still open for filing”, echoing the existing AED 10,000 underpayment mechanism described in Section 9.5.1 of the Corporate Tax Return Guide.

9. To illustrate the timing effects under a forward‑correction model, assume calendar‑year Tax Periods:

  • the 2024 return is due by 30 September 2025;
  • the 2025 return is due by 30 September 2026; and
  • the 2026 return is due by 30 September 2027.

If a nil‑Due‑Tax error in the 2024 return is discovered in March 2026, the earliest available return that can absorb the correction would ordinarily be the 2025 return, filed by 30 September 2026. If the same error is only discovered after the 2025 return has been filed (for example in November 2026), the earliest forward‑correction opportunity would typically shift to the 2026 return, filed by 30 September 2027. This explains why, in some cases, a calendar‑year taxpayer may only be able to implement a “Tax Return” correction route in 2027 unless a Voluntary Disclosure is filed.

In the same framework, errors relating to the 2025 Tax Period that are identified during 2026 before 2025 return is filed would normally be corrected in the 2025 return itself at filing time, because that return is still being prepared and has not yet been submitted.

[1] See Mahmoud Abuwasel, “October 2025 Amendments to the UAE Tax Procedures Law and Relevant Federal Supreme Court Case Law” (Wasel & Wasel, 30 Nov 2025), citing FSC Petitions Nos. 1480/2022 and 1/2023 (Administrative-Tax).

What does “correct via a Tax Return” mean in UAE practice?

10. The phrase “via a Tax Return” is not self-defining and can plausibly be read in more than one way:

  • Variant 1 “Direct correction in the same period’s return (without VD)”. The taxpayer corrects the relevant Tax Period’s return itself (i.e. an amended return for that period), using the Tax Return channel rather than filing a Voluntary Disclosure.
  • Variant 2 “Forward correction in the next (current) period’s return”. The taxpayer corrects the error in the return for the period in which the error is discovered. Under this reading, a 2025 error discovered in January 2026 would be reflected in the 2026 return (filed in 2027), rather than in the 2025 return that is yet to be filed in 2026.
  • Variant 3 “Correction in the earliest return that is still “open” (closest to discovery)”. The taxpayer corrects the error in the earliest return through which it can practically be corrected, which is either (i) the return for a previous Tax Period that is not yet due for submission, or (ii) the return for the Tax Period in which the error is discovered, whichever is earlier. By way of illustration, a 2025 error discovered in August 2026 would be corrected in the 2025 return if it has not yet been filed; if it has already been filed, the correction would be made in the 2026 return.

A fourth reading – treating “via a Tax Return” as meaning “through VD” – can be excluded. Article 10(5) expressly contrasts the two routes: Voluntary Disclosure in specified cases, or Tax Return in any other case.

11. Of the three variants, Variant 3 is the most defensible. It aligns “via a Tax Return” with the UAE’s established approach to return-based correction in other contexts. Article 10(1)(b) of the Executive Regulation uses the same operative concept (“correct the error in the Tax Return”) and then explains it through a priority rule: correct in a return that is not yet due for a previous Tax Period, or otherwise in the return for the Tax Period in which the error is discovered, whichever is earlier. This drafting technique shows how UAE tax procedure typically operationalize a “Tax Return route”: it is neither purely “same-period amendment” nor purely “next-year blending,” but a nearest-open-return model anchored to discovery and practical filing status.

12. This conclusion also fits the policy logic of Article 10(5). If “via a Tax Return” were read as Variant 2 in all cases, nil-difference errors could remain uncorrected for long periods simply because the next return may only become fileable much later (e.g. a calendar-year taxpayer discovering an error early in 2026 but only reflecting it in the 2026 return filed in 2027). That would sit uneasily with the evident intent of the 2026 amendment: to ensure that nil-difference inaccuracies are actually corrected, while reserving VD for the subset of cases the Authority has chosen to control through disclosure.

13. The practical implication is therefore twofold:

  • First, where EmaraTax provides an amended-return workflow for the affected period and field or schedule, “via a Tax Return” can operate as direct correction of that period’s return (Variant 1). This option doesn’t apply in the Authority’s specified VD-only cases.
  • Second, where no such amended-return workflow exists, “via a Tax Return” should be understood as Variant 3: correction in the earliest return through which the error can be implemented within the system’s architecture.

In either case, the taxpayer’s procedural objective remains the same: not merely to explain the error in working papers, but to ensure the Authority’s record is corrected through the channel that Article 10(5) treats as the default route for nil-difference mistakes.

14. Finally, this reading helps maintain the internal coherence of Article 10 as a whole: the UAE framework already distinguishes between (i) errors that affect the amount payable (with separate routing rules, including the AED 10,000 mechanism), and (ii) errors that do not affect Due Tax (now routed by Article 10(5) primarily through the Tax Return channel). Treating “via a Tax Return” as a nearest-open-return model preserves that structure.

How Variant 3 should be implemented

15. At present, neither the Tax Procedures Law nor the Executive Regulation sets out a dedicated, operational “in-return” workflow for correcting nil-difference errors. The tax return forms themselves do not contain a distinct set of fields expressly labelled for “nil-difference corrections”. The system therefore presents a practical gap:

  • the law (post-2026) speaks in principle about correction “via a Tax Return,”
  • but the return design does not yet provide a visible nil-difference schedule through which that instruction can be implemented.

16. In that setting, it is natural that practitioners look for the nearest existing in-return correction mechanism. The only structured correction workflow currently specified for the AED 10,000 or less prior-period correction. Because zero is, arithmetically, less than AED 10,000, nil-difference errors can be described as an extreme point on the same numerical scale. On that purely arithmetic view, it may appear reasonable, pending further FTA guidance, to test whether the AED 10,000 workflow can function as a practical proxy for nil-difference corrections, at least as a temporary implementation method until the Authority specifies a dedicated route.

17. However, this “zero is less than 10,000” bridge is only an entry point for analysis, not the conclusion. Later, we will explain why the AED 10,000 channel is not a literal or systematic fit for nil-difference errors, why it may be practically non-performing for record correction, and why a dedicated nil-difference schedule would better align the return design with the post-2026 routing rule in Article 10(5).

VAT: how the <AED 10,000 correction route works

18. The VAT Returns User Guide allows an earlier error to be corrected in the current VAT Return where the earlier mistake caused payable tax to be less than it should have been by not more than AED 10,000. In such a case, the taxpayer reflects only the net correction in the relevant fields of the current return.

19. That mechanism does not sit comfortably with a reverse-charge error where Box 3 and Box 10 were overstated by equal amounts. Suppose the taxpayer should have reported AED 100,000 in each box, but instead reported AED 120,000 in each. The original error overstated both the output and the recoverable input side by the same amount, so the net payable VAT remained unchanged.

If one were to correct that overstatement through a current-period entry, the correction would logically be a reversal of the excess amounts, not a further positive entry. In other words, the corrective logic would be to reduce the previously overstated figures, not to add AED 20,000 again to both boxes. But once framed correctly in that way, the conceptual problem becomes clearer: the < AED 10,000 route is designed for cases of underpaid payable VAT, whereas this type of reverse-charge mistake does not understate payable VAT at all. It distorts reporting lines, but not the net tax outcome.

20. The difficulty, therefore, is not that the return cannot arithmetically accommodate equal adjustments in Boxes 3 and 10. The difficulty is that the guide’s forward-correction route is expressed as a mechanism for correcting prior-period errors that affected payable VAT by not more than AED 10,000, whereas a nil-net reverse-charge misstatement is not naturally described in those terms. The mechanism reaches net payable tax but it does not clearly provide a dedicated route for cleansing an inaccurate historical reverse-charge reporting footprint.

Corporate Tax: the <AED 10,000 correction workflow

21. By contrast, the Corporate Tax return contains an explicit, structured workflow for prior-period errors with a limited tax impact. CTGTXR1 sets this out as a discrete EmaraTax question sequence:

  • Box 9.5.1 “Has the Taxable Person made an error in a prior Tax Period where the tax impact is AED 10,000 or less?”. If a prior return is incorrect “resulting in a calculation of the Corporate Tax Payable being less than it should have been by AED 10,000 or less,” the taxpayer “shall correct the error in the Tax Return that has not become due for submission for a previous Tax Period or in the Tax Return for the Tax Period in which the error has been discovered, whichever is earlier”
  • Box 9.5.2 “Tax Period(s) in respect of which the error has been reported” – select from a drop-down list; multiple periods can be selected.
  • Box 9.5.3 “Adjustment(s) in respect of errors made in prior Tax Periods”: “Enter the amount for each Tax Period separately. Enter the amount by which the Taxable Income is increased”. In practice, EmaraTax technically permits a “0” entry in this field.
  • Box 9.5.4 “Description of the nature of the adjustments”: “Enter a description, if applicable”. In practice, EmaraTax permits only a very limited amount of text in this field.

The guide also requires aggregation: if there is more than one error for a prior period, the aggregate tax impact must still be AED 10,000 or less.

22. CTGTXR1 also states the channel boundary in direct terms: “Any other error in respect of a prior Tax Period should not be adjusted for as part of the Tax Return and must be amended by way of a Voluntary Disclosure …” with reference to Article 10 of the TPL read together with Article 10 of Cabinet Decision No. 74 of 2023. “Any other” in this context means errors which may not be described as “errors, resulting in a calculation of the Corporate Tax Payable being less than it should have been by AED 10,000 or less”.

23. The practical relevance for nil-difference errors is that the Corporate Tax return presently provides no dedicated nil-difference correction fields (no schedule that allows taxpayers to correct disclosure-only inaccuracies with zero effect on Due Tax). In the current interface, the only structured “prior period correction” workflow is the 9.5.1–9.5.4 AED 10,000 sequence described above.

That is why practitioners inevitably consider whether nil-difference errors might be accommodated there as an extreme case, i.e. by entering “0” as the “amount by which the Taxable Income is increased” and describing the correction in the limited narrative field.

But CTGTXR1 makes clear that this workflow is triggered by an understatement of Corporate Tax Payable of AED 10,000 or less (i.e. an underpayment category), not by the nil-difference category. The result is a technically possible but conceptually strained workaround:

  • a zero-value entry communicates little,
  • the description box is not designed to carry multiple “before-after” disclosures, and
  • the correction may not be reflected where it matters (in the underlying schedules and attributes) unless EmaraTax introduces a genuine nil-difference correction schedule or an amended-return mechanism for those fields.

Interpreting “any other error” in CTGTXR1 after the 2026 amendment

24. CTGTXR1 states that “any other error” in respect of a prior Tax Period should not be adjusted through the Tax Return and must be amended by Voluntary Disclosure.

The phrase “any other” is not free-standing. In context it follows immediately after the Guide’s description of the AED 10,000 or less underpayment correction workflow, which applies only where the prior return was incorrect “resulting in a calculation of the Corporate Tax Payable being less than it should have been by AED 10,000 or less”. Read in that sequence, “any other error” naturally means errors outside the ≤ AED 10,000 underpayment category.

25. Traditionally, errors that result in a greater understatement of Corporate Tax Payable sit beyond the monetary threshold for in-return correction. The interpretive complication arises only when one tries to treat zero as merely an “extreme” point on the same ≤ AED 10,000 underpayment scale. Systematically, however, a nil-difference case is not a small underpayment case at all. It is a different category: no underpayment and no change in Due Tax. This category is routed by Article 10(5) as a standalone rule.

The question after 1 January 2026 is therefore whether CTGTXR1’s phrase “any other error” should be read as an implied “specification” that would push even nil-difference errors into VD.

26. There are two ways to treat this:

  • CTGTXR1 is an FTA-issued operational guide for completing the return in EmaraTax. Where the return design does not provide a dedicated nil-difference correction schedule, the statement “any other error must be amended by VD” may reflect the Authority’s current administrative position on how corrections are to be made through the platform.

On this view, until the Authority updates CTGTXR1 post-2026 or issues a Corporate-Tax equivalent of the VAT “specified cases” decision, the Guide can be treated as an interim indicator of the Authority’s routing expectation.

  • A pre-2026 guide drafted under the earlier regime cannot, by itself, reverse the new statutory default. Operational constraints (most notably, the absence of a nil-difference correction schedule in the return) may explain why the Guide routes “any other error” to VD, but they are not necessarily a legally sufficient “specification” that VD is required for all nil-difference errors.

Adopting this second view does not eliminate the taxpayer’s practical problem: if EmaraTax provides no genuine nil-difference correction workflow, the taxpayer must still choose a channel that the platform will accept. In practice, that often leaves the taxpayer with no realistic alternative but to treat a zero-difference case as an extreme point on the existing AED 10,000 (or less) in-return correction route, and implement the correction through the only available structured interface by:

  1. entering “0” in the field that asks for the amount by which Taxable Income is increased,
  2. providing a brief description in the limited text box, and
  3. where the correction is multi-item or technically complex, attaching an explanatory note that sets out the “before-after” details in a structured way.

This does not claim that the AED 10,000 workflow is conceptually designed for nil-difference errors. Rather, it reflects a practical necessity. Until the FTA introduces a dedicated nil-difference schedule, the taxpayer’s only way to “correct via a Tax Return” may be to use the closest available correction interface and supplement it with clear documentation.

27. These two interpretations point in different directions, but they converge on a single practical discipline: the taxpayer should adopt the method that

  • the portal will process, and
  • most clearly corrects the Authority’s record.

Where the return offers a functional correction path, it should be used. Where it does not, the taxpayer should:

  • either use the nearest available return mechanism with robust attached explanation, or
  • resort to Voluntary Disclosure as a protective compliance measure.

Ambiguity in route selection: what is the safer choice?

28. So, the taxpayers face a genuine ambiguity between two imperfect routes:

  • Route 1: forcing the AED 10,000 workflow with a “0” entry, by completing Box 9.5.3 (“Enter the amount by which the Taxable Income is increased”) as zero and attempting to describe the correction in Box 9.5.4;

versus

  • Route 2: Voluntary Disclosure, even where the error is nil-difference and arguably sits outside Authority-specified VD cases.

29. Both routes have weaknesses:

  • The “0 in the AED 10,000 box” approach is structurally misaligned because that workflow is designed for underpayment corrections. It is aggregated, narrative-constrained, and may be “non-performing” in the sense that it does not reliably update the underlying schedules or attributes.
  • Voluntary Disclosure, by contrast, may be criticized as procedurally misrouted where Article 10(5) points to return-based correction as the default (in non-specified cases), and it may invite avoidable administrative friction.

30. In a situation of genuine ambiguity, however, it is reasonable to argue that a taxpayer may prefer the route that is more transparent and more audit-informative for the Authority. On that basis, Voluntary Disclosure can be the safer defensive choice in certain cases. Not because it is always legally “required,” but because it creates a clearer evidential record: it describes what was wrong, what was corrected, and why the tax outcome did not change. That can be preferable to a zero-value entry in an underpayment box that provides little structured visibility and relies heavily on compressed narrative text.

31. The discussion above suggests a few prudential considerations that taxpayers and advisers may weigh when selecting a correction channel:

  • Where EmaraTax provides a genuine return-based mechanism to correct the relevant item (amended return for that field, or a dedicated nil-difference schedule), that route should be used in line with the post-2026 statutory default.
  • Where no such mechanism exists and the taxpayer must choose between:

i) a technically available but structurally ill-fitting “0 in the AED 10,000 box” workaround and

ii) Voluntary Disclosure,

the taxpayer should consider adopting the route that best ensures the correction is actually reflected on the Authority’s record and is capable of later proof.

This would often mean Voluntary Disclosure route, particularly for items that affect future-tax attributes, regime eligibility, or risk-sensitive disclosures.

32. In all cases, route selection should be documented contemporaneously (why the route was chosen, why tax did not change, what records support the correction). The taxpayers should take professional advice where the correction affects future reliance positions (tax losses, Free Zone eligibility variables, Transfer Pricing disclosures) or where the route choice could influence penalties and audit handling.

Policy and implementation options for nil-difference corrections

33. The analysis above shows that the amended Article 10(5) creates a clear conceptual split. Two implementation paths could materially reduce uncertainty and improve data quality:

1) The FTA could, by issuing a Corporate-Tax equivalent of a “specified cases” instrument (e.g., a decision), confirm that nil-difference errors must be corrected through Voluntary Disclosure (either universally, or by defined categories). This would prioritise evidential completeness and machine-readable narrative explanations. It would also align the correction route with a process the Authority already controls as a distinct compliance workflow. The trade-off is that VD is more burdensome and less structured than an in-return schedule, and it may not integrate efficiently into the Authority’s automated analytics unless translated into structured data.

2) Develop a dedicated nil-difference correction schedule within the Corporate Tax Return (preferred for automation).
Alternatively, and more consistent with the “Tax Return by default” limb of Article 10(5), the FTA could introduce a dedicated schedule expressly designed for nil-difference corrections. To be administratively effective, such a schedule would ideally:

  • allow multiple rows (one per corrected item), rather than one aggregated entry;
  • capture field-level “before – after” values for each corrected data point;
  • require a standardised reason code (classification, disclosure, computational input, factual data point, etc.);
  • flag whether the correction affects a future-tax attribute, a regime eligibility condition, a risk-relevant disclosure footprint, or record-accuracy only; and
  • enable EmaraTax to link the correction to the relevant prior Tax Period so that the FTA’s systems can automatically compare earlier submitted data against the revised values, without relying on narrative text or attachments.

This route would preserve the statutory design intent that most nil-difference errors are corrected “via a Tax Return,” while making corrections visible, machine-processable, and audit-efficient.

34. Either tools would reduce the current reliance on improvisational solutions. A clear VD-only policy would remove route ambiguity. A dedicated nil-difference schedule would remove the structural limitations of the current AED 10,000 workflow (zero-value entries, compressed narrative fields, and dependence on attachments). Until one of these approaches is adopted, the system will continue to generate uncertainty about whether a nil-difference correction has been “performed” in a manner that fully updates the Authority’s record.

Conclusion

35. Federal Decree-Law No. 28 of 2022 (as amended effective 1 January 2026) reframes nil-difference errors as a category that generally must be corrected, even where the tax outcome is unchanged:

  • Voluntary Disclosure applies only in Authority-specified cases,
  • while the Tax Return route is the default “in any other case”.

In principle, this closes the earlier compliance blind spot in which purely informational inaccuracies could remain uncorrected simply because they did not affect Due Tax.

36. The remaining difficulty is operational. Corporate Tax currently lacks a dedicated nil-difference correction schedule, and the only structured in-return correction workflow available in EmaraTax is the AED 10,000 underpayment mechanism (with its “enter the amount by which Taxable Income is increased” field and limited description box). This creates a practical disconnect:

  • taxpayers may be directed toward return-based correction, but
  • the return design does not yet provide a tailored mechanism for nil-difference items.

This pushes taxpayers toward either:

  • technically forcing a “0” entry through an under payment box with attached explanation, or
  • using Voluntary Disclosure defensively even where VD may not be the conceptual default.

37. In that environment, the key risk is not excessive transparency. It is procedural ineffectiveness. A correction that exists as a narrative trail but is not clearly reflected in the structured return record, and therefore may not serve as reliable support for future reliance positions (future-tax attributes, regime eligibility variables, or risk-sensitive disclosures).

Until the FTA clarifies the intended treatment (either by confirming a VD-first approach for nil-difference errors, or by implementing a dedicated nil-difference correction schedule that allows the Authority’s software to compare prior data to corrected values), taxpayers and advisers may need to adopt a cautious approach focused on ensuring that the Authority’s record is actually corrected in a way that is intelligible, provable, and operationally processable.

Disclaimer

Pursuant to the MoF’s press-release issued on 19 May 2023 “a number of posts circulating on social media and other platforms that are issued by private parties, contain inaccurate and unreliable interpretations and analyses of Corporate Tax”.

The Ministry issued a reminder that official sources of information on Federal Taxes in the UAE are the MoF and FTA only. Therefore, analyses that are not based on official publications by the MoF and FTA, or have not been commissioned by them, are unreliable and may contain misleading interpretations of the law. See the full press release here.

You should factor this in when dealing with this article as well. It is not commissioned by the MoF or FTA. The interpretation, conclusions, proposals, surmises, guesswork, etc., it comprises have the status of the author’s opinion only. Furthermore, it is not legal or tax advice. Like any human job, it may contain inaccuracies and mistakes that I have tried my best to avoid. If you find any inaccuracies or errors, please let me know so that I can make corrections.