The UK e-invoicing mandate: what is confirmed and what to do before 2029

UK e-invoicing now has a confirmed deadline. On 26 November 2025 the government published its response to the e-invoicing consultation and confirmed that e-invoicing will become mandatory for VAT invoices from 2029. The month has not yet been confirmed in official documents; April, the start of the tax year, is widely expected.

The full technical detail is still to come. The direction is set, the year is fixed, and finance teams have a clear window to prepare. This piece lays out what the government has actually confirmed, separates it from what remains open, and sets out where a UK finance team can sensibly start.

What the government has confirmed

The confirmation came in the government response to the consultation "Promoting electronic invoicing across UK businesses and the public sector", published on 26 November 2025 by HMRC and the Department for Business and Trade. It followed 342 responses from businesses and representative bodies, and it was set out alongside the Autumn Budget.

The stated case for the mandate is productivity. Structured invoicing removes manual keying, cuts the errors that come with it, and can speed up the payments businesses wait on. It also gives HMRC a cleaner view of VAT and narrows the room for fraud. The wider point is that the UK is following a direction most of its trading partners have already taken, where structured e-invoicing is becoming the default way tax invoices move between businesses.

Three things are now settled:

• E-invoicing will be mandatory. It moves from a voluntary practice to a legal requirement for the invoices in scope.

• The scope is VAT invoices. The requirement covers VAT invoices for business-to-business and business-to-government transactions where VAT is due.

• The start date is 2029. The mandate applies from 2029, giving businesses several years to get ready. The exact start date is expected in the implementation roadmap at Budget 2026.

Several important details are deliberately still open. The government has not yet set the exact electronic formats, the technical rules for how invoices are exchanged, or the precise sequencing for different business sizes. It has also confirmed that the initial mandate will not require real-time reporting of invoice data to HMRC, at least at launch. Those specifics are due in the implementation roadmap.

The timeline

The path to 2029 runs through a series of fixed points. Each stage below is dated, so the roadmap detail expected at Budget 2026 can be read against a timeline that is already clear.

February to May 2025: the consultation

HMRC and the Department for Business and Trade ran a 12-week consultation from 13 February to 7 May 2025. It gathered views on standardising e-invoicing, on whether adoption should be voluntary or mandated, and on which exchange model would suit the UK, including how any approach might align with international networks such as Peppol.

At that point nothing was decided. The consultation document was explicit that there would be no immediate change and that responses would shape any future policy. That is the version of events some older guidance still describes, which is worth bearing in mind if you read anything published before late 2025.

November 2025: the mandate confirmed

At the Autumn Budget on 26 November 2025 the government confirmed it would introduce mandatory e-invoicing for VAT invoices from 2029. The consultation outcome was published the same day, moving the policy from a question to a commitment. The response also indicated that the initial mandate would focus on the invoice itself, without a real-time reporting obligation to HMRC at launch. That decision may be revisited later, though real-time reporting sits outside the starting requirement.

Budget 2026: the implementation roadmap

The government has said it will publish a roadmap to implementing the mandate at Budget 2026, with deeper stakeholder engagement beginning in January 2026. This is the stage that turns the headline into working rules: the electronic formats businesses must issue and accept, the model for exchanging them, and how the requirement phases in across different types and sizes of business.

For most finance teams, Budget 2026 is the date that turns preparation into a concrete plan. It is where the technical answers a team needs to configure or upgrade its systems are expected to land.

2027 and 2028: preparation and testing

The years between the roadmap and the deadline are the preparation window. On the basis of the announced plan, this is when businesses and their software providers align systems to the confirmed formats, and when testing and pilot activity is expected. The likely pattern is that new tools run alongside existing processes for a period, so teams can prove the new flow before they depend on it.

2029: mandatory for VAT invoices

From 2029 (April is widely expected, pending the roadmap), VAT invoices in scope must be issued in the specified electronic format. This is the point at which a PDF emailed to a supplier or customer no longer meets the requirement on its own. A business that has done the readiness work should experience it as a planned switch-on.

Who is affected

The mandate reaches VAT-registered businesses in the UK. If you issue or receive VAT invoices for business-to-business or business-to-government transactions, you are in scope. That covers most finance teams in the mid-market, whatever sector they sit in.

