UAE Tax Invoice Format 2026: FTA VAT Invoice Requirements and Sample

The UAE structures its VAT invoice requirements around two distinct document types: the full tax invoice and the simplified tax invoice. The dividing line is not a single value threshold, which is where most guidance gets it wrong. Under Article 59(5) of the VAT Executive Regulation, a supplier may issue a simplified tax invoice in either of two situations: where the recipient is not VAT-registered — in which case there is no value ceiling at all — or where the recipient is VAT-registered and the consideration for the supply does not exceed AED 10,000. The AED 10,000 figure is a cap on business-to-business simplified invoicing, not a blanket ceiling on every simplified invoice. A full tax invoice is always permissible in either case; issuing the simplified version is an option, never an obligation. Getting this distinction right matters, because the Federal Tax Authority (FTA) treats invoice errors as compliance violations regardless of whether the underlying tax was calculated correctly.

Both invoice types share a core set of mandatory fields. Every UAE VAT invoice must display:

• The words "Tax Invoice" clearly marked on the document
• The supplier's name, address, and Tax Registration Number (TRN)
• The date of issue
• A description of the goods or services supplied
• The VAT amount in AED (if the transaction is conducted in a foreign currency, the AED equivalent must still appear)

Full tax invoices carry additional requirements beyond this baseline. They must include a sequential invoice number, the recipient's name, address, and TRN (where the recipient is registered), unit prices and quantities, any discount details, net amounts per line item, and the applicable VAT rate for each line. These extra fields exist because full tax invoices serve as the primary evidence for higher-value transactions and input tax credit claims. Notably, a sequential number is not among the particulars required on a simplified tax invoice — a point covered in detail below, because it surprises most readers.

Annotated samples of both documents appear in the next section, with each required particular numbered and cross-referenced to the field-by-field explanations that follow.

This two-tier framework operates under Federal Decree-Law No. 8 of 2017 on Value Added Tax, as amended — most recently by Federal Decree-Law No. 16 of 2025, effective 1 January 2026 — with the FTA responsible for enforcement, audit, and penalty assessment. The detailed invoice content rules sit one level down, in Article 59 of the Executive Regulation (Cabinet Decision No. 52 of 2017), which has itself been amended twice recently: by Cabinet Decision No. 100 of 2024, effective 15 November 2024, and Cabinet Decision No. 100 of 2025, effective 29 September 2025. Article 59 now runs to sixteen clauses, and the newest of them changes the two-tier framework fundamentally for any business entering e-invoicing scope — covered in detail below. The law places compliance obligations on both sides of a transaction. Suppliers must issue invoices that meet every mandatory field requirement for the relevant invoice type. Recipients, meanwhile, need to verify that invoices they receive are fully compliant before using them to support input tax credit deductions — a deficient invoice can result in a rejected claim even if the VAT was legitimately charged and paid.

UAE Tax Invoice Format: Annotated Sample Layouts

There is no official UAE tax invoice template that businesses are obliged to copy. Article 59 of the Executive Regulation prescribes required content, not a visual layout — so any layout that carries the required particulars is a valid tax invoice, whether it comes out of an ERP, a spreadsheet, or a point-of-sale terminal. Since April 2026, however, the FTA does publish official annotated specimen invoices in its Knowledge Centre guide, A Comprehensive Handbook on Tax Invoices and Tax Credit Notes, including a simplified tax invoice checklist with numbered callouts and a set of before-and-after examples of non-compliant invoices. Those specimens are illustrative rather than prescriptive — useful as a reference for how the particulars are normally arranged, not as a layout you are required to reproduce.

The two samples below show the same particulars in a conventional arrangement. The bracketed numbers are callouts that cross-reference the numbered field explanations later in this guide. All names, addresses, and TRNs are fictional.

Full Tax Invoice — Annotated Sample

=================================================================
 TAX INVOICE                                                 [1]
=================================================================
 Gulf Technical Services LLC                                 [2]
 Office 1204, Burj Al Salam, Sheikh Zayed Road, Dubai, UAE    [3]
 TRN: 100555555500003                                        [4]
-----------------------------------------------------------------
 BILL TO
 Meridian Contracting LLC                                    [5]
 Warehouse 7, Dubai Investment Park 2, Dubai, UAE             [6]
 TRN: 100444444400003                                        [7]
-----------------------------------------------------------------
 Tax invoice no.:  INV-2026-04821                            [8]
 Date of issue:    12 July 2026                              [9]
 Date of supply:   30 June 2026                              [10]
-----------------------------------------------------------------
 Description                Qty  Unit price   Disc.       Net
                                      (AED)   (AED)     (AED)
 ---------------------------------------------------------------
 Network security                                            [11]
 assessment - Phase 1        1    18,000.00    0.00  18,000.00
 Firewall appliance
 (model NX-450)              2     4,250.00  500.00   8,000.00
                                                             [12]
-----------------------------------------------------------------
 Subtotal excluding VAT (AED)                         26,000.00
 VAT @ 5% (AED)                                        1,300.00
 TOTAL PAYABLE INCLUDING VAT (AED)                    27,300.00
                                                             [13]
=================================================================

Because the consideration here is AED 27,300 and the recipient is VAT-registered, a simplified invoice is not available for this supply — the full set of particulars is mandatory.

Simplified Tax Invoice — Annotated Sample

=================================================
 TAX INVOICE                                 [1]
=================================================
 Al Barsha Cafe LLC                          [2]
 Unit 3, Al Barsha 1, Dubai, UAE
 TRN: 100333333300003
-------------------------------------------------
 Date of issue: 25 July 2026                 [3]
 Invoice no.: 004821
-------------------------------------------------
 Description                            Amount
                                         (AED)
 Flat white x 2                           32.00
 Chicken shawarma platter x 1             45.00 [4]
