Three penalties apply under the UAE e-invoicing rules. Cabinet Decision No. 106 of 2025 sets AED 5,000 for each month without an appointed provider or a working system, AED 100 for every invoice or credit note issued late up to AED 5,000 a month, and AED 1,000 a day for failing to tell the authority that your system has failed.
Three penalties, and they behave differently
Most coverage of the mandate lists the amounts and stops there. The amounts are the least useful part. What matters is what each one measures, because one is a monthly state, one accumulates per document, and one accumulates per day until somebody acts. Those are three different kinds of exposure and they need three different answers.
Before any of them applies you have to be in scope and past your own go-live date. Businesses with revenue of AED 50 million or more appoint an Accredited Service Provider by 30 October 2026 and go live on 1 January 2027; everyone else follows on 1 July 2027. Our UAE e-invoicing readiness work on Odoo starts by settling which of those two waves you are in, because until that is answered nothing else can be sequenced or priced.
Not having a provider or a working system
AED 5,000 for each month. This one is a state rather than an event: either you have an appointed provider and a system that can issue e-invoices, or you do not, and the month ends either way. It also has the clearest fix and the longest lead time, which is an awkward combination — the work that stops it takes months and the charge arrives monthly.
Notice that the wording covers both halves. An appointed provider sitting in front of an ERP that cannot produce a compliant document is not a working system, and a working integration with no provider behind it is not either. Companies tend to treat the appointment as the compliance step. It is the procurement step.
Issuing an invoice or credit note late
AED 100 per document, capped at AED 5,000 a month. The cap sounds reassuring until you divide it by the per-document amount: the number of late documents it takes to reach the ceiling is small enough that one bad week in a busy month gets you there. The cap does not protect you, it only stops the figure being unbounded.
This is the penalty that turns a data problem into a recurring cost. Credit notes are named explicitly alongside invoices, which matters more than it looks, because credit notes are the documents most often raised late, by a different person, after a dispute has been settled.
Not notifying the authority of a system failure
AED 1,000 per day. This is the one almost nobody has a process for. The other two are about invoices; this one is about telling the Federal Tax Authority when the thing that issues them has stopped. It accrues daily, so an outage across a long weekend that nobody reported is not one mistake, it is several.
Ask two questions. Who, by name, would notice that submissions have stopped? And who would make the notification? If the answer to the first is “finance would spot it at month-end”, the exposure is real and it is cheap to close.
Not sure which of your invoices would be late?
Send us your Odoo version and how many legal entities issue invoices. We will tell you which documents your data can produce compliantly today and which ones need work first.
Book the Two-Day AssessmentWhy the per-invoice one deserves most of your attention
The monthly penalty is a project. You either run the project or you do not, and the exposure is predictable while you do. The notification penalty is a procedure — one named owner, one route, done in an afternoon. The per-document penalty is the only one driven by the quality of your data every single day, which makes it the one that carries on costing you after the project has been signed off and the consultants have gone.
And “late” is not only about slow humans. Once invoicing runs through a provider, a document that is rejected has not been issued. If a customer record is missing a registration number, or an emirate is stored as typed text rather than as a code, the invoice bounces and the clock keeps running while somebody works out why. That is why the structure of the PINT AE document and the state of your customer and product records are a penalty question rather than a technical one.
The failures that actually create late invoices
In the Odoo systems we look at, late documents come from a short list of repeating causes, and the invoicing screen is not one of them.
Invoices issued outside the ERP come first. A spreadsheet one entity uses for project billing, a point of sale that prints its own, a legacy module somebody kept running. Each of those is a channel that has to reach the provider, and the ones nobody mentions in the kick-off meeting are the ones still non-compliant in February.
Master data that fails validation is second and is the largest by volume — a customer with no registration number, an emirate typed rather than coded, a product with no classification. These are the same records your sales team reports from, so the clean-up pays for itself past compliance: it is the same master data that makes an AI layer on your Odoo CRM trustworthy rather than confidently wrong.
Third is tax treatment that cannot be expressed in the categories the format permits — an exemption applied by habit, a zero rate with no reason recorded against it. Fourth is credit notes and anything else that corrects an earlier document, because correction flows are reliably the least automated part of the process.
Fifth, and the one that surprises people, is a working system that quietly stops being correct. A custom field feeding the integration gets renamed during an upgrade, nothing errors loudly, and invoices start bouncing weeks later. That is the argument for treating the integration as something maintained rather than something delivered.
What these penalties are not
They are not a reason to sign a provider contract this quarter if you are in the second wave. They are not evidence that you need the most expensive provider, because the penalty attaches to your compliance and not to the logo on your invoice. And they are not a substitute for an opinion from somebody qualified to give one: whether you are in scope, what your thresholds are and what your filing obligations look like belong to your tax adviser.
Nothing here is tax or legal advice. The amounts and the conditions attaching to them belong to Cabinet Decision No. 106 of 2025 and to the Ministry of Finance’s published decisions and guidelines. Read them, or have your adviser read them, before making a decision on the strength of a page like this one.
Where we would tell you to slow down
If you are not in the first wave, the penalty schedule should not push you into a rushed procurement. The work that protects you is the data work, and it is worth doing before you commit to an integration — partly because it is the slow part, and partly because a clean customer and product master makes the provider decision simpler and the integration cheaper. If you are a small business issuing a handful of simple domestic invoices, there is a reasonable case for using your provider’s own interface by hand and buying no integration at all. We would rather say that than sell you something you do not need.
Being straight about our own position
We sell Odoo work, including integration to a provider, so read the above with that in mind. What we will not do is quote a price before knowing which entities issue invoices, which transaction types you use, what has been customised and which channels produce documents outside Odoo. Anyone pricing it before asking those questions is guessing, and the guess is usually low. We also hold no Accredited Service Provider status ourselves and have no commercial interest in which provider you appoint; how to run that selection is a separate question from this one.
Where to start
Do two things this week, neither of which costs anything. Write down every place in your business that issues an invoice or a credit note, including the ones that are embarrassing. Then name the person who would notice if submissions stopped and the person who would make the notification. The first list is your project scope. The second is the entire fix for the daily penalty. For the order to do the rest in, the 30 October deadline post sets out the sequencing.