TECHNICAL
How Peppol Works: A Plain English Guide for Finance Teams
Peppol is at the centre of the UAE’s mandatory e-invoicing system — but most finance professionals have never encountered it before. This guide explains exactly what it is, how it works step by step, and what it means for your team in practical terms. No technical background required.
reading time: 12 min
may 2026
aiverix research
If you have been asked to prepare your business for UAE e-invoicing compliance and the word "Peppol" keeps appearing in every document, every provider pitch, and every government publication — but nobody has explained what it actually means for your finance team — this article is for you. Peppol is not complicated once you understand what problem it is solving. And understanding it properly will help you ask better questions, make better decisions about your provider, and have more confidence in your organisation’s compliance plan.
Start Here: What Problem Does Peppol Solve?
Before Peppol, businesses that wanted to exchange invoices electronically faced a fragmented, expensive problem. Every buyer had different requirements. Some wanted invoices in one format, others in another. Some had portals you had to log into manually. Some required specific EDI connections that each cost thousands of dirhams to set up. If you had 50 major buyers, you could have 50 different invoice submission processes.
Peppol solves this by establishing a single agreed standard — one network, one set of rules — that all participants connect to once. Once you are connected, you can exchange invoices with any other business on the network, anywhere in the world, without needing a separate technical connection to each of them.
The best analogy is email. When email was invented, different organisations used incompatible messaging systems that could not talk to each other. The breakthrough was a shared protocol — SMTP — that let any email system communicate with any other. Peppol is the SMTP of business document exchange. Connect once, reach everyone.
Peppol solves this by establishing a single agreed standard — one network, one set of rules — that all participants connect to once. Once you are connected, you can exchange invoices with any other business on the network, anywhere in the world, without needing a separate technical connection to each of them.
The best analogy is email. When email was invented, different organisations used incompatible messaging systems that could not talk to each other. The breakthrough was a shared protocol — SMTP — that let any email system communicate with any other. Peppol is the SMTP of business document exchange. Connect once, reach everyone.
“
Peppol is not a software product. It is not a company you buy from. It is a globally agreed set of rules and a network infrastructure — like the internet, but built specifically for secure, structured business document exchange.
Where Peppol Came From — and Why the UAE Chose It
Peppol stands for Pan-European Public Procurement Online. It was created in the early 2010s by the European Union to solve a specific problem: government bodies across Europe could not easily receive invoices from suppliers electronically because every supplier used different systems. The EU standardised the exchange format and created a network of certified access points — licensed intermediaries that connect businesses to the network.
It worked. Private sector companies quickly adopted the same standard. Today, Peppol operates in more than 40 countries. Singapore made it mandatory for government invoicing in 2020. Australia and New Zealand adopted it for cross-border B2B transactions. Malaysia is rolling it out. And now the UAE has selected it as the foundation for its national e-invoicing system.
The UAE did not choose Peppol because it was new or experimental. It chose Peppol because it is the most thoroughly tested e-invoicing infrastructure in the world, with real production experience across dozens of different legal and technical environments. Every technical problem that can arise has already been encountered and solved in one of those markets.
It worked. Private sector companies quickly adopted the same standard. Today, Peppol operates in more than 40 countries. Singapore made it mandatory for government invoicing in 2020. Australia and New Zealand adopted it for cross-border B2B transactions. Malaysia is rolling it out. And now the UAE has selected it as the foundation for its national e-invoicing system.
The UAE did not choose Peppol because it was new or experimental. It chose Peppol because it is the most thoroughly tested e-invoicing infrastructure in the world, with real production experience across dozens of different legal and technical environments. Every technical problem that can arise has already been encountered and solved in one of those markets.
40+
Countries currently operating on the Peppol network
210S
Origin — over a decade of real-world production use
1
Connection required — then you can reach any business on the network
2026
UAE voluntary pilot opens — July 1
The UAE's 5-Corner Model: Each Step Explained
The UAE has adopted what is officially called the "5-Corner Model." The corners are not physical locations — they are the five participants involved in every single e-invoice transaction. Understanding who does what at each corner is the key to understanding the entire system.
Corner 1: Your Business
Generates invoice data in your ERP or accounting system.
Corner 2: Your ASP
Validates, converts to PINT AE XML, transmits via Peppol.
Corner 5: FTA
Receives tax data simultaneously — does not pre-approve.
Corner 3: Buyer's ASP
Receives valid invoice, delivers to buyer’s system.
Corner 4: Your Buyer
Receives structured XML invoice directly into their ERP.
Here is what happens at each corner in plain language:
-
Corner 1 — Your Business: Nothing Changes in How You Work
Your finance team continues to create invoices exactly as they do today — inside SAP, Oracle, MS Dynamics, Odoo, QuickBooks, Xero, Tally, or any other ERP or accounting system. You do not need to learn new software or change how you raise invoices. The data you already enter — invoice number, date, buyer details, line items, VAT amount — is exactly what the system needs. Corner 1 is simply your existing process. -
Corner 2 — Your ASP: Where the Compliance Work Happens
Your Accredited Service Provider (ASP) is the organisation you contract with to connect your business to the Peppol network. This is the most important corner from a compliance perspective — and the one your choice of provider directly controls. Your ASP does three things automatically: first, it validates your invoice data against the UAE’s technical rules (checking that all mandatory fields are present, all formats are correct, all tax numbers are valid). Second, it converts your data into PINT AE XML — the structured format the UAE mandates. Third, it transmits the invoice over the Peppol network, digitally signed, to both the FTA and your buyer simultaneously. Your finance team does not see any of this. It happens in the background, in seconds. -
Corner 5 — The FTA: Real-Time Tax Visibility, Not Pre-Approval
The FTA’s e-billing system receives a copy of every invoice’s tax data the moment it is transmitted. This is one of the most important design choices in the UAE’s system — and it is different from how Saudi Arabia’s ZATCA works. In Saudi Arabia, the government must approve each invoice before it reaches the buyer. This means your commercial transaction is delayed until ZATCA responds. The UAE system does not work this way. The FTA receives tax data simultaneously with your buyer — meaning your invoice arrives at your buyer instantly, with no government approval step in between. Once you are set up correctly, your commercial invoice cycle is not disrupted at all. -
Corner 3 — Your Buyer’s ASP: The Other Side of the Network
Your buyer also has an Accredited Service Provider — or will have one by the time the mandate is live. Their ASP receives the invoice from the Peppol network and delivers it directly into their accounting system in whatever format their system requires. This is the true power of the Peppol model: your buyer does not need to log into a portal, download a PDF, or manually re-enter data. The invoice appears in their system automatically. For finance teams on the receiving end of hundreds of supplier invoices per month, this is a significant reduction in manual processing work. -
Corner 4 — Your Buyer: Structured Data, Not a Document
What your buyer receives is not a PDF or a Word document. It is a structured XML file — meaning every piece of invoice data (date, supplier TRN, line items, VAT amount, payment terms) is in a defined, labelled field that their system can read automatically. This eliminates the manual data entry that paper and PDF invoices require, reduces errors, and speeds up payment processing. From your buyer’s perspective, the invoice is processed and matched against their purchase order automatically — no human involvement required in normal conditions.
What Is PINT AE — and Do You Need to Understand It?
Every piece of UAE e-invoicing documentation mentions PINT AE. Finance professionals often encounter this term and assume it is something they need to study. In practice, your finance team does not need to understand PINT AE at a technical level — your ASP handles it entirely. But knowing what it means helps you understand why the system works the way it does.
PINT AE stands for Peppol International Invoice — UAE. It is the specific XML data structure that the UAE has defined as the official invoice format. XML stands for Extensible Markup Language — a way of structuring data so that computers can read it automatically and unambiguously.
The difference between a PDF invoice and a PINT AE XML invoice is the difference between a photograph of a spreadsheet and the actual spreadsheet. A photograph contains the same visual information — but a computer cannot extract individual data fields from it automatically. The spreadsheet, by contrast, has each value in a defined location that any software can read, process, and validate instantly.
PINT AE stands for Peppol International Invoice — UAE. It is the specific XML data structure that the UAE has defined as the official invoice format. XML stands for Extensible Markup Language — a way of structuring data so that computers can read it automatically and unambiguously.
The difference between a PDF invoice and a PINT AE XML invoice is the difference between a photograph of a spreadsheet and the actual spreadsheet. A photograph contains the same visual information — but a computer cannot extract individual data fields from it automatically. The spreadsheet, by contrast, has each value in a defined location that any software can read, process, and validate instantly.
Your ASP — in Aiverix’s case — converts your ERP data into PINT AE format automatically. You do not need to change the way your team enters invoice data. The conversion and transmission happen invisibly, between your system and ours.
Your Peppol ID: What It Is and How You Use It
Every business that participates in the UAE’s Peppol network has a unique address on that network — called a Peppol Participant Identifier, or Peppol ID. This is how invoices know where to be delivered. When your ASP transmits an invoice, it looks up your buyer’s Peppol ID to route the document to the correct destination.
In the UAE, your Peppol ID is formed as follows: the prefix 0235: followed by the first ten digits of your Tax Registration Number (TRN). So if your TRN begins with 1 234 567 890, your Peppol ID is 0235:1 234 567 890.
Before you go live, there is one practical task your team needs to complete: collect the Peppol IDs of your major buyers. This is a data preparation step — you need to update your customer master records with each buyer’s Peppol ID so that invoices can be routed to the correct destination automatically.
In the UAE, your Peppol ID is formed as follows: the prefix 0235: followed by the first ten digits of your Tax Registration Number (TRN). So if your TRN begins with 1 234 567 890, your Peppol ID is 0235:1 234 567 890.
Before you go live, there is one practical task your team needs to complete: collect the Peppol IDs of your major buyers. This is a data preparation step — you need to update your customer master records with each buyer’s Peppol ID so that invoices can be routed to the correct destination automatically.
WHAT IF MY BUYER IS NOT ON PEPPOL YET?
Not every business will be registered on the Peppol network from day one of the mandate. If you transmit an invoice to a buyer who does not yet have a Peppol ID, your ASP routes the invoice to a predefined FTA endpoint. The buyer can still receive and view it through a government portal — but the fully automated delivery into their accounting system only happens once they are registered.
As adoption grows through 2027, the vast majority of your buyers will be on the network. In the meantime, your compliance obligation is met regardless — the invoice is transmitted correctly through your ASP to the FTA. The buyer registration gap is a practical inconvenience, not a compliance failure on your part.
Not every business will be registered on the Peppol network from day one of the mandate. If you transmit an invoice to a buyer who does not yet have a Peppol ID, your ASP routes the invoice to a predefined FTA endpoint. The buyer can still receive and view it through a government portal — but the fully automated delivery into their accounting system only happens once they are registered.
As adoption grows through 2027, the vast majority of your buyers will be on the network. In the meantime, your compliance obligation is met regardless — the invoice is transmitted correctly through your ASP to the FTA. The buyer registration gap is a practical inconvenience, not a compliance failure on your part.
How Peppol Differs from Saudi Arabia's ZATCA — and Why It Matters
Many UAE finance leaders are familiar with how Saudi Arabia’s e-invoicing mandate works, either because their business operates in Saudi Arabia or because they have read about ZATCA in the context of UAE compliance preparation. Understanding the differences between the two systems helps avoid incorrect assumptions about how the UAE mandate will affect daily operations.
The practical implication for UAE businesses is significant: once your Peppol integration is set up and working correctly, your day-to-day invoicing process is not materially disrupted. You raise an invoice in your ERP, your ASP handles the rest in the background, and your buyer receives a structured document in their system automatically. The disruption period is the implementation phase — not the live operation phase.
What Your Finance Team Actually Needs to Do
Now that you understand how Peppol works, here is the practical task list for your team. Notice that most of the technical work sits with your ASP — not with your internal staff.
Tasks for your finance team
Tasks handled entirely by your ASP
Your ASP handles everything technical — so your team does not need to become XML experts or learn how the Peppol network operates at an infrastructure level. Specifically, your ASP is responsible for: converting your invoice data into PINT AE XML format; digitally signing each invoice before transmission; routing invoices to the correct Peppol endpoints; transmitting tax data to the FTA; monitoring for validation errors and alerting your team; managing all regulatory updates as the FTA refines its requirements over time.
IN PRACTICE · WHAT GO-LIVE LOOKS LIKE
A Finance’s Team Perspective: Before and After
Before Peppol: Your accounts receivable team raises an invoice in your ERP, exports a PDF, attaches it to an email, sends it to your buyer’s AP inbox, and waits for confirmation. Someone at your buyer’s company manually checks the email, downloads the PDF, reads the invoice details, and re-enters the data into their accounting system. This process takes minutes per invoice and carries a roughly 10% manual data entry error rate across the industry.
After Peppol: Your accounts receivable team raises an invoice in your ERP exactly as before. In the background, your ASP validates the data, converts it to PINT AE XML, transmits it to the Peppol network, and confirms delivery — all in under ten seconds. Your buyer’s system receives the structured invoice data automatically. No email. No PDF. No manual data entry at either end.
The finance team’s experience of raising an invoice does not change. The compliance infrastructure runs invisibly behind the process they already know.
WHAT THIS MEANS FOR YOUR TEAM
The transition period — implementation, testing, data cleansing — requires focused attention from your finance and IT teams. Once you are live, the ongoing operational effort is minimal. The system runs in the background. Your team raises invoices as they always have. The compliance layer is managed by your ASP.
A Finance’s Team Perspective: Before and After
Before Peppol: Your accounts receivable team raises an invoice in your ERP, exports a PDF, attaches it to an email, sends it to your buyer’s AP inbox, and waits for confirmation. Someone at your buyer’s company manually checks the email, downloads the PDF, reads the invoice details, and re-enters the data into their accounting system. This process takes minutes per invoice and carries a roughly 10% manual data entry error rate across the industry.
After Peppol: Your accounts receivable team raises an invoice in your ERP exactly as before. In the background, your ASP validates the data, converts it to PINT AE XML, transmits it to the Peppol network, and confirms delivery — all in under ten seconds. Your buyer’s system receives the structured invoice data automatically. No email. No PDF. No manual data entry at either end.
The finance team’s experience of raising an invoice does not change. The compliance infrastructure runs invisibly behind the process they already know.
WHAT THIS MEANS FOR YOUR TEAM
The transition period — implementation, testing, data cleansing — requires focused attention from your finance and IT teams. Once you are live, the ongoing operational effort is minimal. The system runs in the background. Your team raises invoices as they always have. The compliance layer is managed by your ASP.
Common Questions Finance Teams Ask About Peppol
No. In almost all cases, your existing ERP stays exactly as it is. Your ASP connects to it via API, SFTP, or file upload — the connection method depends on your ERP and is determined during implementation scoping. Modern cloud ERP systems (SAP Business One, Oracle, MS Dynamics, Odoo, QuickBooks, Xero, Zoho) have standard integration options. Legacy or custom systems may require more development work, but replacement is not necessary.
When an invoice fails Peppol validation — because a mandatory field is missing, a TRN is incorrect, or the data does not match the PINT AE schema — your ASP will notify you with a specific error code and description. Your team corrects the error in the source data and retransmits. A well-configured ASP with auto-retry logic will handle transient network errors automatically, without any action required from your team. Structural data errors — wrong TRN, missing field — require a correction at the source.
Yes. If your buyer does not yet have a Peppol ID, your ASP routes the invoice to the FTA’s designated endpoint for non-registered buyers. Your compliance obligation is met — the invoice has been transmitted through the certified ASP and reported to the FTA. The buyer can access it through a government portal. This fallback mechanism exists specifically to ensure that gaps in buyer adoption do not create compliance problems for sellers.
The UAE e-invoicing mandate applies to B2B and B2G transactions where both parties are conducting business in the UAE. Export invoices — transactions where the buyer is outside the UAE — fall under different rules and are not currently required to go through the EIS. Your ASP can confirm the specific scope that applies to your transaction mix during implementation scoping.
Credit notes and debit notes are included in the mandate. They must also be transmitted through your ASP in PINT AE XML format. The same process applies: your ERP generates the credit note data, your ASP validates, converts, and transmits it. The only difference is the document type indicator in the XML — your ASP handles this automatically.
THE GLOSSARY: KEY TERMS IN PLAIN LANGUAGE
Peppol — The international network and standard that the UAE uses for e-invoice exchange. Think of it as the postal infrastructure, not the letter.
ASP (Accredited Service Provider) — The company you contract with to connect your business to the Peppol network. Only FTA-accredited ASPs can transmit legal UAE e-invoices. Aiverix is an accredited ASP.
PINT AE — The specific XML format the UAE uses for invoices on the Peppol network. Your ASP converts your data into this format automatically.
Peppol ID — Your unique address on the Peppol network. In the UAE: 0235: followed by the first 10 digits of your TRN.
FTA — Federal Tax Authority — the UAE government body that receives real-time tax data from every e-invoice transaction.
EIS (Electronic Invoicing System) — The UAE’s national e-invoicing infrastructure. Invoices must be transmitted through the EIS via a certified ASP to be legally valid from your mandatory date.
Wave 1 — Businesses with AED 50M+ revenue. Must appoint an ASP by July 31, 2026. Must go live by January 1, 2027.
Peppol — The international network and standard that the UAE uses for e-invoice exchange. Think of it as the postal infrastructure, not the letter.
ASP (Accredited Service Provider) — The company you contract with to connect your business to the Peppol network. Only FTA-accredited ASPs can transmit legal UAE e-invoices. Aiverix is an accredited ASP.
PINT AE — The specific XML format the UAE uses for invoices on the Peppol network. Your ASP converts your data into this format automatically.
Peppol ID — Your unique address on the Peppol network. In the UAE: 0235: followed by the first 10 digits of your TRN.
FTA — Federal Tax Authority — the UAE government body that receives real-time tax data from every e-invoice transaction.
EIS (Electronic Invoicing System) — The UAE’s national e-invoicing infrastructure. Invoices must be transmitted through the EIS via a certified ASP to be legally valid from your mandatory date.
Wave 1 — Businesses with AED 50M+ revenue. Must appoint an ASP by July 31, 2026. Must go live by January 1, 2027.
What You Need to Remember
Peppol is not something your finance team needs to master technically. It is the infrastructure that runs behind your invoicing process — managed entirely by your ASP. Your team raises invoices as they do today. Your ASP handles the validation, conversion, and transmission automatically. Your buyers receive structured data directly into their systems. The FTA receives tax reporting in real time.
The practical tasks for your finance team are focused on preparation, not ongoing operation: selecting an accredited ASP, auditing your customer master data, collecting Peppol IDs from major buyers, and completing integration testing before your mandatory go-live date.
The July 31, 2026 ASP appointment deadline applies to all Wave 1 businesses — those with AED 50 million or more in annual revenue. Implementation after appointment typically takes two to four weeks for standard ERP systems. The voluntary pilot period opens July 1, 2026, giving businesses that act early a risk-free window to test and go live before the mandatory date.
Aiverix is an FTA-accredited Accredited Service Provider and certified Peppol Access Point, based in Dubai. We connect to all major ERP systems without replacing them, handle all PINT AE conversion and transmission automatically, and provide a compliance dashboard that gives your CFO and finance team real-time visibility into every invoice. Request a no-cost compliance assessment at aiverix. ae — including a specific integration scoping call for your ERP environment.
The practical tasks for your finance team are focused on preparation, not ongoing operation: selecting an accredited ASP, auditing your customer master data, collecting Peppol IDs from major buyers, and completing integration testing before your mandatory go-live date.
The July 31, 2026 ASP appointment deadline applies to all Wave 1 businesses — those with AED 50 million or more in annual revenue. Implementation after appointment typically takes two to four weeks for standard ERP systems. The voluntary pilot period opens July 1, 2026, giving businesses that act early a risk-free window to test and go live before the mandatory date.
Aiverix is an FTA-accredited Accredited Service Provider and certified Peppol Access Point, based in Dubai. We connect to all major ERP systems without replacing them, handle all PINT AE conversion and transmission automatically, and provide a compliance dashboard that gives your CFO and finance team real-time visibility into every invoice. Request a no-cost compliance assessment at aiverix. ae — including a specific integration scoping call for your ERP environment.