E-invoicing UAE setup — PEPPOL-ready, on time.

It's a national framework from the Ministry of Finance and the FTA that retires the PDF-and-email invoice. Instead, structured electronic invoices move through accredited Access Service Providers (ASPs) over the PEPPOL network using the PEPPOL PINT AE schema. Your invoice goes out as machine-readable XML, gets validated against the schema, travels between you and your buyer through your respective ASPs, and is reported to the FTA in near real time. B2B and B2G transactions are in scope; B2C follows a separate reporting route.

A valid UAE tax invoice carries a set of fields the VAT law spells out. The header has to show the words 'Tax Invoice'. You need the supplier's name, address and TRN, the customer's name and address (with TRN for B2B), a sequential invoice number, and both the date of issue and the date of supply. Every line shows a description, unit price, quantity, VAT rate and VAT amount, and the footer shows the gross amount payable in AED plus the exchange rate where a foreign currency is used. For supplies under AED 10,000 to unregistered customers, a simplified tax invoice is fine. Right now that invoice is still a PDF or paper. Under e-invoicing the same data fields move into the structured PEPPOL PINT AE schema — which is exactly why getting your template and master data right today makes the cutover so much cleaner later. We're happy to review your existing VAT invoice template against both the current FTA requirements and the PEPPOL format coming down the line.

A tax invoice is the document a VAT-registered supplier must issue for a taxable supply, and it's what lets your customer recover the input VAT they paid. Under UAE VAT law it has to carry a defined set of fields: the words 'Tax Invoice' clearly displayed, the supplier's name, address and TRN, the customer's name and address, a unique sequential invoice number, the date of issue and the date of supply, a description of the goods or services, the unit price, quantity and VAT rate per line, the VAT amount in AED, and the gross total payable. A simplified tax invoice — fewer fields — is allowed for supplies under AED 10,000 to unregistered customers. Get any mandatory field wrong and the FTA can treat the invoice as non-compliant, which is a problem both today on PDF invoices and later once the same data has to pass PEPPOL validation.

The FTA tax invoice format is set out in the VAT Executive Regulations, and the UAE invoice format is the same whether you issue on paper, PDF or, soon, structured PEPPOL XML. A full tax invoice format UAE businesses must follow includes: the header label 'Tax Invoice', supplier legal name, address and 15-digit TRN, buyer name and address (plus buyer TRN for B2B), a sequential invoice number, invoice date and date of supply, a line-by-line description with unit price, quantity, applicable VAT rate (standard 5%, zero-rated or exempt) and VAT amount, the total excluding VAT, the total VAT, and the gross amount in AED. Where you invoice in a foreign currency, the AED-equivalent VAT and the exchange rate used must both appear. We review your existing template against this format and flag anything missing before it becomes an audit or e-invoicing issue.

It rolls out in waves. The Ministry of Finance has signalled a first mandatory wave in mid-2026, with large taxpayers — those above defined revenue thresholds or in specific sectors — in scope first. Smaller businesses follow over the next 18 to 24 months. Voluntary pilot enrolment opens ahead of each wave and the FTA publishes the participant criteria. Dates and inclusion are confirmed sector by sector, so we track the schedule and flag your in-scope date as part of the readiness scan.

Usually not. Most major UAE platforms are building PEPPOL connectors or have already shipped them in other PEPPOL markets like Australia, Singapore and the EU — Zoho Books, QuickBooks Online, Odoo, SAP S/4HANA and Business One, Oracle NetSuite, Microsoft Dynamics Business Central, Sage, Tally. The readiness scan checks whether your vendor is bringing your current stack onto the UAE roadmap. Ripping it out and replacing it is the exception, and we'd only suggest it where the system is end-of-life or already failing you on other compliance.

Think of it as your accredited gateway for sending and receiving structured invoices across the PEPPOL network. You never connect to your customers directly — you connect to your ASP, they connect to your customers' ASPs, through the four-corner PEPPOL model (or the five-corner model in the UAE, where the FTA is the fifth corner). The invoice then moves with full delivery confirmation and FTA acknowledgement. The UAE PEPPOL Authority accredits the ASPs, and which one suits you comes down to ERP fit, transaction volume, geography and how you want to integrate.

On a Zoho Books or QuickBooks-grade setup with clean data, four to six weeks from readiness scan to live PEPPOL exchange. Mid-market ERPs like Odoo or Business Central run six to ten. Enterprise ERPs — SAP, Oracle, custom builds — are usually 12 to 20 weeks, and that time goes into master-data cleanup, integration testing and the change-management work finance, IT and sales all have to absorb. Start early, because FTA pilot enrolment alone takes several weeks of testing before they issue a production identifier.

PEPPOL PINT AE wants more structure than a typical PDF carries — buyer and seller TRN, buyer Participant ID, payee details, delivery address, item classification codes and unit-of-measure codes from a controlled list, plus tax category codes (standard-rated, zero-rated, exempt, out-of-scope, reverse-charge), a VAT breakdown by category, payment terms and reference numbers. Here's the good news: most ERPs already hold this data. The work is enrichment, mainly tidying up customer TRNs, item codes and unit-of-measure consistency.

