UAE tax invoice checklist: full and simplified VAT invoices
Review the required information on UAE full and simplified VAT invoices, when the simplified format applies and why a PDF is not structured e-invoicing.
A usable UAE tax invoice must identify the supply and support the tax treatment, not merely show a logo, a total and the word “VAT.” Before checking its fields, establish which invoice rules apply. Article 59 of the current VAT Executive Regulation distinguishes full invoices, permitted simplified invoices and provisions relevant to structured eInvoices. Treating every receipt as the same document creates avoidable problems for both the issuer and the buyer.
For an issuer, the practical objective is a repeatable invoicing process with correct customer information and a controlled numbering sequence. For a buyer, it is a reliable evidence trail linking the document to the purchase, the supplier and any proposed input-tax recovery. Neither objective is achieved by checking only that the arithmetic adds up.
Start with the full-invoice checks
An ordinary full-invoice review should cover these information groups against Article 59 and the facts of the transaction:
| Information group | What to check |
|---|---|
| Supplier | Tax-invoice label, supplier name, address and TRN |
| Registered customer | Name, address and TRN where applicable |
| Document identity | Unique or sequential number, issue date and supply date if different |
| Supply | Meaningful description, quantities or volume, unit prices and rates |
| Amounts | Discounts, AED amounts, gross consideration and VAT |
| Special treatment | Exchange rate or reverse-charge statement where required |
Use the table as a review aid, with the regulation controlling the exact requirement. A description such as “services” may be too vague to connect a document to the actual purchase. A better internal review can ask which agreed work the invoice covers and whether its dates and amounts correspond to that agreement.
Do not repair a supplier’s invoice by editing its PDF and then retaining it as if it were the original. Ask the issuer to resolve missing or incorrect information through the appropriate process. Keep the original, the query and the corrected document connected so a reviewer understands why the evidence changed.
Work through an example before configuring a template
Consider an illustrative ordinary domestic standard-rated supply to a registered customer. The supplier provides ten units at AED 1,200 each, with no discount. The net value is AED 12,000; 5% VAT is AED 600; the gross amount is AED 12,600. Assume there is no reverse charge and no structured eInvoicing rule displacing the ordinary rules.
A reviewer should check more than the AED 600 calculation. Confirm that the supplier and customer details identify the correct legal persons, the invoice number is controlled, the description matches the goods, and any different supply date is recorded. If the invoice uses a foreign currency, assess the required AED tax amount and exchange-rate information rather than assuming a foreign-currency total is sufficient.
Now imagine the issuer accidentally uses the customer’s trading name while the TRN belongs to another entity in the group. The arithmetic remains correct, but the document needs investigation. The example shows why a template should draw from reviewed master data rather than freely copied text from a previous invoice.
Decide whether simplification is actually permitted
Under the ordinary Article 59 rules, a simplified invoice may be available where the recipient is unregistered, or where a registered recipient’s consideration for the supply does not exceed AED 10,000. Reverse-charge cases are excluded from this simplification. A simplified invoice still needs the tax-invoice label, supplier name/address/TRN, issue date, supply description, consideration and VAT charged in AED.
Compare two illustrative supplies to a registered recipient. An AED 8,400 gross supply can meet the ordinary value condition, while an AED 12,600 gross supply does not. The threshold concerns consideration; avoid treating it as a universal AED 10,000 VAT-exclusive allowance. The examples assume the other conditions are satisfied and that the ordinary simplification remains available for the transaction.
A card-machine slip with a payment amount alone is not made into a simplified tax invoice by calling it a receipt. Equally, a buyer should not reject every permitted simplified invoice merely because it omits fields required only on a full invoice. Identify the document type before deciding what is missing.
Check when the invoice was due
Document timing is a separate review from document content. The regulation generally provides fourteen days from the supply date for an ordinary full invoice. A simplified invoice is ordinarily issued on the supply date, while summary invoices have their own timing provisions. Establish the relevant date of supply and any special rule before calculating a deadline.
For an illustrative ordinary supply dated 10 November, the general fourteen-day rule points to 24 November. A simplified invoice for that supply would ordinarily be issued on 10 November. These are examples of the stated timing rules, not a conclusion that the payment date always establishes the date of supply. An advance, recurring service or other special transaction needs its own date analysis.
Operationally, capture the information when the supply occurs. Waiting until a customer requests an invoice can leave the finance team reconstructing descriptions, dates and tax treatment from incomplete messages. A queue of completed but uninvoiced supplies should therefore have an owner and a review schedule.
Build an exception workflow for received invoices
When reviewing purchases, identify the problem precisely: supplier details do not match, a TRN is missing where required, the amount differs from the agreement, or the document does not explain what was supplied. Give the supplier a specific correction request and retain the correspondence. Mark the proposed recovery as unresolved until the relevant issue is assessed.
The input-tax recovery guide explains why invoice completeness is one gate rather than the whole recovery decision. Business purpose, receipt of the supply, timing, restrictions and current verification requirements also matter. A perfectly formatted invoice cannot turn a private purchase into a supported business claim.
Finally, review the transition to structured eInvoicing separately. The Ministry of Finance portal describes structured invoice data and its exchange/reporting framework; a PDF, scan or emailed document alone is a different thing. Article 59 contains specific eInvoice provisions, so ordinary simplifications should not be carried across automatically. Use the e-invoicing timeline to plan the transition and test the applicable document requirements against the chosen implementation.
Sources checked on 26 October 2026. Examples are illustrative and assume the stated ordinary invoice conditions.