Updates
UK E-Invoicing in 2026: The Readiness Checklist Distributors Should Finish This Year
The UK's direction has been clear since the Autumn Budget 2025: from April 2029, VAT-registered businesses will need to exchange structured e-invoices for business-to-business and business-to-government transactions. A PDF attached to an email will not be the compliance method. The invoice has to be data another system can read, check, and post.
October 2026 is a useful moment to stop treating that date as distant. There are still two full financial years to run before the mandate, which is enough time to change the process properly. It is not enough time to leave the first live partner until the winter before the deadline. The original summary of the mandate is in our December 2025 briefing. This piece is the work to finish while 2026 is still open.
Finish these six items this year
1. List who you invoice, and how the invoice leaves today
Split customers into three groups: already on EDI or XML, portal-only, and PDF or paper. The first group is your pilot. The second group is a conversation about receiving a structured file instead of a typed upload. The third group is the real project. For a distributor, that list is usually shorter than it feels once the top 20 customers by invoice count are on it.
2. Treat the ERP invoice as the source, not a spreadsheet beside it
Structured invoicing breaks if the legal invoice is rebuilt by hand from the sales ledger. The file you send should come from the posted invoice: customer references, PO number, line SKUs, quantities, net, VAT, and gross. If those values are corrected in a PDF template and nowhere else, you do not yet have a source of truth.
3. Validate before the invoice is sent
The checks are ordinary, and they are the ones that cause disputes when they are skipped:
- Invoice total equals the sum of the lines
- VAT is calculated on the right rate for the line
- The buyer's purchase order number is present when they require it
- Quantities and prices still match the order, the shipment, or the contract price
- Mandatory references for that customer are filled, including account numbers and delivery note references
RDS Cloud already runs this kind of validation on the way out, and holds a message that fails rather than delivering a file the partner will reject.
4. Agree the formats you will actually support
You do not need a different project for every customer, but you do need a short list. For UK and European distribution that list is usually EDIFACT, a customer XML, and, where a partner or a public body already insists on it, a PEPPOL-style invoice. RDS Cloud maps those from the same ERP extract. With 500+ formats already built for UK and European partners, most of that work is configuration, and a new map of a known layout is typically live in under two hours.
5. Keep the audit trail with the invoice
When HMRC or a customer asks what was sent, "we emailed a PDF" is a weak answer. Store the structured payload, the time it was sent, the validation result, and the delivery response. That record is also what your own credit-control team will want when a customer says the invoice never arrived.
6. Put at least one willing partner live before the year ends
A checklist that never sends an invoice is still a plan. Choose a customer who already sends you orders electronically and invoice them in structured form for a full month. Measure rejects, missing references, and how long exceptions take to clear. Then add the next customer. By the time the mandate dates are close, the operating rhythm should already be dull.
What 2026 readiness is not
It is not a rip-and-replace of the finance system. It is not a promise that every PDF disappears this quarter. Retail consumers are outside the B2B and B2G scope being discussed, and some long-tail customers will stay on a transitional process for a while. The mistake is leaving the high-volume customers in that transitional pile. They are the ones who will feel a rejected invoice as a late payment.
Distributors who already exchange orders through RDS Cloud are closer than they think. The order path, the customer references, and the trading-partner connections are the hard part. The invoice uses the same route in the other direction.
Want a practical gap review against this list? See how RDS Cloud handles structured invoicing or request a demo. If you are starting from the mandate itself, begin with how RDS Cloud supports the April 2029 requirement.