Once structured invoices are flowing through PEPPOL with FTA acknowledgement, the VAT-201 return becomes substantially easier to prepare. Output VAT is captured at the invoice level with full traceability to the FTA's records. Input VAT recovery is supported by structured supplier invoices with verified TRNs. Reverse-charge entries on imported services are flagged at source. The first VAT-201 after go-live is the most important one to review carefully. Any data-mapping issues in the PEPPOL setup will surface in that reconciliation. We plan the cutover to start at the beginning of a tax period for exactly that reason.

Yes. All UAE entities are in scope for e-invoicing under the same framework as mainland businesses. That includes mainland licensees, designated-zone companies and non-designated free-zone companies. The PEPPOL PINT AE schema and the FTA acknowledgement flow are the same. The waves are determined by FTA-published criteria (typically revenue thresholds and activity codes), not by entity type. We confirm your specific in-scope date as part of the readiness scan.

A failed PEPPOL invoice is rejected by the ASP before it reaches the buyer — your customer never sees a non-compliant invoice. Common failure causes are missing or invalid TRN, missing item classification, unit-of-measure mismatch, incorrect tax category or malformed XML. The rejection message identifies the failing field so it can be corrected; the corrected invoice is re-submitted through the ASP. The risk is operational, not regulatory — the FTA only sees successfully exchanged invoices — but unresolved rejections delay receivables and create reconciliation noise. We design the rollback contingency so the AR team can issue a manual invoice in the rare cases where PEPPOL exchange is unavailable.

For a full tax invoice: the words 'Tax Invoice', supplier name, address and TRN, customer details with TRN where registered, a sequential number, issue and supply dates, per-line description, quantity, unit price, taxable amount and VAT rate, the total VAT in AED with any exchange rate used, and the gross total. A simplified tax invoice — allowed for unregistered customers or supplies of AED 10,000 or less — needs the supplier details, date, description, and VAT-inclusive total. Our free tax invoice generator produces both formats correctly.

Scope and fields. The simplified tax invoice exists for retail-scale transactions — unregistered customers or consideration up to AED 10,000 — and omits customer details and line-level VAT breakdowns. The full tax invoice is mandatory for B2B supplies to registered customers and larger transactions, and it is the document the customer's input VAT claim legally depends on. Issuing a simplified invoice where a full one was required is a compliance failure on your side that surfaces in the customer's FTA audit.

In phases, under the Ministerial Decisions issued in 2025: businesses with revenue of AED 50 million or more must appoint an accredited service provider by 31 July 2026 and issue e-invoices from 1 January 2027; smaller businesses follow with ASP appointment by 31 March 2027 and go-live from 1 July 2027; government entities complete the rollout from 1 October 2027. A pilot is running through 2026 and voluntary adoption is open — dates should be confirmed against the MoF's e-invoicing programme page as the rollout progresses.

The licensed intermediary every UAE business will transmit e-invoices through — accredited by the Ministry of Finance, connected to the Peppol network, and responsible for validating, exchanging and reporting your invoice data to the central platform. You contract with one ASP; your customers and suppliers each have their own. Choosing an ASP whose connectors actually fit your accounting software is the selection criterion that matters most, and it's the comparison we run in setup engagements.

PINT AE is the UAE localisation of the international Peppol invoice format — the data dictionary defining exactly which fields a UAE e-invoice carries. The five-corner model is the delivery architecture: supplier (1) to supplier's ASP (2) to buyer's ASP (3) to buyer (4), with both providers reporting the data to the FTA's central platform (5) in near real time. Together they replace PDF-and-email invoicing with structured, validated, continuously reported exchange.

The announced mandate covers B2B and B2G transactions first; consumer-facing invoicing continues under the existing VAT invoice rules, with B2C phases signalled for later consideration. Retailers aren't off the hook though — a shop that also supplies registered businesses (wholesale lines, corporate accounts) has in-scope invoices from day one of its tier, and the accounting system needs to route the two flows correctly. That routing design is part of our readiness work.

Three things, in order: clean your master data (customer TRNs, addresses, item descriptions — the fields PINT AE validates), confirm your accounting software's e-invoicing path (native ASP connector, middleware, or migration), and fix your current tax invoice format so the transition starts from compliance rather than catch-up. If your revenue is near or above AED 50 million, ASP selection is already urgent given the July 2026 appointment deadline. We run all three as a fixed-scope readiness engagement.

Yes — electronic credit notes travel the same five-corner rails as invoices, carrying the same structured fields plus the reference to the original invoice they adjust. That reference discipline is stricter than most UAE businesses' current practice, where credit notes are often issued loosely. Getting the credit-note workflow right — sequential numbering, original-invoice linkage, VAT adjustment in the correct period — is part of the format work we fix before go-live.