-------------------------------------------------
 TOTAL INCLUDING VAT (AED)                77.00 [5]
 of which VAT @ 5% (AED)                   3.67 [6]
=================================================

Two details in this sample are worth pointing out, because they are where simplified invoices most often go wrong.

First, the VAT figure is calculated out of the total rather than added to it: AED 77.00 × 5 ÷ 105 = AED 3.67. A simplified invoice states a VAT-inclusive total, so the tax component has to be extracted from it, not applied on top. Consumer-facing businesses are separately required to display prices inclusive of VAT, and adding 5% at the till to an advertised price is one of the failures the FTA's handbook illustrates directly.

Second, the invoice number. Article 59(2) does not list a sequential number among the particulars required on a simplified tax invoice, and it does not require the recipient's name, address, or TRN, the date of supply, or any per-line breakdown either — that is the whole point of the simplified form.

There is a genuine divergence to be aware of here, and it is the reason the number appears in the sample above. The FTA's own simplified tax invoice checklist in the April 2026 handbook annotates a sequential invoice number as one of its six callouts, and the accompanying summary of what a simplified invoice should contain also mentions recipient details and unit prices — items that Article 59(2) does not require. The Executive Regulation is the binding text and the shorter list is the legal minimum. But where the regulation sets a floor and the tax authority's published guidance illustrates something fuller, the practical course is to follow the guidance: include a sequential number on simplified invoices. It costs nothing, every point-of-sale system generates one anyway, and it removes any argument during an inspection. This guide flags the distinction rather than papering over it, because knowing which parts of a checklist are legally required and which are prudent practice matters when you are deciding what your systems must enforce.

UAE Tax Invoice Mandatory Fields: Full vs Simplified Reference

Article 59(1) sets out the particulars for a full tax invoice in twelve lettered paragraphs, (a) through (l). This guide expands them into thirteen numbered fields below, because paragraphs (b) and (c) each bundle three separate pieces of information — name, address, and TRN — that businesses tend to get wrong independently of one another. Article 59(2) sets out the simplified tax invoice particulars separately, in five paragraphs.

The table below maps every particular to its legal basis, to whether it is required on each invoice type, and to the failure mode auditors actually find. It lists the particulars individually rather than following the thirteen-field numbering, so paragraph (h) — which bundles unit price, quantity, tax rate, and line amount — appears as one row while the recipient's details appear as three. Anything not listed as required for a simplified invoice is not mandated by Article 59(2).

Particular	Article 59 basis	Full invoice	Simplified invoice	Most common failure
The words "Tax Invoice"	59(1)(a) / 59(2)(a)	Required	Required	Document labeled "Invoice", "Sales Invoice", or "Receipt"
Supplier's legal name	59(1)(b) / 59(2)(b)	Required	Required	Trading name used instead of the FTA-registered legal name
Supplier's address	59(1)(b) / 59(2)(b)	Required	Required	Head-office address shown for a supply made by a branch
Supplier's TRN	59(1)(b) / 59(2)(b)	Required	Required	Omitted on point-of-sale receipts
Recipient's name	59(1)(c)	Required where the recipient is a Registrant	Not required	Department or project name instead of the registered entity
Recipient's address	59(1)(c)	Required where the recipient is a Registrant	Not required	Site or delivery address instead of the registered address
Recipient's TRN	59(1)(c)	Required where the recipient is a Registrant	Not required	Never collected at onboarding, so left blank
Sequential invoice number	59(1)(d)	Required	Not required	Numbering restarted mid-year or duplicated across branches
Date of issue	59(1)(e) / 59(2)(c)	Required	Required	Backdated to fit a filing period
Date of supply	59(1)(f)	Required only where it differs from the date of issue	Not required	Omitted when it differs, shifting the tax period
Description of goods or services	59(1)(g) / 59(2)(d)	Required	Required	"Consulting" or "Services" with no specificity
Unit price, quantity or volume, tax rate, and amount payable per line	59(1)(h)	Required	Not required	Multiple items bundled into one lump-sum line
Discount offered	59(1)(i)	Required where a discount applies	Not required	Discount netted silently into the unit price
Gross amount payable in AED	59(1)(j)	Required	Required as part of the VAT-inclusive total, 59(2)(e)	Stated only in the invoice currency
Tax amount in AED, plus the exchange rate where a foreign currency is converted	59(1)(k) / 59(2)(e)	Required	Required	Exchange rate omitted entirely on foreign-currency invoices
Statement that the recipient must account for the tax, with a reference to the relevant provision	59(1)(l)	Required where the reverse charge applies	Not available — 59(5) excludes reverse charge supplies	Left off completely, or stated without the legal reference

Note the last row. Article 59(1)(l) is the particular most often missing from UAE invoice guidance altogether, and it carries a structural consequence: because Article 59(5) excludes reverse charge supplies from simplified invoicing, a supply on which the recipient accounts for the tax always requires a full tax invoice, regardless of value.

Note also that the exchange rate in 59(1)(k) is only required where a currency conversion has actually taken place. An invoice denominated in AED throughout does not need to state a rate.

Full Tax Invoice: Every Mandatory Field Explained

A full tax invoice is the default. Article 59 of the UAE VAT Executive Regulation requires that where a registrant must issue a tax invoice, it meets the full set of particulars in clause 1 — the simplified form is an exception to that rule, available only in the two situations set out above and examined in detail below. Where the recipient is VAT-registered and the consideration exceeds AED 10,000, or where the reverse charge applies, the full form is the only option. Missing even one required particular can invalidate the invoice for input tax credit purposes and expose your business to FTA penalties.

Here is every mandatory field, what it means in practice, and where errors tend to occur.

1. The Words "Tax Invoice"

The phrase "Tax Invoice" must be clearly displayed on the document. This sounds trivial, but invoices generated from generic accounting templates sometimes default to "Invoice" or "Commercial Invoice" without the tax designation. The FTA expects the exact wording — not a variation. Note that a commercial invoice used for UAE customs import clearance is a separate document with its own mandatory fields — it does not substitute for a VAT tax invoice.

