The United Kingdom’s e-invoicing mandate is confirmed, but the detailed playbook is still being written.
At the Autumn Budget in November 2025, the government confirmed that all value-added tax (VAT) invoices in B2B and B2G transactions must be issued as e-invoices from April 1, 2029. This followed a 12-week consultation run jointly by His Majesty’s Revenue and Customs (HMRC) and the Department for Business and Trade. Stakeholder collaboration began in January 2026, and the technical standards and roadmap are expected at Budget 2026.
Unlike European Union (EU) member states preparing for ViDA (VAT in the Digital Age), the UK is developing a domestic e-invoicing framework entirely outside the EU regulatory structure since Brexit. For finance leaders managing UK operations alongside EU entities, that means two separate compliance tracks.
Key takeaways
- The UK government confirmed mandatory B2B and B2G e-invoicing starting April 1, 2029 at Autumn Budget 2025, though upcoming developments may define a phased roll-out.
- The 2029 mandate requires structured, machine-readable invoices, so PDFs, Word files, HTML and images are explicitly excluded from the definition of e-invoicing.
- Real-time reporting to HMRC is not part of the initial 2029 requirements, as there was a deliberate government decision to phase complexity.
- Technical standards and an implementation roadmap are expected at Budget 2026; businesses can use the interim to monitor these publications and begin data readiness work now.
The UK e-invoicing landscape at a glance
Three overlapping digital tax and invoicing frameworks sit alongside each other in the UK. They’re related, but they aren't the same thing. Here’s where they overlap and stay separate, according to UK government bulletins and publications:
If your team is already using MTD-compatible software and invoicing the NHS via PEPPOL, you have a head start, but neither automatically satisfies the 2029 requirements.
What’s confirmed for the UK e-invoicing mandate
The mandate’s core elements – including deadline, scope and definition – are locked in. Here’s what finance teams can treat as settled.
The April 2029 deadline
From April 1, 2029, all VAT invoices in B2B and B2G transactions need to be issued as e-invoices. Consumer transactions (B2C) are not currently expected to fall within scope.
The mandate followed a joint HMRC and Department for Business and Trade consultation that ran from February 13th to May 7th, 2025.
What “e-invoice” means under the UK framework
Most UK businesses already send invoices digitally via email, portals or accounting software. But under the 2029 mandate, that doesn’t count.
The UK definition explicitly excludes PDF invoices (even if sent digitally), Word or Excel files, HTML invoices and optical character recognition-scanned images (OCR).
What does qualify are invoices that can be processed automatically by the recipient’s financial system without anyone needing to open, read or re-enter anything. If a human has to look at the invoice for it to be useful, it’s not an e-invoice under this framework.
The specific format hasn’t been confirmed yet; that’s expected at Budget 2026.
What isn’t included in the 2029 mandate
What the government chose to leave out is just as telling as what’s in.
Real-time transaction reporting to HMRC is not part of the initial 2029 requirements. The government deliberately focused the first phase on structured invoice exchange between businesses, not on building a government clearance model where HMRC sits in the middle of every transaction.
The UK’s initial model is likely to be a decentralized exchange framework where businesses send structured invoices to each other through the network, and HMRC is not a real-time intermediary. The government has indicated reporting may be explored later, but it’s explicitly out of scope for 2029.
What’s still being developed for UK e-invoicing
The destination is clear, but the route is still being mapped. These are the open questions that will shape implementation planning for the UK’s e-invoicing mandate.
Technical standards and format
The format your invoices will need to follow hasn’t been published yet.
The government committed to publishing technical standards at Budget 2026. As of mid-2026, businesses do not yet have confirmed:
- The specific XML schema or format required (though PEPPOL UBL and the emerging PINT UK specification are likely candidates)
- Whether a single standard or multiple will be permitted
- Platform requirements for invoice exchange
The consultation outcome made clear that the government wants interoperability. As a result, whichever software provider a business selects, it needs to be able to exchange invoices with any other UK VAT-registered business.
Implementation roadmap and scope
The phased rollout details are still in active design.
Working groups began shaping the framework through a co-design process in January 2026. The roadmap will cover any anticipated phased approach, size-based thresholds and the transition timeline to April 2029.
The government has indicated the mandate will apply to VAT-registered businesses, but the precise scope – whether it covers all VAT invoices or only those above certain thresholds – is still being refined.
Making Tax Digital: How it relates to e-invoicing
Finance teams often conflate Making Tax Digital with mandatory B2B e-invoicing, but they’re two separate requirements and the distinction matters for planning.
MTD for VAT requires businesses to keep digital records and submit VAT returns using HMRC-compatible software. It’s about how you report VAT to HMRC.
E-invoicing is about the format of the invoice itself, defining how it’s created, transmitted and received between trading partners.
For example, if your team generates a PDF invoice, emails it to a customer and records the transaction in MTD-compatible software, you’re MTD compliant. But that PDF is not an e-invoice under the 2029 mandate. The invoice itself needs to be in a structured, machine-readable format that flows between financial systems without manual intervention.
If your team is treating MTD compliance as a proxy for e-invoicing readiness, the 2029 mandate introduces a layer of change that hasn’t been priced into your planning yet.
The current state of B2G e-invoicing in the UK
E-invoicing isn’t entirely new in the UK. The public sector has been doing it for years – and that foundation matters for what’s coming.
PEPPOL in the UK public sector
The UK’s public sector is already operating on structured e-invoicing infrastructure.
NHS England already requires suppliers to submit structured electronic invoices via the PEPPOL network, using the PEPPOL BIS 3.0 format through certified access points. The Crown Commercial Service supports broader PEPPOL adoption across central government procurement.
These businesses are already issuing structured, machine-readable invoices using UBL (Universal Business Language) through a four-corner model.
What PEPPOL means for the UK’s 2029 mandate
Existing PEPPOL adoption gives the UK a technical head start, but it’s not the full picture.
Given that PEPPOL is already operational for B2G and uses structured XML formats, it’s widely expected to influence the B2B standard. But “widely expected” doesn’t mean it’s confirmed. The government hasn’t formally mandated a specific format for the 2029 B2B framework. Treat this as informed expectation, not settled policy.
Businesses already issuing PEPPOL-compliant invoices to public sector bodies are ahead of the curve. But extending that capability from a subset of public sector customers to every B2B customer touches invoice generation workflows, customer data management, onboarding processes and potentially your ERP configuration. The technical standard may be familiar – the scope of rollout is a different challenge.
How the UK mandate differs from EU e-invoicing frameworks
This section is particularly relevant for international businesses managing UK operations alongside EU entities.
Post-Brexit means no ViDA obligation
The UK’s exit from the EU created a clean regulatory split on e-invoicing.
The UK is not subject to ViDA. If your business has VAT-registered entities in EU countries, those entities need to comply with ViDA and country-specific mandates separately. UK operations sit under the domestic UK framework only.
No centralized clearance model (at least initially)
The structural difference between the UK and most EU mandates is significant.
Italy’s SDI and Poland’s KSeF operate as centralized government clearance hubs. This means every invoice passes through a government system before it’s legally issued. France is building an approved platform model with government oversight through Plateforme de Dématérialisation Partenaire (PDPs).
The UK has taken a different path. The expected model is a decentralized exchange network – closer to how PEPPOL already works – where the tax authority isn’t an intermediary. For systems teams, that means the UK integration architecture will look different from what you’ve built for Italian, Polish or French compliance.
How the UK compares to other European mandates
Here’s how the UK’s approach stacks up against the three most referenced EU mandates.
What finance teams should do now
While 2029 feels far away, it’s closer than you think when you map out the actual work. The technical standards haven’t landed, but significant preparation doesn’t depend on the final standard. We recommend businesses start looking at the changes they need to make and developing a plan now.
Understand your invoicing landscape
The gap between current practice and the structured format requirement is the change you need to evaluate here. If you already invoice NHS or government bodies through PEPPOL, document what’s already in place, including your access point, format and ERP integration. This is your technical baseline, and it can help you determine what (if anything) needs to be changed.
- Map current invoice issuance; identify what share are PDF, what share use structured formats (EDI, PEPPOL) and what share involve manual processes like email or post
- Identify which customers already require PEPPOL invoices today (NHS, central government) and document the access points, formats and workflows in place
- Document your current ERP or accounting software, version and any existing e-invoicing or EDI modules already active
- Calculate total outbound and inbound invoice volume by format type to size the scope of the transition
Engage your ERP vendor
Talk with your vendor about its game plan for UK e-invoicing. If your vendor hasn’t started planning, that’s a data point worth noting now.
- Confirm your ERP vendor is actively tracking the UK e-invoicing mandate and has assigned resources to it
- Ask for its planned compliance roadmap timeline, including when it expects to publish it after the Budget 2026 standards land
- Confirm whether PEPPOL invoice generation and receipt are available in your current system or require additional modules
- Ask what lead time your vendor typically needs between standard publication and feature availability – this shapes your own implementation timeline
Monitor Budget 2026
Budget 2026 is the trigger event for concrete technology decisions so make sure team members are aware that this is when more information will be coming in late 2026. As of writing, the standards haven’t yet been set. Ideally, have someone in charge of distributing the information across finance and IT once the decision lands.
- Set a calendar alert for Budget 2026; this is when the technical standards and implementation roadmap are expected
- If you have EU entities, confirm a separate ViDA readiness process is in place; UK compliance does not cover EU obligations
- Track outputs from HMRC’s stakeholder working groups and PEPPOL Authority updates for early signals on format and platform decisions
Clean your customer and supplier data
Structured invoice exchange depends on accurate data. Data quality issues invisible in PDF workflows become blocking errors in structured invoice workflows.
- Audit customer VAT numbers for completeness, accuracy and alignment with HMRC records
- Audit supplier VAT numbers, registered addresses and legal entity names against official registries
- Identify accounts where invoice delivery is handled informally (including email attachments, portal uploads and post), as these will need structured delivery paths
- Flag any data fields maintained manually in spreadsheets or outside your ERP that would need to be brought into structured workflows
Common questions and misconceptions
Since the e-invoicing mandate for the UK is still new, it makes sense that there are typically questions and even misconceptions. These are the most common misconceptions and how they’re not quite accurate.
Stay up-to-date as new developments emerge
The UK’s e-invoicing framework is still actively being shaped through stakeholder working groups, and the technical standards landing at Budget 2026 will change the picture significantly.
Keep tracking HMRC updates, engage your vendors early and revisit your readiness assessment as new details emerge. What applies to your business today could look different in six months.
