ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

United Arab Emirates — MoF E-Billing System

The UAE introduced VAT in 2018, then announced in 2024 a national e-invoicing system in 5-corner based on PEPPOL PINT AE, with a phased rollout in 2026-2027. The model combines decentralised B2B exchange with real-time fiscal reporting to the Federal Tax Authority.

Regulatory timeline

  • 27 August 2017 — Federal Decree-Law 8/2017 on VAT. The founding VAT law in the UAE, in force on 1 January 2018 at a standard rate of 5 %.
  • 26 November 2017 — Cabinet Decision 52/2017. VAT Executive Regulations, defining invoicing obligations.
  • 1 January 2018 — VAT go-live. Mandatory VAT (5 %) invoicing for any business with turnover > AED 375,000.
  • 1 June 2023 — Corporate Tax. Introduction of corporate income tax (9 %), complicating reporting obligations and paving the way for e-invoicing.
  • 30 April 2024 — Official MoF E-Billing System announcement. The Ministry of Finance announces a national e-invoicing project in 5-corner on PEPPOL.
  • Q4 2024 — Public consultation. The MoF publishes draft PINT AE specifications and runs a consultation with vendors and federations.
  • 2025 — Pilot programme. Onboarding phase for Accredited Service Providers (ASP) and voluntary testing.
  • Mid-2026 — Planned Phase 1. Mandatory go-live for large enterprises (> AED 50 M turnover), with progress reporting expected Q2 2026.

Technical schema

The format is PINT AE, the Emirati profile of the PEPPOL International (PINT) specification based on UBL 2.1. Features:

  • CustomizationID: urn:peppol:pint:billing-1@ae-1 — current version of the UAE profile.
  • EndpointID schemeID: 0235 for the 15-digit Emirati TRN (Tax Registration Number).
  • DocumentCurrencyCode: AED for domestic transactions, multi-currency support for exports.
  • VAT: 5 % standard, 0 % for exports outside GCC and certain sectors (health, education), exemption for financial services and residential real estate.
  • Code Lists: UN/CEFACT codes for document types, ISO 4217 for currencies, ISO 3166-1 for countries. A UAE-specific code list (Emirate, Free Zone) is published by the FTA.

Minimal example of a PINT AE Invoice:

xmlpint-ae-invoice.xml
<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:CustomizationID>urn:peppol:pint:billing-1@ae-1</cbc:CustomizationID>
  <cbc:ProfileID>urn:peppol:bis:billing</cbc:ProfileID>
  <cbc:ID>AE-2026-00000142</cbc:ID>
  <cbc:IssueDate>2026-05-16</cbc:IssueDate>
  <cbc:DueDate>2026-06-15</cbc:DueDate>
  <cbc:InvoiceTypeCode>388</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>AED</cbc:DocumentCurrencyCode>
  <cbc:TaxCurrencyCode>AED</cbc:TaxCurrencyCode>
  <cac:AccountingSupplierParty>
    <cac:Party>
      <cbc:EndpointID schemeID="0235">100074024500003</cbc:EndpointID>
      <cac:PartyIdentification>
        <cbc:ID schemeID="0235">100074024500003</cbc:ID>
      </cac:PartyIdentification>
      <cac:PartyTaxScheme>
        <cbc:CompanyID>100074024500003</cbc:CompanyID>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:PartyTaxScheme>
      <cac:PartyLegalEntity>
        <cbc:RegistrationName>Ediverse Demo LLC</cbc:RegistrationName>
      </cac:PartyLegalEntity>
    </cac:Party>
  </cac:AccountingSupplierParty>
</Invoice>

Submission flow

The model is 5-corner DCTCE: B2B exchange follows the classical PEPPOL 4-corner pattern (supplier → sender ASP → receiver ASP → buyer), with a fifth corner for real-time fiscal reporting to the MoF national platform (which feeds the FTA for VAT enforcement).

textmof-ebilling-flow.txt
┌─────────────┐    ┌─────────────┐    ┌─────────────┐    ┌─────────────┐
│ AE supplier │───>│ Sender ASP  │───>│ Receiver ASP│───>│ AE customer │
│ (corner 1)  │    │ accredited  │    │ accredited  │    │ (corner 4)  │
│             │    │ (corner 2)  │    │ (corner 3)  │    │             │
└─────────────┘    └──────┬──────┘    └──────┬──────┘    └─────────────┘
                          │                  │
                          ▼                  ▼
                ┌──────────────────────────────────┐
                │ MoF / FTA Federal e-Invoicing    │  ← real-time reporting
                │ Platform (CTC reporting)         │     (5-corner model)
                └──────────────────────────────────┘

This design preserves channel-agnostic B2B usage (the buyer receives the invoice independent of fiscal control) while giving the FTA real-time visibility on taxable transactions, on the same PEPPOL PINT pattern already adopted by Malaysia, Australia and New Zealand.

Validation

Common pitfalls

  1. Pre-mandate: anticipate, don't wait. The mandate is not yet live in production (go-live planned mid-2026). Vendors who wait for the final order before starting their PINT AE integration risk being 3 to 6 months behind their early-adopter customers.
  2. 15-digit TRN ≠ VAT number. The Emirati TRN is the official 15-digit fiscal identifier (starts with 100). Don't confuse it with a trade-licence number or a free-zone code. The PEPPOL schemeID is 0235 for the TRN.
  3. Free Zones and outside-GCC. The UAE has 45+ Free Zones (DMCC, JAFZA, DIFC, ADGM…) with their own VAT regimes (0 %, exemption, domestic). The invoice must reflect the exact status; a mismatch between free-zone address and VAT rate triggers an FTA audit.
  4. Multi-currency and Central Bank rate. Invoices in USD or EUR are common (Dubai is a trading hub). AED conversion must use the UAE Central Bank rate (CBUAE) of the issue date, otherwise FTA reporting is wrong.
  5. Bilingual Arabic and English. Invoices for the public sector and many private buyers require a bilingual Arabic/English visual representation. PINT AE must carry both languages in Note and line descriptions, otherwise human rendering is contested.