Insights
The UK has chosen Peppol: what the 2029 e-invoicing mandate means for your finance operation
From 1 April 2029, VAT invoices between UK businesses must be structured e-invoices exchanged over Peppol. What's decided, what's still open, and a platform-agnostic readiness plan, whether you run Oracle, SAP, Workday, Dynamics or something else.
The debate is over. On 28 October 2026, HMRC published its roadmap for mandatory e-invoicing. From 1 April 2029, VAT-registered businesses will generally have to issue and receive VAT invoices to and from other VAT-registered businesses as structured electronic invoices, exchanged over the Peppol network.
For finance teams, that turns e-invoicing from “something happening in Europe” into a dated UK programme. The good news is that the UK has chosen one of the lighter-touch models available. The bad news is that two and a half years is less time than it sounds once you count requirements, supplier onboarding, testing and change management.
This article sets out what has been decided, what is still open, and how to prepare whatever ERP or finance platform you run.
- 1 Apr 2029mandate takes effect for B2B and B2G VAT invoices
- Peppolfour-corner exchange network
- HMRCto become the UK Peppol Authority
- 0invoices routed through HMRC: no clearance model
When does UK e-invoicing start, and what has been decided?
| Decided in the roadmap | |
|---|---|
| Start date | 1 April 2029 |
| Who | VAT-registered businesses, including non-established businesses registered for UK VAT that make domestic supplies to VAT-registered customers |
| What | VAT invoices between VAT-registered persons where a VAT invoice is already required, covering domestic B2B and supplies to the public sector |
| Format | Structured data exchanged system to system. PDFs, Word files, images and emailed invoices will not count |
| Network | Peppol, using certified Access Points in a four-corner model |
| HMRC’s role | Governance as the UK Peppol Authority, taking over from the current arrangement. Invoices are not submitted to, validated by or routed through HMRC |
| What doesn’t change | When a VAT invoice is required, and what it must contain |
| Penalties | Intended to use the existing VAT invoicing penalty framework, with detail to follow |
How does the UK Peppol model work?
Peppol uses a four-corner model. Supplier and buyer each connect to the network through a certified Access Point, usually provided by their finance software or an e-invoicing provider. Each Access Point delivers to the other, so you don’t need a separate connection to every trading partner. It works a lot like email: one connection reaches everyone else on the network.
- 1Supplier's finance systemOracle, SAP, Workday, Dynamics, NetSuite, Sage…
- 2Supplier's Access PointCertified and accredited provider
- 3Buyer's Access PointCertified and accredited provider
- 4Buyer's finance systemAny ERP or AP platform
Invoices travel directly between Access Points. HMRC governs the network but doesn't receive invoice copies just because they travel over Peppol.
Many countries have chosen a clearance model, where every invoice passes through a tax authority platform before it is valid. The UK has not. That makes UK compliance mainly a question of exchange and data quality, not real-time tax reporting, at least for now. Alongside the roadmap, HMRC opened a separate consultation (closing 20 January 2027) on whether it should receive or access selected e-invoice data in future. It has stated that no decision has been made.
What counts as an e-invoice under the UK mandate?
Won't count from April 2029
- PDF invoices, even if emailed
- Word documents or spreadsheets
- Scanned or photographed paper
- Invoices keyed into a supplier portal by hand
Will count
- Structured data, readable by both systems without re-keying
- Exchanged through certified Peppol Access Points
- Meets the UK data and validation rules HMRC will publish
- Uses an accepted UK business identifier
This is the part many organisations underestimate. If your AP team relies on a scanning or OCR service to read PDF invoices, that route will be out of step with the mandate for in-scope invoices. Your suppliers will be sending structured data instead, so your systems need to receive and process it.
Who is in scope?
| In scope from April 2029 | Generally out of scope |
|---|---|
| Domestic B2B VAT invoices between VAT-registered persons | Most B2C transactions |
| Supplies to the public sector (B2G) | Supplies to non-VAT-registered businesses |
| Non-established, UK VAT-registered suppliers making domestic supplies to VAT-registered customers | Certain cross-border transactions |
| Businesses granted a digital exclusion exemption (details due by April 2028) |
Businesses outside the mandate can still use e-invoicing voluntarily, and many will, because their customers will expect it.
UK e-invoicing timeline: the road to April 2029
- 28 Oct 2026 · You are hereRoadmap publishedPlus a consultation on future digital reporting, closing 20 January 2027
- Spring 2027Technical consultation and enabling legislationStandards and Access Point certification
- Summer 2027Consultation on point-of-sale software standardsAimed at electronic sales suppression
- Autumn 2027Guidance on EDI and existing B2B networksHow they will work alongside Peppol
- Oct 2027 – Apr 2028Detailed requirements publishedScope, exemptions, technical standards, business identifiers, software-provider obligations
- By Apr 2028Digital exclusion and taxpayer obligations confirmedAfter this, changes are to be kept to a minimum
- Summer 2028Readiness testing beginsWith software providers
- Winter 2028Governance, onboarding and infrastructure fully available
- 1 Apr 2029Mandate takes effect
Dates as set out in HMRC's October 2026 roadmap. Check GOV.UK for updates as detailed requirements are published.
Two dates matter most for planning:
- April 2028. That is when the rules are expected to settle. Your design should be ready to finalise then, not to start.
- Summer 2028. That is when readiness testing begins. Your provider, master data and processes need to be ready to test with real trading partners.
What’s still open: the UK-specific technical specification (most observers expect it to build on Peppol’s existing invoice specification, which is based on the European standard EN 16931), the accepted UK business identifiers, how EDI will co-exist with Peppol, and whether HMRC will later receive any invoice data.
Oracle, SAP, Workday or Dynamics: which connection route should you use?
Whether you run Oracle Fusion or E-Business Suite, SAP S/4HANA or ECC, Workday Financials, Microsoft Dynamics 365, NetSuite, Sage or a mix after acquisitions, the questions are the same. The mandate defines what must be exchanged and how it travels, not which system produces it. There are four common ways to connect:
| Connection route | How it works | Good fit when | Watch out for |
|---|---|---|---|
| ERP’s native e-invoicing capability | Your ERP vendor’s own e-invoicing service or certified partner connects you to Peppol | A single, modern ERP with a vendor roadmap for UK Peppol | Timing of UK accreditation; coverage across all entities and legacy instances |
| AP automation or e-invoicing provider | A specialist platform acts as your Access Point and integrates with one or more ERPs | Several ERPs, high invoice volumes, or existing AP automation | Integration effort, duplicated validation logic, contract terms |
| Existing EDI or B2B network | Your current EDI provider bridges to Peppol | Large EDI estates in retail, logistics or manufacturing | Wait for HMRC’s autumn 2027 guidance on how EDI will co-exist |
| Direct Access Point | You operate or contract an Access Point directly | Very large organisations with in-house integration capability | Certification, security and service obligations sit with you |
Many groups will end up with a hybrid. What matters is that the decision is made deliberately, on cost, risk and how much of your estate each route covers, rather than inherited from whichever vendor raises it first.
What changes in accounts payable and accounts receivable?
The mandate touches both sides of the ledger. Here’s how the flows change, in any system.
- 01ReceiveStructured invoice arrives via your Access Point
- 02ValidateFormat, mandatory fields, identifiers
- 03MatchTo PO and receipt, within tolerances
- 04Resolve exceptionsPrice, quantity, missing PO
- 05Post and payWith the structured invoice retained as the record
- System / automated
- Control point
- People decision
- 01BillBilling event or sales order in the ERP
- 02EnrichCustomer identifier, tax codes, PO reference
- 03TransformTo the UK Peppol specification
- 04SendVia your Access Point
- 05TrackDelivery status and rejections
- System / automated
- Control point
- People decision
And here is where to look in your own estate:
| Area | What to check, in any ERP | Typical gap |
|---|---|---|
| Supplier and customer master data | Legal names, VAT numbers, and the UK business identifier once confirmed | Duplicates, missing VAT numbers, inconsistent records after acquisitions |
| AP intake | How many invoices arrive as PDF or paper, and through how many inboxes and portals | Several intake channels, each with its own workaround |
| PO and matching | Share of invoices with a valid PO; match tolerances | High non-PO volumes; retrospective POs |
| Tax determination | VAT codes, reverse charge (including construction), rate mapping | Codes that can’t be mapped reliably to structured invoice fields |
| AR billing | Whether customer PO references and identifiers are captured at source | Billing data held in spreadsheets or side systems |
| Integration | Which entities, instances and legacy systems issue or receive invoices | Unknown long tail of systems that also raise invoices |
| Controls and records | Approval evidence, audit trail, how the legal invoice record is kept | The PDF treated as the master record |
Don’t automate the mess: apply SECAR
E-invoicing is tempting to treat as a connector project: buy an Access Point, map fields, go live. That works at the network edge, but it leaves every upstream problem in place: duplicate suppliers, invoices without POs, unmapped tax codes, and inboxes nobody owns. Structured data makes bad master data fail faster.
We use the SECAR sequence so the mandate becomes a transformation opportunity rather than a compliance cost:
- 01SimplifyOne intake route for in-scope invoices; fewer approval layers
- 02EliminatePDF and paper channels, retrospective POs, shadow trackers
- 03ConsolidateClean supplier and customer masters, identifiers, tax codes
- 04AutomateAccess Point integration, validation and matching
- 05RelocateStable exception handling to your shared service team
- People decision
- Control point
- System / automated
Done in that order, the same programme that delivers compliance can also raise first-time match rates, reduce manual processing in AP and AR, and give earlier visibility of disputes.
A UK e-invoicing readiness plan: people, process, technology and control
| Now to spring 2027 | Spring 2027 – April 2028 | April 2028 – April 2029 | |
|---|---|---|---|
| People | Name an executive owner and global process owners for P2P and O2C | Engage key suppliers and customers; plan training | Supplier onboarding campaign; train AP, AR and helpdesk |
| Process | Baseline invoice volumes by channel, entity and supplier | Design future-state intake, exception and dispute processes | Dress rehearsals; cut over intake channels |
| Technology | Inventory every system that issues or receives invoices | Choose a connection route; contract providers with UK accreditation in mind | Build, integrate and join readiness testing from summer 2028 |
| Control | Assess master-data quality and VAT code mapping | Define validation rules, the record-keeping approach and evidence | Go-live controls, monitoring and post-go-live reconciliation |
How does the UK compare with e-invoicing in Europe?
The UK is joining a wave of mandates across Europe, several of them also built on Peppol. For groups trading across borders, a single design that can extend to several countries is worth far more than a series of country-by-country fixes.
- Country with a B2B e-invoicing mandate in force or legislated
- United Kingdom
Illustrative and selective. Requirements and dates vary by country and change over time, so always check the current local rules.
| Country | Model | Status |
|---|---|---|
| Belgium | Peppol-based, no clearance | Mandatory for domestic B2B since January 2026 |
| Germany | Structured e-invoices (EN 16931-based formats) | Receiving required since 2025; issuing phased in from 2027 |
| France | Platform-based with e-reporting | Phased introduction from September 2026 |
| Poland | National clearance platform (KSeF) | Phased introduction from 2026 |
| United Kingdom | Peppol, four-corner, no clearance | Mandatory from 1 April 2029 |
The bottom line
The UK has chosen a model that is interoperable, decentralised and familiar, which makes it more achievable than many international mandates. The deadline is fixed, the rules will settle by April 2028, and testing starts in summer 2028.
Organisations that start now can treat e-invoicing as a lever for cleaner master data, fewer manual touches and better-controlled P2P and O2C processes. Those that wait will be buying whatever connector is available in 2028, fitted on top of whatever processes they happen to have.
Sources: HMRC e-invoicing digital reporting consultation (GOV.UK); KPMG: UK publishes B2B e-invoicing roadmap; Sovos: UK publishes e-invoicing roadmap. This article is general guidance, not tax or legal advice. Requirements will be confirmed in HMRC’s detailed specifications.
Frequently asked questions
When does UK e-invoicing become mandatory?
From 1 April 2029. HMRC confirmed the date in its e-invoicing roadmap published on 28 October 2026.
Which e-invoicing standard has the UK chosen?
Peppol. Invoices will be exchanged through certified Peppol Access Points using a four-corner model, with limited UK-specific requirements that HMRC will publish between October 2027 and April 2028.
Will HMRC receive copies of my invoices?
Not under the 2029 mandate. Invoices are not submitted to, validated by or routed through HMRC. A separate consultation, closing 20 January 2027, asks whether HMRC should access selected invoice data in future; no decision has been made.
Does a PDF invoice sent by email still count?
No, not for in-scope transactions. PDFs, Word documents, images and emailed invoices will not meet the mandate. Invoices must be structured data that systems can exchange and process without re-keying.
Who is in scope of the UK e-invoicing mandate?
VAT-registered businesses issuing VAT invoices to other VAT-registered businesses or the public sector, including non-established businesses registered for UK VAT. Most B2C sales, supplies to non-VAT-registered customers, certain cross-border supplies and businesses with a digital exclusion exemption are generally out of scope.
What is a Peppol Access Point?
A certified service provider that connects your finance system to the Peppol network. Most businesses will use one provided by their ERP vendor, AP automation platform or e-invoicing provider rather than running their own.
Do I need to replace my ERP to comply?
No. The mandate defines what must be exchanged and how it travels, not which system produces it. The main decisions are your connection route, the quality of supplier and customer master data, VAT code mapping, and how AP and AR handle structured invoices and exceptions.
When should we start preparing?
Now. Detailed rules are expected to settle by April 2028 and readiness testing begins in summer 2028, so master-data clean-up, system inventory and route selection should be well under way during 2027.
Published 5 November 2026 · Simplabs Limited