It applies on both sides of the invoice. On the sales ledger you have to issue VAT invoices in the required format, and on the purchase ledger you have to be able to receive and process them. For an accounts payable team, the receiving side is where most of the daily work sits, because it is the point at which supplier invoices land, get matched and get posted.

The public sector is included through the business-to-government part of the scope. Public bodies already have a track record here: the NHS has run structured e-invoicing over Peppol for several years, which is part of why the model is familiar to policymakers. Businesses below the VAT registration threshold are not directly in scope, though they can still be pulled towards structured invoicing by larger customers and suppliers that are.

Until the mandate starts, e-invoicing between UK businesses stays voluntary, with exceptions in the public sector: bodies covered by the Procurement Act 2023 must be able to accept e-invoices, and NHS Supply Chain requires its suppliers to send them through Peppol. For most private-sector invoices, nothing forces a change today. The value of the confirmed deadline is that it lets teams plan on a known date and treat the readiness work as a scheduled project. Teams that already receive structured invoices from European suppliers have a head start, because the plumbing is not new to them.

What structured e-invoicing actually means

This is where a lot of teams get caught out, because "e-invoice" sounds like something most of them already do. Emailing a PDF invoice counts as electronic. The mandate means something more specific: a structured e-invoice.

A PDF is a picture of an invoice. Software has to read it, interpret the layout, and extract the fields, and it can get that wrong. A structured e-invoice carries the data itself in a defined machine-readable format, so the buyer's system reads the supplier number, the line items, the tax and the totals directly, with no interpretation step in the middle. Formats such as UBL and CII, exchanged over networks like Peppol, are how that structured data moves between organisations.

The practical difference shows up in accuracy and effort. When an invoice arrives as structured data, the fields are already in the shape your finance system expects, so there is nothing to re-key and far less to check. When it arrives as a PDF or a scan, extraction has a ceiling, because layouts vary and some documents are simply hard to read. Good software gets you most of the way, and your team handles the exceptions. Structured invoicing is designed to shrink that exception pile at the source.

None of this means paper and PDFs vanish overnight. Plenty of suppliers will keep sending them well past 2029, especially smaller ones outside the scope. A finance team needs to handle both the structured invoices the mandate requires and the unstructured ones that keep arriving, in the same process.

If you are new to how that exchange works, it is worth understanding what Peppol is, since it is the network many countries already use for structured e-invoicing. The government has not yet said which standard the UK will use.

What finance teams should do now

There is no need to change systems this year. There is real value in getting your house in order early, so that when the roadmap lands at Budget 2026 you already have a plan to adjust. A sensible readiness list:

• Map how invoices reach you today. PDF by email, paper, supplier portals, EDI, structured formats: know the mix and the volumes for each.

• Check what your ERP can already take. Confirm whether your finance system can accept structured invoice data and post it cleanly with your nominal codes, tax groups and dimensions intact.

• Look at supplier and customer readiness. The mandate applies on both sides of an invoice. Understanding which of your trading partners are already structured tells you how big the change really is.

• Assess your current process for exceptions. Structured data removes some manual keying, but matching, approvals and exception handling still need to work. A tidy process now is easier to extend later.

• Ask your software providers where they stand. Any AP or invoicing software you rely on should be able to describe how it will support UK structured e-invoicing as the rules are confirmed.

• Watch Budget 2026. The roadmap is the moment to move from readiness to a firm plan, because it sets the formats and the exchange model you will build to.

Where Stratas fits

The 2029 deadline is a reason to prepare how invoices arrive, so structured formats can slot in when the rules take effect. The ERP you already run can stay in place while that happens.

Stratas captures invoices in whatever form suppliers send them, from PDFs and scanned documents to structured formats and Peppol, and processes them through one AP automation workflow. The data is extracted, matched and approved, then posted into your existing ERP with your nominal codes, tax groups and dimensions preserved. That works across the systems finance teams actually run, including Sage 200, Sage X3, Business Central, NetSuite and OrderWise, alongside 100+ ERP integrations in total.

The value in the run-up to 2029 is that the way invoices arrive can change without the systems behind them changing with it. Structured invoices and PDFs go through the same process and land in the same ledger, so preparing for the mandate does not mean re-platforming your finance function to do it.

If it is not the right fit for how your business trades, we will say so. What we can offer is a platform built to absorb the change the mandate brings, on the ERP you already use.