UAE eInvoicing credit notes: rules for correcting an Electronic Invoice

An Electronic Invoice under the UAE mandate is a structured invoice created and exchanged entirely in XML format, not a PDF or a scanned document. A supplier's Accredited Service Provider (ASP) validates it, exchanges it with the buyer's ASP, and reports it to the Federal Tax Authority (FTA) as Tax Data. Can an invoice like that be edited or cancelled once all three steps are done? Not in place. The Ministry of Finance's Electronic Invoicing Guidelines (Guidelines v1.1) don't describe an edit or delete function for a document once it has reached that stage. What they describe instead is a separate document for the correction itself. A specific set of rules decides when that document is a credit note rather than a fresh invoice.

A supplier issues an Electronic Invoice for 500 units delivered to a buyer. Two days later, the buyer reports that only 480 arrived undamaged; the remaining 20 were written off in transit. By the time that report comes in, the invoice is already past the point where it could simply be edited. This guide covers what happens next: when a credit note applies rather than a new invoice, and what has to appear on one. It also covers who's responsible if the correction itself is handled wrong.

This guide focuses on what happens after that point: once an Electronic Invoice has already been validated, exchanged, and reported. For the full step-by-step exchange process, see How UAE eInvoicing works. For the complete set of eight transaction scenarios, see UAE eInvoicing use cases. Summary invoicing gets a second mention below, because it is where the Guidelines apply the rule most explicitly.

Do a draft, a rejected invoice, and a reported invoice need the same fix?

Whether a correction is even the right question depends on where the document is. A draft that hasn't been transmitted yet is simply corrected before it's sent: an internal editing matter, not an eInvoicing one. A submission that fails validation is a different case again, and it needs care: exchange and reporting are two separate outcomes. A rejection by the buyer's ASP stops the exchange, but the tax data may already have gone to the FTA, because reporting happens alongside delivery rather than after it. Check both outcomes with your ASP before deciding what, if anything, needs correcting. 

Which document corrects which situation?

The practical split, before any category names enter the picture: reducing what's owed goes through a credit note. Adding to it, or fixing an amount that was under-billed, goes through an additional Electronic Invoice instead. A non-financial error isn't addressed by name in Guidelines v1.1 at all, so it shouldn't be forced into either category by assumption. The table below sets out exactly which document applies to each situation.

What are the six Electronic Invoice categories?

Guidelines v1.1 sets out six Electronic Invoice categories in total, split across standard billing and self-billing:

A Commercial Invoice is the term Guidelines v1.1 uses for an invoice issued on sales that don't require a Tax Invoice under the VAT Decree-Law. That covers exempt or out-of-scope supplies, or a supplier that isn't VAT-registered at all. Self-billing narrows the field further, since it only applies for VAT purposes. There's no self-billed Commercial Invoice, and no self-billed Electronic Credit Note either. Only a self-billed electronic Tax Invoice or Tax Credit Note exists, covered in full in Self-billing under UAE eInvoicing.

Provisional invoices don't get a category of their own, either. Every provisional invoice issued should itself be an Electronic Invoice. Any later adjustment to that provisional amount is handled the same way as any other correction. It goes through an Electronic Credit Note or an additional Electronic Invoice, not through editing what was already sent.

Why does a negative total mean a credit note, not an invoice?

The UAE does not permit negative invoices at all. The PINT AE specification states it plainly: reverting an invoice that has been issued and received can only be done by issuing a credit note, and businesses cannot issue negative invoices. That applies to every scenario, not to one situation in particular.

This matters because the general Peppol model allows either approach. A reduction can be represented as a credit note, where the amounts keep the same sign as the invoice being corrected and the document type code signals the reversal. Or it can be represented as a negative invoice, where the amounts flip sign instead. The UAE-specific rules close off the second option. Where a general Peppol page and the UAE section disagree, the UAE section governs.

Guidelines v1.1 applies the same rule to summary invoicing specifically: if a consolidated invoice for a billing period would come out negative, it must be issued as an electronic credit note rather than as an invoice carrying a negative total.

A handful of practical constraints are specific to credit notes, set out in Guidelines v1.1's own list of considerations. They're worth building directly into a template or ERP configuration:

