Corner 1 - Seller
You. Your ERP creates the invoice as PINT AE XML with all required fields, tax codes and totals.
The Ministry of Finance has confirmed a phased Peppol-based mandate. Here is a plain, non-hype guide for shop owners, distributors and contractors on what changes, what does not, and how to prepare your books and ERP without panic.
UAE B2B and B2G invoicing is moving from PDFs and emails to structured, machine-readable documents exchanged through accredited service providers.
The Ministry of Finance has confirmed that the UAE will adopt the Peppol 5-corner model for e-invoicing, with a phased rollout starting in 2026 and broader coverage during 2027. Under this model an invoice is no longer a PDF you attach to an email. It is a structured XML document, in the Peppol PINT AE format, that your ERP hands to an accredited service provider (ASP). The ASP validates it, sends it to the buyer's ASP, and reports the tax data to the Federal Tax Authority. Your customer receives the same invoice as structured data, ready to post into their own books. The rules focus on tax invoices, tax credit notes, and self-billed invoices for VAT-registered businesses. Simplified retail receipts and B2C sales in a shop are handled differently and are not the initial focus of the mandate. For a corner shop or a distributor, the change is real but limited: the invoices you already print for other businesses need to travel through a certified pipe, in a fixed format, with a known set of fields.
Peppol 5-corner adds a tax authority to the classic 4-corner exchange. Here is who does what.
You. Your ERP creates the invoice as PINT AE XML with all required fields, tax codes and totals.
Your accredited service provider validates the XML, signs it, and routes it to the buyer's ASP over the Peppol network.
The buyer's ASP receives, validates and delivers the invoice to their accounting system.
Your customer. They post the invoice straight from structured data, without retyping.
Tax data is reported to the Federal Tax Authority through the accredited network, in near real time.
You do not need to solve everything at once. Work through these steps in order.
Every e-invoice will carry your Tax Registration Number, English and Arabic legal name, and address. Fix any mismatches with the FTA record before you go live.
Each B2B customer needs a valid TRN, legal name and, ideally, a Peppol participant ID. Sweep your ledger and remove duplicates now, not during the cut-over.
Every line will need a UAE VAT category - 5% standard, zero-rated, exempt, or out-of-scope - plus a unit of measure from an accepted list. Standardise codes across branches.
Your billing software must be able to generate the required XML and connect to an ASP. If it cannot, plan the switch this year, not in the last quarter before your wave.
The Ministry publishes an ASP list. Ask your ERP vendor which ASPs they integrate with, and whether the connection is included or billed separately.
Well before your mandatory date, send real invoices to one friendly B2B customer end-to-end. Reconcile what they post against what you posted.
Print this and tick as you go. If most boxes are open, start now.
How a typical B2B sale changes for a Dubai trading company.
| Step | Today (PDF era) | After the mandate |
|---|---|---|
| Create invoice | Type in ERP, print PDF | Type in ERP, ERP builds PINT AE XML |
| Send to customer | Email PDF attachment | ERP hands XML to ASP, ASP routes it |
| Customer posting | Retype from PDF | Import structured data, one click |
| FTA visibility | Only via VAT201 quarterly | Near real time, through the ASP |
| Errors | Found weeks later, in reconciliation | Rejected at ASP validation, same day |
| Storage | PDF on email, print in file | XML retained in ERP and ASP archive |
The 5% VAT rate, the VAT201 return, the 5-year record retention rule and your right to keep your books on your own PC are all unchanged. The FTA does not require your ledger to live in any specific cloud. Offline-first ERPs remain fully compliant - the e-invoice simply travels through the ASP when connectivity is available, and can be queued locally when it is not.
Zeyto is engineered for the 2027 mandate on the same offline-first foundation you already use.
Most sales are B2C simplified receipts and stay simple. The handful of B2B invoices to hotels or offices are the ones that must go through an ASP. Plan the switch on that basis.
Excel cannot emit PINT AE XML. This is the group with the shortest runway - move to a real ERP this year.
Van invoices must still be issued in the field, often without signal. An offline-first ERP with an outbound queue is the safe pattern.
Progress bills and retention need careful tax-code mapping before you switch. Do a dry run on one project before rolling out.
Zeyto is one binary, one signed licence, and a local PostgreSQL database. It works offline today, and it is being prepared for the 2027 e-invoicing mandate on the same foundation.