Will the UK use a centralised clearance model?

No. The UK has chosen a decentralised model, and HMRC confirmed on 23 June 2026 that Peppol will be the core interoperability network for e-invoicing in the UK. Invoices will pass between trading parties over an interoperable network rather than through a government clearance platform.

Are UK public sector suppliers already required to send e-invoices?

Generally no. The Public Procurement (Electronic Invoices etc.) Regulations 2019 oblige contracting authorities to receive and process compliant e-invoices; they do not oblige suppliers to send them. The exception is NHS England, whose suppliers are required to issue e-invoices via the Peppol network.

UK e-invoicing from April 2029: what has been decided

What has actually been decided?

The joint HMRC and Department for Business and Trade consultation response puts it without hedging: "As a result, and as announced at Budget 2025, the UK will introduce mandatory e-invoicing for all VAT invoices from 2029." The same document commits to "publish a roadmap to implementing this mandate at Budget 26."

Decided	Detail
That there is a mandate	Announced at Budget 2025, 26 November 2025
Start	April 2029 — HMRC Transformation Roadmap: update 2026
Model	Decentralised — not centralised clearance
Network	Peppol, confirmed 23 June 2026 as "the core interoperability network for e-invoicing in the UK"
Scope	All VAT invoices: B2B and B2G where VAT is due. B2C and non-VAT-registered businesses out of scope
No CTC in 2029	Real-time reporting explicitly excluded from the 2029 mandate

Where April 2029 comes from — and what it is not

From HMRC, not from the tax-year calendar. HMRC's Transformation Roadmap: update 2026, published 2 July 2026 and updated 27 July 2026, states that the government "will also mandate e-invoicing for all VAT invoices from April 2029." That is a primary source naming the month, and it settles a question this article previously left open: an earlier version argued April was an inference by professional bodies from the tax-year start, because the November 2025 consultation response, Budget 2025 and HMRC's Tax Update 2026 of 23 June 2026 all say 2029 without a month. The roadmap update, published nine days after the last of those, does name one. Corrected 8 September 2026.

What April 2029 is not is a commencement date. No legislation has been introduced, and an announced start becomes an obligation only when a Finance Act and its regulations say when. Plan to April 2029; do not treat it as enacted.

What has not been decided?

The legislation. None has been introduced. The Finance Bill 2026-27 draft legislation collection of 13 July 2026, updated 14 August 2026, contains no e-invoicing measure — so April 2029 has no commencement provision behind it yet.
Phasing. The consultation response sets out none by business size — unlike the staged approaches taken elsewhere in Europe.
The implementation roadmap and standards, promised at Budget 2026 and not yet published.

An unusual position: a firm commitment with a soft edge on every implementation detail. It argues for building capability rather than building to a date.

What does "decentralised, on Peppol" mean in practice?

Invoices travel between trading parties across an interoperable network, rather than passing through a government platform for clearance before they are valid. Poland's KSeF and France's approved-platform regime are both more interventionist. The compliance question shifts from "will the tax authority accept this" to "can my counterparty's system consume this" — an interoperability problem, solved by data quality far more than by filing logic.

Why the Peppol confirmation is the most actionable fact

Because it removes the main reason to wait. Until 23 June 2026, investing in Peppol capability was a bet on the eventual architecture. Now the transport layer is known, whatever the roadmap says about dates. That is newer than much of the vendor commentary still in circulation, written while the network question was open — and it means anyone already supplying NHS England has much of the groundwork done.

Does UK public procurement already require e-invoicing?

This is the correction with the most immediate practical value, because much published material has it backwards. The Public Procurement (Electronic Invoices etc.) Regulations 2019 (SI 2019/624), in force 18 April 2019 and extended to sub-central authorities and utilities on 18 April 2020, oblige contracting authorities to receive and process compliant electronic invoices to EN 16931. They do not oblige suppliers to send them.

Party	Obligation today
Contracting authority	Must receive and process compliant e-invoices, and pay undisputed ones within 30 days
Supplier (general)	No obligation to send an e-invoice
Supplier to NHS England	Must issue e-invoices via Peppol — the one genuine sending obligation in the UK today

The Procurement Act 2023 guidance Electronic Invoicing and Payment, published 13 February 2025 and updated 20 July 2026, runs the same way: authorities must accept and process undisputed electronic invoices in BS EN 16931-1:2017, using syntaxes listed in PD CEN/TS 16931-2:2017, and pay within 30 days. Notably, it does not name Peppol.

