AEVOMIND INSIGHTS — FINANCE & INTEGRATION

E-invoicing from April 2029: what the government's roadmap says, what is still undecided, and how to get your invoice data ready

5 November 2026 · 10 min read · By the AevoMind team

Two glass blocks facing each other, each sending a thin line of light to a small glowing gold hub between them, standing for two systems exchanging invoices through a shared route.

The government's roadmap, published on GOV.UK on 28 October 2026, says VAT-registered persons must be able to issue and receive VAT invoices as e-invoices from 1 April 2029, using Peppol. The detailed requirements arrive between October 2027 and April 2028, and the roadmap says there is no need to start implementing before then. What is worth doing now is getting invoice data structured and connected. Software can help with that, but not with deciding who is right in a dispute.

The short answer

The government has set a date. In its e-invoicing implementation roadmap, published on 28 October 2026, it says: “From 1 April 2029, VAT-registered persons (including public sector bodies) will need to be able to issue and receive VAT invoices as e-invoices, unless a specific exemption applies.” The detail of what that means in practice is still to come, and the roadmap is open about it.

The roadmap’s own advice is calm: “There is no need to begin implementing e-invoicing before the detailed requirements are published.” What is worth doing now is a data question rather than a software purchase: how structured your invoice data is, and how many systems it passes through. A connected system with clean customer and supplier records and an integration layer is in a better position than a pile of PDFs and spreadsheets. It does not make a business e-invoicing compliant on its own.

Five matte green steps rising left to right, the tallest topped with a brushed-gold bar, standing for staged milestones leading to a fixed date.
A fixed date, with the detail arriving in stages before it.

What e-invoicing is, and what it replaces

The roadmap defines it plainly: “E-invoicing is the exchange of structured invoice data directly between buyers’ and suppliers’ financial systems.” That is different from emailing a PDF. A PDF is a picture of an invoice that a person has to read and retype. A structured invoice is data that the receiving system can read, match and process without anyone retyping it.

It is not illegal to send electronic invoices today. The roadmap says: “electronic invoices are already permitted, but only as an option for businesses”, and HMRC’s current guidance is technology neutral, so PDFs, EDI systems and structured formats are all acceptable provided the legal requirements for authenticity, integrity and legibility are met. What changes from April 2029 is that a structured e-invoice becomes the required form for VAT invoices.

Who it applies to, and who it does not

The roadmap says the requirement covers VAT-registered persons: VAT-registered businesses, sole traders, partnerships, charities, and public bodies registered for VAT. VAT invoices are required when a VAT-registered person makes a taxable supply to another VAT-registered person within the UK, and those are the invoices that will have to be e-invoices.

Three groups sit outside it. Sales to consumers and to customers who are not VAT registered do not need VAT invoices, so they are not covered. Cross-border transactions are not covered either, though a business can choose to send an e-invoice by agreement. And the government says it will publish “narrow exemptions” for people unable to use digital tools, with guidance for those groups by the end of 2027. The roadmap also says that organisations which are not required to use e-invoicing may choose to do so voluntarily.

A mesh of glowing glass nodes joined by thin lines of light, with one gold node at the centre joined to all the others, standing for many systems connecting through one shared network.
Different systems, one shared way of exchanging invoices.

Peppol: how invoices will travel

The government has already decided how invoices will be exchanged. The roadmap says that “Peppol will be the UK’s core interoperability framework.” Peppol is an international framework that lets organisations using different software exchange e-invoices through common standards and rules.

For most businesses the technical side will be somebody else’s job. Organisations will typically reach Peppol through an Access Point run by their software provider, and the roadmap says: “Businesses will not need to become Access Points themselves.” Access Point providers will have to be certified. Two things will still land on the business: it will need to ensure its chosen software supports the future UK requirements, and every user will need a business identifier as part of its Peppol participant identity. The decision on which identifiers the UK will accept is due between October 2027 and April 2028.

On privacy, the roadmap says the Peppol Authority, which HMRC will become, “will not receive copies of VAT invoices for business transactions”. It also reports that a consultation on e-invoicing digital reporting was launched at Budget 2026, and states that “No decisions have been taken on whether e-invoicing digital reporting should be introduced.” Treat that as undecided in either direction.

The timeline, and what is still undecided

The roadmap sets out a sequence of stages:

On the legal side, the roadmap says primary legislation is to be introduced in Finance Bill 2026 and is expected to become law in Spring 2027, while the detailed secondary legislation may not conclude until Autumn 2028 or early 2029. In plain terms, the standards, exemptions and identifiers that a business needs in order to build or buy a solution are not yet published, and are not due for roughly another year at the earliest.

A clear glass card standing upright beside a brushed-gold seal disc on a green surface, standing for a sealed, structured invoice.
A sealed, structured document that the receiving system can trust and read.

Why the government is doing it, in its own figures

The roadmap links e-invoicing to late payment. It says late payments cost the UK economy £11 billion each year and that “small businesses spend 86 hours per year chasing late payments”, and it describes poor information flow, such as an invoice that arrives incomplete, incorrect or at the wrong part of an organisation, as a major reason for paying late. Those are the roadmap’s figures, which it footnotes, and we have not checked them independently.

