UAE e-invoicing fines and penalties
UAE e-invoicing penalties under Cabinet Decision 106 of 2025 range from AED 2,500 to AED 50,000 per invoice. See the full fines schedule inside.
What are UAE e-invoicing penalties?
UAE e-invoicing penalties are fines the Federal Tax Authority (FTA) can charge a business for failing to issue, transmit, store, or report electronic invoices under the rules set by Cabinet Decision 106 of 2025. Fines start at AED 2,500 and reach AED 50,000 per invoice. They apply once the e-invoicing mandate goes live in 2027.
Why the UAE introduced a penalty regime
The UAE is moving from paper and PDF invoices to a structured electronic format called PINT AE (Peppol International Invoice, UAE version). The Ministry of Finance (MoF) and the FTA need every taxable business to send invoice data through an accredited service provider (ASP) on the 5-corner DCTCE (Decentralized Continuous Transaction Control and Exchange) network.
Without fines, large taxpayers could ignore the mandate. The penalty schedule in Cabinet Decision 106 of 2025 gives the FTA the legal power to enforce the timeline. It also pushes finance teams to act early instead of waiting until the deadline.
For background on the legal framework behind these fines, see our UAE e-invoicing law reference and the broader UAE e-invoicing guide.
When the fines start to apply
You will not be fined in 2025 or in most of 2026. The penalty regime is tied to the official go-live dates set by the MoF.
- Q2 2026: Pilot phase opens. No penalties for pilot participants.
- October 30, 2026: Deadline for Phase 1 taxpayers (AED 50M and above in turnover) to appoint an ASP.
- January 1, 2027: Mandatory go-live for Phase 1. Fines start applying to large taxpayers.
- July 1, 2027: Mandatory go-live for SMEs under AED 50M turnover.
- October 1, 2027: Mandatory go-live for government bodies.
Read the full schedule on the UAE e-invoicing timeline page.
The full UAE e-invoicing fines schedule
Cabinet Decision 106 of 2025 sets a range of AED 2,500 to AED 50,000 per invoice, depending on the type of breach. The table below summarises the main triggers. These figures are the published anchors used by the FTA.
| Breach | Penalty per invoice (AED) | Who it hits |
|---|---|---|
| Failing to issue an e-invoice when required | 5,000 to 20,000 | Supplier (seller) |
| Issuing an invoice in the wrong format (PDF, paper, non-PINT AE) | 2,500 to 10,000 | Supplier |
| Failing to transmit through an accredited ASP | 5,000 to 15,000 | Supplier |
| Missing or incorrect Tax Registration Number (TRN) on the e-invoice | 2,500 to 5,000 | Supplier or buyer |
| Failing to report invoice data to the FTA on time | 5,000 to 20,000 | Supplier |
| Failing to store e-invoices for the required retention period | 10,000 to 50,000 | Supplier and buyer |
| Repeated or systematic non-compliance | Up to 50,000 | Supplier |
The exact amount inside each band depends on the size of the business, the volume of invoices, and whether the breach is a first offence or a repeat.
How a single breach can stack into a large bill
The fines are per invoice, not per month. A mid-size UAE wholesaler issuing 800 invoices a month that sends every one as a PDF instead of PINT AE could face penalties of AED 2 million in a single month at the low end of the band. That is why finance leaders are treating this as a board-level risk.
The breaches that cause most UAE e-invoicing fines
Based on similar regimes in Saudi Arabia and Italy, four behaviours trigger most penalties. Each one is avoidable with the right setup.
1. Sending PDF invoices after go-live
A PDF is not a valid UAE e-invoice. The FTA only accepts structured UBL (Universal Business Language) XML in the PINT AE format, exchanged over the Peppol network. For a side-by-side comparison, read PDF invoice vs UAE e-invoice.
2. Using a non-accredited service provider
Only ASPs on the official MoF list can transmit invoices. There are 32 pre-approved accredited service providers as of the latest update. Sending invoices through any other channel is treated as a failure to transmit. See how to choose a UAE accredited service provider.
3. Missing or wrong buyer TRN
Every B2B e-invoice must carry the buyer Tax Registration Number. A missing TRN blocks the invoice at the FTA reporting layer (corner 5 of the DCTCE model) and triggers a fine. Cleaning up your customer master data before go-live is one of the cheapest ways to avoid penalties.
4. Late or missing FTA reporting
In the 5-corner DCTCE model, the ASP reports a copy of every invoice to the FTA in near real time. If your ASP fails or your ERP outbox is broken for a day, every unreported invoice can count as a separate breach. Learn how the flow works in our piece on the Peppol 5-corner model in UAE.
Who is liable: the supplier, the buyer, or both?
In most cases the supplier is liable because the supplier issues the invoice. But Cabinet Decision 106 of 2025 also places duties on the buyer.
- Supplier duties: Issue the invoice in PINT AE, transmit through an ASP, report to the FTA, store the record.
- Buyer duties: Accept e-invoices through Peppol, store them for the legal retention period, report self-billed invoices when applicable.
- Joint duties: Both parties must hold matching records. A mismatch can trigger an audit.
If your business issues self-billed invoices on behalf of a vendor, you carry the supplier duties for those documents. See self-billing under UAE e-invoicing.
How penalties are calculated in practice
The FTA uses a three-step process when it raises an assessment.
- Detection: The breach is found through ASP transmission logs, FTA reporting gaps, an audit, or a buyer complaint.
- Classification: The FTA places the breach into one of the bands in Cabinet Decision 106 of 2025.
- Aggravation or mitigation: Repeat offences push the fine to the top of the band. Voluntary disclosure pushes it to the bottom.
The FTA has 5 years to assess most breaches, in line with the general statute of limitations in Federal Decree-Law 17 of 2024 on tax procedures.
Can you appeal a UAE e-invoicing penalty?
Yes. The standard FTA appeal route applies. You can request reconsideration within 40 business days of the assessment, then escalate to the Tax Disputes Resolution Committee. A clean audit trail from your ASP is the single strongest piece of evidence in an appeal.
Penalty bands by company size
The FTA has signalled that fines will be applied with proportion. Smaller businesses generally sit at the low end of each band, larger groups at the top.
| Turnover band | Typical position in the fine range | Go-live date |
|---|---|---|
| AED 50M and above | Mid to top of band | January 1, 2027 |
| Under AED 50M (SME) | Bottom of band | July 1, 2027 |
| Government bodies | Case by case | October 1, 2027 |
SMEs get an extra six months to comply, but the fines themselves are not smaller in law. They are smaller in practice because the FTA scales the assessment. SMEs can read our dedicated page on UAE e-invoicing for SMEs.
A practical checklist to avoid UAE e-invoicing fines
Most fines come from preventable gaps. Work through this list in the 12 months before go-live.
- Sign with an accredited ASP before October 30, 2026.
- Clean your customer and vendor master data, including every TRN.
- Map your ERP outputs to PINT AE fields and test in the Q2 2026 pilot.
- Set up monitoring on the ASP outbox so failed transmissions are caught the same day.
- Configure storage for the legal retention period in an FTA-compliant archive.
- Train AP and AR teams on credit notes, self-billing, and reverse charge under the new rules.
- Run a dry run in December 2026 with real volumes, not sample data.
For the source rules behind each item, the UAE MoF e-invoicing portal publishes updated technical guidance, and the UAE Federal Tax Authority issues the assessment notices.
How the UAE penalty regime compares to Saudi Arabia
Saudi Arabia rolled out ZATCA e-invoicing from 2021. Penalties there start at SAR 1,000 and double for repeat breaches. The UAE penalty structure is broader on the top end (up to AED 50,000) but slower on enforcement, with a phased go-live. We have written a full comparison on UAE FTA vs Saudi ZATCA.
What happens during the pilot phase
The pilot opens in Q2 2026. Participants are not fined for breaches during the pilot, but they must use the same PINT AE format and accredited ASPs that will be required in production. The pilot is the best window to find and fix integration gaps before fines start. The technical format is published as part of the Peppol UAE specification.
Where Massive fits
The single biggest driver of UAE e-invoicing penalties is a broken or missing connection between your ERP and an accredited ASP. If your invoices never reach the Peppol network in the right format, every one of them is a potential fine.
Massive's UAE e-invoicing software connects ERPs like SAP, Oracle, Dynamics 365, Tally, Zoho, and QuickBooks to accredited ASPs, validates each invoice against PINT AE before it leaves your system, and keeps a full audit trail for FTA appeals. That stops the four breaches above at source and protects you from the AED 2,500 to AED 50,000 per-invoice fines under Cabinet Decision 106 of 2025.