UAE E-Invoicing Rules: The Outage Rule Was Deleted Today

On Friday, a finance manager in Dubai finished the outage procedure. Two pages, neatly written. If the invoicing system went down, who would be told, in what order, and how the Federal Tax Authority would hear about it within two business days. On Monday morning, the rule that procedure was built to satisfy stopped existing. The UAE e-invoicing framework had been rewritten over the weekend, and the rewrite landed on the desk before the coffee did.

That is not an exaggeration for effect. The Ministry of Finance announced Ministerial Decision No. 197 of 2026 today, Monday 19 October 2026, amending Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System. The Ministry states the changes took effect on 1 October 2026. Three duties businesses have spent October building procedures for moved at once, and each one deserves a calm, separate look — because the relief is real, but so is the risk of unwinding the wrong thing in a hurry.

Compliance built the procedure. The amendment deleted the rule — and kept the deadline.

UAE E-Invoicing Rules: What MD 197 Changed Today

Start with the source, because this story will be retold loosely by the end of the week. The Ministry of Finance release, published today at mof.gov.ae, describes three targeted changes, framed as providing greater clarity and reducing operational burdens on businesses in the UAE. Coverage at Gulf Business restates the same three points. They are:

• Tax-group transactions become Excluded Transactions, temporarily. Business transactions between persons who are members of the same Tax Group will be treated as Excluded Transactions for twenty-four months commencing on 1 January 2027 — running, in other words, to the end of December 2028.
• The in-UAE storage requirement is removed. Amended Article 11 still requires every person subject to the system to retain all electronic invoices, electronic credit notes and associated data for the period prescribed under the Tax Procedures Law, and to ensure those records can be provided to the FTA on request. What is gone is the previous requirement that the data be stored within the UAE.
• The System Failure provisions are repealed. Article 12 is repealed and the related definition is deleted from Article 1, removing the requirement to notify the FTA of a system failure within two business days of its occurrence.

One caution belongs at the top, and we will keep it in sight. These are the Ministry's own release and the summaries reporting it today. Before any business unwinds a procedure, a contract clause or a hosting decision, it should confirm the amended text of Ministerial Decision No. 243 of 2025 as it now stands, and check its own Accredited Service Provider contract position. A press release tells you the direction. Your contracts and the amended decision text tell you what you may actually stop doing, and when.

The Outage Procedure You Built in October

Of the three changes, the repeal of Article 12 is the sharpest, because it lands on work that is only days old. Under the framework as it stood until today, a technical malfunction that prevented compliance was not, by itself, the worst problem. Silence was. Both sides of a transaction carried a duty to notify the FTA within two business days, through the designated route, and we wrote a whole piece about exactly that duty on 17 October — our guide to the outage rule and why silence was the breach. That piece was accurate when it was published. Two days later, the duty it explained has been repealed.

We are not embarrassed by that, and you should not be embarrassed if your own SOPs went through the same cycle. This is what a new system looks like in its first months: the regulator issues a framework, businesses build to it in good faith, the regulator hears where the burden bites hardest, and the framework is trimmed before go-live. The businesses that suffer are not the ones who built early. They are the ones still training staff in November on a duty that died in October — or who hear a garbled version, assume every outage duty has vanished, and stop keeping the internal incident records their own ASP contract still expects.

So handle the repeal like an accountant, not like a headline. Retire the FTA notification step from the outage SOP, because the Ministry says that step no longer exists. Keep the rest of the SOP — who detects the failure, who calls the provider, how invoices are queued and reconciled once the system returns — because none of that was ever only about the FTA. An outage still stops your billing, still delays your customers' input tax evidence, and still needs an internal trail. The rule that was deleted was the two-day notice. The operational problem it was attached to is still entirely yours.

And check the contract before you celebrate. Many ASP agreements signed in the last three weeks will contain notification clauses, service credits and incident-reporting duties written against the old Article 12. A repealed regulation does not rewrite a signed contract. If your provider's terms still promise, or demand, a two-day notification workflow, that workflow survives as a commercial obligation until the contract is varied — which is a short conversation to have now, while every provider in the market is having the same one.

Storage: From Where It Sits to Whether You Can Produce It

The second change is quieter and, for groups with overseas systems, larger. The old Article 11 position, as businesses understood it through October, had a geography test inside it: electronic invoice and credit-note data was to be stored within the UAE. Finance and IT teams have spent real money on that sentence — local hosting quotes, data-residency clauses, arguments about whether a group ERP instance in Europe could ever be compliant.

Amended Article 11, in the Ministry's words, removes that requirement and shifts the focus from the location of storage to the retention and accessibility of the records. Read the replacement test carefully, because it is a test, not an absence of one. You must still retain every electronic invoice, every electronic credit note and the associated data, for the full period prescribed under the Tax Procedures Law. And you must be able to provide the records to the FTA on request. Where the server sits no longer answers the question. Whether you can produce a complete, readable, untampered record, promptly, when asked — that answers it now.

That distinction matters for how you redesign the archive. A business that treats the amendment as permission to let invoices scatter across a foreign group system, a provider portal and a departing employee's mailbox has not been liberated by Article 11. It has been set a harder exam. Producibility means retrieval rights that survive a provider exit, export formats you have actually tested, and an index that lets your team find a specific credit note without a support ticket to another time zone. The discipline is the same one we described for transfer pricing adjustments under CTP011: less permission, more proof.

One practical step follows. If you signed, or were about to sign, a storage arrangement priced mainly on UAE residency, pause and re-price it against the new test before the term locks in. You may still choose local storage for speed, control or group policy — all good reasons. You are simply no longer buying it because the e-invoicing rules compel the geography. And whatever you choose, write the producibility standard into the contract: retention period, export on demand, and access for the FTA on request, in terms a provider can be held to.