2. Supplier's Name

The full legal name of the entity making the supply, exactly as registered with the FTA. Trading names or abbreviations that differ from the registered name create verification problems during audits.

3. Supplier's Address

The supplier's registered business address. For businesses with multiple branches, this should be the address of the branch making the supply or the principal place of business as recorded in the VAT registration.

4. Supplier's Tax Registration Number (TRN)

The supplier's 15-digit TRN issued by the FTA. This is the single most verified field on any UAE VAT invoice. Recipients use it to confirm the supplier is legitimately VAT-registered before claiming input tax credits.

5. Recipient's Name

The full legal name of the person or entity receiving the supply. For B2B transactions, this must match the recipient's official registration — not a department name, project code, or informal reference.

Worth reading Article 59(1)(c) carefully here: it groups the recipient's name, address, and TRN into a single particular and conditions all three on the recipient being a Registrant. Fields 5, 6, and 7 below therefore stand or fall together. Where you are invoicing a VAT-registered customer, all three are mandatory; where the recipient is not registered, the paragraph does not bite — though in practice most suppliers include the customer's name regardless, and doing so costs nothing.

6. Recipient's Address

The recipient's registered business address. This field establishes the place of supply for certain transaction types and supports the audit trail connecting the invoice to the correct entity.

7. Recipient's TRN (If VAT-Registered)

If the recipient holds a UAE VAT registration, their TRN must appear on the invoice. This field is conditional — it only applies when the recipient is registered. However, omitting it for a registered recipient is a common compliance gap, particularly when suppliers do not ask customers for their TRN at the point of sale or onboarding.

8. Sequential Tax Invoice Number

Each tax invoice must carry a unique, sequential number that allows the FTA to identify the document and trace it within your records. Your numbering system does not need to follow a specific format, but it must be sequential and must not contain gaps or duplicates. Restarting numbering mid-year or across branches without a distinguishing prefix is a frequent source of audit findings.

9. Date of Issue

The date the invoice was created and issued to the recipient. This is the administrative date — when the document was produced.

10. Date of Supply

This is the date the goods were delivered or the services were performed. The date of supply determines which tax period the transaction falls into for VAT return purposes. When you deliver goods on 28 March but issue the invoice on 3 April, the supply belongs to the March tax period, not April. Misaligning these dates is one of the most consequential errors in UAE VAT reporting because it shifts the tax liability to the wrong period, potentially triggering late-payment penalties.

If the date of supply and the date of issue are the same, you still satisfy the requirement — there is no need to list the date twice, but many businesses include both for clarity.

11. Description of Goods or Services

A sufficiently detailed description of what was supplied. "Professional services" or "goods" alone is not adequate. The FTA expects enough specificity that an auditor can determine the nature of the supply, the applicable VAT rate, and whether any exemptions or zero-rating provisions apply. For example, "IT consulting services — network security assessment, January 2026" is far more defensible than "consulting."

12. Unit Price, Discounts, and Net Amount

For each line item, the invoice must show the unit price exclusive of VAT, any discounts applied, and the resulting net amount payable per line. This breakdown matters because the FTA needs to verify that the VAT calculation is applied to the correct base amount. Bundling multiple items into a single line with one lump-sum price — without showing unit-level detail — does not meet the requirement.

13. VAT Rate, VAT Amount in AED, and Total Amount Payable

Each line item must show the VAT rate applied (5%, 0%, or exempt), the VAT amount expressed in AED, and the total amount inclusive of VAT. Two critical points here:

• The VAT amount must always be stated in AED — and so must the exchange rate. If your transaction is invoiced in a foreign currency (USD, EUR, GBP), you are required to convert the VAT portion to AED and display that converted amount on the invoice. The rate used is the rate published by the UAE Central Bank at the date of supply. Article 59(1)(k) goes one step further than most guidance acknowledges: it requires the tax amount in AED together with the rate of exchange applied where a conversion has taken place. Stating the converted AED figure but omitting the rate you used leaves the particular incomplete. Where the invoice is denominated in AED throughout, no rate needs to be shown.
• Zero-rated supplies still require full compliance. Exports qualifying for zero-rating, international transport services, and other 0% supplies must include every one of these 13 fields. The invoice must explicitly state the 0% VAT rate — you cannot simply omit the VAT line and assume the zero-rating is implied.

The Reverse Charge Statement: The Particular Most Guidance Omits

Article 59(1)(l) adds a particular that most UAE invoice checklists leave out entirely. Where the supply is one on which the recipient is required to account for the tax, the invoice must carry a statement to that effect and a reference to the relevant provision of the Decree-Law. Both halves are required — a bare "reverse charge applies" note without the legal reference does not satisfy the paragraph.

This has a consequence for which invoice type you may issue. Article 59(5) makes simplified invoices unavailable where the reverse charge mechanism applies, so a reverse charge supply always requires a full tax invoice, whatever its value.

One recent change is worth noting for anyone who built a process around the old rule. Federal Decree-Law No. 16 of 2025, effective 1 January 2026, removed the requirement for a recipient to self-issue an invoice under the reverse charge mechanism. The obligation to retain supporting documentation for the supply remains — what has gone is the specific requirement to raise a self-billed document.

When the Invoice Must Be Issued: The 14-Day Rule

Getting the fields right is only half of the obligation; Article 59(13) also sets when the document has to exist. The general rule is 14 days from the date of supply, with two named exceptions that pull in opposite directions:

• Simplified tax invoices must be issued on the date of supply itself — not within 14 days. This is the deadline most retail and food-service operators are unaware of, and it is why a point-of-sale system that batches receipts overnight can be non-compliant even when every particular is present.
• Summary tax invoices, used where a supplier makes multiple supplies to the same customer within a month, must be issued and delivered within 14 days of the end of the calendar month in which the date of supply falls.

