Electronic invoice in United Kingdom
Public sector acceptance of EN 16931-compliant invoices with growing Peppol adoption
The United Kingdom has moved from voluntary e-invoicing to preparing a national mandate. From April 2029, every document that is a VAT invoice under UK law will have to be issued and received in structured electronic form. On 23 June 2026 HMRC confirmed that Peppol will be the core interoperability network — which settles the biggest open question and points at a classic four-corner architecture.
Two things follow that are unusual for a mandate of this size. The model is decentralised, with no clearance — no invoice will be routed through a government platform for approval. And real-time reporting is explicitly not being introduced alongside it in 2029. What remains genuinely undecided is set out under Settled and unsettled; the detailed roadmap is due with Budget 2026.
A long stretch of receiver-side obligations, then a single national mandate announced in 2025 and dated in 2026.
The Public Procurement (Electronic Invoices etc.) Regulations 2019 take effect for England, Wales and Northern Ireland, with sub-central authorities and utilities following in 2020. Scotland introduced the equivalent duty through its own regulations on the same dates.
Suppliers to NHS bodies move to Peppol-compliant e-invoicing under procurement and contractual requirements. See The NHS exception.
Section 67 implies into every covered public contract a term that the authority must accept and process an undisputed electronic invoice in the required structured format — and the parties cannot contract out of that supplier right.
The government announces at Budget 2025 that all VAT invoices are to become electronic from 2029.
HMRC confirms Peppol as the core interoperability network for UK e-invoicing and specifies April 2029, as part of the Tax Update 2026: Simplification, Modernisation and Fairness policy paper.
HMRC has said a detailed roadmap will be published alongside Budget 2026, setting out when the key design elements and regulatory requirements will be released. This is the next moment anything becomes concrete.
A single announced date rather than a phased distribution by company size — though transitional provisions, exclusions and special regimes have not been published.
Commentary predicting large businesses in April 2029 and smaller ones in April 2030 is inference, not policy. What the government has announced is a single date. Whether phasing appears at all will be visible in the Budget 2026 roadmap — treat any staged UK timetable published before then as a forecast.
With three years to go and a roadmap still pending, the most useful thing a page like this can do is separate what has actually been decided from what has not.
April 2029. All VAT invoices in scope. Peppol as the core interoperability network. A decentralised model, not clearance. No real-time reporting at launch. Primarily B2B and B2G.
A roadmap at Budget 2026.
Mandatory formats and the required identifier scheme. Territorial reach for exports, imports and non-established businesses. Exemptions and transitional rules. Whether phasing applies.
The penalty regime, and any regulatory framework for software and service providers.
"Core network" is also a deliberately loaded phrase. It leaves room for legacy systems, sector-specific networks, direct integrations and potentially alternative channels that meet interoperability requirements — and the government has said it will keep discussing the role of legacy systems that cannot interoperate. Peppol confirmed does not mean Peppol only.
The scoping test is worth stating precisely because it is unusual: the mandate attaches to the document being a VAT invoice under UK law, not to a turnover threshold or a sector. That is why ordinary consumer sales drop out — not because B2C was carved out, but because no VAT invoice is required for them in the first place.
Until 2029 the UK public sector runs on a receiver-side duty. Contracting authorities must accept and process an undisputed invoice conforming to the European standard; suppliers may still send paper, a PDF or use another agreed channel if the buyer accepts it.
The Procurement Act 2023 sharpened this from 24 February 2025. Section 67 implies a term into every covered public contract requiring the authority to accept and process an undisputed electronic invoice in the required structured format — and, importantly, the parties cannot contract out of it. A public buyer cannot refuse a correct EN 16931 e-invoice.
So the current position is asymmetric in the supplier's favour, and worth using. A supplier that wants to invoice a UK public body electronically has an enforceable right to do so — while a supplier that prefers PDF generally still can, right up until the 2029 mandate closes the option.
The NHS runs a stricter regime than the rest of UK B2G, and it is the one part of the country where Peppol is already effectively compulsory. NHS England procurement information requires suppliers to submit all invoices through a Peppol-compliant e-invoicing system, and the NHS Standard Contract for 2026/27 provides that the provider must submit invoices through the NHS e-Invoicing Platform or an alternative Peppol-compatible system.
Invoices are typically Peppol BIS Billing 3.0 enriched with GS1 identifiers, as part of a fully digital procurement process — which is why NHS work often needs GLN handling that the rest of the UK market does not.
The NHS requirement is a sector and contract obligation, not a general rule for UK B2G. The practical consequence of ignoring it is also contractual: a non-compliant invoice can be rejected, may not count as a valid invoice, can delay the start of the payment period and may need reissuing. NHS England states that non-compliant invoices are handled by NHS Shared Business Services.
Domestic B2B invoicing is currently unregulated as to format. PDF, XML, EDI and other electronic formats are all acceptable with the recipient's agreement and subject to the VAT conditions on authenticity of origin, integrity of content and legibility. That ends in April 2029 for anything that is a VAT invoice.
For B2C, a VAT invoice is normally not required for ordinary consumer sales, and retail receipts and other documents apply instead. The government has explicitly tied the future regime mainly to B2B and B2G, and no general B2C mandate has been announced.
The UK has kept to a decentralised design: the seller creates the invoice, the seller's service provider transmits it across the network, the buyer's service provider delivers it into the buyer's system, and no government platform sits between them as a mandatory clearance node. The June 2026 confirmation of Peppol as the core network points at classic four-corner architecture.
No invoice will need prior approval, a unique government number or a clearance code from HMRC before valid delivery to the buyer. Technical validation — structure, mandatory fields, identifiers, arithmetic — will almost certainly be applied by service providers, but that is not tax clearance.
On reporting, the government has been unusually clear: HMRC is considering future transmission of transaction data in real or near-real time, but has stated that real-time reporting will not be introduced at the same time as the 2029 mandate. It could be added later, once e-invoicing is widely used and technically robust. The right classification for April 2029 is therefore mandatory decentralised e-invoicing without CTC reporting at launch.
Today the UK imposes no invoice syntax. The VAT rules require the content, not the container: a valid VAT invoice may be paper, PDF, structured XML, or delivered by EDI or Peppol, provided authenticity of origin, integrity of content and legibility are ensured with the recipient's agreement.
In B2G, EN 16931 is the reference standard behind the reception obligation, and Peppol BIS Billing 3.0 is what is used in practice — universally so in the NHS. For the 2029 mandate the government has confirmed the network but not yet published the mandatory formats.
The defensible build today is Peppol BIS Billing 3.0 on EN 16931, kept configurable. Peppol being confirmed as the core network makes BIS Billing the overwhelmingly likely baseline — but "overwhelmingly likely" is not the same as published, and a UK-specific CIUS remains entirely possible.
A PDF is a perfectly valid VAT invoice today, in both B2B and general B2G. It is not a structured e-invoice, so it will not satisfy an NHS contract requiring Peppol, and it will not satisfy the 2029 mandate for any document that is a VAT invoice. The window for PDF in UK B2B closes in April 2029 — which is late by European standards and worth using rather than rushing.
Four schemes from the Peppol electronic address code list are practically relevant in the UK:
Nothing has been mandated. The government has not published a required primary EAS for 2029, has not created a Peppol scheme for the Companies House number, has not set priority rules between VAT number, GLN and others, and has not specified how an identifier is to be verified as belonging to a client. 9932 with the GB VAT number is the natural fit for a VAT-based regime — but do not design as though it were settled.
Peppol has been the core interoperability network since 23 June 2026. What has not happened is the appointment of a UK-wide Peppol Authority for the national mandate — and the current governance is easy to misread.
So a provider serving UK clients today deals with OpenPeppol governance, plus the NHS authority's requirements where NHS work is involved. Whether a separate UK-wide authority is created for the 2029 mandate is one of the things the Budget 2026 roadmap should answer.
No UK accreditation comparable to the Slovak digitálny poštár exists in the current regime. To operate in the NHS and Peppol environment a provider must be a Peppol-certified Service Provider and comply with the Service Provider Agreement, the Access Point and SMP technical specifications, AS4 transport requirements, Peppol PKI and certificates, the Service Level Requirements, the participant registration rules, and any applicable Peppol Authority Specific Requirements. The NHS itself simply recommends choosing any Peppol-certified provider from the OpenPeppol list.
The government has said explicitly that it will develop the right regulatory framework for software providers. Plausible additions include a registration or approval scheme, mandatory conformance testing, security and resilience controls, customer identity verification, data retention and audit log requirements, incident reporting, liability requirements, UK-specific Peppol Authority Specific Requirements, interoperability with Making Tax Digital, participant migration rules between Access Points, and mandatory validation and rejection codes. These are directions of travel, not current obligations — but a provider planning UK capacity should assume some of them will land.
ViDA is EU legislation and creates no direct mandate for the United Kingdom as a third country. EU digital reporting based on mandatory e-invoicing for cross-border B2B applies from 1 July 2030 — which means the UK domestic mandate starts earlier, in April 2029.
Under the Windsor Framework, Northern Ireland continues to apply part of EU VAT law in relation to goods. The UK government has previously acknowledged that the ViDA provisions on goods and digital reporting could potentially affect Northern Ireland, and HMRC has said it continues to analyse the impact. No separate scheme for applying ViDA in Northern Ireland has been published. For a business with NI goods flows, this is the open question to keep monitoring.
No penalty regime for the 2029 mandate has been published. It is not known whether sanctions will be calculated per invoice, per day, as a fixed penalty, on a points system, by reference to turnover or VAT at stake, in the manner of Making Tax Digital, or separately for seller, buyer and software provider. Respondents to the consultation asked for exactly this clarity; the government has so far only confirmed that the regulatory framework is in development.
Breaches of the VAT invoice and record requirements can already fall under section 69 of the Value Added Tax Act 1994 — for example issuing a VAT invoice late, omitting mandatory particulars, misrecording taxable, exempt and zero-rated supplies, breaching the credit note rules, or failing the record-keeping requirements. The general regulatory penalty is a daily rate:
HMRC also notes that persistent failure to meet the current conditions for electronic invoicing can lead to a penalty and to a requirement to revert to paper invoicing until the defects are corrected. These existing penalties should not be assumed to be the 2029 penalties — new legislation may establish a separate system.
Currently a structured e-invoice is not the only basis for recovering input VAT. A taxpayer normally needs a valid VAT invoice, which may be paper, PDF, structured XML, or delivered by EDI or Peppol; an electronic invoice is acceptable evidence where authenticity, integrity and legibility are ensured. Where no VAT invoice exists, HMRC may in exceptional circumstances accept alternative evidence — proof of supply, proof of payment, supplier details, evidence of the VAT amount, correspondence attempting to obtain a correct invoice — but that is discretionary and does not displace the general requirement.
Importantly, the government has not announced that after April 2029 input VAT will automatically be lost merely because an invoice did not travel through Peppol, went by another structured channel, or was technically misregistered in an SMP. That is a question the roadmap will have to answer, and it should not be assumed either way.
VAT records must generally be kept for six years. Electronic storage is accepted, and HMRC allows the invoicing, processing and storage functions to be outsourced — but the underlying obligation is not transferable.
Six years is short by continental standards, but it spans the mandate. Invoices issued today under the voluntary regime will still be within the retention period when the structured regime is in force — so the archive needs to hold both worlds at once.
Three years is enough time to do this calmly, and the sensible work is the same whatever the roadmap says:
9932, with GLN 0088 handled properly for NHS and supply chain counterpartiesThe United Kingdom has committed to a national e-invoicing mandate from April 2029 covering every document that is a VAT invoice, with Peppol confirmed as the core interoperability network since June 2026. The design is decentralised, without clearance, and without real-time reporting at launch — a deliberately lighter model than most of Europe.
Almost everything else is still to come. Mandatory formats, the required identifier scheme, territorial reach, exemptions, phasing, penalties and any provider regulatory framework are all unpublished, and the roadmap is due with Budget 2026.
Which makes the useful advice unusually simple. Build Peppol BIS Billing 3.0 now, keep the format and identifier layers configurable, and spend the intervening years on invoice data quality — the one part of the project the roadmap cannot change.