Peppol is an open international network that allows organisations to exchange structured business documents, such as invoices, and credit notes directly between their finance systems.
It is not a piece of software you buy, and it is not a government portal you log into. It is a set of agreed document standards combined with a delivery network, operated under rules maintained by the non-profit body OpenPeppol.
For UK finance teams, Peppol has moved from a technical curiosity to something worth understanding properly. In its Tax update 2026 policy paper, published in June 2026, the government confirmed that Peppol will be the core interoperability network for eInvoicing in the United Kingdom. That decision shapes how invoices will move between UK businesses when the mandate takes effect in April 2029, and it gives finance teams and software providers a clear technical direction to plan against.
The UK eInvoicing mandate was confirmed at the Autumn Budget in November 2025, and it will require all VAT-registered businesses to exchange VAT invoices in a structured electronic format from 1 April 2029. B2B and B2G transactions are in scope; business-to-consumer invoicing is not. What the Budget announcement did not settle was the technical route, and that uncertainty made it difficult for finance teams to plan with any confidence.
The June 2026 confirmation removes much of that uncertainty. HMRC presented the Peppol decision as an indication of the direction of travel, intended to let software developers and businesses begin planning their products and their rollout rather than waiting for final legislation. The remaining detail, including phasing, enforcement and the confirmed technical specification, is expected in an implementation roadmap published alongside Budget 2026.
For anyone reviewing finance systems in the next two or three years, this matters more than the 2029 date suggests. Systems selected now will still be running when the mandate arrives, so Peppol capability is reasonably part of the evaluation criteria today.
Peppol stands for Pan-European Public Procurement OnLine. It began as an EU pilot in 2008, intended to make cross-border public procurement simpler, and it has since grown into an open infrastructure used across more than thirty countries. The UK is not new to it: structured electronic invoicing over Peppol has been required for NHS business-to-government transactions since 2019, so a meaningful number of UK suppliers already have practical experience of it.
The most useful comparison is email. You do not negotiate a connection with each person you write to, and you do not need to use the same email provider as they do. You connect once through a provider, and the network handles addressing and delivery. Peppol works on the same principle, but for structured business documents rather than messages, and with the significant addition that the content is standardised so that the receiving system can process it automatically.
Two components make this work. The first is a set of standard document specifications that define exactly how an invoice is structured, so that sender and receiver interpret every field identically. The second is a delivery network of certified providers, together with a discovery layer that works out where a document should be sent. Neither is much use without the other.
Peppol operates on what is known as a decentralised four-corner model. The four corners are the supplier, the supplier’s service provider, the buyer’s service provider, and the buyer. Documents pass between the two service providers rather than through a central government platform, which is a deliberate contrast with the clearance models used in countries such as Italy.
The process runs roughly as follows:
The practical significance of that discovery step is easy to miss. It is what allows a supplier to send an invoice to any organisation on the network without holding a prior technical agreement with them, and it is the main reason Peppol scales in a way that point-to-point connections do not.
It is also worth being clear about what the model does not do. The government has confirmed that real-time reporting to HMRC is not part of the 2029 mandate, and the first phase covers structured invoice exchange only. HMRC has said the architecture should remain open to digital reporting in future, so a reporting layer could be added later, but that is not the position today.
An Access Point is a certified service provider that connects an organisation to the Peppol network. It handles recipient lookup, format validation, secure transmission and proof of delivery on your behalf. You integrate your finance system with your Access Point once, and through it you can reach every other participant on the network, regardless of which provider they have chosen.
Because senders and receivers each select their own provider, there is no requirement for trading partners to align on software, and no single point of failure in the network. Providers compete on service, price and integration quality rather than on network access, which is a genuine advantage compared with traditional arrangements where switching provider means renegotiating connections.
One caveat applies specifically to the UK. Accreditation requirements for UK Access Point providers have not yet been published, so any current claim about UK-specific certification should be read as provisional until the Budget 2026 roadmap arrives.
The confusion here is understandable, because all three move an invoice from one organisation to another.
Emailed PDF
Traditional EDI
Peppol
Data format
Unstructured document
Structured, but format varies by agreement
Standardised structured data
Setup per partner
None
Individual technical agreement required
One connection reaches all participants
Onboarding a new supplier
Immediate
Weeks or months of mapping
Lookup and send
Automatic processing
Requires OCR and manual checking
Yes, once mapped
Yes, by design
Suitable for the 2029 mandate
No
Treatment still under review
Yes
EDI is not obsolete, and organisations with mature EDI arrangements should not assume they need to abandon them. The government has acknowledged that the future of existing peer-to-peer EDI arrangements under the mandate is still being worked through, and has said it will continue engaging with stakeholders on legacy systems that cannot interoperate with the future model.
Emailing a PDF, however, does not meet the definition of eInvoicing under the mandate, however convenient it currently feels.
Most of the practical work sits inside your own systems and data rather than at the network layer. Three questions are worth putting to your finance software provider now.
Can the system produce and receive structured invoice data? Producing a PDF and producing an EN 16931-compliant structured invoice are different capabilities. The receiving side matters just as much, and is often the weaker of the two in older systems.
Can it integrate with an Access Point? This is usually an API question. A finance system with open, well-documented APIs can be connected to a provider without bespoke development, whereas a closed system may require middleware and ongoing maintenance.
Can it hold the master data Peppol depends on? Participant identifiers need somewhere to live in your customer and supplier records, and existing VAT numbers, addresses and entity details need to be accurate. Poor master data is one of the most common causes of delay in Peppol implementations, and it is also the part you can begin fixing immediately, without waiting for anything to be confirmed.
This is where the choice of finance system has practical consequences. bluQube’s approach to interoperability is built around open APIs and bluQube Connect, which is designed to let finance systems exchange data with external services without custom integration work for each connection. The same principle applies whichever system you use: the more openly it integrates, the less disruptive the transition to structured invoicing is likely to be.
There is no need to connect to Peppol today, and no advantage in rushing a decision before the Budget 2026 roadmap is published. There is, however, useful groundwork available.
If you supply the public sector, the timeline is effectively shorter. Public bodies have been working with Peppol for years, and buyers are likely to move ahead of the statutory deadline.
Not yet, for most organisations. Structured eInvoicing over Peppol has been required for NHS business-to-government transactions since 2019, and eInvoicing becomes mandatory for all VAT-registered businesses from 1 April 2029. Between now and then, it remains voluntary.
No, but many organisations will choose to. Suppliers to the public sector and those with European trading partners often find there is a commercial reason to move earlier.
Not under the 2029 mandate. The first phase covers structured invoice exchange between businesses only, with no clearance or continuous transaction controls. HMRC has indicated the architecture should remain capable of supporting digital reporting later.
No. Peppol is the network your finance system sends and receives documents through, in much the same way that email does not replace the software you write documents in.
Understanding what Peppol is puts UK finance teams in a considerably better position than waiting for the mandate to arrive. It is an open network built on published standards, chosen precisely because it avoids locking businesses into a single provider or a central government platform, and because it keeps UK organisations interoperable with the European partners many of them already trade with.
The detail is not yet complete, and the implementation roadmap due at Budget 2026 will answer several questions that remain open. That is not a reason to wait. The work that will determine how smoothly the transition goes, cleaning up supplier and customer master data, understanding your current invoice volumes and formats, and establishing whether your finance system can produce and consume structured data, can all begin now and is worth doing regardless of what the roadmap confirms.
The most useful next step is a straightforward one: find out what your current finance system can actually do, and what your software provider intends to do about it.
We use cookies to enhance your browsing experience, serve personalised ads or content and analyise our traffic. By clicking accept all, you consent to our use of cookies. Cookie policy.