● A single electronic Tax Credit Note can reference multiple past electronic Tax Invoices, rather than needing one credit note per invoice being corrected.

● An Electronic Credit Note can cover only part of an Electronic Invoice's amount. A partial correction doesn't require reversing the whole invoice.

● A Tax Registration Number (TRN) is mandatory on an electronic Tax Invoice and an electronic Tax Credit Note. A Commercial Invoice and its credit note do not carry the same requirement. This follows the document category, not the tax treatment of an individual line: a Tax Invoice that includes an exempt line is still a Tax Invoice.

● A credit note reason code is compulsory, in the field PINT AE calls BTAE-03. OpenPeppol publishes the list of permitted values. A credit note must also reference the invoice it corrects, with one exception: a volume discount. Where the reason code is VD, the preceding invoice reference is not required. That exception exists because a volume discount is typically earned across many invoices rather than tied to one.

What does each document type code confirm?

The PINT AE Billing specification states the pairing for each UAE category directly, not just by naming convention. A UAE tax invoice is associated with code 380, and a UAE tax credit note with code 381. A UAE commercial invoice is associated with code 480, and a UAE commercial credit note (the Electronic Credit Note) with code 81. Its companion Self-Billing specification confirms the other two the same way: 389 for a self-billed invoice, 261 for its credit note. One naming quirk needs unpacking: code 380's own generic label, “Commercial invoice,” is Peppol's standard worldwide business term for an ordinary invoice. It isn't a reference to the UAE's own Commercial Invoice category, which maps instead to code 480, not to 380.

What happens if a credit note is missed or handled wrong?

A missed or late electronic credit note carries its own specific penalty under Cabinet Decision 106 of 2025: AED 100 for each electronic credit note not issued or sent within the required timeframe, capped at AED 5,000 per month. That mirrors the penalty structure for eInvoices themselves, applied separately to credit notes rather than folded into it.

These fines apply to businesses that are required to implement eInvoicing. The Ministry has confirmed that a business applying the system voluntarily is exempt until it becomes mandatorily subject to it.

Retention doesn't relax for a credit note either. Article 11 of Ministerial Decision No. 243 of 2025 requires a Person to retain Electronic Invoices, Electronic Credit Notes, and any associated data for the same period. This applies to whichever type of document it is, and the records must be producible to the FTA on request.

Zoho Software Trading LLC is an Accredited Service Provider for UAE eInvoicing.

Explore UAE eInvoicing with Zoho Books.

Frequently asked questions

When is a credit note required instead of a new invoice?

When the correction reduces what is owed. If the correction adds to it, issue an additional eInvoice for the difference instead. The UAE does not allow negative invoices in any scenario, so a reduction always takes a credit note. See "Which document corrects which situation?" above for the full routing.

Can one credit note cover multiple invoices, or only part of one?

Yes to both. A single Tax Credit Note can reference more than one past Tax Invoice, and a credit note doesn't have to reverse an invoice's full amount to be valid.

Does a Commercial Invoice's credit note need a TRN?

A commercial credit note does not carry the same mandatory TRN requirement as an electronic Tax Credit Note. It still has to carry the other identification fields PINT AE requires, so confirm those with your ASP rather than assuming none apply.

Does self-billing extend to credit notes?

Only as far as a self-billed electronic Tax Credit Note. Self-billing applies for VAT purposes only, so there's no self-billed version of a Commercial Invoice or its Electronic Credit Note. See Self-billing under UAE eInvoicing for the full scope and workflow.

Is there a debit note under UAE eInvoicing?

No. Guidelines v1.1's six Electronic Invoice categories don't include a separate debit note. An increase in what's owed is handled the same way as any other under-billed correction. It goes through an additional Electronic Invoice for the difference, not a distinct debit note document.

Related guides

● How UAE eInvoicing works: the 5-corner model, end to end

● UAE eInvoicing use cases: scenarios, document types and required data

● UAE eInvoicing glossary: PINT AE, Peppol, ASP, TIN, MLS and more

● UAE eInvoice format: PINT AE mandatory fields and XML structure