The FTA may also specify further cases by decision. Missing the applicable deadline is a distinct violation from getting a particular wrong, and it carries its own penalty — covered below.

Using This as a Compliance Checklist

Walk through your most recent batch of issued invoices against these 13 fields. Pay particular attention to the recipient's TRN (field 7), the date of supply versus date of issue distinction (fields 9 and 10), and the AED requirement for VAT amounts on foreign-currency transactions (field 13). These three areas account for a disproportionate share of invoice compliance failures in FTA audits.

---

Simplified Tax Invoice: When It Applies and What to Include

Not every transaction requires the full set of invoice fields outlined above. UAE VAT law provides a simplified tax invoice option that reduces the administrative burden on suppliers while still meeting FTA documentation standards — used mainly in retail and other consumer-facing settings, though as the rule below makes clear, "consumer-facing" rather than "small" is the better description of when it is available.

The entitlement rule has two limbs, and conflating them is the single most widespread error in UAE invoice guidance. Article 59(5) permits a simplified tax invoice in either of the following situations:

• The recipient is not a Registrant. Where you are supplying a consumer or an unregistered business, a simplified tax invoice is available with no value ceiling whatsoever. An individual buying AED 40,000 of goods in a single transaction can be given a simplified tax invoice.
• The recipient is a Registrant and the consideration does not exceed AED 10,000. Here the cap does apply, and the FTA's handbook glosses the consideration as the VAT-inclusive price.

The FTA's own guidance states the test in exactly these two limbs, so this is not a strained reading of the regulation. The AED 10,000 figure is a limit on B2B simplified invoicing only. Stating it as a blanket ceiling on all simplified invoices — as a great deal of published guidance does — overstates the obligation for retail and consumer supplies and understates it nowhere.

Two qualifications complete the picture. First, the reverse charge mechanism is carved out: where the recipient accounts for the tax, a simplified invoice is not available at any value. Second, issuing a simplified invoice is optional — a point the FTA's handbook makes explicitly, noting that a supplier may choose to issue a full tax invoice even where the recipient is not registered for VAT. Clause 5 is an exception a supplier may rely on, not a rule it must follow.

Six mandatory fields must appear on every simplified tax invoice. Article 59(2) expresses them as five lettered paragraphs, with the total consideration and the tax amount appearing together in paragraph (e); they are separated here because they are two distinct figures on the page and are got wrong independently:

1. The words "Tax Invoice" — the same labeling requirement as a full tax invoice
2. Supplier's name, address, and TRN — identifying the registered taxable person making the supply
3. Date of issue — the date the invoice is created
4. Description of goods or services supplied — sufficient detail to identify what was provided
5. Total amount payable inclusive of VAT — a single figure representing the full charge to the buyer
6. VAT amount in AED — the tax component stated separately in UAE dirhams

The practical advantage of a simplified tax invoice is what it omits. Unlike a full tax invoice, there is no requirement to include the recipient's name, address, or TRN, nor is there any need for unit prices, discount breakdowns, or per-line-item net amounts. This makes simplified invoices considerably faster to produce, particularly in retail and point-of-sale environments where transactions are high-volume and low-value.

That speed comes with a trade-off for the buyer, however. Because simplified invoices lack recipient identification and itemized pricing, they provide less documentation support for input tax credit claims. Recipients who need to recover VAT on purchases should request a full tax invoice even when the supply falls below the AED 10,000 threshold.

The most common compliance error involving simplified invoices is issuing one to a VAT-registered customer for a supply exceeding AED 10,000 — typically because the supplier's system applies the simplified format by default and never checks whether the buyer is registered. Note where the risk actually sits: the same AED 12,000 supply may legitimately carry a simplified invoice if the customer is an unregistered consumer, and cannot if the customer is a registered business. It is the recipient's registration status, not the value alone, that decides. The safest approach whenever the customer is or might be VAT-registered and the value is anywhere near the threshold: issue a full tax invoice. A full tax invoice is always acceptable — it exceeds the minimum requirements rather than falling short of them.

The UAE's two-tier approach is not unique. Many VAT jurisdictions distinguish between simplified and full invoice requirements, though the qualifying criteria and mandatory fields vary. Thailand's threshold-based tax invoice system, for example, follows a comparable structure with its own distinct thresholds and documentation rules. Sri Lanka's tax invoice format requirements offer another regional comparison for VAT-registered businesses tracking mandatory fields and 2026 rule changes. Closer to home, Saudi Arabia's ZATCA-mandated VAT invoice fields share several structural similarities with the UAE framework but diverge on language requirements, electronic clearance procedures, and the specific data elements ZATCA enforces. Knowing which document your own jurisdiction requires, and when, reduces audit exposure.

The Two-Tier System Has an Expiry Date: Article 59(16)

The most consequential recent change to Article 59 is also the least reported, and it dissolves the distinction this section has just described.

Clause 16 was added to Article 59 by the recent amendments. It provides that where a registrant is required to issue tax invoices as electronic invoices under Clause 5 of Article 65 of the Decree-Law — the e-invoicing mandate — or where a registrant issues electronic invoices voluntarily, clauses 2, 3, 5, 7, 8, and 15 of Article 59 cease to apply.

Read that list against what those clauses do, and the effect is substantial:

• Clause 5 is the entitlement to issue a simplified invoice, and clause 2 is its list of particulars. With both switched off, simplified tax invoices stop existing for a business in e-invoicing scope. Every invoice must carry the full Article 59(1) particulars.
• The AED 10,000 threshold becomes irrelevant for that business, because the provision containing it no longer applies to it.
• Clause 3 is the exemption from issuing an invoice at all for wholly zero-rated supplies where sufficient records exist. That exemption also disappears — in-scope businesses must issue invoices for zero-rated supplies too.
• Clause 7 is the FTA's power to waive particulars where invoicing would be impractical, and clause 8 is the general permission to issue invoices by electronic means on stated conditions. Both are superseded by the e-invoicing system's own rules.

