Credit Note Issuance in the UAE 2026: the VAT Workflow That Survives an FTA Review

Credit note issuance is one of the messiest areas of UAE VAT compliance, and it’s getting harder as the FTA’s e-invoicing programme moves all B2B credit notes onto the structured PINT-AE format through 2026 and 2027. A credit note that fails the format test, misses a mandatory field, skips customer notification, or sits unmatched on the customer’s books for a return cycle — that’s exactly what an FTA reviewer pulls first.

This article is for AR team leads, finance managers and owner-operators of VAT-registered UAE businesses. It walks through Article 62 of the VAT Decree-Law, the mandatory fields on a UAE tax credit note, the PINT-AE structured format, the customer notification path, when the output-VAT reversal lands, and the approval workflow that survives an FTA review.

What counts as a tax credit note

A tax credit note is a formal document issued by a VAT-registered supplier to a customer to reverse all or part of a previously issued tax invoice. Once the original invoice has been issued and recorded, it’s the only valid way to adjust output VAT — there’s no informal workaround the FTA will accept.

When a credit note is required

When a credit note is NOT the right tool

A few situations look like credit-note territory but aren’t. If the error is caught before the customer ever receives the invoice, cancel and reissue rather than credit-note it. A duplicate invoice gets cancelled, not credit-noted — crediting one of the pair leaves a misleading audit trail. Where a posting error is internal and the original invoice is actually correct, fix the journal and leave the customer-facing document alone. And a refund of an advance payment made before any supply happens is an advance refund, not a credit note, since no output VAT was due yet.

Article 62, in plain language

The statutory authority for credit notes sits in Article 62 of Federal Decree-Law No. 8/2017 on Value Added Tax (as amended by Federal Decree-Law No. 18/2022) and the related Executive Regulations issued by the Federal Tax Authority.

Article 62 — the four core requirements

1. A tax credit note must be issued whenever output VAT charged on a tax invoice exceeds the actual VAT due — because the supply was reduced, cancelled or returned.

2. It must go out within 14 days of the date the adjustment event occurred, whether that’s a return, a cancellation or an agreed price reduction.

3. It has to carry the prescribed information (see mandatory fields below).

4. And it must actually reach the customer. Both the supplier’s output-VAT reversal and the customer’s input-VAT reversal depend on that transmission.

The fields the FTA expects to see

These fields are required for every UAE tax credit note. Missing any one of them creates a defective document that does not legally support the VAT reversal.

For taxpayers in scope of PINT-AE, all of these fields must be in the structured XML — the PDF rendering is a secondary representation, not the legal document.

What PINT-AE actually demands

The UAE’s e-invoicing programme is rolling out through 2026 and 2027 (see UAE e-invoicing 2026 and Phase 2 readiness 2027 for the timeline). The structured format is PINT-AE — the UAE specification of the international Peppol Invoice standard.

What PINT-AE changes for credit notes

In-scope taxpayer thresholds

The PINT-AE mandate rolls out in waves:

1. Wave 1 (first phase) — large taxpayers above defined revenue thresholds
2. Wave 2 — mid-market businesses
3. Wave 3 — remaining VAT-registered businesses

The specific revenue thresholds and dates are set by the FTA and Ministry of Finance through implementing regulations. Businesses should confirm their wave assignment with their accountant or directly through the FTA portal.

ERP and accounting system readiness

For credit-note issuance under PINT-AE, the source system needs:

• A structured chart-of-accounts mapping that produces the required PINT-AE fields
• A credit-note module that generates the structured XML, not just a PDF
• An accredited service provider integration for transmission and acknowledgement
• A reason-code framework that maps internal credit-note reasons to PINT-AE classifications
• Archive capability for the structured XML files (retention typically 5 years)

See e-invoicing ERP mapping UAE chart of accounts for the ERP readiness framework.

Six stages, one workflow

A working credit-note workflow has six stages. Each stage has a defined owner and a defined output.

Stage 1: Request

