Preparing your invoice data for UK e-invoicing in 2029

From 1 April 2029, VAT-registered businesses in the UK are expected to send and receive VAT invoices as e-invoices over the Peppol network, according to the government roadmap published on 28 October 2026. The mandate is not yet law. Primary legislation and the detailed technical rules are still to come, with final requirements due between October 2027 and April 2028. What you can do now is fix the data behind each invoice: complete VAT details, a unique invoice number on every document, one clean record for each customer and supplier, and accounting exports that keep every field intact. Automation can capture, check and move that data. A person still owns the figures, approves exceptions and decides the VAT treatment.
In short
- The UK e-invoicing mandate is planned for 1 April 2029, but it is not yet law, and the detailed rules are due between October 2027 and April 2028.
- Clean customer and supplier IDs, complete VAT fields and consistent invoice numbers are the data work to start now.
- Automate capture, validation and exports, but keep a person on VAT decisions and exceptions.
- Do not automate over messy master records or while the rules for your business are still unclear.
- Put the milestone dates in your diary and test your exports each time your accounting software updates.
What the 2029 date means for your invoices
The government has set a single go-live date for the domestic B2B and B2G mandate. From 1 April 2029, VAT-registered businesses and public sector bodies will need to send and receive VAT invoices as e-invoices, using Peppol as the core framework. That is a change in format, not only in software. An invoice that exists as a PDF attachment will no longer be enough once the rules apply.
Two points matter for planning. First, the mandate is not yet law. The roadmap describes the plan, but the detailed scope, technical requirements and exemptions are still to be set out in regulations or in an HMRC notice with force of law. The roadmap also points to primary legislation going through Parliament in the Finance Bill 2026 cycle, with technical consultations planned for spring 2027. Second, the exemptions are expected to be narrow. The government says they will be tightly defined and limited, with the main exemption aimed at businesses that are digitally excluded. Most VAT-registered businesses should plan on being in scope.
Three gaps in the plan affect your data work today. The roadmap does not yet say which business identifier HMRC will accept, because the UK has no single universal business identifier. HMRC will decide that framework between October 2027 and April 2028. A separate consultation on digital reporting, which could use invoice-level data for reporting to HMRC, is open until 20 January 2027. Nothing has been decided on that point. Overseas businesses making domestic UK supplies that need a VAT invoice are also expected to be in scope from April 2029.
Why messy invoice data costs money
Most businesses already pay for invoice data problems, even before any mandate. Someone retypes an invoice into the accounts package. Someone chases a missing VAT number. A customer is set up twice under two spellings, so statements do not match and payments go to the wrong account. The cost is staff time, delayed payments and the occasional duplicate payment.
Public benchmarks give a sense of scale, with an important caveat. A 2026 benchmark compilation that attributes its figures to Levvel Research and APQC puts the average manual invoice processing cost at between $9.87 and $15.00 per invoice, and it reports lower figures for businesses with full accounts payable automation. These are US dollar figures for accounts payable, not UK pounds for sales invoicing, so treat them as a rough order of magnitude only. The better measure is your own. Count how many sales and purchase invoices you handle in a month, time how long one takes from receipt to the accounts package, and multiply by the loaded hourly cost of the person doing it. That number is the baseline the free audit would work from.
The 2029 change adds a second cost. When the format rules bite, invoices that fail validation will need to be corrected and reissued. A business with clean identifiers and consistent fields will find that a routine job. A business with three versions of the same customer will find it a project.
Manual way vs automated way
The table below compares how most businesses handle invoice data today with how a data-ready process would work. The automated column describes what software can do. It does not mean that no one checks the output.
| Area | Manual way | Automated way |
|---|---|---|
| Where invoice data starts | PDFs in email, paper post and shared folders, retyped by hand | Invoices captured from a shared mailbox or upload point, with key fields read by optical character recognition (OCR) and checked against a rule set |
| Customer and supplier records | Duplicates created whenever someone types a new name | One master record per customer and supplier, with a unique ID and a VAT number field that is checked for format |
| VAT details | Checked by eye, if at all | Each line checked for a rate, a unit price and a total, with exceptions sent to a person |
| Invoice numbers | Numbered by hand in different series | Sequential numbering enforced by the invoicing or accounting system, with gaps reported |
| Accounting exports | Copied across by spreadsheet, fields dropped or renamed | Scheduled exports that keep field names and codes fixed, with a log of each run |
| Credit notes and corrections | Handled as new invoices with a note in the description | Linked to the original invoice number, so the link is visible to the reader |
| Readiness for 2029 | Found out when the final rules arrive | Gaps listed now, and the fix tested before the rules are set |
The data checklist to start now
Before buying any tool, check what each invoice carries today. The core VAT details are already fixed by law for a full VAT invoice. The guidance from HMRC asks for a sequential number, your VAT registration number, the tax point, and for each line the quantity, the unit price and the VAT rate. The total VAT must be shown in sterling. A full VAT invoice also needs the customer's name and address. Simplified invoices follow a lighter set of rules for supplies of £250 or less, when the customer agrees.
Beyond those legal fields, the data you need is:
- One unique ID for every customer and supplier, kept in the accounts package and the CRM, with the same ID used on every invoice.
- A VAT number field for each trading partner, checked for format, plus the company registration number where you hold it.
- A single invoice number series for sales and a separate one for credit notes, with no reuse of numbers.
- Product or service codes for each line, so the same item is described the same way every time.
- A link from each credit note and correction to the invoice it changes.
- Export files that keep field names, decimal places and tax codes stable from month to month.
Expect this list to change. The identifier framework is still to be decided, so keep your ID field flexible. Store the company registration number and the VAT number separately, so either can be added to an invoice later without rebuilding the record.
Step-by-step: how to automate the data work
Step 1: Fix the master records first
Start with the customer and supplier list in your accounts package. Merge duplicates, add VAT numbers where you hold them, and retire inactive accounts. Do this in a spreadsheet export before any automation touches the data, because automation copies whatever errors it finds. Xero, QuickBooks and Zoho Books all keep contact records that can be exported for this clean-up. Check each product's current export format in the vendor's own help pages before you change anything.
Step 2: Capture invoices from one place
Pick one inbox or upload point for supplier invoices and one place where sales invoices are issued. Email is still the default for most UK businesses, so a shared accounts mailbox is a practical starting point. An automation tool such as Power Automate or Zapier can watch the mailbox, file each PDF against a supplier ID and pass the attachment to an extraction step. OCR reads the printed text. A large language model can map that text to your fields, such as invoice number, date, VAT amount and rate. Each extraction should be stored with the original PDF so a person can compare them.
Step 3: Validate before anything posts
Write a short rule set and run it on every extracted invoice. Typical checks include: the invoice number has not been used before for that supplier, the VAT number matches the expected format, the line totals add up to the net and VAT amounts, and the VAT rate is one you use. Anything that fails goes to a review queue. The rules catch mechanical errors. They do not decide whether a supply is standard-rated, zero-rated or exempt. That judgement stays with a trained person or your adviser.
Step 4: Use WhatsApp only where your customers use it
Some UK businesses use WhatsApp to confirm billing details, send payment reminders or ask for a missing VAT number. The WhatsApp Business Platform, accessed through an approved provider, can handle those messages. Business-initiated messages usually need pre-approved templates, and customers must have agreed to receive them. Where customers prefer email or a portal, keep to that channel. Record every confirmed detail back in the master record, so the answer is not stored only in a chat thread.
Step 5: Plan the exports for the Peppol route
Most businesses will not run a Peppol connection themselves. The roadmap expects software providers to be accredited with the UK Peppol Authority, and your accounting software or a Peppol access point provider is likely to handle the sending and receiving. Your job is to make sure your exports carry clean data into that system. Ask your software provider, before 2028, how it plans to meet the final requirements, and what it will charge for the connection. Keep the answers in writing.
Step 6: Track the milestones and test
The roadmap sets out a sequence. Technical consultations are planned for spring 2027, final requirements are due between October 2027 and April 2028, readiness testing is planned for summer 2028, and the mandate starts on 1 April 2029. Put those dates in the diary. Run a test export and import each time your software updates. A test file that works in 2028 may need a fix once the final rules are set.
What breaks, and how to prevent it
The most common failure is a customer who appears under two IDs. The fix is a merge step that runs before any new invoice is posted, and a rule that blocks a new customer if a close name already exists. The second failure is a mistyped VAT number. A format check catches obvious errors, but it cannot confirm that the number belongs to the right company. For that, a person or a registered lookup should check it on the first invoice.
OCR can misread a digit, a decimal point or a faint scan. Set a rule that any total that differs from the sum of its lines goes to review. Keep the original PDF attached to every record. A third failure is the credit note that sits as a separate invoice with no link to the original. Make the link a required field.
Watch for changes in the rules. Once the final requirements are published, the rules may differ from what you built in 2027. Build your validation rules as a list that can be edited, not hard-coded into a template, so you can change them without rebuilding the process.
When not to automate
Automation is not worth building for every business. If you issue a handful of invoices a month, the time spent setting up capture, validation and exports may be more than the time saved. In that case, a clean accounts package, a numbering rule and a monthly check of the master records may be enough until the final rules are known.
Do not automate a process that is still being designed. If you are not sure whether your sales invoices are in scope, or whether you invoice overseas customers in a way that needs a different format, settle those questions first. A workflow built on an unclear rule will need rework.
Do not automate over bad data. If the master records are a mess, automation will spread the mess faster. Clean the data first, then automate. Finally, do not hand the VAT decision to a tool. Software can flag a rate that looks wrong. Only a person with the facts about the supply can confirm it.
What it takes: time, not price
The biggest resource is attention, not money. Counted from this page, the roadmap gives UK businesses roughly 29 months to go-live. The first year of that window is for deciding and cleaning: agreeing ownership of the master records, fixing numbering, and listing every place invoice data is typed by hand. The second year is for testing exports and connections once the final rules are set. The last months before April 2029 are for dry runs and staff training.
Expect the work to fall on a few people: the person who runs the accounts package, the person who approves invoices, and whoever manages the customer list. Give them a fixed slot in the diary each month. The gap between businesses that are ready and those that are not usually comes down to whether that slot was used.
This explains the rule in general terms; it is not legal or tax advice for your case.
How AiStaffo would automate this
AiStaffo would start by connecting to the accounts package and the shared invoice mailbox, then build a customer and supplier list with one ID per trading partner. Incoming invoices would be read, matched to that list and checked against a fixed rule set for invoice numbers, VAT fields and totals. Anything that does not pass would go to a review queue, and a person would approve it before it is posted. Exports would keep field names and codes stable, ready for the Peppol route once the final UK rules are set. The owner still decides VAT treatment, signs off exceptions and chooses the accounting software provider. Results depend on the business's own invoice volumes and data quality, which the free audit measures. Book a free automation audit.
Questions people ask
Is UK e-invoicing mandatory now?
What invoice details do I need to have right now?
Which business ID will UK e-invoices use?
Can I just use my accounting software for e-invoicing?
Do I need WhatsApp Business for this?
Is this legal or tax advice?
Book a free automation audit
Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.

































