.svg)
Most finance teams have now heard that Peppol is the network the UK government has named for mandatory e-invoicing. Fewer understand what that actually means in practice: how the network works, what connecting to it involves, and what it means for the AP and AR systems already in place.
This article covers the mechanics of Peppol: what it is, how structured invoices move through it, what a Peppol ID and access point provider are, and what UK businesses need to do to get on the network before April 2029.
Peppol (Pan-European Public Procurement On-Line) is a set of open standards and governance rules that allow businesses using different software and different service providers to exchange structured electronic documents reliably. It is not a platform. There is no Peppol portal to log into, no central government system to connect to.
Peppol is better understood as an interoperability framework: a common language and a set of agreed rules that make it possible for a sender using one accounting system and one service provider to send an invoice to a recipient using completely different software and a different service provider, and for both sides to handle the transaction automatically.
That is the key point. The mandate does not require all UK businesses to use the same software. It requires them to connect to a common network through which structured invoices can move between any two participants.
Peppol already operates in more than 40 countries. Belgium made B2B Peppol e-invoicing mandatory from January 2026. Singapore, Japan, Australia, New Zealand, and Malaysia all use Peppol-based frameworks for cross-border and domestic e-invoicing. The UK's 2029 mandate is the next addition to an existing global infrastructure.
This is worth being clear about because confusion here leads to poor preparation decisions.
Peppol is not a clearance system. The Italian SdI model, where every invoice passes through a government platform before reaching the recipient, is a clearance model. The UK's confirmed approach is decentralised: businesses exchange invoices directly through the Peppol network, without a government system sitting in the middle. HMRC's current scope does not include real-time reporting to government. The 2029 mandate is about structured invoice exchange, not transaction monitoring.
Peppol is not a specific piece of software. Connecting to Peppol means working with a certified access point provider: a company whose job it is to route your invoices through the network. That provider may be your AP software vendor, your ERP vendor, or a specialist intermediary. The choice matters, but Peppol itself is the network they connect you to.
The Peppol network uses what is called the four-corner model. Understanding it makes the practical steps much easier to follow.
Corner 1 is the sender: the business issuing the invoice. That business connects to the network through their certified access point provider.
Corner 2 is the sender's access point provider. This is a certified company that receives the invoice from the sender's system, validates it against the relevant format requirements, and routes it across the Peppol network.
Corner 3 is the recipient's access point provider. This is a certified company on the receiving side that accepts the routed invoice from the Peppol network and delivers it into the recipient's system.
Corner 4 is the recipient: the business receiving the invoice. They receive it directly into their AP system, where it can be processed automatically without any manual data entry.
Neither party needs to be connected to the same software or the same access point provider. They only need to both have a Peppol ID and a connected access point.
This is what makes the network work at scale. A business can send to any Peppol-connected recipient regardless of what accounting software, ERP, or service provider that recipient uses. The network handles the routing. The certified access points handle the format validation and delivery.
Every participant on the Peppol network has a unique identifier called a Peppol ID. This is how senders address invoices to the right recipient and how the network routes them correctly.
A Peppol ID is made up of two parts: a scheme code that identifies the type of identifier, and the identifier itself. For UK businesses, the most common scheme is scheme 9932, which uses the VAT registration number. A UK business's Peppol ID would look something like 0088:1234567890 or 9932:GB123456789.
Each legal entity that sends or receives invoices needs its own Peppol ID. A business with multiple subsidiaries, each registered separately, needs a Peppol ID for each entity.
NHS suppliers registered on the Peppol network are identified using a GS1 Global Location Number (scheme 0088) rather than their VAT number, because that is how NHS procurement systems address them. Businesses already supplying the NHS on Peppol BIS 3.0 will need to confirm how their existing identifier maps to the 2029 framework once the UK's technical specifications are finalised.
Before registering with an access point provider, it is worth checking the Peppol Directory to see whether a previous registration exists for your business. ERP vendors and procurement platforms sometimes register participants as part of onboarding.
An access point provider is a certified company that connects your business to the Peppol network. They handle the technical routing, format validation, and delivery of invoices between your system and the network.
Becoming your own access point is technically possible but is a significant engineering investment. It is realistic only for large enterprises with dedicated integration teams. For almost all mid-market businesses, the practical path is to work with a certified provider.
The official registry of certified Peppol access point providers is maintained by OpenPeppol. Certification is not a lightweight process. Providers must meet technical and operational standards set by the OpenPeppol authority.
Not all access point providers are the same. When evaluating options, the questions that matter most are:
Integration with your existing systems. The access point needs to connect to the system where invoices are actually created and received. If your AP platform or ERP vendor has a certified access point offering, that is often the most straightforward path because the integration is already built. If it does not, a specialist intermediary will need to build the connection, which adds time and cost.
Support for UK-specific requirements. The UK's format requirements are still being finalised through the HMRC co-design process. A draft UK-specific Peppol format (PINT UK) was published for concept demonstration in April 2026, but it is not yet an official specification. When the technical specifications are finalised, you will want a provider that updates their format support promptly. Check that your provider has a clear position on UK mandate readiness and communicates format updates to customers.
Document types covered. Peppol supports multiple document types beyond invoices: purchase orders, order responses, despatch advice, credit notes. If your business eventually wants to automate purchase order exchange alongside invoices, check that your provider supports those document types.
Geographic coverage. If your business trades across multiple countries, a provider with coverage in multiple Peppol-connected markets avoids having to manage separate provider relationships for different jurisdictions.
Peppol uses a structured data format built on the EN 16931 European standard for electronic invoices. EN 16931 defines the semantic data model (the required and optional fields an e-invoice must contain) but does not mandate a specific syntax.
In practice, Peppol invoices are most commonly expressed in UBL 2.1 (Universal Business Language) XML format, which is the syntax used for Peppol BIS Billing 3.0, the format already in use across the NHS and UK public sector procurement.
The UK-specific format extension, PINT UK, is based on the same PINT (Peppol International) methodology used across Singapore, Japan, Australia, New Zealand, and EU countries. As of April 2026, a concept draft (v0.0.1) exists, but the official UK specification is still being developed through the HMRC co-design process that began in March 2026.
What this means practically: the core format infrastructure (EN 16931 + UBL) is established and already in use. The UK-specific extension adds rules specific to UK VAT invoicing requirements. Businesses that implement AP automation now using Peppol BIS 3.0 (as NHS suppliers already do) are building on the right foundation. The UK extension, when finalised, adds UK-specific validation rules on top of that base.
The key takeaway is that Peppol is not new technology. The format, the network, and the access point model are all operational in dozens of countries. The UK mandate applies an existing, working infrastructure to B2B trade.
Connecting to Peppol via an access point handles the network side: getting structured invoices from your suppliers into your system. What happens to those invoices once they arrive is a separate question.
An incoming Peppol invoice is a structured XML file with all invoice data in machine-readable fields. If your AP system can ingest that file and process it automatically (matching against purchase orders, routing for approval, posting to the ERP) then the mandate delivers real operational efficiency. Each invoice arrives pre-structured and moves through the AP workflow without manual data entry.
If your AP system receives the structured file but cannot process it automatically, you have better-quality input data but the same manual processing burden. The access point connects you to the network. The AP automation platform determines what happens to invoices once they arrive.
Dost integrates with SAP, Microsoft Business Central, Sage (200, Intacct, X3), and Oracle in real time. Invoices received through Peppol-connected channels flow directly into the Dost AP workflow: extraction, validation, three-way matching, approval routing, and ERP reconciliation, without manual steps at any stage. The network delivers the structured data. The platform handles everything that follows.
Want to see what your AP process could look like when structured invoices flow automatically from day one? Use Dost's ROI calculator to estimate your potential savings based on current invoice volume.
For businesses in scope of the mandate — UK VAT-registered businesses issuing and receiving B2B and B2G VAT invoices — connecting to Peppol is the confirmed approach. In practice, this means registering with a certified access point provider, which assigns and registers your Peppol ID on the network as part of onboarding. The ID itself is tied to your VAT registration number (scheme 9932 for UK businesses). The technical specifications for the UK implementation are still being finalised by HMRC, so the precise registration process may be updated once those are published.
Yes, partially. UK public sector bodies are already required to accept EN 16931-compliant e-invoices under procurement rules, and NHS suppliers already use Peppol BIS 3.0 to send structured invoices to NHS entities. The 2029 mandate extends this existing Peppol infrastructure from public sector procurement to all B2B VAT invoicing. Businesses already sending Peppol invoices to the NHS are connected to the network; they will need to confirm their setup against the UK-specific requirements once those are finalised.
The technical registration — getting a Peppol ID and being routable on the network — typically takes a few working days through a certified access point provider, and can be same-day for a single entity. The more significant timeline factor is integrating the access point with the systems where invoices are actually created and received. If your AP platform or ERP vendor already has a certified access point service, that integration is built. If it requires custom development, the timeline depends on the integration complexity. For most mid-market businesses, the full implementation including AP system integration should be planned as a three-to-six month project, not a last-minute registration.
Peppol is not complicated once you understand that it is a network, not a platform. UK businesses will need a Peppol ID, a certified access point provider to connect them to the network, and an AP system that can process the structured invoices that arrive through it.
The access point question and the AP automation question are related but separate. Getting on the network is a relatively quick registration process. Making full use of structured invoice data (processing invoices automatically, matching against POs, routing approvals) requires an AP platform built to handle that input.
For businesses that address both before April 2029, the mandate does not create disruption. It creates the infrastructure for a more automated, more controlled AP process that finance teams have had every reason to want regardless of any regulatory requirement.
See what that looks like in practice with Dost's ROI calculator.
