The UAE tax system is operationally inseparable from the EmaraTax portal. Corporate Tax and other federal tax returns are not merely “uploaded documents”. They are structured submissions built through mandatory fields, validation rules, and system logic.
The legal tension appears when the portal’s logic reflects a particular methodological reading of the law, i.e. an “answer” embedded in software, while a taxpayer, acting in good faith and supported by a reasoned legal analysis, disagrees with that methodology. In such a case, the taxpayer may face a procedural dead end: the system prevents moving to subsequent steps, and therefore prevents submission of the return altogether.
This is not a narrow technical inconvenience. It has structural legal significance, because the legislative framework makes timely filing mandatory, treats completeness as a condition of acceptance, and places responsibility for accuracy on the taxpayer. The portal becomes the gatekeeper not only of how one files, but, in practice, of what the law is treated as requiring.
“Form and manner prescribed” as the hinge between law and code
Article 53(1) of Corporate Tax Law imposes a filing obligation “in the form and manner prescribed by the Authority”. Article 1 of Tax Procedures Law then defines a “Tax Return” as the information and data submitted “in the form and manner as prescribed by the Authority”, including attachments and schedules.
These provisions do not treat “form” as an aesthetic matter. They make the prescribed form and manner constitutive of what counts as a return. If EmaraTax is the prescribed mechanism, then EmaraTax’s schema (mandatory fields, required classifications, computational pathways, and validation constraints) becomes part of the legal architecture of filing.
This is precisely where implementation design becomes legally consequential: the portal does not merely “collect data.” It can also operationalize an interpretive position—by allowing some pathways and disallowing others.
Completeness, acceptance, and the portal’s power to stop the return from existing
Article 8 of Tax Procedures Law provides both the obligation to submit the return and the legal effect of incompleteness: an incomplete Tax Return “shall be considered as not accepted” if it does not include the minimum information required as specified in the Tax Law.
Clause 3 of this Article makes the taxpayer responsible for accuracy in the Tax Return, and Article 51 confirms that the burden of proving accuracy falls on the taxpayer.
From the Authority’s perspective, a portal that blocks progression until minimum information is provided can be framed as a front-end enforcement of the “acceptance” standard. The difficulty is that “minimum information” can slide into “mandatory methodology.” When the taxpayer’s disagreement is not about withholding information, but about characterisation or treatment (i.e. how the information must be mapped into categories and computations), the portal can convert a completeness concept into a substantive interpretive constraint. The return is not rejected after submission. Rather, submission becomes technically impossible unless the taxpayer adopts the portal’s embedded view.
The compliance dilemma is two-sided
A recurring simplification is to treat this as a one-directional risk (i.e. the taxpayer wants a lower tax outcome, and the system pushes a higher one). In practice, the dilemma cuts both ways: the portal’s methodology might be unfavourable or favourable compared to the taxpayer’s interpretation.
First scenario: the portal produces a higher tax result than the taxpayer’s view (taxpayer’s view = less tax).
If the system forces the taxpayer into a treatment that increases tax relative to the taxpayer’s considered legal position, the taxpayer faces a coercive choice: pay more than the taxpayer believes the law requires, or fail to file at all. That is not simply a cash-flow issue. It implicates the taxpayer’s ability to exercise what is, in substance, a right to be taxed strictly in accordance with law, no more and no less. Yet the portal may not allow submission unless the taxpayer abandons the position.
Second scenario: the portal produces a lower tax result than the taxpayer’s view (taxpayer’s view = more tax).
If the system pushes a treatment that reduces tax relative to the taxpayer’s view, the taxpayer again faces a coercive choice: submit a return that the taxpayer believes is legally incorrect, or be unable to file. The legal stakes here are obvious: the Tax Procedures Law treats submission of an incorrect Tax Return as a trigger for Tax Assessment and Tax Penalty.
Crucially, the statutory trigger is framed as “submitting an incorrect Tax Return”, without the text (as provided) conditioning that exposure on whether the error increased or decreased tax.[1] That matters because it destabilizes the idea that a taxpayer can “choose the conservative direction” to eliminate risk. In a methodology-lock environment, either direction can be problematic:
- one direction may risk overpayment and loss of a lawful position;
- the other may risk being characterized as an incorrect return, with the penalty architecture engaged.[2]
This is what makes the problem particularly acute: the framework simultaneously demands (i) acceptance-level completeness, (ii) taxpayer responsibility for accuracy, and (iii) taxpayer burden of proof. At the same time, the portal may not permit a return to be filed unless the taxpayer adopts the portal’s methodology. Yet it does so
- without protecting the taxpayer from penalty exposure if that embedded methodology is legally incorrect, and
- without providing a formal pathway for the taxpayer to escalate an alternative interpretation of the law when that interpretation is incompatible with the portal’s filing algorithms.
[1] Article 24(1)(j) of Tax Procedures Law.
[2] The penalty would be rather small, though (AED 500).
Administrative interpretation “by code” and why the sequence mat-ters
The Authority’s statutory jurisdictions include implementing applicable tax laws, keeping taxpayer records, issuing directives and clarifications regarding taxpayers’ obligations, reviewing and auditing returns, approving or amending them, requesting additional information, and implementing a mechanism to settle disputes.[1]
Read as a system, this contemplates a sequence:
- the taxpayer files,
- the Authority then reviews, audits, amends (assess), and
- disputes are managed through an implemented mechanism.
A portal that prevents filing unless a taxpayer adopts the Authority’s embedded methodology risks reversing that sequence. The administrative view is enforced before a return exists and before a review or audit can be engaged. The taxpayer is denied the ability to lodge the submission that would ordinarily be the starting point for the Authority’s downstream powers. That is not merely inconvenient. It can amount to a procedural foreclosure of the normal path by which disagreements become formalized and reviewable.
[1] Article 4 of the Law No. 13 of 26 September 2016 “On the Establishing the Federal Tax Authority”.
The 2025–2026 shift
In 2025, a new Article 54(bis) was introduced into Tax Procedures Law, and it provides that “without prejudice to the provisions of the tax legislations in force, the Authority may issue decisions that include directives on the implementation of the provisions of this Federal Decree-Law and the Tax Law in relation to tax transactions, which shall be binding on both the Authority and the Taxpayer”.
This is a pivotal addition for the methodology-lock debate. If a specific interpretive methodology is effectively mandated across taxpayers by being embedded into the filing infrastructure, the legal system now contains a conceptually appropriate instrument to formalize that position: a binding directive. The difficulty, however, is that the portal can operate as a de facto binding directive without the procedural clarity, visibility, and contestability that typically accompanies formal instruments.
This is also where practice becomes uncomfortable. Taxpayers may sometimes receive informal oral or email communications from which it can be inferred that the Authority considers the system’s approach to reflect the correct construction of the law. But the portal still provides no pathway for a taxpayer to file on the taxpayer’s interpretation, obtain an official, challengeable outcome (an assessment or decision), and then escalate the matter through dispute channels that the system is expressly meant to provide.
If Article 54 (bis) is to enhance legal certainty rather than simply entrench “law by interface” it should support two complementary expectations:
- where the Authority intends a methodology to be binding in its application to transactions, that intention should be expressed through the formal channel contemplated by Article 54 (bis), i.e. inform of formal decisions; and
- the filing system should preserve a reserved procedural route for taxpayers who, acting in good faith and with substantiated reasoning, cannot adopt the embedded methodology but still need to file and crystallize the disagreement into a form that can be formally reviewed and challenged.
Protecting a taxpayer interpretation
Within the current framework, promulgating a taxpayer’s view, where it diverges from the portal’s embedded methodology, can become a substantial challenge. It may require a non-standard, sophisticated approach to preserve compliance (timeliness and acceptance), protect the taxpayer’s interpretation, and manage the allocation of risk created by the accuracy obligation and the burden of proof. The central difficulty is how to fulfil the tax return compliance obligation while preserving the taxpayer’s position on accuracy and the proper construction of the law, and how to escalate that position within the legally available tax dispute resolution mechanisms.
This article does not set out particular techniques. They are fact-sensitive and, in practice, must be tailored to the taxpayer’s transaction pattern, evidentiary posture, and risk profile. For policy purposes, however, the structural point is clear: in our view, a system should not require a taxpayer to choose between (i) abandoning a reasoned legal position and (ii) losing the ability to file.
Conclusion
A system that legally requires filing “in the form and manner prescribed” will inevitably turn software into law’s practical interface. But that interface should preserve the conceptual separation between: (i) capturing minimum required information for acceptance, and (ii) resolving contested interpretive questions through review, audit, amendment, and dispute mechanisms.
Where EmaraTax hard-codes a single methodology and blocks filing when a taxpayer cannot adopt it, the system risks converting “form and manner” into a substantive interpretive leaving the taxpayer carrying statutory responsibility for accuracy and the statutory burden of proof. The introduction of Article 54 (bis) underscores that the legal system recognizes the need for formal, binding interpretive instruments. Yet the system design challenge remains: taxpayers must be able to file in good faith even where they disagree, so that the disagreement can become formal, reviewable, and, if necessary, disputable.
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.