The exception matters. Per the HMRC and DBT consultation document, "The UK does not currently mandate standards for e-invoicing, other than requirements set by NHS England for their suppliers", and those suppliers "are required to issue e-invoices via the Pan-European Public Procurement On-Line (PEPPOL) network." Sell to NHS England and you have a live Peppol obligation today — and a head start on 2029.

Is real-time reporting coming as well?

Not in 2029. The consultation response is explicit that real-time digital reporting "will not be implemented in 2029 but would be implemented once e-invoicing use was well established."

Deferred, not abandoned. An architecture assuming invoice data will only ever be examined after the fact, in audit, is designing to a state the government has already said it expects to leave. Keep issuance observable in near real time internally, even while the external obligation stays post-audit.

What does a live mandate actually look like?

Two comparators, both operating rather than pending: France's reform has been live since September 2026, on an approved-platform model, and Poland's KSeF is live and now enforcing, on full central clearance. The transferable lesson is not about formats. It is that master data — VAT numbers, registered addresses, buyer and purchase order references — becomes a hard failure point once transmission is machine-to-machine. Invoices a human counterpart would have quietly fixed get rejected instead.

What is worth doing before the roadmap lands?

Each of these earns its keep whatever the implementation roadmap adds:

Establish Peppol access. The network is confirmed; this is no longer a bet.
Fix master data. VAT numbers, addresses, buyer and PO references, validated at entry rather than at transmission.
Build the ability to receive, not just send. Inbound is the half most projects under-scope, and where the counterparty controls data quality.
Keep an audit trail for automated issuance — what was issued, on whose authority, against which policy version.
Plan to April 2029, but keep contracts and vendor commitments able to absorb a change — the date is announced policy, not yet a commencement provision.

Frequently asked questions

Is the mandate confirmed, or just proposed?

Confirmed as policy at Budget 2025. Not yet enacted — no legislation has been introduced.

Is it April 2029?

Yes, as announced policy — HMRC's Transformation Roadmap: update 2026 says "from April 2029". No legislation yet sets a commencement date.

Will invoices go through HMRC?

No. The model is decentralised, with Peppol as the core interoperability network.

Does it cover B2C?

No. Scope is all VAT invoices — B2B and B2G where VAT is due.

Will small businesses get a later deadline?

Unknown. No phasing by size is set out in the consultation response.

Must I send e-invoices to the public sector today?

Only if you supply NHS England, where Peppol is already required. Otherwise the obligation sits with the authority to receive, not with you to send.

Where this leads

The UK has made a durable decision about direction and named a date it has not yet legislated — a combination that rewards capability-building and punishes programmes that treat April 2029 as fixed in law.

The second-order issue arrives with automation. Once invoices are issued by systems rather than people — and by 2029 many will be issued by AI-assisted workflows — the governance question is the one UK automated decision-making law now asks of any system acting on a counterparty: what did it do, on whose authority, and what record survives. Our AI agent governance guide covers that ground.

BarzelVault applies policy, approval controls and a verifiable record to automated actions before they execute — which is the evidence an automated invoicing workflow needs when someone asks what was issued and on whose authority. FinOps Atlas answers the cost side of the same automated workflows.

In practice

The control has to run before the invoice becomes irreversible.

An accepted structured invoice can be corrected but never deleted, and from the penalty date every defect has a price. Barzel puts the approval threshold, the duplicate check and the signed record in front of submission, so the process can be defended on the day an auditor or the tax authority asks.

UK e-invoicing mandate announced for 2029

BarzelVault

The AI action firewall: decide what an agent may do before it does it.

Approval thresholds and policy checks enforced before execution; human approvals that expire and escalate.
Cryptographically signed audit receipts: trigger, inputs, policy version, approver, outcome.
Credential isolation, spend and action limits, and an emergency kill switch.

Free tier: 10,000 calls a monthPaid plans from $199 a monthLive on MCPize

Start free Ask by email Product page Documentation

Barzel FinOps Atlas

Intelligent financial operations for AI agents and automation.

Cost per action, workflow and business outcome, allocated as it happens.
Spend limits and anomaly detection before the bill, not after.
Financial evidence tracing and close-readiness for SOX, SOC 2 and external audit.

Free tier: 500 calls a monthPaid plans from $29 a monthLive on MCPize