Peppol compared to how invoicing works today
| Email a PDF | Peppol | |
|---|---|---|
| What is sent | A document | Structured data |
| Format | Whatever you choose | A defined specification |
| Validation | None: errors found later | At the network, before delivery |
| Connection | Direct to the recipient | Via your provider and theirs |
| Must both parties use the same tool? | No | No |
| Delivery confirmation | Uncertain | Built in |
| Machine readable by the recipient | No: usually re-keyed | Yes |
| Rejection | Not a concept | A non-conforming document does not arrive |
The fifth row resolves most of the confusion we hear. Businesses assume they will need to coordinate with each customer about which system to use. They will not. That is precisely the problem an interoperable network exists to solve.
Why that is the answer
The design principle behind Peppol is interoperability, and the email analogy is genuinely useful for understanding it.
When you send an email you do not need to know what mail provider the recipient uses. You connect to yours, they connect to theirs, and an agreed set of standards handles the rest. Nobody negotiates a bilateral arrangement with each correspondent.
Peppol applies the same idea to business documents. Each participant connects to an access point (in the UAE, an accredited service provider) and documents route between access points according to the standard. This is why the model is sometimes described as four-corner: sender, sender’s access point, receiver’s access point, receiver. The UAE adds the tax authority as a fifth corner receiving the reported data.
The difference from email is that the content is structured and validated. An email will deliver almost anything. Peppol will not deliver a document that does not conform to the specification, which is the entire point, and also the thing businesses need to prepare for.
What interoperability means practically
Several consequences worth knowing before you plan:
- Provider choice is entirely your own decision: it depends on your integration, support and cost needs, not on what your customers use
- You do not need to onboard customers individually. A customer already on the network is reachable
- Your customers need not coordinate with you or grant permission to receive from you
- It is international. Peppol is used in a growing number of countries, so cross-border invoicing to other Peppol jurisdictions becomes simpler over time
- Your provider is replaceable in principle: migration is possible, which is why exit terms matter
- Participants are identified by a registered identifier, which is part of why customer master data accuracy matters so much
The fourth point is a genuine medium-term benefit that gets overlooked because it is not a compliance requirement. Businesses invoicing customers in other Peppol countries may find cross-border invoicing gets easier rather than harder.
Why the UAE adopted an existing network
The alternative would have been to build a national system from scratch, and several countries have done exactly that. The UAE did not, and the reasoning affects your vendor options.
An international standard means existing software vendors, existing accredited providers and existing implementation expertise. An ERP vendor that already supports Peppol for European or Asian markets has a substantial head start on UAE conformance, and your business benefits from that.
It also means the specification is maintained by an established body rather than developed independently, and that businesses operating in several Peppol jurisdictions face one model rather than several.
The UAE profile is a national adaptation rather than a separate system. That is the standard approach: a country-specific profile of a shared international specification, accommodating local tax requirements while remaining interoperable.
What the network does not do
Some boundaries, because the network gets credited with more than it does.
It does not clean your data. Peppol will deliver a conforming invoice with a wrong customer name perfectly well. Validation is against the specification, not against reality.
It does not determine tax treatment. Whether a supply is standard rated, zero rated or exempt is your determination, carried in the invoice rather than decided by it.
It does not replace your accounting system. Invoices are still raised in your system; the network transports them.
It does not archive for you. Retention remains your obligation, 5 years generally; 15 years for real estate records, and what your provider stores is a contract question.
It is not a payment network. An invoice delivered over Peppol is still paid however you and your customer arrange it.
How a document actually reaches your customer
Worth walking through once, because it demystifies the model and explains where things can go wrong:
- Your system produces the invoice data and passes it to your provider
- Your provider converts and validates it against the specification. A non-conforming document is rejected here, before it goes anywhere
- Your provider looks up the recipient by their registered identifier to find which access point serves them
- The document is transmitted to that access point over the network
- Your customer’s provider delivers it into their system as structured data, not as a document to re-key
- Delivery is confirmed back along the same path
- The tax data is reported to the authority as part of the exchange
The second and third steps are where most failures occur, and they fail for different reasons. Step two fails on your data quality, a missing tax registration number or a malformed field. Step three fails on the recipient identifier being wrong or absent, which is a customer master data problem rather than a technical one. Both are fixed before go-live or discovered after it.
What trips people up
- Assuming you and your customer need the same provider. You do not: that is the point of interoperability.
- Planning to onboard customers individually. Customers already on the network are reachable.
- Choosing a provider based on what a large customer uses rather than on your own integration needs.
- Expecting the network to validate your data against reality. It validates format only.
- Assuming it replaces your accounting system. Invoices are still raised in your system.
- Assuming archiving is handled. Retention remains your obligation.
- Treating it as a payment network. Delivery and payment are separate.
How to act on this
- Stop worrying about what your customers use: it does not affect your choice.
- Choose a provider on integration fit, support and cost.
- Check whether your software vendor already supports Peppol in other markets: a real head start.
- Focus on data quality, since the network validates format rather than accuracy.
- Clarify archiving in the provider contract.
Related questions
Frequently Asked Questions
What is Peppol?
An international network for exchanging business documents in a standard format. You connect once to your provider, your customer connects to theirs, and the network handles delivery, much as email works, but with structured, validated content.
Do our customers need the same provider as us?
No. That is precisely what an interoperable network is for. Your provider choice depends on your own integration, support and cost needs, not on what your customers use.
Do we need to onboard each customer?
No. A customer already on the network is reachable without any bilateral arrangement. You do not need their coordination or permission to send to them.
Is Peppol only used in the UAE?
No. It is used in a growing number of countries, which is part of why the UAE adopted it rather than building a national system. A software vendor already supporting Peppol elsewhere has a head start on UAE conformance.
What is the UAE profile?
A national adaptation of the shared international specification, accommodating UAE tax requirements while remaining interoperable. That is the standard approach rather than anything unusual, countries profile the specification rather than replacing it.
Does the network check our invoice is correct?
It validates against the specification, not against reality. A conforming invoice with the wrong customer name will deliver perfectly well. Data accuracy is your responsibility; format conformance is what the network enforces.
Does Peppol replace our accounting system?
No. Invoices are still raised in your system; the network transports them. What may need to change is whether your system can produce structured output in the required format and connect to a provider.
Is it a payment system?
No. An invoice delivered over Peppol is still paid however you and your customer arrange it. Delivery and payment are entirely separate.
Can we change providers later?
In principle yes, since the network is interoperable and your identifier travels with you. In practice migration takes effort, which is why exit terms and data portability are worth reading at contract stage rather than at migration.
If your vendor supports it in other markets, you have a real head start on UAE conformance. Tell us your system and version and we will check.
Check my compliance status 058 101 9570
Last reviewed 27 July 2026. Rates, thresholds and deadlines change, the e-invoicing provider deadline has already moved once. Confirm current requirements with the Federal Tax Authority before acting, or ask us to check your position.