On 19 October 2026, the UAE Ministry of Finance issued Ministerial Decision No. 197 of 2026, amending selected provisions of Ministerial Decision No. 243 of 2025 — the decision that established the country's Electronic Invoicing System. The changes took effect retroactively on 1 October 2026 and are explicitly aimed at "reducing operational burdens on businesses" ahead of the January 2027 go-live.
For finance teams already mid-implementation, this is welcome news: three of the more operationally awkward requirements have been softened. None of the deadlines moved.
The three changes that matter
1. Tax-group transactions get a 24-month exclusion
Business Transactions between Persons that are members of the same Tax Group are treated as Excluded Transactions for 24 months starting 1 January 2027 — i.e., through the end of December 2028.
What this means in practice: if your group invoices internally — shared-services recharges, intercompany management fees, cost allocations — those internal invoices do not need to flow through the e-invoicing system during the window.
Important boundary: the exclusion applies only to member-to-member transactions. When a tax-group member invoices a third party, that invoice is fully in scope. If your ERP can't easily split "internal" from "external" flows, make sure your routing rules handle this correctly — treating everything as excluded (or everything as in-scope) both create problems: compliance gaps on one side, wasted per-invoice ASP fees on the other.
This formalises the VAT-group grace period first described in the Guidelines Version 1.1 update — it's now law, not guidance.
2. UAE data-storage requirement removed
Article 11 on the Storage of Electronic Invoice and Electronic Credit Note Data was amended. The previous requirement to keep e-invoice data physically within the UAE is gone.
What remains — and this is the operative part:
- You must retain all Electronic Invoices, Electronic Credit Notes, and associated data for the period prescribed under the Tax Procedures Law.
- You must be able to produce those records to the FTA on request.
The Ministry deliberately shifted the test from where data sits to whether you can produce it. Businesses running regional or global cloud infrastructure (AWS, Azure, Google Cloud regions outside the UAE) can now keep their existing architecture — provided retrieval is fast enough to satisfy an FTA information request.
Our recommendation stays the same: even though offshore storage is now legal, keep your e-invoice archive reachable and well-indexed. "The FTA asked and it took us three weeks to export" is not a position you want to be in. TrustBill retains your full PINT-AE archive in-country regardless — belt and braces that costs you nothing extra.
3. The 48-hour system-failure notification is gone
The obligation to notify the FTA of a technical system failure within two business days has been removed entirely.
This was one of the more operationally tense requirements — a hard notification clock that started ticking the moment your ERP or ASP connection went down, often before you'd even diagnosed the outage. Its removal reduces incident-response paperwork.
Practical caveat: the notification requirement is gone; the compliance requirement is not. You are still obliged to issue compliant e-invoices. If your system is down for a week, you haven't incurred a notification penalty — but every non-transmitted invoice is still a non-compliance event. Your incident plan should now focus on failover and catch-up transmission rather than notification drafts.
What did NOT change
Worth repeating, because "eased regulations" headlines can be misread as "mandate softened":
- The phased deadlines stand. ASP appointment: 30 October 2026 (Phase 1, revenue ≥ AED 50M) and 31 March 2027 (Phase 2). Mandatory go-live: 1 January 2027 and 1 July 2027 respectively; 1 October 2027 for government entities. See the complete deadline timeline.
- PINT-AE is still the format. Structured UBL XML, digitally signed, transmitted through the Peppol 5-corner model.
- An Accredited Service Provider is still mandatory. You cannot submit e-invoices to the FTA directly — and under Ministerial Decision No. 168 of 2026 (effective the same day, 1 October), the ASP pre-approval stage was scrapped: providers may now only operate after completing full accreditation. Verify your provider's status on the accredited ASP partners page.
- Penalties under Cabinet Decision 106 of 2025 stand — AED 5,000 per month for non-implementation, plus per-invoice penalties for non-compliant issuance. Model your exposure with the penalty calculator.
What to do this week
- Map your tax-group flows. If you operate a VAT group, list every entity pair that invoices internally and confirm your e-invoicing routing excludes them — and only them.
- Review your storage architecture. If UAE-only storage was driving a costly migration decision, you can now re-evaluate. Keep FTA-retrievability as the acceptance criterion.
- Simplify your incident runbook. Remove the FTA-notification step; keep the failover and catch-up-transmission steps.
- Reconfirm your ASP appointment. If you're a Phase 1 business, the 30 October 2026 deadline is days away. The penalty for missing it is not eased by this decision.
How TrustBill fits
TrustBill already handles the unchanged 95% — PINT-AE generation, digital signing, ASP submission, and an in-country archive you can export to the FTA in one click. Tax-group exclusion routing and per-entity scope rules are configurable in the dashboard, so the new flexibility lands as a settings change rather than a code change.
Questions on how Ministerial Decision 197 applies to your structure? Talk to our compliance team — or start a trial and run your entity map through the readiness check.
