UK e-invoicing 2029: Peppol is confirmed
UK e-invoicing 2029: Peppol is confirmed. What software vendors need to do now.
UK e-invoicing 2029: Peppol is confirmed. What software vendors need to do now.
By Iopole, June 2026
What just happened
On 23 June 2026, HM Treasury and HMRC (His Majesty's Revenue and Customs, the UK tax authority) officially confirmed that Peppol will be the core interoperability network for the UK's upcoming e-invoicing mandate.
This was expected by most market observers, but it was not formally confirmed until now. The announcement removes the last major technical uncertainty and starts the clock for every software vendor serving UK businesses.
The mandate in three points
Who and when: From 1 April 2029, every VAT-registered business in the UK must issue and receive structured e-invoices for B2B (business-to-business) and B2G (business-to-government) transactions. B2C transactions are out of scope for the initial rollout. There are no size-based exemptions: the mandate applies to large enterprises and SMEs alike.
What format: A PDF is not an e-invoice. The mandate requires machine-readable structured data, specifically XML-based formats that systems can process automatically, without human intervention.
What model: The UK has chosen a decentralised four-corner model. No government clearance platform sits between sender and receiver. Invoices flow directly from the sender's Access Point (AP) to the receiver's Access Point over the Peppol network. Two things are explicitly out of scope for phase 1: CTC (Continuous Transaction Controls, where the government validates each transaction in real time) and e-reporting (periodic submission of transaction data to the tax authority). The UK starts with a post-audit approach and may add reporting obligations later.
The technical architecture
How Peppol works (briefly)
Peppol is an open network governed by OpenPeppol, an international non-profit association. It is not software and not a platform. It is a set of technical specifications and governance rules that allow heterogeneous systems to exchange structured documents interoperably.
Three layers underpin it:
- AS4 (transport protocol): the secure messaging layer through which one Access Point delivers a document to another. It uses SOAP-based web services with TLS encryption and message-level non-repudiation.
- SML (Service Metadata Locator): the central DNS-based directory that maps a recipient's identifier to their Access Point.
- SMP (Service Metadata Publisher): a registry operated by each certified Access Point, listing the participants it serves and the document types they accept.
Together, SML and SMP enable dynamic discovery: any sender can locate any registered recipient's Access Point without any bilateral pre-configuration. This is what makes Peppol fundamentally different from legacy EDI networks, where every trading partner relationship required a custom setup.
The format: PINT UK, not BIS Billing 3.0
This is the most important technical decision in the UK mandate, and the one most likely to be misunderstood.
Peppol BIS Billing 3.0 is the dominant e-invoice format in Europe. It is built on EN 16931, a CEN standard that encodes EU-specific VAT rules, terminology, and identifiers. It is what the NHS uses today for supplier invoicing, and what Belgium mandated for B2B in January 2026.
The UK is post-Brexit. It is no longer bound by EU Directive 2014/55/EU or ViDA (VAT in the Digital Age, the EU's digital tax reform). UK VAT rules have their own specifics that BIS Billing 3.0 cannot accommodate cleanly.
PINT (Peppol International Invoice Model) was designed precisely for this situation: countries outside the EU regulatory framework that still want to join the Peppol network. PINT defines a common invoice core and allows each country to build a national specification (a "country spec") on top of it, encoding local tax rules while remaining interoperable with the global network.
PINT UK is the UK country spec, currently being developed by the OpenPeppol UK Working Group (active since late 2025, with an 18-month mandate aligned with the 2029 deadline). The Working Group builds on the BIS Billing 3.0 work done for the NHS and on early PINT concept work by UK stakeholders.
Worth noting: the British Standards Institution (BSI) retains full CEN membership, so EN 16931 remains a relevant technical reference for UK implementations, even if it carries no legal force.
One thing to factor into your product roadmap: OpenPeppol has announced BIS 4.0, a unified specification that converges BIS Billing 3.0 and PINT into a single standard. If you are building Peppol support today for France or Belgium, design your format layer to be modular. Implementing BIS Billing 3.0 and PINT as separate branches is technical debt you will pay when BIS 4.0 lands.
What is still open
Several structural questions remain unanswered until Budget 2026 (expected November 2026):
- PINT UK validation rules: the final Schematron rules (the business rule constraints that an Access Point applies before transmitting an invoice), mandatory fields beyond the PINT core, and UK-specific VAT field extensions.
- Phased rollout by company size: possible but not confirmed. Germany and Poland phased by revenue. The UK has stated a universal obligation, but implementation detail may include grace periods.
- The UK Peppol Authority: in Peppol governance, each country needs a designated national Peppol Authority (PA), which validates Service Metadata Publishers and oversees Access Point compliance on its territory. No UK PA has been named yet. Until one is, UK-based Access Points operate under OpenPeppol's international jurisdiction by default.
- Legacy EDI systems: thousands of UK businesses, particularly in retail, automotive, and manufacturing, already exchange structured invoices over proprietary EDI networks (VANs: Value Added Networks, operated by providers such as OpenText and IBM Sterling). They argue they already do structured e-invoicing. The open question: will they be required to route through a certified Peppol Access Point, or will interoperability bridges be accepted as compliant? HMRC has said explicitly that engagement with stakeholders on this point is ongoing. EDI vendor lobbying is active.
- Penalties and enforcement details.
UK vs France: same network, different architecture
Both France and the UK use Peppol as the exchange network. That is where the similarity ends.
| Dimension | France | UK |
|---|---|---|
| Model | Five-corner (four-corner plus PPF as fifth node) | Four-corner, pure |
| Government platform | PPF (Public Invoicing Portal) | None planned |
| Certified operators | Accredited Platforms (PA), approved by DGFiP | Access Points, certified by OpenPeppol |
| Invoice format | Factur-X, UBL, CII | PINT UK |
| E-reporting | Mandatory (separate flows to DGFiP via PPF) | Not in scope for phase 1 |
| Real-time controls | None (post-audit) | None (post-audit) |
| Go-live | September 2026 (large enterprises first) | April 2029 |
The practical implication: being a French Accredited Platform grants no status in the UK. Being a certified Peppol Access Point, which any serious Accredited Platform must be, does. AP certification is the transferable asset.
Conversely, a UK-based ISV looking to support French customers will need to understand the five-corner model, the PPF, and French e-reporting obligations, none of which have any UK equivalent.
What this means for software vendors
If you are already connected to the Peppol network (for France, Belgium, NHS, or any other market): you have the infrastructure. Extending to UK means implementing PINT UK when the spec is published, registering your clients in the UK SML zone once a Peppol Authority is named, and handling UK-specific VAT fields. This is an extension, not a rebuild.
If you are not yet on Peppol: you have two options.
Building your own certified Access Point takes a minimum of 12 months: AS4 implementation, OpenPeppol conformance testing, PKI certificate management, 24/7 infrastructure, and ongoing recertification. It gives you full control and the ability to offer Peppol services to your clients as part of your product.
Partnering with an existing Access Point via API is faster (3 to 9 months depending on integration depth), but creates a dependency on your partner's infrastructure and compliance maintenance.
Either way: this decision needs to be made in 2026, not 2028.
The real deadline is not April 2029. Your enterprise customers with UK invoicing flows need to be in stable production at least six months before the mandate, meaning autumn 2028. To launch implementation in early 2028, they need to have selected their vendor by end of 2027, after a 6 to 12-month RFP and evaluation cycle. That RFP starts in 2027. If your product does not support Peppol UK when the RFP lands, you are not shortlisted, regardless of the 2029 statutory deadline.
What to do before November 2026
Map your UK exposure. Identify which clients on your platform have UK invoicing counterparties. Estimate volumes. This determines urgency and project sizing.
Decide your Access Point strategy. Build or partner, both paths require a 2026 decision to be ready for the 2027 RFP cycle.
Design for BIS 4.0. If you are implementing Peppol support now, keep your format and validation layer modular. The convergence of BIS Billing 3.0 and PINT into BIS 4.0 is coming. Build for it now or refactor later.
Engage the OpenPeppol UK Working Group. The PINT UK specification is being written now. Vendors who participate in consultation and testing phases implement against final rules, not against a published spec they have to reverse-engineer after the fact.
Iopole: Peppol infrastructure for software vendors
Iopole is a certified Peppol Access Point, live in production on the French and Belgian markets and compatible with NHS invoicing flows. Our infrastructure is international by design, with ViDA 2030 on our roadmap.
We offer Peppol as a Service for software vendors who want to connect to the Peppol network without managing OpenPeppol certification directly: one API connection, all Peppol markets covered, compliance updates handled.
If you have clients with UK invoicing flows, or if you are evaluating your Peppol strategy ahead of November 2026, we are the right conversation to have now.
Sources: Tax Update 2026 (GOV.UK, 23 June 2026), OpenPeppol UK Working Group, HMRC consultation response November 2025, OpenPeppol technical documentation.
