FTA Compliant Invoice: What a UAE Tax Invoice Must Contain

An FTA compliant invoice is a tax invoice that carries every particular listed in Article 59 of Cabinet Decision 52 of 2017 (the VAT Executive Regulation, as amended). For a full tax invoice, that means the words "Tax Invoice", supplier and recipient details, a unique number, dates, line-by-line pricing, VAT in AED, and a reverse charge statement where it applies. If you are building your own invoicing, a missing field is a compliance gap, not a cosmetic issue.

This guide lists each field, shows where businesses slip, and gives a build checklist. Article 59 has been amended, so read the current text on tax.gov.ae before you finalise anything.

What must a full tax invoice contain under Article 59?

A full tax invoice must contain all of the particulars in Article 59(1). The regulation says a tax invoice "shall contain all of the following particulars", so partial compliance does not count. The official regulation on tax.gov.ae lists these items:

Two points matter for software. First, items (f), (i) and (l) are conditional. Your system needs fields for them and logic that prints them when they apply. Second, item (h) works per line, so the data model must store unit price, quantity and VAT rate on every line.

What is a simplified tax invoice, and when can you use one?

A simplified tax invoice is a shorter document allowed in limited cases under Article 59(5). It carries fewer particulars than a full invoice. Article 59(2) requires:

• The words "Tax Invoice".
• The supplier's name, address and TRN.
• The date of issue.
• A description of the goods or services supplied.
• The total consideration and the tax amount charged.

FTA public clarification VATP006, as described by secondary sources, says a simplified invoice is optional where the recipient is not VAT-registered, or is registered and the consideration is small. Sources disagree on whether the AED 10,000 limit is "under" or "or less". Do not guess. Read Article 59(5) in the official PDF and the FTA clarification, then code the exact rule.

A simple approach is to default to a full tax invoice. Switch to the simplified format only when your finance team signs off on the rule.

When must you issue the invoice?

Secondary sources consistently say a tax invoice must be issued within 14 days of the date of supply. The primary text is Article 59(13) in the same PDF. We could not find a tax.gov.ae page that restates the 14-day rule in plain language, so check Article 59(13) yourself. At least one secondary source mentions exceptions to it.

The same secondary sources describe a summary invoice under Article 59(6). It lets you issue one tax invoice for several supplies to the same recipient in a calendar month. They say it must be issued within 14 days of the end of that month. If you offer this, build it as a separate invoice type and confirm the wording in the regulation first.

Say a Dubai trading company delivers to the same Abu Dhabi customer on 3, 12 and 25 March. It could issue three tax invoices, each within its own 14-day window. Or it could use a summary invoice for the month, if Article 59 allows it for those supplies. Your system must support whichever route you choose and show the right dates.

How do you handle foreign currency and zero-rated sales?

Show the amounts in AED, and record the exchange rate when you convert. Article 59(1)(h) and (j) require the amount payable per item and the gross amount in AED. Article 59(1)(k) requires the VAT amount in AED, plus the exchange rate applied where the currency was converted from a currency other than the dirham.

So an invoice raised in US dollars to an overseas buyer cannot show dollars alone. Store the rate, its source and the date, so you can show how the AED figures were reached.

Zero-rated supplies need care. Article 59(4) says a tax invoice is not required for a wholly zero-rated supply. The text in our research was cut off, so read the full wording and any exceptions in the PDF. Even where no tax invoice is required, you may still want to issue a commercial invoice for your own records.

How do you build an FTA compliant invoice into your own system?

Build the data model first and the PDF template second. Missing data is the usual cause of non-compliance, not bad layout. Follow these steps:

1. Capture seller data once. Store the legal name, address and TRN, and print them on every document.
2. Capture customer data. Add name, address and an optional TRN field. Mark whether the customer is VAT-registered.
3. Create a sequence rule. Use one unbroken numbering series, or another unique-number scheme that identifies the invoice and its order in a sequence. Block edits to issued numbers.
4. Store two dates. Keep the date of issue and the date of supply as separate fields. Print the supply date when it differs.
5. Model line items properly. Each line holds a description, unit price, quantity, VAT rate, discount and amount in AED.
6. Add currency logic. If the sale is not in AED, save the exchange rate and print the VAT amount in AED.
7. Add a reverse charge flag. When ticked, print the statement and the reference to the relevant Decree-Law provision.
8. Label the document type. Print "Tax Invoice" on full and simplified invoices.
9. Test with real cases. Run a discounted sale, a USD sale, a reverse charge sale and a mixed-rate invoice. Check each against the Article 59 table above.

If you do not have developers, a custom software build can scope these rules into your existing ERP or order system. Freight forwarders who invoice from job files can look at Freight Management, which covers inquiry to invoice. Check any tool against Article 59 before you rely on it.

What about the UAE e-invoicing system?

Article 59 is the field baseline today, but e-invoicing rules are changing. Ministerial Decision 244 of 2025 covers the implementation of the Electronic Invoicing System. The Ministry of Finance has also announced targeted amendments, including an extension of the ASP deadline.

We have not summarised the dates or scope here, because they can change. Read the decision and the announcement to see whether your business is in scope and when. If you are building invoicing now, keep your data fields structured so you can adapt later.

Common mistakes to check before go-live

• Printing "Invoice" instead of "Tax Invoice".
• Leaving out the customer TRN for a VAT-registered buyer.
• Using a plain running number that can be edited or duplicated.
• Showing only a line total with no unit price, quantity or VAT rate.
• Hiding discounts inside the price.
• Using a foreign currency total with no AED VAT amount or exchange rate.
• Treating secondary blog summaries as law. Check the regulation as amended.

This post is general information, not tax advice. For your own case, confirm with the FTA or a registered tax agent.