Already preparing for UAE e-invoicing? Before approving your next system change, revisit the assumptions behind it. Ministerial Decision No. 197 of 2026 changes several operational rules that finance, tax and technology teams may need to reflect in their implementation plans.
Ministerial Decision No. 197 of 2026 took effect on 1 October 2026 and changes four areas businesses should revisit: qualifying VAT Tax Group transactions, invoice-data storage, system-failure procedures and invoice timing.
The practical next step is to review transaction mapping, record-retrieval arrangements, incident procedures and invoice-timing settings before approving further system changes.
On 19 October 2026, the UAE Ministry of Finance announced Ministerial Decision No. 197 of 2026 , amending certain provisions of Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System. The amending decision took effect on 1 October 2026.
For a finance team, the useful question is not simply, “What changed?” It is, “Which part of our current implementation plan needs a second look?”
Start with your transaction mapping, record-storage arrangements, incident procedures and invoice-timing settings. These are the areas to bring into your next discussion with the people responsible for finance, tax and technology.
| Area | Key point |
|---|---|
| VAT Tax Group transactions | Qualifying intra-group transactions receive a 24-month exclusion starting on 1 January 2027. |
| Invoice-data storage | The UAE-specific storage-location requirement has been removed. |
| System-failure notification | The former Article 12 notification provision has been repealed. |
| Invoice timing | Amended Article 6(5) specifies 14 Business Days, subject to Article 6(4). |
The Ministry announcement explains the first three developments; the amending decision itself contains the invoice-timing amendment.
Here, a Tax Group means persons registered with the Federal Tax Authority as one taxable person under the VAT Law. Common ownership or Corporate Tax Group membership alone is insufficient. The exclusion is transaction-specific, not a blanket exemption for every group company.
For implementation purposes, avoid relying on a single “intercompany” label in the accounting system. That label may be useful internally, but it is not a substitute for checking the legal position.
A sensible starting point is a transaction register showing the issuing entity, receiving entity, relevant VAT grouping details and the treatment proposed for review. Ask the tax reviewer to confirm the mapping before a developer or service provider turns it into a system rule.
Prepare a sample containing an internal recharge, an external customer invoice and a credit note. Use that sample to check whether the proposed configuration distinguishes the transactions correctly. This is a testing exercise, not a conclusion about the treatment of any particular transaction.
Keep a record of the approved decision and who reviewed it. Also assign someone to revisit any temporary treatment before its permitted period ends. The aim is to prevent a convenient software setting from becoming an unexamined compliance assumption.
Amended Article 11 removes the UAE-location requirement while preserving retention for the period prescribed under the Tax Procedures Law and the ability to provide the records to the Federal Tax Authority on request.
When discussing storage with a software provider, go beyond asking where the servers are located. Ask the provider to demonstrate how your team would retrieve a complete invoice record, a related credit note and the associated data. Check whether the information can be exported in a usable form and whether access would remain available after changing providers or ending the contract.
An effective practical test is to ask someone who does not normally process invoices to retrieve a small sample using the documented procedure. Record what they could access, what was missing and whether they needed the provider’s assistance.
Before changing a hosting arrangement, ask your legal and IT teams to check separate privacy, confidentiality, sector-specific and contractual requirements. Do not treat this particular amendment as approval for every possible data-storage arrangement.
Demonstrate that the records can be retrieved, rather than relying only on a promise that they are stored.
Decision No. 197 repeals Article 12 and deletes the related System Failure definition, removing that provision’s requirement to notify the Federal Tax Authority within two Business Days from the date of occurrence of the System Failure.
Check the documents your team is actually using: implementation checklists, operating procedures, staff instructions and provider agreements. A recently updated project plan is not enough if an older procedure is still guiding daily work.
At the same time, keep a clear internal process for dealing with failed transmissions. As a practical control, assign responsibility for identifying affected invoices, investigating the cause, coordinating with the provider and confirming successful recovery. Ask the team to document how it will avoid duplicate processing when a transmission is retried.
A useful test is to walk through a failed batch and its recovery. Who notices the problem? Who decides whether to retry? How does finance confirm that the final records are complete?
These are recommended operating controls, not a restatement of the repealed notification rule. Your team should separately check whether another applicable requirement or contractual obligation needs to be addressed.
Amended Article 6(5) sets a 14-Business-Day period from the Date of Business Transaction for issuing and transmitting the relevant electronic invoice or credit note, subject to Article 6(4).
That qualification matters. Article 6(4) directs VAT-registered issuers to the timelines prescribed by the VAT Law. The original Article 6(5) used “14 days”; the amendment changes that wording without removing the qualification concerning VAT-registered issuers.
There are also defined terms to consider. Under the framework, Business Days exclude weekends and official Federal Government holidays. The Date of Business Transaction is the earlier of the transaction occurring or payment being received.
Before changing an automatic deadline in the accounting system, ask the tax reviewer to confirm the applicable provision and the date that starts the calculation. Then test the result using representative transactions rather than only a straightforward invoice created and paid on the same day.
Include an advance-payment scenario and a transaction close to a holiday period where relevant to your business. For a VAT-registered business, the instruction to the software team should not simply be, “Change every deadline to 14 Business Days.” It should be, “Confirm the applicable rule, document it and test the calculation.”
The decision also revises the Accredited Service Provider definition and introduces VAT-based definitions of Tax Group and Taxable Person. Update internal terminology against the current legal wording.
Continue planning against the applicable phased timetable under Decision No. 244 of 2025, as amended by Decision No. 66 of 2026. The October operational amendments should not be treated as a general extension of implementation deadlines.
| In-scope category | Deadline to appoint an Accredited Service Provider | Mandatory implementation |
|---|---|---|
| Businesses with Revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Businesses with Revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities within scope | 31 March 2027 | 1 October 2027 |
The first row reflects Decision No. 66 of 2026; the remaining dates appear in Decision No. 244 of 2025.
Revenue has a defined meaning: gross income earned during the most recent Accounting Period, supported by the prescribed financial statements or, where unavailable, other documentation acceptable to the Federal Tax Authority. Do not assume that a calendar-year sales estimate is automatically the correct measure.
Newly established businesses and businesses with unusual accounting periods should obtain a specific assessment of the applicable guidance.
For the broader preparation process, see EMARK’s UAE E-Invoicing Readiness Checklist . This amendment review should sit alongside that work, not replace it.
The following are suggested operational checks, not additional statutory requirements.
| Review area | Question to resolve | Suggested owner |
|---|---|---|
| Transaction mapping | Have we documented the proposed treatment for each relevant entity and transaction type? | Finance and tax |
| Invoice timing | Has the applicable rule been approved before changing system calculations? | Tax and finance systems |
| Record retrieval | Can another authorised employee retrieve complete records using the written procedure? | Finance and IT |
| Incident recovery | Who confirms that failed or retried transmissions have been resolved correctly? | Finance operations and IT |
| Provider coordination | Have we recorded the provider’s answers, agreed changes and testing responsibilities? | Implementation lead |
Bring evidence to the meeting: the transaction register, sample records, provider responses and test results. For each unresolved issue, record the decision required, the person responsible and the target date. This is more useful than marking the whole project “under review” without identifying what needs to happen next.
It also gives management a clearer basis for deciding whether the project can proceed or whether a particular configuration needs further work.
You do not need to turn every regulatory update into a complete restart. A practical approach is to maintain two records: the main implementation plan and a short change log explaining what the latest amendment affects.
For each proposed adjustment, record the previous assumption, the reason for changing it, the approval and the test performed. This makes it easier to distinguish a necessary compliance change from a separate software enhancement.
During testing, also compare a sample of invoice outputs with the accounting records. EMARK’s VAT reconciliation checklist provides a separate reference for the pre-filing reconciliation work.
The objective is not to produce more project documentation. It is to make the decisions traceable and the results testable.
Before signing off the next implementation milestone, ask your team to show what has been checked, what has changed and what still needs a decision. EMARK supports UAE e-invoicing readiness and implementation reviews across finance processes, system readiness and invoice data.
No. It concerns qualifying transactions between members of the same VAT Tax Group, rather than all their external sales.
No. It must consider the VAT-law timelines referenced in Article 6(4), rather than automatically applying the amended Article 6(5) period.
The applicable appointment deadline remains 30 October 2026, with implementation by 1 January 2027, for in-scope businesses meeting the AED 50 million Revenue threshold. Plan against those dates unless an applicable official amendment changes them.
Do not make that decision from the announcement alone. First compare your current system’s capabilities with the requirements applicable to your business. Ask the provider to demonstrate the proposed changes and test them using your own transaction scenarios.
Use the results to decide whether configuration, integration or replacement is justified.
The article is based on the official UAE Ministry of Finance materials below. Confirm later amendments before changing compliance procedures or system settings.
This article provides general information based on the official materials referenced above and the regulatory position reviewed on 19 October 2026. It does not replace tax, legal or accounting advice for a particular business. Confirm the applicable requirements and subsequent amendments before changing compliance procedures or system settings.