Back to the blog Tax & compliance

The UK E-Invoicing Mandate: What Small Businesses Actually Need to Do

From 1 April 2029, a PDF will no longer be a valid VAT invoice in the UK. Every B2B and business-to-government VAT invoice will have to be issued in a structured, machine-readable format.

That is a real change and it is worth understanding. It is also nearly three years away, the technical standards have not been published, and a lot of the content currently being written about it is selling something. So here is what is actually settled, what is not, and what a small business should do about it this year — which is, genuinely, very little.

Where this currently stands

UK e-invoicing mandate timeline Consultation ran February to May 2025. The mandate was confirmed at Budget 2025 with a consultation response in November 2025. HMRC began stakeholder co-design in January 2026 and an implementation roadmap and standards are due at Budget 2026. Preparation runs through 2027 and 2028. The mandate takes effect on 1 April 2029. 2025 Consulted & confirmed 2026 — now Co-design; roadmap at Budget 2027–2028 Software and businesses prepare 1 Apr 2029 Mandatory for all VAT invoices

The consultation ran from February to May 2025. The mandate was confirmed at Budget 2025, with the consultation response published that November. HMRC opened a stakeholder collaboration phase in January 2026, bringing software providers, tax advisers and businesses together to co-design the regime, and the implementation roadmap and technical standards are expected at Budget 2026.

Which means the detail you would need in order to prepare properly does not exist yet.

What "structured" actually means

This is the part that trips people up, because a PDF feels electronic. It is not, in the sense the mandate cares about.

A PDF is a picture of an invoice. A person can read it; software cannot reliably parse it without OCR, which introduces exactly the misread line items and manual corrections the mandate exists to remove. A structured e-invoice is an XML document — the expected formats are UBL and UN/CEFACT CII, with Peppol BIS Billing 3.0 as the profile — that your client's accounting system can ingest and validate without anyone opening it.

Peppol is the network the UK is building on. Its model routes an invoice from your software, through a certified access point, across the network, to your client's access point and into their system. You will not interact with any of that directly; your invoicing software will.

Worth saying plainly: you can still send a PDF. Nothing stops you attaching a human-readable copy for the person who wants to look at it. What changes is that the PDF alone stops being the legal artefact.

What is not in the mandate

The loudest fear during consultation was that e-invoicing would arrive bundled with real-time reporting — a live feed of every invoice to HMRC as you issue it, as operates in several other countries.

That is not part of the initial mandate. The government has indicated it may be explored later, once e-invoicing is established, but it is not what April 2029 brings. If you read something implying HMRC will be watching your invoices in real time from 2029, that is not what has been announced.

What to do in 2026

Very little, and deliberately so.

  • Do not buy anything yet. The standards are unpublished and transitional arrangements for smaller businesses are still being designed. Anything sold today as UK-mandate-ready is sold against a specification that does not exist.
  • Check that your invoicing software has said something. Not that it is compliant — nothing can be yet — but that the people building it are engaged with the co-design process and have a position. Silence from a vendor on a confirmed 2029 mandate is the signal worth noticing.
  • Keep your invoice data clean. This is the only genuinely useful preparation available right now. Structured invoicing needs consistent client records, correct VAT numbers, itemised lines and sane invoice numbering. If that is a mess in 2028, migration will be painful regardless of which tool you use.
  • Revisit this after Budget 2026. That is when the roadmap lands and the picture becomes concrete enough to plan against.

The honest read

For a freelancer or a small business issuing a few dozen invoices a month, this will almost certainly arrive as a software update rather than a project. The heavy lifting sits with the tool you invoice from, not with you.

The businesses that will feel it are the ones on spreadsheets, hand-built templates, or an accounting setup nobody maintains. If that is you, the three years between now and 2029 are a comfortable runway — and the fix is the same thing that would make your invoicing better today, mandate or no mandate.

Where Billvy sits on this: we are watching the co-design process and we will support the published standard when it exists. We are not going to claim readiness for a specification nobody has seen.

Clean invoice data, starting now

Consistent client records, itemised lines and sequential invoice numbers — the groundwork that makes any future migration straightforward. Free to start, no card required.

Start free

Frequently asked questions

Will a PDF invoice still be valid after April 2029?

Not as the VAT invoice itself. You can still send one alongside a structured invoice for the human reading it, but the PDF will no longer be the legal document.

Does this mean HMRC sees my invoices in real time?

No, not in the initial mandate. Real-time reporting was raised during consultation and the government confirmed it is not part of the first phase, while noting it may be considered later.

Do I need to buy e-invoicing software now?

No. The roadmap and standards are due at Budget 2026 and small-business transitional arrangements are still being designed. Buying against an unpublished specification is a good way to pay twice.

Sources

Checked September 2026. Mandate timelines move — several countries have already shifted theirs — so verify current status before making decisions. General information, not tax or legal advice.