United Arab Emirates
E-invoicing in the UAE (PINT AE)
Each page here is a field, a rule or a concept, written from the authority’s own documents (checked on 4 November 2026) and the JooDax programs’ code, saying plainly what is built and what is not.
E-invoicing
BuiltUAE e-invoicing covers B2B and B2G only, not B2C: businesses with revenue of AED 50 million or more go live on 1 January 2027, the rest on 1 July 2027 and government entities on 1 October 2027, each through an accredited service provider (ASP) in PINT AE on Peppol, so the software never talks to the FTA. Built in phase 7: JooDax writes the PINT AE document from the Ministry's list (version 1.1, 28 October 2026) of 51 mandatory fields for a tax invoice and 49 for a commercial one, with type codes 380/381/480/81, the eight transaction-type flags and line amounts in AED, rejects what the provider would reject, and drops the file in a folder the provider's agent collects. Not built: the link to any provider's interface (the customer chooses and contracts the ASP), the official Schematron check, invoices in other currencies, document-level discounts and charges, credit-note reason codes other than VD, and tying the document to till invoices and customer records.
Sections
Concepts
- The five-corner model (DCTCE) behind UAE e-invoicingAn invoice never goes straight from seller to authority: it passes through the seller’s provider and the buyer’s provider, and each reports to the Federal Tax Authority.
- The accredited service provider (ASP): its role and how to choose oneEvery business in scope contracts one provider accredited by the Ministry of Finance to send, receive and report its invoices.
- PINT AE: the UAE specialisation of Peppol’s international model, and how it relates to EN 16931PINT AE is the UAE flavour of Peppol’s international billing model, adding UAE terms and rules; unlike the EU flavour, it does not claim conformance to EN 16931.
- Tax invoice and commercial invoice in the UAE systemThe tax invoice (380) is for supplies under VAT, the commercial invoice (480) for sales needing no tax invoice; each has its credit note and its own field list.
- The eight transaction type flags and what each one demandsAn eight-digit string in ProfileExecutionID declaring an invoice’s special cases, each with data that must come along.
- Predefined endpoints: 9900000097, 98 and 99Three fixed addresses written for the buyer when the document is not delivered over the network: deemed supply, buyer not in scope, and export outside Peppol.
- Credit notes in the UAE: the two types, the reasons and the referenceThere are no negative invoices in the UAE: every reduction or cancellation is a credit note (381 or 81) naming one of six reasons and pointing to the original invoice.
- Self-billing in the UAE systemThe buyer issues the tax invoice on the supplier’s behalf by agreement, under the VAT law’s conditions, with its own codes 389 and 261.
- Who UAE e-invoicing covers, and whenEveryone doing business in the UAE, VAT-registered or not, for B2B and B2G transactions; in phases starting 1 January 2027 for revenue of AED 50 million or more.
- TIN, TRN and the participant identifierThe TIN is ten digits, the first ten of the TRN, and builds the participant identifier 0235:TIN; the TRN is fifteen digits, for VAT.
- Tax categories on a UAE invoiceSix categories: standard 5%, zero rated, exempt, out of scope, reverse charge, and the margin-scheme category; each with its conditions in the rules.
- Dirham amounts and rounding on a UAE invoiceAn invoice may be in any currency, but each line’s VAT and amount payable are always given in dirhams; rounding is to two decimals.
- Keeping e-invoices in the UAEInvoices and their data are kept five years in most cases, seven for real estate, in a way that preserves integrity and allows production to the FTA on request.
- What JooDax hands over in the UAE: a PINT AE document in the ASP’s folderJooDax writes a PINT AE document from the Ministry’s field list, refuses it while a field is missing, then places it whole in a folder the ASP’s agent collects.
Timeline
| Date | Who |
|---|---|
| 1 July 2026 | Pilot programme (by written agreement) and voluntary adoption for anyone |
| 31 October 2026 | Last date to appoint an ASP: annual revenue of AED 50 million or more |
| 1 January 2027 | Mandatory start: revenue of AED 50 million or more |
| 1 January 2027 | Start of the 24-month grace period for transactions within a VAT group |
| 31 March 2027 | Last date to appoint an ASP: revenue below AED 50 million, and government entities |
| 1 July 2027 | Mandatory start: revenue below AED 50 million |
| 1 October 2027 | Mandatory start: government entities |
Fields
- IBT-001 · Invoice number
- IBT-002 · Invoice issue date
- IBT-003 · Invoice type code
- IBT-005 · Invoice currency code
- BTAE-02 · Invoice transaction type code
- IBT-009 · Payment due date
- IBT-023 · Business process type
- IBT-024 · Specification identifier
- IBT-081 · Payment means type code
- IBT-027 · Seller name
- IBT-034 · Seller electronic address
- IBT-034-1 · Seller electronic identifier (scheme)
- IBT-030 · Seller legal registration identifier
- BTAE-15 · Seller legal registration identifier type
- IBT-031 · Seller VAT identifier (TRN)
- IBT-031-1 · Seller tax scheme code
- IBT-032 · Seller tax registration identifier (TIN)
- IBT-035 · Seller address line 1
- IBT-037 · Seller city
- IBT-039 · Seller country subdivision
- IBT-040 · Seller country code
- IBT-044 · Buyer name
- IBT-049 · Buyer electronic address
- IBT-049-1 · Buyer electronic identifier (scheme)
- IBT-048 · Buyer VAT identifier (TRN)
- IBT-048-1 · Buyer tax scheme code
- IBT-047 · Buyer legal registration identifier
- BTAE-16 · Buyer legal registration identifier type
- IBT-050 · Buyer address line 1
- IBT-052 · Buyer city
- IBT-054 · Buyer country subdivision
- IBT-055 · Buyer country code
- IBT-106 · Sum of invoice line net amount
- IBT-109 · Invoice total amount without tax
- IBT-110 · Invoice total tax amount
- IBT-112 · Invoice total amount with tax
- IBT-115 · Amount due for payment
- IBT-116 · Tax category taxable amount
- IBT-117 · Tax category tax amount
- IBT-118 · Tax category code
- IBT-119 · Tax category rate
- IBT-126 · Invoice line identifier
- IBT-129 · Invoiced quantity
- IBT-130 · Unit of measure code
- IBT-131 · Invoice line net amount
- IBT-146 · Item net price
- IBT-147 · Item price discount
- IBT-148 · Item gross price
- IBT-149 · Item price base quantity
- IBT-151 · Invoiced item tax category code
- IBT-152 · Invoiced item tax rate
- BTAE-08 · VAT line amount in AED
- BTAE-10 · Invoice line amount in AED
- IBT-153 · Item name
- IBT-154 · Item description
- BTAE-07 · Unique identifier number (UUID)
- BTAE-03 · Credit note reason code
- IBT-025 · Preceding invoice reference
JooDax programs in United Arab Emirates
Sources
- UAE Electronic Invoice Mandatory Fields (vV 1.1) — Ministry of Finance, United Arab Emirates
- UAE Electronic Invoicing Guidelines (vV 2.0) — Ministry of Finance, United Arab Emirates
- eInvoicing (UAE Electronic Invoicing Guidelines – Official eInvoicing Guide) (vweb page; footer "updated 04/11/2026") — Ministry of Finance, United Arab Emirates
- eInvoicing Accredited Service Providers (ASPs) (vweb page; footer "updated 04/11/2026") — Ministry of Finance, United Arab Emirates
- Considerations for Selecting an Accredited Service Provider (vV 1.1) — Ministry of Finance, United Arab Emirates
- UAE eInvoicing Programme (introduction slides) (vOctober 2026 (from the file name)) — Ministry of Finance, United Arab Emirates
- PINT AE Billing version 1.0.4 (v1.0.4 (PDK 1.4.4, released 29 Jul 2026)) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE Billing 1.0.4 – specification text (BIS) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE Billing 1.0.4 – Invoice transaction, semantic model (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE Billing 1.0.4 – Invoice transaction, syntax binding (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE Billing 1.0.4 – Credit note transaction, syntax binding (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE Billing 1.0.4 – AE specific PINT rules (jurisdiction aligned rules) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- Release notes for PINT AE Billing (v1.0.0 to 1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE code list: Transaction type (AE-TransType) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE code list: Document name code, subset invoice type code (UNCL1001) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE code list: Document name code, subset credit note type code (UNCL1001) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE code list: Reasons for credit note (AE-CreditReason) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE code list: AE VAT category codes (AETaxCat) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE code list: Payment means codes used in AE (UNCL4461) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- UAE Tax Data Document version 1.0.4 (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- Peppol PINT BIS Billing version 1.1.3 (specification text) (v1.1.3) — OpenPeppol AISBL (docs.peppol.eu)
- EU PINT Billing V1.1.1 (v1.1.1) — OpenPeppol AISBL (docs.peppol.eu)
Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.