The clause catches voluntary adopters as well as mandated ones, which creates a trap worth naming. A business that opts into e-invoicing early — perhaps to test its systems ahead of its deadline — loses the ability to issue simplified tax invoices from the moment it does so. For a retailer or food-service operator, that is a far larger operational change than the file format.

The practical implication for planning: if your business will fall into e-invoicing scope, treat the two-tier framework as a transitional state rather than a permanent feature of UAE VAT. The deadlines that determine when it lapses for you are set out at the end of this guide.

Is My Invoice Format Acceptable? Common Questions

Because Article 59 regulates content rather than layout or medium, most "is this allowed?" questions resolve the same way: if the document carries every required particular, it is a tax invoice. The answers below apply that principle, and flag where the legislation is genuinely silent rather than pretending to a certainty that does not exist.

Can I issue tax invoices from Excel or Word? Yes, on the reasoning above — nothing in Article 59 prescribes the software used, and clause 8 expressly contemplates issuing invoices by electronic means provided you can store a copy securely and guarantee the authenticity and integrity of the content. Attach an expiry date to that answer, though. Once your business falls into e-invoicing scope, Article 59(16) disapplies clause 8 for you, and you will be required to issue structured PINT-AE XML through an accredited service provider — from 1 January 2027 for larger businesses and 1 July 2027 for the rest. A spreadsheet-based process is viable today and has a known end date.

Are handwritten invoices acceptable? Probably, but treat this as reasoning rather than a confirmed FTA position. The legislation defines a tax invoice as a written or electronic document, and Article 59 prescribes no medium — so a handwritten document carrying all of the Article 59(1) particulars is not prohibited by anything we can point to. What does not exist is an FTA statement endorsing the practice, and sources asserting one are generally not authoritative. In practical terms a handwritten invoice is legible-handwriting risk plus a record-keeping burden for no gain, and it cannot satisfy the e-invoicing requirements once those apply to you.

Does my invoice need to be in Arabic? Not on the face of the invoice. Article 59's list of particulars contains no language requirement, so an English-only tax invoice is compliant. The Arabic question concerns documents submitted to the FTA: Cabinet Decision No. 74 of 2023 allows the Authority to accept records in English and provides that it may, at its discretion, request a certified Arabic translation. So the practical rule is that you invoice in English and keep the possibility of a translation request in mind for audit correspondence — not that you produce bilingual invoices as a matter of course.

Can a proforma invoice serve as a tax invoice? No — and this one is categorical rather than hedged. Article 59(1)(a) requires the words "Tax Invoice" to be clearly displayed, which a proforma invoice by definition does not carry, and a document that is not a tax invoice cannot support an input tax credit claim. The same applies to quotations, purchase orders, delivery notes, and payment receipts. If a supplier sends you a proforma against which you intend to recover VAT, request the tax invoice.

Can I invoice in a foreign currency, and which rate applies? Yes, you can denominate the invoice in any currency. The VAT amount must still be shown in AED, converted at the rate published by the UAE Central Bank at the date of supply, and Article 59(1)(k) requires the rate you applied to appear on the invoice alongside the converted figure. Using the rate at the invoice date rather than the date of supply is a common and easily audited error, particularly around month-end.

Can one invoice carry multiple VAT rates? Yes. Article 59(1)(h) requires the rate of tax to be shown for each good or service supplied, which means mixed invoices are expressly contemplated — a single document can carry standard-rated, zero-rated, and exempt lines. What it cannot do is present a blended rate or a single tax figure with no line-level attribution. Each line shows its own rate, and the totals must reconcile to the sum of the lines.

What about commercial invoices and free zone supplies? These are separate regimes rather than format variations. A commercial invoice used for customs clearance is a different document with its own required contents and does not substitute for a VAT tax invoice, and supplies crossing designated zone boundaries can carry VAT treatment that changes what the invoice needs to say. Both are covered in dedicated guides linked from this article rather than summarized here, because in each case the invoice question follows from the underlying VAT analysis.

Tax Registration Numbers: Requirements and FTA Verification

The Tax Registration Number (TRN) is a 15-digit identifier assigned by the Federal Tax Authority upon VAT registration. Every VAT-registered entity in the UAE receives a unique TRN, and this number serves as the primary link between a business and its tax obligations across all FTA systems and filings.

Where the TRN must appear on invoices:

• All tax invoices (full and simplified): The supplier's TRN is mandatory on every invoice type without exception.
• Full tax invoices only: The recipient's TRN must also be included when the recipient is VAT-registered. This dual-TRN requirement on full invoices enables the FTA to cross-reference transactions between both parties during audits.

Getting TRN placement wrong is one of the most common compliance failures. A simplified invoice missing the supplier's TRN is technically invalid. A full invoice omitting a VAT-registered recipient's TRN creates problems on both sides of the transaction.

How to verify a TRN on the FTA portal:

The FTA maintains a free, publicly accessible TRN verification tool, and it is worth being precise about where it lives, because it is not a standalone page and not inside EmaraTax. It is an embedded widget on the FTA homepage itself:

1. Open the FTA homepage and click the TRN verification icon in the quick-access panel on the right-hand side. A dialog opens in place — you are not navigated to a separate page.
2. Enter the full 15-digit TRN from the invoice you are reviewing and complete the CAPTCHA.
3. The tool returns the registered legal name associated with that TRN, or reports it as invalid.
4. Cross-check the returned legal name against the supplier name on the invoice to confirm they match.

No login, EmaraTax account, or UAE Pass authentication is required — this is a public lookup, which means your AP clerks can run it without needing tax-portal credentials.