A credit-note request is raised by sales, AR, the warehouse, or the customer. The request captures:

• Original invoice number and date
• Customer name and TRN
• Reason code (return / price adjustment / cancellation / discount / write-off / error correction)
• AED amount requested
• Supporting documents (return note, customer email, dispute reference)

Stage 2: Approval

Approval thresholds:

Approval is documented. The “approve by WhatsApp” shortcut is the single biggest internal-fraud risk in UAE SME AR — a sales rep can collude with a customer to issue an unjustified credit note that writes down the balance and pockets the difference. Documented dual approval defeats this.

Stage 3: Issuance

The accounting or ERP system generates the credit note with:

• Sequential number from the credit-note series
• All mandatory fields populated
• VAT amount at the rate of the original supply
• Reference to the original tax invoice
• Issue date inside the 14-day window from the adjustment event

For PINT-AE in-scope businesses, the structured XML is generated alongside the PDF rendering.

Stage 4: Transmission

The credit note is delivered to the customer:

• Out of PINT-AE scope — by email (PDF) with delivery confirmation, or through the customer’s portal
• In PINT-AE scope — through the accredited service provider with platform-logged transmission and acknowledgement

Stage 5: Customer confirmation

The customer’s AR/AP team should acknowledge receipt and confirm that:

• The credit note is accepted (not disputed)
• The input-VAT reversal will be posted in their next VAT return period

Where the customer disputes the credit note (e.g. disagrees with the reason or AED amount), do not post the output-VAT reversal until the dispute is resolved. A premature reversal creates a matching mismatch with the FTA’s records and may trigger a review.

Stage 6: Reversal on the VAT return

The output-VAT reversal flows through the VAT return for the period in which the credit note is issued.

Partial returns, partial credits

Partial credit notes come up all the time — partial returns, partial discounts, short-shipment adjustments. The rules are simple enough:

• The credit note references the original invoice
• The credit note credits only the adjusted portion (net + VAT)
• The original invoice remains in place for the unchanged portion
• Multiple credit notes can reference the same original invoice
• Each credit note needs its own sequential number, date, reason and full mandatory-field set

Worked example

Original tax invoice INV-2026-001234 issued for AED 50,000 + AED 2,500 VAT = AED 52,500 (sale of 500 units of widget X at AED 100 each).

Customer returns 100 units as defective.

Credit note CN-2026-000087 issued referencing INV-2026-001234:

• Reason: “Return of 100 defective units”
• Net amount credited: AED 10,000 (100 units × AED 100)
• VAT credited: AED 500
• Total credited: AED 10,500

On the supplier’s next VAT return: output VAT reduced by AED 500. On the customer’s next VAT return: input VAT reduced by AED 500.

When the debt has genuinely gone bad

Bad-debt VAT relief allows a supplier to reverse output VAT on a debt that has genuinely gone bad. The rules under Article 64 of the VAT Decree-Law and the executive regulations:

Conditions to claim

1. The debt has been written off in the supplier’s books in accordance with applicable accounting standards (typically IFRS 9 expected credit loss methodology — see IFRS 9 ECL article coming in the next AR-AP chunk)
2. At least six months have passed since the date of the supply (not the date of the invoice)
3. The customer has been notified that the supplier intends to write off the receivable
4. The supplier has taken reasonable steps to recover the debt (statement of account, demand letter, follow-up calls, escalation log)
5. The supplier issues a tax credit note as the mechanism for the reversal

Customer-side obligation

The customer who originally claimed input VAT on the bad-debt invoice must reverse the input VAT on their next VAT return once they receive the bad-debt credit note. This is a frequent compliance gap — customers often miss the reversal trigger and remain exposed to FTA recovery.

Documentation to keep

• Original tax invoice
• Ageing report showing the debt’s progression past 6 months
• Dunning correspondence (emails, letters, call logs)
• Customer notification of write-off intent
• Board / management approval of the write-off
• The issued tax credit note

Bad-debt relief is an area the FTA scrutinises closely — keep the supporting file ready to defend on review.