That is also the sensible way to think about preparation. The hours that e-invoicing is meant to remove are the ones spent retyping, matching and correcting invoice data. Our own article on chasing late invoices covers the debtor side of the same problem.

What software can do now, and what it cannot

The chart below uses illustrative figures, not client data, to show where invoice admin time goes for a business sending about 300 invoices and receiving about 200 a month.

Most invoice admin is re-keying and matching, not judgingIllustrative hours a month for a business sending about 300 and receiving about 200 invoices, by hand and with structured data
By handWith structured data
Re-keying received invoices into the finance system20 hrs4 hrs
Matching purchase orders to received invoices12 hrs4 hrs
Correcting wrong or missing customer details on invoices8 hrs2 hrs
Resolving queries on disputed or rejected invoices6 hrs5 hrs

Illustrative inputs, not client data. Totals: 46 hours a month by hand against 15 with structured invoice data flowing between systems. Resolving a disputed invoice falls least, on purpose: a person decides who is right. Structured data removes the retyping and matching, not the judgement. Substitute hours you have measured.

Show the data
By handWith structured data
Re-keying received invoices into the finance system20 hrs4 hrs
Matching purchase orders to received invoices12 hrs4 hrs
Correcting wrong or missing customer details on invoices8 hrs2 hrs
Resolving queries on disputed or rejected invoices6 hrs5 hrs

The shape is the point. Retyping and matching are mechanical and disappear when structured data flows between systems. A dispute over what was delivered does not, and a person still decides it.

What can be done before the requirements are published is groundwork. A connected finance system, such as the one described on our finance and invoicing page, keeps invoices, credit notes and purchase orders as records rather than documents. The integration hub and public API and partner access describe the connectors, API gateway and webhooks that let those records move between systems. Practical preparation includes:

We do not claim e-invoicing or Peppol capability. The standards are not published, and certification of Access Points is something a provider must complete once the requirements exist. What a system can honestly offer now is clean, structured, connected data, and a connection to whichever certified route you choose. For the related data-sharing question, see the Friday export and why businesses end up with a dozen disconnected tools.

Two glass spheres joined by a thin tube carrying a row of identical glowing beads, standing for structured records passing from one system to another without retyping.
Identical structured records moving from one system to another, with no retyping.

Where to start this week

  1. Check whether you are VAT registered and which of your customers and suppliers are, because only invoices between VAT-registered parties are in scope.
  2. Ask your accounting software provider what its plans are for UK e-invoicing, as the roadmap says many small and medium businesses will not need separate e-invoicing software.
  3. Audit your customer and supplier records: legal name, address and VAT number in one place, and correct.
  4. Count how many invoices are retyped and who retypes them. That is the time to measure.
  5. Note the dates: Spring 2027 for the technical consultation, and October 2027 to April 2028 for the published requirements.

This is general information based on the government’s roadmap as we read it on 5 November 2026. We have not read the VAT invoicing rules in VAT Notice 700, the Finance Bill clauses, the Budget 2026 consultation on digital reporting or the Peppol specifications, and the details may change as the requirements are published. It is not tax or legal advice.

Frequently asked questions

When does e-invoicing become mandatory for VAT invoices in the UK?

The government's e-invoicing implementation roadmap, published on GOV.UK on 28 October 2026, says that from 1 April 2029 VAT-registered persons, including public sector bodies, will need to be able to issue and receive VAT invoices as e-invoices unless a specific exemption applies. It confirms the requirement was announced at Budget 2025. The detailed requirements, including scope, exemptions and standards, are due to be published between October 2027 and April 2028.

Who does the e-invoicing requirement apply to?

The roadmap says it applies to VAT-registered persons, which includes VAT-registered businesses, sole traders, partnerships, charities and public bodies. VAT invoices are required when a VAT-registered person makes a taxable supply to another VAT-registered person within the UK. The roadmap says VAT invoices are not required for sales to consumers or to customers who are not VAT registered, and that e-invoices will not be required for cross-border transactions, so those are outside the requirement.

What is Peppol and do we need to connect to it ourselves?

The roadmap says the UK will adopt Peppol, an international framework for exchanging e-invoices between organisations using different software, as its core interoperability framework. Organisations will typically reach it through an Access Point provided by their software provider, and the roadmap says businesses will not need to become Access Points themselves. Access Point providers must be certified. All users will need a business identifier as part of their Peppol participant identity, and the UK's decision on which identifiers are accepted is due between October 2027 and April 2028.

Do we need to do anything now?

The roadmap says there is no need to begin implementing e-invoicing before the detailed requirements are published. It suggests that organisations may wish to research the market of e-invoicing software providers, learn how similar businesses are implementing it, or talk to an accountant or adviser. The practical preparation that does not depend on the detail is knowing what invoice data you hold, how clean it is, and which systems it passes through.

Will HMRC receive a copy of every invoice?

The roadmap says the Peppol Authority, which HMRC will become, will not receive copies of VAT invoices for business transactions. Separately, a consultation on e-invoicing digital reporting was launched at Budget 2026 to explore whether information created through e-invoicing could support tax administration. The roadmap describes it as early-stage and says no decisions have been taken on whether digital reporting should be introduced.