This verification step takes under a minute but protects your business from significant financial exposure. If a supplier provides an invalid or incorrect TRN on their invoice, and you claim input tax credit based on that document, the FTA can deny your entire credit claim for that transaction. The financial risk falls squarely on the recipient, not the supplier who made the error. Building TRN verification into your accounts payable workflow is a practical safeguard — the first invalid TRN it catches will save more than the verification step costs.

Businesses operating across UAE free zones face an additional layer of complexity. Entities in designated zones may receive distinct VAT treatment, and the intersection of free zone status with TRN requirements affects how invoices should be structured for transactions crossing zone boundaries. The UAE free zone invoicing and VAT rules guide covers how to structure invoices for transactions crossing zone boundaries — incorrect invoicing can trigger both VAT liability and penalties.

Validating Incoming Invoices for Input Tax Credit Claims

Most UAE VAT guidance focuses on what issuers must include on their invoices. But for businesses claiming input tax credits, the more pressing question is what to check on invoices you receive. The FTA places the verification burden squarely on the recipient. If a supplier sends you a non-compliant invoice and you claim input tax credit based on it, your claim is the one that gets rejected. The supplier faces no consequence for your denied credit. That lost VAT recovery is a direct, unrecoverable cost to your business.

This makes incoming invoice validation a financial control function, not an administrative formality.

Pre-Processing Validation Checklist

Before recording any supplier invoice in your VAT return, AP teams should confirm every item below:

If you are compiling the return support in Excel, keep these checks tied to a UAE VAT purchase register built from invoices so each claimed credit stays traceable to its source document. For refund claims, extend that file into a VAT311 refund supporting document pack so invoice evidence, reconciliations, and FTA follow-up records stay together.

1. Invoice type is correct for the transaction. Because your business is VAT-registered, a supplier invoicing you may only use the simplified format where the consideration does not exceed AED 10,000 — the no-ceiling limb of Article 59(5) applies to unregistered recipients, not to you. So if you receive a simplified tax invoice for a supply above AED 10,000, it is not a valid basis for an input tax credit claim and should not be processed as one. The same applies at any value to a supply on which you account for the tax under the reverse charge, where the simplified format is unavailable entirely. Note also that a simplified invoice omits your name and TRN by design, which is why it supports a credit claim poorly even below the threshold.

2. Supplier TRN is present and valid. The Tax Registration Number must appear on the invoice. Cross-check it against the FTA's online TRN verification tool on the tax.gov.ae portal. An invalid, expired, or missing TRN renders the invoice non-compliant regardless of whether every other field is correct.

3. "Tax Invoice" header label is present. The document must be explicitly labeled "Tax Invoice." Purchase orders, proforma invoices, delivery notes, and payment receipts are not tax invoices, and input tax credit cannot be claimed against them.

4. VAT amount is stated in AED and arithmetically correct. Verify that the VAT charge equals exactly 5% of the taxable amount. For invoices with mixed supplies (standard-rated, zero-rated, exempt), confirm each line's VAT treatment and recalculate the total. Rounding errors or incorrect VAT rates are grounds for the FTA to deny the credit.

5. Recipient details are correctly stated (full tax invoices only). Your company name, address, and TRN must appear on any full tax invoice you receive. A misspelled company name, wrong TRN, or missing address creates a mismatch between the invoice and your VAT registration record, giving the FTA reason to question the claim.

6. Date of supply falls within the correct tax period. The tax point on the invoice determines which VAT return period the input tax credit belongs to. Claiming a credit in the wrong period, whether too early or too late, can trigger penalties during an FTA audit even if the invoice itself is otherwise compliant.

Common Failure Scenarios

In practice, four issues account for the majority of incoming invoice rejections:

• Missing "Tax Invoice" header. Suppliers, particularly smaller vendors, often issue invoices that contain all the right data but omit the required header label. Without it, the document is not a tax invoice under UAE VAT law.
• Wrong or missing recipient TRN. Suppliers serving multiple clients sometimes copy the wrong TRN or leave the field blank. This is especially common when supplier accounting systems auto-populate from outdated customer records.
• Incorrect VAT calculation. Manual invoicing and spreadsheet-based billing frequently produce arithmetic errors, particularly on multi-line invoices or invoices with a mix of taxable and exempt supplies.
• Simplified invoice used above AED 10,000 for a registered buyer. Some suppliers default to the simplified format for every transaction because their system never asks whether the customer is VAT-registered. Since you are registered, the AED 10,000 cap applies to invoices issued to you, and a simplified invoice above it is insufficient for your input tax credit claim.

Note that these validation steps assume the supplier is charging and remitting VAT on their invoice. When your business receives services from non-resident suppliers — particularly from GCC neighbors like Saudi Arabia, where non-resident suppliers face distinct reverse charge obligations — the UAE recipient self-accounts for VAT under the reverse charge mechanism, and the standard invoice validation workflow above does not apply to the VAT component.

What to Do When an Invoice Fails Validation

Request a corrected invoice from the supplier before your VAT return filing deadline. Do not claim input tax credit on a non-compliant invoice while waiting for a correction to arrive. A five-minute email to a supplier requesting a revised invoice costs far less than a denied credit claim and any penalties the FTA may impose for filing an inaccurate return. If the corrected invoice arrives after the current period's filing deadline, claim the credit in the next eligible period rather than filing based on a defective document. Once your invoice-level checks are complete, the figures still need to roll up cleanly into Form 201 — a pre-filing reconciliation that ties purchase invoices to Article 55 input VAT recoverability, reverse charge entries, and credit-note period assignment catches the timing differences that individual invoice validation cannot.

---

FTA Penalties for Invoice Non-Compliance

Invoice compliance in the UAE is not a theoretical concern. According to the UAE Federal Tax Authority's 2024 compliance report, the FTA conducted 93,000 field inspection visits across all seven emirates in 2024 — a 135% year-on-year increase — recovering more than AED 348 million in tax dues and associated fines. The agency is inspecting more businesses, more frequently, and invoice documentation is a primary focus of every visit.