Tax Groups: Excluded for 24 Months, Not Forever

The third change will be the most misreported, so let us be precise. From 1 January 2027, business transactions between persons who are members of the same Tax Group are treated as Excluded Transactions for twenty-four months. The Ministry frames this as flexibility and more time to adapt, and for groups whose entities invoice each other constantly — shared services, internal recharges, group trading — it removes a large volume of internal traffic from the new network during its first two years.

Three limits keep this honest. First, the exclusion is for transactions between members of the same Tax Group. It is not a group-wide holiday from e-invoicing. Every sale those same entities make to customers outside the group stays exactly where it was: in scope, on the normal phase dates, through an ASP. A group that reads today's news as we are exempt has misread the one sentence that matters. Second, the exclusion is temporary by design — twenty-four months from 1 January 2027, ending in December 2028. Internal invoicing processes that are left unbuilt because they are excluded today become a cliff-edge project in the second half of 2028. Third, excluded from the e-invoicing system does not mean excluded from tax. The underlying VAT and corporate tax treatment of intra-group transactions, and the records behind them, continue as before. The channel changes. The tax does not.

The sensible use of the twenty-four months is sequencing, not sleep. Put external invoicing first — it carries the live deadlines — and diarise the internal build for when the network, your provider and your own first year of experience are all more mature. That is, in effect, the Ministry's own stated intention: more time to adapt, offered to the transactions where adaptation is hardest to standardise. Treating a sequencing gift as a cancellation is how a manageable 2028 project becomes a panicked one. We made a similar point about a different deadline in our piece on DMTT registration and the data behind it: the date on the form is rarely the real work. Here, the real work is everything the group sells to the outside world, and none of that moved today.

UAE E-Invoicing Rules: What Did Not Change

A relief announcement is a dangerous document, because the eye skips to what was removed. So, plainly, here is what MD 197 does not do, on anything published today.

• It does not move the appointment deadline. Businesses in the first phase still need their Accredited Service Provider appointed by 30 October 2026 — eleven days from today, Monday 19 October 2026. Nothing in the Ministry's release touches that date.
• It does not move go-live. The first phase still goes live on 1 January 2027. The tax-group exclusion itself is counted from that same date, which tells you the date is assumed, not postponed.
• It does not dilute retention. The Tax Procedures Law retention period and the duty to produce records to the FTA on request are restated inside the amended Article 11, not softened by it.
• It does not help a business that has not started. Every removed duty was a duty of the system you join through an ASP. If you have no provider, no mapping and no plan, today changed nothing about your position — except that three of your competitors' October problems just got smaller while yours stayed the same.

There is also a wider lesson in the timing. The framework summaries businesses relied on in September were accurate and are now partly history, in the same season that saw supplier verification duties under the KYS rules change what a bookkeeper must check by hand. The pattern is not instability. It is a system being built in public, at speed. The rational response is not to wait for a final version that is not coming. Build on the current text, keep the build modular, and keep the compliance calendar a living document — the habit behind staying ahead of payroll rule changes like the WPS joiner rules as well.

A Monday-Morning Checklist for MD 197

If you own e-invoicing readiness, work through these in order this week. None of them needs a board meeting. All of them are cheaper today than in December.

• Confirm the amended text. Read Ministerial Decision No. 197 of 2026 against your copy of MD 243 of 2025, and note the 1 October 2026 effective date your summaries state. File the note. Do not rebuild procedures from a news summary alone — including this one.
• Retire, do not delete, the outage SOP. Remove the two-business-day FTA notification step, mark the version superseded and keep the internal incident workflow. Deleting the whole document throws away the parts you still need.
• Open the ASP contract. Find every clause written against Article 12, in-UAE storage, or intra-group invoicing volume. List what needs varying, and put the list to your provider while the whole market is renegotiating the same clauses.
• Re-test storage against producibility. Wherever the data will sit, prove you can retrieve a complete invoice and credit-note record, with its associated data, on request. Run the test. Do not assume the portal does it.
• Split the invoice population in two. Intra–Tax Group transactions, excluded from 1 January 2027 for twenty-four months, in one pile. Everything external, unchanged and deadline-driven, in the other. If your project plan cannot show that split, it is planning the wrong volumes.
• Leave the deadlines alone. ASP appointment by 30 October 2026 and go-live on 1 January 2027 stay in the calendar in the same ink. Relief on three duties is not relief on the programme.
• Brief the board in one paragraph. Three duties eased, none of them the deadline, retention and producibility now the storage test, internal invoices sequenced to 2028. Boards that hear relief and stop asking questions are how readiness programmes quietly die.

Less Permission, More Proof — Again

Ministerial Decision No. 197 of 2026 is genuinely good news, and it deserves to be reported that way. A notification duty that would have consumed the first incident of every implementation is gone. A storage rule that forced geography over accessibility is gone. Internal group traffic gets two years to join a network that will be better for the wait. The Ministry said it was reducing operational burdens, and on the text published today, it has.

But read the shape of what replaced each duty, because the shape is the strategy. Storage became producibility. The outage notice became your own incident discipline. The group exclusion became a sequencing decision with a 2028 date inside it. Nothing in MD 197 rewards a business for doing less thinking. It rewards businesses whose records, contracts and calendars are good enough that a rule can be deleted on a Monday and their programme barely wobbles.

If your e-invoicing file was built against the October text and you want it re-tested against the amended one — SOPs, ASP clauses, storage position and the tax-group split — Escrow's VAT and FTA compliance team can run that review before the 30 October appointment deadline. Start with a free VAT compliance health check at escrowconsultinggroup.com, and bring the procedure you finished on Friday. We will help you keep the parts that still protect you.