TECHNICAL
Peppol Access Points, Participant Identifiers and the UAE Network: What Finance Teams Need to Actually Do
The introductory guide to Peppol explains what the network is. This article goes one level deeper — into the operational specifics that only become relevant when you are actively implementing. How your Participant Identifier is created. How invoice routing works. What predefined endpoints do. How OpenPeppol governs the network. And what your ASP contract must specifically cover to keep you compliant long after go-live.
reading time: 12 min
SOURCES: MOF OFFICIAL PUBLICATIONS
may 2026
aiverix research
If you have read the introductory Peppol guide in this series, you already know what Peppol is, how the 5-corner model works, and why the UAE chose it as the foundation for its Electronic Invoicing System. This article is for the next level of understanding — the operational details that finance teams and ERP teams encounter during implementation and that are rarely explained clearly in product brochures or regulatory summaries. Specifically: how your Peppol Participant Identifier is generated and what it is made from; how the Peppol network decides where to route your invoice; what predefined endpoints are and when to use each one; what OpenPeppol is and why it matters for your ASP selection; and what your ASP contract should include to protect your compliance over the long term.
“
OFFICIAL SOURCES:
UAE Electronic Invoicing Guidelines V1.0, Sections 2, 5, and 5.2 — Ministry of Finance, 23 February 2026
UAE Electronic Invoice Mandatory Fields V1.0, Section 2 — Ministry of Finance, 23 February 2026
UAE Electronic Invoicing Guidelines V1.0, Sections 2, 5, and 5.2 — Ministry of Finance, 23 February 2026
UAE Electronic Invoice Mandatory Fields V1.0, Section 2 — Ministry of Finance, 23 February 2026
Your Peppol Participant Identifier: What It Is and How It Is Created
Your Peppol Participant Identifier — also called your End Point ID in the official Guidelines — is your unique address on the UAE Peppol network. It is the address your buyers need to deliver invoices to you, and the address your ASP registers so that invoices sent to you can be correctly routed through the network.
The format is fixed and defined by the Ministry of Finance. It consists of two parts separated by a colon: the UAE network prefix code, followed by your Tax Identification Number.
The format is fixed and defined by the Ministry of Finance. It consists of two parts separated by a colon: the UAE network prefix code, followed by your Tax Identification Number.
The prefix 0235 is the country identifier for the UAE on the Peppol network. It is the same for every business in the UAE — it does not vary. Your TIN is the first 10 digits of your 15-digit Tax Registration Number. If you are registered for VAT or Corporate Tax with the FTA, you already have a TIN. If you are not registered for any tax type but are in scope for e-invoicing, you must register with the FTA via EmaraTax to obtain a TIN before your Participant Identifier can be created.
“
Your Participant Identifier for Electronic Invoicing will be your Tax Identification Number (TIN). The TIN is the first 10 digits of the 15-digit TRN issued to all entities registered with the UAE Federal Tax Authority.
0235
Fixed UAE prefix — same for every business in the UAE on the Peppol network
10
Digits — your TIN, the first 10 digits of your 15-digit TRN
1
Participant Identifier per entity — even within a tax group, each entity has its own
40+
Countries on the global Peppol network where your ID will be recognised
How the identifier is actually generated
Your Participant Identifier is not created automatically when you register for VAT or Corporate Tax. It does not exist until your ASP formally registers it on the Peppol network during the EmaraTax onboarding process. This is an important operational point: you can have a TIN, you can have a signed ASP contract, and you can have your ERP fully integrated — but until your ASP has completed the EmaraTax onboarding and registered your Participant Identifier on the network, you do not have an address on the Peppol network and you cannot receive or send invoices through it.
The registration process works as follows. You log into EmaraTax and navigate to the E-INVOICING section. You select your chosen ASP from the official list and click "Proceed to ASP." You are redirected to your ASP’s portal, where you complete the commercial onboarding. Your ASP then registers your TIN on the Peppol network through their certified Access Point connection. Upon successful registration, your ASP provides you with your Participant Identifier — confirmed as active on the network.
The registration process works as follows. You log into EmaraTax and navigate to the E-INVOICING section. You select your chosen ASP from the official list and click "Proceed to ASP." You are redirected to your ASP’s portal, where you complete the commercial onboarding. Your ASP then registers your TIN on the Peppol network through their certified Access Point connection. Upon successful registration, your ASP provides you with your Participant Identifier — confirmed as active on the network.
Tax groups: each entity has its own identifier
If your business is part of a UAE VAT group, an important rule applies: each entity in the group has its own TIN — the first 10 digits of its own Corporate Tax TRN — and therefore its own Peppol Participant Identifier. The group representative’s TIN does not serve as the identifier for other group members. Each entity must be individually onboarded and will receive its own unique address on the network. Different entities within the same group can use different ASPs if they choose to.
How Invoice Routing Works on the Peppol Network
When your ASP transmits an invoice on your behalf, it needs to know where to send it. The routing process uses the buyer’s Peppol Participant Identifier to look up the buyer’s ASP in the Peppol directory and deliver the invoice to the correct destination. Here is the step-by-step routing process in plain language.
STEP 1 — CORNER 1
STEP 1 — CORNER 1
Your ERP sends invoice data to your ASP
Invoice data leaves your system in your ERP’s native format — your ASP handles the conversion from here.
STEP 2 — CORNER 2 (YOUR ASP)
STEP 2 — CORNER 2 (YOUR ASP)
Your ASP validates, converts to PINT AE XML, and looks up the buyer
Your ASP checks the buyer’s Peppol Participant Identifier against the Peppol Directory — a global registry of all registered participants across all Peppol-connected countries. If the buyer’s ID is found, routing proceeds to their ASP. If not found, a predefined endpoint is used.
STEP 3 — PEPPOL NETWORK
STEP 3 — PEPPOL NETWORK
The invoice travels through the Peppol network securely
The invoice is transmitted digitally signed, encrypted in transit, from your ASP’s Access Point to the buyer’s ASP’s Access Point. Both Access Points must be certified by OpenPeppol — this certification is what makes the transmission legally valid on the network.
PARALLEL — CORNER 5
PARALLEL — CORNER 5
Your ASP simultaneously reports tax data to the FTA
At the same time as the invoice is transmitted to the buyer’s ASP, your ASP sends a Tax Data Document to the FTA’s e-billing system (Corner 5). This happens in near real time — not at month end.
STEP 4 — CORNERS 3 AND 4
STEP 4 — CORNERS 3 AND 4
Buyer’s ASP delivers to buyer’s system
The buyer’s ASP receives the invoice, validates it, and delivers it to the buyer’s accounting system in their preferred format. The buyer’s ASP also reports tax data to the FTA from their side. Both ASPs send confirmation messages back to confirm successful delivery and reporting.
Predefined Endpoints: When the Normal Routing Does Not Apply
Not every invoice has a straightforward buyer with a registered Peppol ID. For situations where normal routing to a buyer’s ASP is not possible, the UAE framework provides three predefined endpoints — fixed addresses managed by the FTA that handle specific routing scenarios.
Your ASP looks up the buyer’s Peppol ID in the Peppol Directory before transmitting. If the lookup fails — or if your invoice is for a scenario where no buyer exists — the correct predefined endpoint must be used instead. Here is the routing decision process:
Your ASP looks up the buyer’s Peppol ID in the Peppol Directory before transmitting. If the lookup fails — or if your invoice is for a scenario where no buyer exists — the correct predefined endpoint must be used instead. Here is the routing decision process:
WHAT THE FALLBACK ENDPOINT MEANS FOR YOUR BUYERS
When you route an invoice through the fallback endpoint 0235:9 900 000 098because your buyer is not yet registered on Peppol, your compliance obligation is fully met. The invoice is transmitted correctly through your ASP, tax data is reported to the FTA, and the buyer can access the invoice through the FTA portal.
However, the buyer does not receive structured XML data directly into their accounting system — they have to access it manually through a portal. As the UAE mandate matures and more buyers register their Peppol IDs, this manual step disappears. The goal is that eventually all buyers will be registered, and the fallback endpoint becomes unnecessary. For the transition period — roughly from January 2027 through mid-2027 when Wave 2 goes live — expect to use the fallback endpoint for a significant proportion of your invoices.
When you route an invoice through the fallback endpoint 0235:9 900 000 098because your buyer is not yet registered on Peppol, your compliance obligation is fully met. The invoice is transmitted correctly through your ASP, tax data is reported to the FTA, and the buyer can access the invoice through the FTA portal.
However, the buyer does not receive structured XML data directly into their accounting system — they have to access it manually through a portal. As the UAE mandate matures and more buyers register their Peppol IDs, this manual step disappears. The goal is that eventually all buyers will be registered, and the fallback endpoint becomes unnecessary. For the transition period — roughly from January 2027 through mid-2027 when Wave 2 goes live — expect to use the fallback endpoint for a significant proportion of your invoices.
What a Certified Peppol Access Point Is — and Why It Matters
A Peppol Access Point is a technical service that connects a business to the Peppol network. Your ASP must operate a certified Access Point in order to legally transmit invoices on the UAE Peppol network. The certification is granted by OpenPeppol — the international non-profit organisation that governs the Peppol standards and network worldwide.
OpenPeppol was established to maintain the Peppol Interoperability Framework — the set of technical standards and governance rules that make the network function consistently across all connected countries. When you see an ASP described as a "certified Peppol Access Point," it means they have been assessed by OpenPeppol and found to meet the technical requirements necessary to connect to and operate on the global Peppol network.
OpenPeppol was established to maintain the Peppol Interoperability Framework — the set of technical standards and governance rules that make the network function consistently across all connected countries. When you see an ASP described as a "certified Peppol Access Point," it means they have been assessed by OpenPeppol and found to meet the technical requirements necessary to connect to and operate on the global Peppol network.
“
OpenPeppol is an international non-profit association responsible for the development and maintenance of the Peppol Interoperability Framework.
For UAE businesses, the significance is this: your ASP must hold both FTA accreditation (which authorises them to operate in the UAE specifically) and OpenPeppol certification (which authorises them to connect to the global Peppol network). One without the other is insufficient. An ASP with FTA accreditation but no OpenPeppol certification cannot technically connect to the Peppol network. An ASP with OpenPeppol certification but no FTA accreditation is not authorised to transmit UAE invoices legally.
The Peppol Service Provider Agreement
When an ASP becomes a certified Peppol Access Point, they sign a Peppol Service Provider Agreement with OpenPeppol. This agreement governs their technical obligations on the network — including maintaining compliance with the latest PINT AE specifications, adhering to security standards, and ensuring their Access Point remains connected and operational.
From your perspective as a UAE business, the Peppol Service Provider Agreement is what ensures your ASP will stay current with regulatory changes. As the UAE Ministry of Finance updates the PINT AE technical specifications over time — which it will, as the system matures — your ASP is contractually obligated to OpenPeppol to implement those updates. This is one of the key reasons why using a certified ASP is preferable to building a direct Peppol connection internally: the maintenance obligation is continuous, and a certified ASP absorbs it as part of their service.
From your perspective as a UAE business, the Peppol Service Provider Agreement is what ensures your ASP will stay current with regulatory changes. As the UAE Ministry of Finance updates the PINT AE technical specifications over time — which it will, as the system matures — your ASP is contractually obligated to OpenPeppol to implement those updates. This is one of the key reasons why using a certified ASP is preferable to building a direct Peppol connection internally: the maintenance obligation is continuous, and a certified ASP absorbs it as part of their service.
Collecting Buyer Peppol IDs — The Practical Pre-Go-Live Task
Once you understand how routing works, the practical implication becomes clear: before you go live, you need to collect Peppol Participant Identifiers from your major buyers and store them in your ERP customer master records. Without these IDs, every invoice routes through the fallback endpoint, and your buyers receive their invoices through the FTA portal rather than directly into their accounting systems.
Collecting buyer Peppol IDs is an administrative task — similar to collecting bank account details for payment processing. The process is straightforward:
Collecting buyer Peppol IDs is an administrative task — similar to collecting bank account details for payment processing. The process is straightforward:
DO NOT WAIT UNTIL GO-LIVE TO COLLECT BUYERS IDS
Italy’s SDI rollout documented this problem clearly. Businesses that left buyer identifier collection until the week before go-live found themselves with thousands of customer records to update under deadline pressure — making errors, missing records, and generating large volumes of fallback-routed invoices in their first weeks of operation.
The UAE equivalent is collecting Peppol IDs. Start the process as soon as you appoint your ASP. Send a single clear communication to your accounts receivable team explaining what a Peppol ID is, what it looks like, and how to update the customer master. Make it a standard part of your buyer onboarding process for any new customer added after July 2026.
Italy’s SDI rollout documented this problem clearly. Businesses that left buyer identifier collection until the week before go-live found themselves with thousands of customer records to update under deadline pressure — making errors, missing records, and generating large volumes of fallback-routed invoices in their first weeks of operation.
The UAE equivalent is collecting Peppol IDs. Start the process as soon as you appoint your ASP. Send a single clear communication to your accounts receivable team explaining what a Peppol ID is, what it looks like, and how to update the customer master. Make it a standard part of your buyer onboarding process for any new customer added after July 2026.
What Your ASP Contract Must Cover — A Peppol Perspective
The standard ASP sales conversation focuses on pricing, ERP compatibility, and implementation timeline. The questions that matter most for your long-term compliance — particularly around Peppol network operations — are rarely raised unless you ask them directly. Here are the specific contract clauses your legal and finance teams should verify before signing.
The UUID: What It Is and Why You Do Not Need to Worry About It
Every UAE electronic invoice receives a UUID — a Universally Unique Identifier. This is a 128-bit number generated automatically by the Electronic Invoicing System to uniquely identify each invoice and prevent duplication. The UUID is different from your invoice number — it is generated by the system, not by your ERP.
According to the official Guidelines, generating the UUID is the responsibility of your ASP — not your finance team or your ERP. Your ERP provides the invoice number, which is your internal sequential invoice reference. The ASP adds the UUID as a system-level identifier before transmitting the invoice. You will see the UUID in your compliance dashboard and in any FTA correspondence about a specific invoice, but you do not need to generate or manage it yourself.
According to the official Guidelines, generating the UUID is the responsibility of your ASP — not your finance team or your ERP. Your ERP provides the invoice number, which is your internal sequential invoice reference. The ASP adds the UUID as a system-level identifier before transmitting the invoice. You will see the UUID in your compliance dashboard and in any FTA correspondence about a specific invoice, but you do not need to generate or manage it yourself.
SUMMARY: WHAT HAPPENS AUTOMATICALLY VS WHAT YOUR TEAM DOES
Happens automatically — managed by your ASP: UUID generation for each invoice; PINT AE XML conversion; digital signing; Peppol network routing; FTA tax data reporting; confirmation message processing; regulatory spec updates.
Your team’s responsibility: Invoice data quality in your ERP (all 51 mandatory fields populated correctly); buyer Peppol IDs collected and stored in customer master; invoice transaction type code configured correctly per transaction type; EmaraTax onboarding completed; data retention practices in place; monitoring compliance dashboard for rejection notifications.
The division is clean: your team owns the data and the governance. Your ASP owns the technical transmission and network operations. Neither side can cover for failures in the other.
Happens automatically — managed by your ASP: UUID generation for each invoice; PINT AE XML conversion; digital signing; Peppol network routing; FTA tax data reporting; confirmation message processing; regulatory spec updates.
Your team’s responsibility: Invoice data quality in your ERP (all 51 mandatory fields populated correctly); buyer Peppol IDs collected and stored in customer master; invoice transaction type code configured correctly per transaction type; EmaraTax onboarding completed; data retention practices in place; monitoring compliance dashboard for rejection notifications.
The division is clean: your team owns the data and the governance. Your ASP owns the technical transmission and network operations. Neither side can cover for failures in the other.
The Operational Details That Make the Difference
The difference between a smooth e-invoicing go-live and a difficult one usually comes down to the operational details covered in this article — not the high-level concept. Businesses that understand how routing works collect buyer Peppol IDs before go-live and configure fallback endpoints correctly. Businesses that understand what their ASP contract needs to contain protect themselves against disruptions, provider changes, and regulatory updates. Businesses that understand UUID generation stop worrying about something their ASP handles automatically.
The practical action items from this article are three: first, collect your major buyers' Peppol IDs as soon as possible and update your customer master records. Second, verify that your ASP has both FTA accreditation and OpenPeppol certification — not one or the other. Third, review your ASP contract against the seven clauses in the table above before signing.
Aiverix is an FTA-accredited Accredited Service Provider and certified Peppol Access Point. Our contracts include explicit data retention, uptime SLA, regulatory update, and disruption notification commitments. We provide a full compliance dashboard with real-time routing status and individual invoice XML retrieval. Request a no-cost compliance assessment at aiverix.ae.
The practical action items from this article are three: first, collect your major buyers' Peppol IDs as soon as possible and update your customer master records. Second, verify that your ASP has both FTA accreditation and OpenPeppol certification — not one or the other. Third, review your ASP contract against the seven clauses in the table above before signing.
Aiverix is an FTA-accredited Accredited Service Provider and certified Peppol Access Point. Our contracts include explicit data retention, uptime SLA, regulatory update, and disruption notification commitments. We provide a full compliance dashboard with real-time routing status and individual invoice XML retrieval. Request a no-cost compliance assessment at aiverix.ae.