UAE FTA-Compliant Tax Invoice Format Guide

1. Why this format matters — the customer-VAT recovery link

Federal Decree-Law 8/2017 Article 67 ties an invoice's format compliance directly to the buyer's right to recover the VAT they paid. If your invoice is missing a required field — even something as small as the customer's TRN — your B2B buyer loses their input-VAT recovery on that purchase.

That means a non-compliant invoice doesn't just hurt your audit trail; it costs your customer real money. UAE companies maintain "invoice compliance scorecards" on their suppliers — vendors who consistently send malformed invoices get dropped.

2. Full Tax Invoice — every required field

A "Full Tax Invoice" is required whenever the supply exceeds 10,000 OR when the buyer is VAT-registered. Article 65(2) lists 14 required fields:

1. The words "Tax Invoice" in a prominent place (in English, Arabic, or both)
2. Supplier name, address, and TRN (15 digits)
3. Customer name, address — and TRN if customer is VAT-registered
4. Sequential invoice number (no gaps, no resets except documented annual)
5. Date of issuance
6. Date of supply (if different from invoice date)
7. Description of goods or services
8. Unit price + quantity, in AED
9. Discount given (if any), shown as a line item
10. Net amount per line
11. VAT rate applied (5%, 0%, exempt, reverse-charge) per line
12. VAT amount per line, in AED
13. Total payable in AED — net + VAT
14. If any item is zero-rated or exempt, a note indicating the classification

3. Simplified Tax Invoice — when it's allowed

For B2C retail under 10,000 per transaction, you can use the Simplified Tax Invoice (Article 65(3)). Fewer required fields:

1. The words "Tax Invoice"
2. Supplier name, address, and TRN
3. Date of issuance
4. Description of goods or services
5. Total payable in AED (VAT-inclusive is allowed)

Notably absent: customer name, customer TRN, line-item VAT breakdown. This is what every UAE restaurant, retail POS, and coffee shop issues by default.

4. Worked example — a full tax invoice

This single example covers all 14 Article 65(2) requirements. Most UAE accounting software produces this template by default; the trap is in the missing fields when your sales rep manually issues an invoice via Excel.

5. Arabic-language requirements

Article 65(8) requires that tax invoices be in Arabic or have an Arabic translation upon request. In practice:

• If buyer is Arabic-speaking and requests: You must provide the Arabic version within 14 days.
• If goods/services are sold within UAE Mainland Arabic-speaking jurisdiction: Many vendors issue bilingual invoices by default.
• If issuing to a designated free-zone customer: English-only is generally accepted by FTA but verify per free-zone rule.

Practical advice: issue all tax invoices bilingually from the start. The cost is zero (template auto-generates), and you avoid the 14-day amendment workflow when a customer requests Arabic.

6. AED rounding conventions

Article 65(6) of Cabinet Decision 52/2017 sets rounding rules:

• All amounts shown in AED with 2 decimal places (fils precision).
• VAT calculations should not introduce more than 2 decimal places.
• If a value calculates to more than 2 decimals, round to the nearest fils (0.005 rounds up).
• Sum of rounded line VATs must equal the total VAT shown (otherwise there's a 0.01 mismatch that the FTA flags).

For multi-line invoices, the safe approach is: round each line's VAT to 2 decimals, then sum. Don't sum unrounded numbers and round at the end — that's where 0.01 mismatches creep in.

7. E-invoicing UBL 2.1 future-state (July 2026 mandate)

Cabinet Decision 28/2024 introduces e-invoicing in the UAE in phased rollout. Phase 1 (Business-to-Government) mandatory from July 2026. Phase 2 (Business-to-Business) and Phase 3 (Business-to-Consumer) follow on schedules to be confirmed.

The technical format is UBL 2.1 conforming to PEPPOL PINT-AE. Key changes:

• Invoices must be issued in XML (UBL 2.1) format, not just PDF.
• Each invoice must be cryptographically signed.
• Issuance routes through an accredited Service Provider (ASP) — direct vendor-to-buyer XML transmission with the ASP as intermediary.
• Real-time transmission to FTA — no batched end-of-period filing for B2G.

If you're a UAE business with any government contracts, you have until July 2026 to wire up e-invoicing. HIBR ERP is on the PEPPOL PINT-AE pathway with ClearTax UAE as our ASP partner — Phase-1 ready before the mandate hits.

8. The 9 most-common FTA audit-failure patterns

1. Missing customer TRN on a B2B invoice. Buyer's input-VAT recovery rights compromised. Most-flagged failure.
2. Non-sequential invoice numbers. Gaps without documented explanation suggest hidden transactions.
3. Date of supply missing. Required when different from invoice date — common for project-based services.
4. Wrong VAT rate applied. 5% applied to zero-rated exports, or vice versa.
5. VAT amount calculation error. Line-level VAT doesn't equal Net × 5%.
6. Discount handling. Discount applied to VAT-inclusive total instead of net.
7. Reverse-charge invoices missing the indicator. Cross-border services without "reverse charge" annotation.
8. Multi-currency without AED conversion. Invoices in USD must show AED equivalent using UAE Central Bank reference rate (Article 60).
9. Credit notes that don't reference the original invoice. Required cross-reference per Article 70.

9. Pre-issue checklist

Before clicking "Issue" on any tax invoice:

• ☐ Words "Tax Invoice" present (English, Arabic, or both)
• ☐ Supplier name, address, TRN all present
• ☐ Customer name + TRN (if VAT-registered)
• ☐ Sequential invoice number from your numbering sequence
• ☐ Date of issuance + date of supply (if different)
• ☐ Each line item has description + quantity + unit price
• ☐ Each line has applicable VAT rate (5% / 0% / exempt / reverse-charge)
• ☐ Discount shown as a line item (if any)
• ☐ Net amount + VAT amount + total payable, all in AED with 2 decimals
• ☐ Zero-rated or exempt classifications noted
• ☐ Currency conversion shown (if invoice originated in non-AED currency)
• ☐ If e-invoicing required (Phase 1 B2G from July 2026): UBL 2.1 XML + ASP transmission