Where SMEs slip up

Error 1: Late issuance (past 14 days)

The credit note is issued more than 14 days after the adjustment event. Usually because the workflow is slow or the request sat in someone’s inbox. Fix: build issuance into the same-week cadence; for material credit notes, issue same-day or next-day. Late credit notes are technically defective but the FTA usually accepts them with the period-of-issuance reversal. The risk shows up at audit, not enforcement.

Error 2: Missing original invoice reference

The credit note does not cross-reference a specific tax invoice. Fix: every credit note must reference an issued tax invoice number and date. A credit note with no invoice reference is functionally defective.

Error 3: Wrong VAT rate

The credit note applies 5% VAT to an originally zero-rated or exempt supply. Fix: the credit note must use the VAT rate of the original supply. A return of zero-rated exports gets a credit note with zero VAT; a return of standard-rated goods gets 5% credit.

Error 4: Customer not VAT-registered

The customer is a B2C end-consumer or a non-VAT-registered SME. Fix: simplified credit-note rules apply for B2C — the customer TRN field is omitted, and the simplified tax-invoice / credit-note format applies. The supplier’s output-VAT reversal still flows, but the customer cannot recover any input VAT (because they did not claim any).

Error 5: Output reversal without customer acknowledgement

The supplier reverses output VAT on a credit note the customer is disputing. Fix: hold the output reversal until the dispute is resolved. Premature reversal creates a mismatch and an FTA flag.

Error 6: Wrong period reversal

The supplier posts the output reversal in the period of the original supply instead of the period of the credit note. Fix: Article 62 timing places the reversal in the credit-note period. Adjusting prior-period returns is more complex and may need a voluntary disclosure if material.

Error 7: Credit note used to write down a disputed balance without an actual return or adjustment

The credit note is being used as a “balance clean-up tool” rather than for a real adjustment event. Fix: if the original supply happened and the customer received the value, the receivable is either collectable, disputed, or bad debt — not a credit-note candidate. Use the dispute log for disputes and the bad-debt process for write-offs.

What the FTA reviewer pulls first

When the FTA reviews credit notes (which they do routinely as part of VAT-return verification), they typically sample:

• Largest credit notes by AED value in the period
• Round-number credit notes (often a sign of approximation rather than real adjustment)
• Credit notes against recent invoices (testing for cancellation patterns that should have been pre-issuance corrections)
• Bad-debt credit notes (full documentation review)
• Credit notes with no clear reason (testing for write-down without justification)

For each sampled credit note, the FTA reviewer will want:

• The original tax invoice
• The adjustment trigger evidence (return note, customer email, approved discount memo)
• The customer notification (email, portal log, PINT-AE transmission record)
• The customer’s confirmation of input-VAT reversal (where in scope)
• The journal posting reversing the output VAT
• The link to the VAT return where the reversal was claimed

A clean workflow produces all of this as a natural by-product. A messy one means scrambling for evidence weeks after the review request lands.

“

Under Phase 2 e-invoicing, every B2B credit note becomes a structured electronic record. The “we’ll send the customer a PDF later” approach stops working. Businesses that build the structured workflow now have a one-time setup cost. Businesses that wait until enforcement starts have a one-time setup cost plus six months of unmatched credit notes to clean up under FTA pressure.

A month in the credit-note cycle

A working monthly credit-note cadence for a UAE SME with regular returns, post-supply discounts and occasional cancellations:

Our read on this

Credit-note issuance is a small process with large compliance consequences. Between the 14-day rule, the mandatory fields, the PINT-AE mandate, the customer notification requirement and the FTA’s audit focus on credit notes, the informal workflow is finished.

Build issuance, approval, transmission and reversal as a six-stage workflow inside the accounting or ERP system. Output PINT-AE where in scope, log customer confirmations, and keep a clean link from credit note to VAT return. Do that and credit notes stop being something you think about — they just get issued, transmitted, reversed and reconciled every cycle. Skip it and they end up as the most expensive line on your next penalty assessment.