Peppol e-invoicing in the UAE: how an invoice travels from your system to the buyer and the FTA
How does Peppol e-invoicing work in the UAE?
Every in-scope UAE business will soon send invoices over a network it has never configured, and most finance teams still cannot explain what happens between clicking send and the buyer’s ledger. That gap causes rejected documents, unreachable customers, and credit notes that fail validation, because the network applies strict rules on addressing, document types, and tax data before an invoice leaves your provider.
Peppol e-invoicing UAE rules mean that businesses exchange PINT AE documents between accredited access points under the Ministry of Finance framework, with tax data reported to the FTA in parallel. This guide follows one invoice across the network, explains the documents, addresses, and rules that apply, and gives you a test list to run before your deadline, with the role Wafeq plays in each step.
[Diagram: one UAE invoice travelling from the supplier’s system through the supplier’s provider and the buyer’s provider to the buyer, with a parallel tax data report to the FTA. To be designed.]
Peppol in the UAE at a glance
Peppol is the international network UAE e-invoices travel over, PINT AE is the UAE invoice format, and your accredited provider connects you to both. The table separates the five layers, so you can see which ones you manage and which your provider manages.
Layer | What it does | Who handles it | What you must do |
|---|---|---|---|
Network | Exchanges documents between accredited access points under shared rules | Your provider and the buyer’s provider | Appoint a provider before your deadline |
Format | Defines the data model: UBL 2.1 invoice and credit note with UAE extensions (PINT AE) | Your system and your provider | Supply complete, correct data |
Addressing | Identifies sender and receiver by the scheme 0235 and a 10-digit TIN | Your provider registers the ID | Keep your customers’ TINs accurate |
Tax reporting | Reports each document’s tax data to the FTA | Your provider | Reconcile e-invoices to VAT returns |
Governance | Sets the rules, accreditation, and penalties | Ministry of Finance and FTA | Meet the dates for your revenue band |
The dates and duties that sit on top of this are covered in the guide to UAE e-invoicing requirements. This article stays on the network itself.
Read also: UAE FTA e-invoicing: what your accounting system must support before the deadline
Who takes part in a Peppol e-invoice exchange in the UAE?
Five parties take part: the supplier, the supplier’s provider, the buyer’s provider, the buyer, and the FTA, which receives the tax data. The UAE calls these the five corners. Each corner has a different job, and a problem at any one of them stops the invoice.
Corner | Party | What it does |
|---|---|---|
1 | Supplier | Creates the invoice or credit note in its accounting system |
2 | Supplier’s Accredited Service Provider | Validates the document against PINT AE and sends it over Peppol |
3 | Buyer’s Accredited Service Provider | Receives and verifies the document, then passes it on |
4 | Buyer | Receives the structured document in its accounting or payables system |
5 | FTA | Receives the tax data of the exchange from the providers |
Both providers are Accredited Service Providers, which the Ministry of Finance accredits to operate as Peppol access points. The role is explained in what an Accredited Service Provider is and why e-invoicing is not legal without one
You can also check any provider on the Ministry of Finance list of accredited providers.
Why does the buyer’s provider matter?
The buyer must also be reachable on the network through its own provider, because your provider can only deliver to an address that is registered. That is why customer data quality affects your invoices as much as your own set-up.
A buyer that is in scope but not yet onboarded creates a practical problem for the supplier. Ask your provider how it treats documents for buyers it cannot reach, and agree what your team does in that case.
Get up to 30% Off Wafeq yearly packages
Enter your email to receive your exclusive discount code. New users only!
What does the FTA receive?
The FTA receives a Tax Data Document, a standard report of the invoice’s tax data that the invoice issuer and the receiver both report. OpenPeppol publishes the UAE Tax Data Document specification alongside the invoice formats.
This is part of the exchange that gives the FTA visibility without a central clearance step. The invoice goes to the buyer in parallel, not after approval.
How does this differ from clearance models?
In the UAE, an invoice reaches the buyer without waiting for approval, whereas Saudi Arabia’s Fatoora clears B2B invoices before delivery. Many businesses operate in both countries, so it helps to keep the two models apart in your processes.
Question | UAE (Peppol, decentralized) | Saudi Arabia (Fatoora, clearance) |
|---|---|---|
Who receives the invoice first? | The buyer, through the buyer’s provider | The authority’s platform, which clears B2B invoices |
How does the authority see the data? | Providers report the tax data in parallel | Through the clearance step |
How is the buyer addressed? | 0235 plus the 10-digit TIN | Through the invoice data and the authority’s rules |
Who connects you? | An Accredited Service Provider | Your system integrates with the authority’s platform |
Read also: How to choose a UAE FTA Accredited Service Provider: the questions every business must ask
Which documents travel over the Peppol network in the UAE?
UAE e-invoicing uses three specifications: PINT AE Billing, PINT AE Self-Billing, and the Tax Data Document for reporting to the FTA. OpenPeppol published version 1.0.4 of all three on 29 July 2026. Check for newer versions, because the Ministry of Finance can update them.
The PINT AE Billing specification covers invoices and credit notes. The PINT AE Self-Billing specification covers invoices that a recipient issues on behalf of the supplier, with the same data model. The UAE Tax Data Document specification covers the report to the tax authorities.
Document | Type code | Used for |
|---|---|---|
Tax invoice | 380 | A standard UAE tax invoice |
Tax credit note | 381 | Reversing or reducing a tax invoice |
Self-billing invoice | 389 | An invoice issued by the recipient on behalf of the supplier |
Self-billing credit note | 261 | A credit note issued by the recipient under self-billing |
Invoice out of scope of tax | 480 | A commercial invoice outside the scope of VAT |
Credit note out of scope of tax | 81 | A credit note related to an out-of-scope transaction |
Why can’t you issue a negative invoice?
UAE rules allow reversal only through a credit note, so negative invoices are not allowed, and every credit note needs a reason code. A credit note must also reference the original invoice, except for volume discounts, which use the reason code VD.
That is why a reported invoice cannot simply be edited. The correction route is a credit note, followed by a new invoice if needed. Your system should make the reason code and the preceding invoice reference mandatory fields when staff create a credit note.
What are the special transaction types?
An eight-position transaction type code flags free zone, deemed supply, profit margin scheme, summary invoice, continuous supply, agent billing, e-commerce, and export transactions. Each position is 1 if the special type applies and 0 if it does not, so a standard invoice carries 00000000.
- Position 1: free trade zone, so a free zone transaction is 10000000.
- Position 2: deemed supply.
- Position 3: profit margin scheme.
- Position 4: summary invoice.
- Position 5: continuous supply.
- Position 6: disclosed agent billing.
- Position 7: supply through e-commerce.
- Position 8: exports, so an export transaction is 00000001.
Read also: 3 costly mistakes UAE businesses make when preparing for e-invoicing
How does addressing work: participant IDs and special endpoints?
Every UAE participant is addressed as 0235 followed by its 10-digit TIN, and three predefined endpoints cover buyers that cannot receive documents on the network. The scheme 0235 is the same for every UAE business, and the TIN is the first ten digits of the 15-digit TRN.
An invoice carries both numbers. The seller’s and buyer’s VAT registration number, the TRN, identifies the taxpayer for VAT. The TIN is the electronic address that routes the document. Mixing them up is a common cause of failure, so validate the numbers you hold using the steps in how to validate TRNs in the UAE.
Predefined endpoint | When to use it | What happens |
|---|---|---|
0235:9900000097 | The invoice is a deemed supply | Reported to the FTA only, not exchanged with the buyer’s provider |
0235:9900000098 | The buyer is not subject to UAE e-invoicing regulations | Reported to the FTA only |
0235:9900000099 | An export where the receiver is not registered on Peppol | Reported to the FTA only |
What if a customer is not on the network?
When the buyer is not subject to UAE e-invoicing regulations, use the predefined endpoint, and the document is reported to the FTA only. Typical cases are consumers, foreign customers on exports, and deemed supplies.
For an in-scope customer that has not registered yet, the position is different, because the document should reach the customer’s own provider. Agree with your provider how those documents are handled, and record the customer’s real participant ID as soon as it is available.
How should you store customer participant IDs?
Store each customer’s TRN and TIN in separate fields, validate both, and record the date you last checked them. Keeping them separate prevents the most common addressing error, which is using the full TRN as the endpoint.
For VAT groups, each member entity uses its own TIN, not the group representative’s, so keep a record for every legal entity you invoice. Review the records when a customer changes its legal name, address, or registration.
Read also: How to obtain your UAE Peppol participant ID
How does the network find and reach the buyer?
Peppol finds the buyer’s access point through a lookup of the buyer’s identifier, then delivers the document securely between the two access points. This is the part of the network your provider handles for you. Knowing it helps you ask better questions.
In Peppol’s standard design, participants are registered in a directory that lists the documents each can receive, where to deliver them, and access points exchange documents using a secure messaging protocol called AS4. OpenPeppol governs the rules and certifies access points under a service provider agreement. The Peppol interoperability framework describes the model, and the UAE applies it with PINT AE and the five-corner flow.
Where does your own system fit in?
Your system creates the invoice data and hands it to your provider, which does the addressing, validation, and transmission on your behalf. How the hand-off works, for example, by API, depends on your provider and your accounting software.
- Ask how your system passes documents to the provider and how errors are returned.
- Ask how failed transmissions are retried and who is alerted.
- Ask how incidents are reported, since you must notify the FTA of a system failure within two business days.
Read also: How to implement e-invoicing in the UAE: finalized framework, integration, validation and reporting
Which validation rules apply before an invoice is sent?
Your provider checks each document against the PINT AE rules before sending, covering identifiers, tax categories, AED amounts, and calculations. A document that fails is rejected and must be fixed before it can be delivered. The table lists the main rule areas from the specification.
Rule area | What it requires | Typical failure |
|---|---|---|
Profile identifiers | Customization ID urn:peppol:pint:billing-1@ae-1 and profile ID urn:peppol:bis:billing | Missing or wrong identifiers, usually set by the provider |
Parties | Seller and buyer registration identifiers with a type (trade licence, Emirates ID, passport, or Cabinet decision), the TRN, the TIN, and the 0235 electronic address | The full TRN used as the endpoint |
Tax categories | Category codes S, E, O, Z, and AE, with a rate for every category except E and O; the tax amount for AE is zero | A reverse charge line that still carries tax |
AED amounts | VAT line amount, amount payable, and total with VAT stated in AED, whatever the invoice currency | AED values missing on foreign-currency invoices |
Calculations | Totals must follow the specification’s formulas, with two decimals for the main amounts | Rounding differences |
Credit notes | Codes 381 or 81, a reason code, and a reference to the preceding invoice | A credit note without a reason code |
Attachments | Supporting documents are allowed; a PDF copy of the invoice itself is not | Attaching the PDF invoice as a file |
The rules are set out in the PINT AE business interoperability specification, and your provider enforces them, so most failures are data problems at source.
Why do foreign-currency invoices fail?
Foreign-currency invoices fail when VAT is not also stated in AED, because the specification requires AED tax amounts regardless of the invoice currency. The AED values must also reconcile with the exchange rate used on the date of supply.
Check that your system stores the exchange rate, calculates VAT in AED, and sends both values. This is one of the first things to test, because many exporters and importers invoice in dollars or euros.
Read also: VAT invoice requirements in the UAE
Which Peppol tests should you run before your deadline?
Run ten scenarios in the pilot or voluntary window, from a normal invoice and credit note to exports, free zone supplies, rejections, and outages. Each test takes minutes and catches problems that would otherwise appear on a live invoice. Use real customers’ data, anonymized if needed.
No. | Test | What to check | Expected result |
|---|---|---|---|
1 | Normal tax invoice | Mandatory fields, TRN and TIN, 0235 address | Accepted and delivered |
2 | Credit note | Code 381, reason code, preceding invoice reference | Accepted and linked to the invoice |
3 | Export to a customer outside the network | Transaction type flag and predefined endpoint 0235:9900000099 | Reported to the FTA only |
4 | Deemed supply | Flag and endpoint 0235:9900000097 | Reported to the FTA only |
5 | Free zone transaction | Free zone transaction type flag | Accepted with the right VAT treatment |
6 | Foreign-currency invoice | VAT and totals stated in AED | Accepted; AED values reconcile |
7 | Reverse charge line | Category AE with zero tax amount | Accepted |
8 | Received e-invoice | Document arrives as structured data and posts to payables | Posted without re-keying |
9 | Rejected document | How the rejection reason is shown and who fixes it | Reason visible; fix and resend works |
10 | Provider outage | Alerts, retries, and the two-business-day FTA notice | Incident procedure followed |
Smaller businesses can start with tests 1, 2, 6, and 8, and use the e-invoicing readiness checklist for SMEs for the wider preparation plan.
How should you record test evidence?
Keep a dated test log with the scenario, document reference, result, and tester, because it doubles as compliance evidence. Save a screenshot that shows the final status of each document, and note who fixed any rejection.
Repeat the log when your provider updates its connection or when a specification version changes. A short, regular test is much cheaper than discovering a problem on a live invoice.
Read also: E-invoice management software in the UAE: what businesses need to know
How does Wafeq handle Peppol e-invoicing?
Wafeq is both your accounting system and your provider, so invoices are validated against PINT AE, sent over Peppol, and reported to the FTA. Wafeq FZ-LLC is an Accredited Service Provider on the Ministry of Finance list (ID 129932), and e-invoicing is included in the Starter, Plus, and Premium plans at no extra cost. You appoint Wafeq in EmaraTax by its ASP ID.
- Participant ID: Wafeq says your 0235 ID is generated from your validated FTA details as part of setup.
- Customer lookup: when you create a customer, you can look up its TIN or VAT number, verify the number with the FTA, and check whether it is on the Peppol network.
- Validation: documents are checked against the required data before they leave your ledger.
- Corrections: a reported invoice is locked, and voiding it creates a credit note, which matches the UAE rule on credit notes.
- Receiving: structured invoices from suppliers arrive for review and posting, without re-keying.
You can see how the flow looks in practice on Wafeq’s UAE e-invoicing page. Wafeq cannot test your customers’ readiness for you, so the scenarios in this guide are still worth running.
Read also: UAE e-invoicing penalties: what businesses need to know
Read also: UAE e-invoicing timeline: don’t miss your ASP deadline or go-live date
Peppol e-invoicing in the UAE becomes manageable once you see it as a short chain: your system creates a PINT AE document, your provider validates and sends it, the buyer’s provider delivers it, and the FTA receives the tax data. Most failures come from data you control, such as the wrong endpoint format, missing AED values, or a credit note without a reason.
Learn the document types and endpoints that apply to your sales, run the ten test scenarios in the pilot window, and give each failure type an owner. Then your Peppol exchange will run quietly in the background, which is how it should run.
FAQs about Peppol e-invoicing in the UAE
What is Peppol?
Peppol is an international network and set of specifications, governed by OpenPeppol, for exchanging electronic documents such as invoices between accredited access points. The UAE adopted it as the backbone of its e-invoicing system.
What is PINT AE?
PINT AE is the UAE version of the Peppol International invoice specification, built on UBL 2.1 with UAE-specific fields for VAT and free zones. OpenPeppol publishes it as PINT AE Billing and PINT AE Self-Billing.
Do I connect to Peppol myself?
No, you connect through an Accredited Service Provider, which operates as your access point and handles addressing, validation, and transmission. There is no direct self-registration route for UAE businesses.
Does the invoice wait for FTA approval before it reaches the buyer?
No, the UAE model is decentralized: the invoice goes to the buyer through the providers while the tax data is reported to the FTA. That differs from clearance models, where the authority approves each invoice first.
What is the format of a UAE Peppol ID?
The format is 0235 followed by the 10-digit TIN, which is the first ten digits of the 15-digit TRN. Do not use the full TRN as the endpoint.
Can I send a PDF with the invoice?
You can attach supporting documents, but attaching a PDF copy of the invoice itself does not comply with the PINT AE specification. A human-readable view can still be generated for people, but the structured document is the invoice.
Which version of the specification applies?
OpenPeppol’s UAE specifications were at version 1.0.4 when last released on 29 July 2026, so check for updates before you build or test. Your provider is responsible for implementing updates, and you should ask how it informs customers.
Does a VAT group share one Peppol ID?
No, each member entity has its own TIN and its own network address, so group finance teams need a record for every entity. Using the group representative’s TIN for a member is a common source of routing failures.
Do consumers receive Peppol invoices?
No. Business-to-consumer transactions aren't subject to the system for now, so consumer invoices do not travel over the network. Businesses that sell to consumers still receive supplier invoices over Peppol.
Ready to send your first Peppol invoice?
Ready to send your first Peppol invoice?
Wafeq is an Accredited Service Provider (ID 129932), so your Peppol ID, validation, delivery, and FTA reporting are handled, and e-invoicing is included in your plan at no cost. Run the test scenarios from this guide on your own invoices.