The administrative penalties for VAT violations sit in Cabinet Decision No. 40 of 2017 as amended, whose current penalty table was substituted by Cabinet Decision No. 129 of 2025 with effect from 14 April 2026. The invoice-related rows of that table (Table No. 3, on VAT violations) are:

Violation	Administrative penalty
Failure to issue a tax invoice or the alternative document when making a supply, within the period legally specified	AED 2,500 for each detected case
Failure to issue a tax credit note or the alternative document within the period legally specified	AED 2,500 for each detected case
Failure to comply with the conditions and procedures for issuing a tax invoice or tax credit note electronically	AED 2,500 for each detected case
Failure to display prices inclusive of tax	AED 5,000

Three points about this structure matter more than the headline figures, and each of them is widely misreported.

The unit of assessment is the "detected case", not the audit. A single inspection that identifies a systemic failure across many transactions is not a single AED 2,500 charge. Businesses issuing high invoice volumes therefore carry exposure proportional to the number of instances an inspection actually detects, which is what makes a systemic defect — a template missing the TRN, or a point-of-sale system that never issues tax invoices at all — materially more expensive than an isolated mistake.

The penalty attaches to failing to issue a compliant document within the specified period — not to each individual defective field. There is no separate penalty in the table for an invoice that is issued on time but omits a particular. That does not make field defects costless: a document that fails to carry the Article 59 particulars is exposed to challenge as not being a valid tax invoice, and it independently costs the recipient their input tax credit, which is usually the larger number. But the "AED 5,000 per non-compliant invoice" figure that circulates widely in UAE invoice guidance does not correspond to anything in the penalty table.

The prices-inclusive-of-tax penalty is a flat AED 5,000 with no first-offense or repeat tier. Guidance describing an escalation from AED 15,000 to AED 50,000 for this violation is out of date on the first figure and appears to have imported the second from an unrelated row — the AED 50,000 in Table No. 3 belongs to the designated zone violation, where the penalty is the higher of AED 50,000 or 50% of the tax chargeable on the goods concerned.

E-Invoicing Carries Its Own Penalty Regime

Separately from the VAT penalty table, Cabinet Decision No. 106 of 2025 established penalties specific to the electronic invoicing system:

Violation	Penalty
Failure to implement the e-invoicing system, or to appoint an accredited service provider, by the applicable deadline	AED 5,000 per month
Failure to issue or transmit an invoice or credit note in the required electronic format	AED 100 per document, capped at AED 5,000 per month per category
Failure to notify the FTA of system failures, or of changes to registration details	AED 1,000 per day

One feature of this regime is worth planning around: businesses that adopt e-invoicing voluntarily, ahead of their mandatory deadline, are not exposed to these penalties. Early adoption is therefore a low-risk way to test systems — with the significant caveat covered earlier that voluntary adoption also triggers Article 59(16) and ends your ability to issue simplified tax invoices.

Beyond fines, VAT-registered businesses must retain tax invoices and related records for at least five years after the end of the relevant tax period. Businesses subject to UAE corporate tax face longer retention obligations of seven years. Records must be capable of being produced within the period the FTA specifies when it makes a request — the Authority sets that deadline case by case rather than applying a fixed turnaround, and retention periods can extend further where a dispute, an audit, or a notified intention to audit is in play. An audit can reach back across that entire window, which means non-compliant invoices issued years ago still carry penalty exposure today.

The tables above cover invoice-specific violations only. Cabinet Decision No. 40 of 2017 addresses additional VAT violations — late filing, late payment, registration failures — not dealt with here.

---

Preparing for the UAE E-Invoicing Mandate

This is no longer a future planning exercise. The pilot phase commenced on 1 July 2026, and voluntary implementation opened on the same date. For the largest category of businesses the live compliance question is no longer whether to prepare but whether an accredited service provider will be appointed in time, because that deadline — 30 October 2026 — is the nearest one in the entire framework, and it arrives before any obligation to actually issue an electronic invoice.

The timeline sits in Ministerial Decision No. 244 of 2025, as amended by Ministerial Decision No. 66 of 2026. The amendment, issued in May 2026, extended the service-provider appointment deadline for the first category from 31 July to 30 October 2026 on market-readiness grounds — but it did not move the go-live dates. The compression is real: the extra three months to appoint a provider come out of the implementation window, not out of the deadline.

Category	Appoint service provider by	Implement e-invoicing by
Revenue of AED 50,000,000 or more	30 October 2026	1 January 2027
Revenue below AED 50,000,000	31 March 2027	1 July 2027
Government entities	31 March 2027	1 October 2027

Note that if you are reading published guidance elsewhere that gives 31 July 2026 as the appointment deadline, it predates the amendment. Some official material still carries the superseded date.

Who is in scope. Wider than many businesses assume. The mandate covers B2B and B2G transactions and applies to any person conducting business in the UAE regardless of VAT-registration status — so being below the VAT registration threshold does not exempt you. B2C transactions are outside scope for now, pending a further ministerial decision. There are targeted exclusions, including sovereign government activities, international passenger air transport, and certain VAT-exempt and zero-rated financial services. Transactions within a VAT group have a 24-month grace period from 1 January 2027, which affects timing only and not whether the group is in scope. For the full rollout schedule, appointment deadlines, and penalty framework, see the dedicated UAE e-invoicing mandate timeline and compliance guide.

How it works. The UAE has adopted a five-corner decentralized continuous transaction control model built on Peppol. This is worth stating precisely, because it is often described as a reporting obligation, which understates it: invoices are exchanged between accredited service providers acting for each party, and the tax authority receives the data as a fifth corner in near real time. You do not upload invoices to a government portal, and you do not email PDFs — the document moves through the network in a structured format, and your service provider is a required participant rather than an optional convenience.

