.svg)
In June 2026, the UK government confirmed that structured electronic invoicing will be mandatory for B2B VAT transactions from April 2029. It also named Peppol as the core interoperability network that businesses will need to connect to.
For most finance teams, this is still on the horizon. But the decisions made now — on systems, integrations, and AP processes — will determine how straightforward or disruptive 2029 is in practice. This article covers what the mandate actually involves, who it affects, and what preparation looks like in realistic terms.
The UK e-invoicing mandate was confirmed through HMRC's Tax Update 2026: Simplification, Modernisation and Fairness policy paper. The key commitments are:
The mandate applies to businesses issuing and receiving VAT invoices in B2B and B2G transactions. Businesses already supplying the NHS and other public sector bodies under existing procurement rules will be familiar with the Peppol BIS 3.0 format — the mandate extends that logic to private sector B2B trade.
This is worth being specific about, because the term is frequently used loosely.
A structured e-invoice is not a PDF sent by email. A PDF, even one generated by accounting software, is a human-readable document. The receiving business still has to extract the data manually or via OCR to get it into their AP system.
A structured e-invoice is a machine-readable data file, built to the EN 16931 standard, that can be received, read, and processed automatically by the recipient's system without any manual extraction step. The data fields, supplier, buyer, invoice number, line items, amounts, tax, payment terms, are standardised so that systems on both sides can communicate directly.
The practical effect of the mandate is to make this structured exchange the legal minimum for VAT invoices, rather than an optional upgrade.
Peppol (Pan-European Public Procurement On-Line) is the interoperability framework that allows businesses using different software and different access point providers to exchange structured documents reliably. It already operates across more than 40 countries, including Belgium (mandatory from January 2026), Singapore, and the UAE.
The four-corner model works like this: the sender connects to their own certified Peppol access point provider, which routes the invoice across the Peppol network to the recipient's access point provider, which delivers it directly into the recipient's system. Neither party needs to be on the same platform. They only need to be connected through certified providers.
For UK businesses, connecting to the Peppol network means working with a certified access point provider, which may be their AP software provider, their ERP vendor, or a specialist intermediary.
The April 2029 mandate applies to UK VAT-registered businesses issuing and receiving VAT invoices in B2B and B2G transactions. That covers the vast majority of UK businesses that currently issue VAT invoices.
Northern Ireland faces a separate consideration. It remains within the UK VAT system but aligns with EU VAT rules for goods. The EU's ViDA (VAT in the Digital Age) initiative introduces its own e-invoicing and e-reporting requirements, with goods shipped between Northern Ireland and the EU likely subject to ViDA obligations from July 2030. Businesses operating across that border should assess both timelines.
Public sector suppliers are already partially covered. Public bodies must accept EN 16931-compliant e-invoices under existing procurement rules, and NHS suppliers have been sending structured Peppol invoices for some time. For those businesses, the 2029 mandate extends existing practice to all their B2B transactions.
For most mid-market businesses with no current Peppol connection, April 2029 represents a hard deadline for having structured invoice exchange in place. Three years sounds like ample time. It is not, particularly for businesses running on ERP systems that require integration work or that are considering a system change before the mandate arrives.
The HMRC co-design process is ongoing, and full technical specifications are expected following the Budget 2026 roadmap. But there are concrete steps finance teams can take now, before those specifications are finalised.
The first question is whether your current systems can generate and receive structured e-invoices. This is not a software version question. It is a data structure question. Can your accounting or ERP system output an EN 16931-compliant XML invoice? Can it receive one and post it without manual intervention?
For many mid-market businesses using legacy AP processes, the honest answer is no. The invoice data exists in the system, but extracting it in a structured format, or ingesting an incoming structured invoice automatically, requires either a capability that does not currently exist in the system or an integration that has not been built.
Connecting to Peppol requires a certified access point provider. The question for most businesses is whether that comes via their ERP vendor, their AP automation provider, or a separate integration.
If your AP platform already integrates natively with Peppol, or your ERP vendor has a certified access point offering, the path is relatively straightforward. If neither is true, the integration work is the critical path for 2029 compliance.
The core architecture of the mandate is confirmed: structured e-invoices, Peppol network, April 2029. The technical details still being worked through are around specific format requirements and enforcement. But businesses that wait for final specifications before starting to assess their readiness will find themselves under time pressure in 2027 and 2028 when implementation queues at ERP vendors and access point providers fill up.
The e-invoicing mandate will require structured invoice exchange. But the same infrastructure that supports compliance — machine-readable invoices received directly into the AP system — is also what enables automated processing, automated matching, and straight-through payment. Businesses that implement AP automation to comply with the mandate will also be eliminating manual data entry, reducing exceptions, and improving processing speed as a direct consequence.
The mandate is a regulatory floor. What most finance teams will discover, once they have structured invoices flowing automatically into their system, is that the operational benefits exceed the compliance requirement.
The UK is not the first country to mandate e-invoicing, and the pattern from other markets is instructive.
Italy introduced mandatory B2B e-invoicing through the SdI clearance model in 2019. Early experience showed significant operational disruption for businesses that treated it as a last-minute compliance exercise, and material efficiency gains for businesses that used it as a trigger to modernise AP.
Belgium made B2B e-invoicing mandatory from January 2026, using the Peppol network — the same model the UK is adopting. Businesses that had already integrated Peppol-connected AP systems found the transition straightforward. Those that had not faced a compressed implementation timeline.
France, Germany, and Spain are all implementing or planning B2B e-invoicing mandates through 2026 to 2028 under ViDA and national programmes. The direction across Europe is unambiguous: structured invoice exchange is becoming the standard.
The UK's April 2029 deadline is later than most comparable European markets. That gap is an advantage if it is used for preparation, not a reason to defer.
The e-invoicing mandate changes the AP landscape in one specific way: it makes structured invoice receipt the default rather than the exception. Today, most UK businesses receive a mix of PDFs, scanned documents, paper invoices, and the occasional structured file. Processing all of those requires some combination of manual entry, OCR, and exception handling.
From 2029, all VAT invoices in scope will arrive as structured data. The question is what happens when they do.
If the receiving business has an AP system that can ingest structured invoices and process them automatically — matching against purchase orders, routing for approval, posting to the ERP — then each invoice is processed without manual intervention. The mandate creates the conditions for straight-through processing at scale.
If the receiving business has the structured invoice arriving but no automation to process it, the data quality is better but the processing burden is unchanged. The invoice still needs to be matched, coded, and approved manually.
Dost integrates with SAP, Microsoft Business Central, Sage (200, Intacct, X3), and Oracle in real time. Structured invoices received through Peppol-connected channels can be processed automatically through the full AP workflow: extraction, validation, matching, approval routing, and ERP reconciliation. The mandate provides the structured input. The automation platform handles everything that follows.
See what your AP process could look like with structured invoice data at the input. Use Dost's ROI calculator to estimate your savings based on current invoice volume and processing costs.
Yes. The UK government confirmed mandatory structured e-invoicing for B2B VAT transactions from April 2029 in the HMRC Tax Update 2026: Simplification, Modernisation and Fairness policy paper published in June 2026. Peppol was confirmed as the core interoperability network. Full technical specifications and the detailed implementation roadmap were expected to follow Budget 2026.
It applies to UK VAT-registered businesses issuing and receiving VAT invoices in B2B and B2G transactions. The 2029 scope is invoice exchange only — not real-time reporting to HMRC. Businesses in Northern Ireland that trade goods with the EU should also monitor the EU's ViDA timeline, which introduces separate e-invoicing and e-reporting requirements, likely from July 2030 for cross-border goods transactions.
Peppol is an interoperability framework that allows businesses using different software and platforms to exchange structured electronic documents reliably. The UK government named it as the core network for the 2029 mandate. In practice, this means UK businesses will need to connect to the Peppol network through a certified access point provider — either via their ERP vendor, their AP platform, or a specialist intermediary. Peppol already operates in Belgium, Singapore, the UAE, and more than 40 other countries, so UK implementation follows a well-established model.
The UK e-invoicing mandate is confirmed, the network is confirmed, and the deadline is confirmed. April 2029 is further away than most compliance deadlines feel when they are first announced, and that creates a temptation to defer serious preparation.
The businesses that will find 2029 straightforward are the ones that use the next two years to assess their AP infrastructure, identify their Peppol connectivity path, and put structured invoice processing in place before the deadline rather than in response to it.
For finance teams that automate their AP process now, the mandate is not a disruption. It is the point at which the efficiency case for AP automation becomes a regulatory requirement — and the benefits that were already there become unavoidable for the businesses that have not yet captured them.
Calculate what an automated AP process connected to structured e-invoicing could save your team.
