UK E-Invoicing: Build, Buy or Extend Your Finance Stack?

The UK’s e-invoicing mandate is no longer a question of if. From April 1, 2029, every VAT invoice covering B2B and B2G transactions must move through structured, machine-readable channels rather than an emailed PDF.

HMRC confirmed Peppol as the UK’s interoperability network on June 23, 2026, closing the biggest open question finance leaders had been waiting on. That certainty starts a clock: as with earlier European mandates, implementation capacity tightens as the deadline nears, and businesses that prepare early end up with more options than those who wait.

The question is no longer whether to prepare, but how. Three paths are on the table: build in-house, buy a dedicated solution, or extend systems already in place. Each has a different cost profile, timeline, and risk of stalling midway through 2029.

Key takeaways

• The mandate takes effect April 1, 2029, covering all B2B and B2G VAT invoices.
• Peppol is confirmed as the interoperability network: a four-corner model, no real-time HMRC reporting at launch.
• Budget 2026 publishes the detailed technical roadmap; core scope and timeline are already locked.
• Businesses choose between building compliance internally, buying a dedicated platform, or extending an existing ERP system.
• The right choice depends on how deeply e-invoicing needs to sit inside existing processes.

What’s actually confirmed

The network decision, part of the government’s Tax Update 2026, follows a joint HMRC/Department for Business and Trade consultation held from February 13 to May 7, 2025.

The UK will use a decentralised four-corner model: suppliers and buyers exchange invoices through their own providers or Peppol access points, and HMRC won’t receive invoice data in real time at launch.

This mirrors Belgium’s 2026 approach and builds on infrastructure the UK’s public sector already runs. NHS Supply Chain has required structured invoices via Peppol BIS 3.0 since 2022, so the network isn’t new to UK business; mandatory economy-wide adoption is.

Still open: the specific UK invoice specification, accreditation requirements for service providers, and whether smaller businesses get a phased start.

OpenPeppol set up a dedicated UK working group in late 2025 to define that baseline specification; the roadmap arrives at Budget 2026, making 2027 and 2028 the real preparation window.

PDFs sent by email or portal will not meet the coming definition of e-invoicing. The requirement is structured, system-readable data, and that’s where most of the compliance gap sits.

Three paths finance teams are weighing

Build: what it actually takes

Building in-house gives a finance and IT team full control over how e-invoicing connects to their processes, which matters most where approval chains are unusual, ERP configurations are heavily customised, or data residency requirements are strict.

Peppol connectivity is not a one-time build. Specifications evolve, accreditation applies to access point connections, and every future regulatory change becomes the internal team’s job to track and implement.

For businesses that have built this elsewhere in Europe, ongoing maintenance has proven to be the real cost. Build suits businesses with unique requirements and capacity to spare for the years after launch.

Buy: a dedicated e-invoicing platform

Buying a dedicated solution is the fastest route to compliance for most businesses: specialist Peppol access point providers handle format conversion, certification, and network connectivity, so a business plugs in without building that expertise.

The trade-off surfaces after go-live: a standalone tool outside the core finance stack becomes another system to reconcile and another integration point whenever the ERP changes.

Businesses needing only outbound or inbound e-invoicing find that a fair price for speed. Those already juggling disconnected point solutions take on more fragmentation with each new one.

Extend: adding e-invoicing to the stack you already run

For many mid-size and enterprise finance teams, the more pragmatic path is extending systems already in place: a business running SAP, another ERP, or a broader finance platform can add Peppol and e-invoicing as a module, meeting the 2029 requirement without a new standalone system.

This is the category where platforms like Doxis sit. Doxis builds e-invoicing and Peppol connectivity for SAP into its broader SAP-integrated invoice and order management capability, so it becomes a feature of the ERP a finance team already runs, rather than a separate product to bolt on and reconcile.

That’s the core appeal of extending: e-invoicing joins a system finance teams already use daily, with one login and one place to check status. It’s rarely the fastest option to stand up, but it’s often the one with the lowest long-term operational overhead.

A five-question framework

Score the decision against these factors before defaulting to whichever option looks cheapest on paper:

1. How deep does e-invoicing need to sit in your workflows? Data flowing directly into approval chains, VAT reporting, and payment runs usually favours extending over bolting on a separate tool.
2. How much in-house development capacity can you spare this year and every year after? Building only pays off if a team commits to maintaining it through future regulatory changes.
3. How many countries and formats are already in scope? Businesses managing mandates in Germany, France, or elsewhere in the EU get more value from a multi-jurisdiction platform than a UK-only solution.
4. What’s your realistic timeline? A 2027 target leaves room to build or extend deliberately; late 2028 will need the speed a buy option offers.
5. How much vendor sprawl can your team absorb? Every standalone tool adds a reconciliation point. Teams managing disconnected systems get more value from consolidating into one platform.

What to do before Budget 2026

Enough is confirmed to start planning now. Reviewing whether current invoicing already produces structured, Peppol-compliant data is a reasonable first step. Most PDF-based processes do not.

Mapping which systems could be extended, which processes need a new build, and which gaps a bought solution would cover gives finance and IT teams a head start once the roadmap lands.

Businesses that treat 2026 and 2027 as a planning window will have real choices left by 2029. Those waiting for certainty on every point will likely find their options, and their preferred vendors’ capacity, considerably narrower by the time they start.