At the core of this transition is the PINT-AE format — the UAE's localized version of the Peppol International (PINT) standard, currently published as PINT AE Billing v1.0.4 (released 3 June 2026) under the specification identifier urn:peppol:pint:billing-1@ae-1. Peppol is the same interoperability framework being adopted by global e-invoicing mandates and standards across dozens of jurisdictions, from Europe to Asia-Pacific. By aligning with PINT rather than building a proprietary system, the UAE is positioning its e-invoicing infrastructure for cross-border compatibility from day one.

The mandatory data elements are specified by the Ministry of Finance rather than the FTA, in its UAE Electronic Invoice Mandatory Fields document dated 23 February 2026: 51 mandatory elements for an electronic tax invoice, organized into six categories covering invoice details, seller, buyer, document totals, tax breakdown, and invoice lines. A commercial electronic invoice has a shorter list of 49. Two practical constraints follow from the specification: taxpayers may not add custom fields to PINT-AE, so any bespoke data your current invoices carry needs another home; and your network participant identifier is scheme 0235 followed by a 10-digit TIN, which is the first 10 digits of your 15-digit corporate tax registration number. Members of a tax group use their own registration number for this purpose, not the group representative's.

What changes — and what does not. Every mandatory field on a current UAE paper or PDF tax invoice has a direct structural equivalent in the PINT-AE XML schema, so if your invoices already contain every field covered in this guide — supplier and recipient details, TRNs, line-item breakdowns, VAT amounts at each rate, and sequential numbering — you are capturing the right information. Much of the shift is in how that information is delivered: from human-readable documents to machine-readable structured data transmitted through the network.

But it would be wrong to describe this as purely a delivery change, and this is where Article 59(16) becomes the most important provision in the entire framework for anyone entering scope. As set out earlier in this guide, once you are required to issue electronic invoices — or once you choose to do so voluntarily — clauses 2, 3, 5, 7, 8, and 15 of Article 59 stop applying to you. In concrete terms:

• Simplified tax invoices cease to be available to you. Every invoice you issue must carry the full Article 59(1) particulars, including the recipient's name, address, and TRN where they are registered, and line-level unit prices and tax rates. For a business currently issuing high volumes of simplified invoices, this is the single largest operational change in the transition — considerably larger than the file format.
• The AED 10,000 threshold becomes irrelevant to you, because the clause that contains it no longer applies.
• The exemption from issuing an invoice for wholly zero-rated supplies disappears. Where you currently rely on having sufficient records instead of issuing a document, you will need to issue one.
• Any FTA waiver of particulars you rely on falls away, as does the general permission to issue invoices electronically on your own terms — the e-invoicing system's rules replace it.

The sequencing implication is worth being explicit about: the field-capture work and the invoice-type work are two separate projects. Adding data elements to your invoice template is the easy half. Redesigning a retail or point-of-sale process that has always issued simplified invoices, so that it collects and prints registered customer details on every transaction, is the half that needs lead time.

That said, several fields take on heightened importance once invoices become electronic:

• Sequential invoice numbers transition from a printed reference to a machine-readable unique identifier. Any gaps, duplicates, or inconsistencies that might pass unnoticed on paper will be flagged automatically in a structured system.
• Tax Registration Numbers will be validated in real time against the FTA registry. Incorrect or expired TRNs that currently require manual verification will trigger immediate rejection at the point of submission.
• VAT calculations must be precise to the fils (the smallest denomination) with zero rounding ambiguity. The PINT-AE schema enforces mathematical consistency between line-item amounts, tax rates, and invoice totals — discrepancies that a human reviewer might overlook will fail automated validation.
• Date of supply may become a mandatory XML element even when it matches the date of issue. Current paper and PDF practice allows you to omit the date of supply when both dates are the same, but a structured schema typically requires explicit values in both fields.
• Line-item descriptions move from free-text fields to structured data elements. Vague entries like "professional services — March" will need to map to defined categories with quantities, unit prices, and applicable tax rates explicitly broken out.

Practical Steps to Prepare Now

If your revenue is AED 50 million or above, the appointment deadline is the immediate constraint and the sequence below should be compressed accordingly. For everyone else there is more room, but the work is the same:

1. Appoint an accredited service provider. For the first category this is a hard deadline of 30 October 2026, not a planning item — the Ministry of Finance publishes the list of accredited providers, and the pool of implementation capacity is finite as deadlines converge. Confirm which category you fall into before anything else.
2. Establish whether you will lose simplified invoices, and if so, scope that change first. If any material share of your current invoicing uses the simplified format, the process redesign is your critical path — not the schema mapping.
3. Audit your invoices against the required field checklists covered in earlier sections of this article. Identify any fields you routinely omit or abbreviate — those are your highest-risk gaps. Check the Article 59(1)(k) exchange rate and the 59(1)(l) reverse charge statement specifically, since both are commonly absent.
4. Verify TRN accuracy for every supplier and customer in your records, and identify your own 10-digit TIN as derived from your corporate tax registration number. Cross-check active registrations against the FTA's verification tool before the automated system does it for you.
5. Standardize your date formats across all invoice templates. The PINT-AE schema expects ISO 8601 formatting (YYYY-MM-DD), so adopting it now avoids conversion issues later.
6. Talk to your accounting software or ERP provider about their PINT-AE readiness timeline, referencing v1.0.4 specifically. Ask whether their support will be a core update or a paid add-on module, whether they integrate with your chosen service provider, and how they handle the custom fields you use today, given that PINT-AE does not permit taxpayer-defined additions.
7. Review your line-item practices. Start structuring descriptions with discrete quantities, unit prices, and tax breakdowns rather than lump-sum entries. This habit change is the one most likely to require staff retraining.

Businesses that treat the current required field standards as their baseline — rather than a ceiling — will find the transition to electronic invoicing far less disruptive as their own deadline arrives.