E-invoicing is coming. Your ERP wasn't built for it.
From April 2029, every UK VAT invoice must be issued electronically — and the government has been explicit that PDFs, scans and OCR don't count. If you run Sage 200, Pegasus Opera, Syspro, WinMan or OrderWise, here's what that actually means, and what's worth doing about it now.
What's actually been announced
The headline facts, minus the compliance-industry noise. Details beyond these are still being designed — the technical standards arrive with the Budget 2026 roadmap.
Mandatory from April 2029
Confirmed at the Autumn 2025 Budget: all UK VAT invoices — B2B and B2G — must be issued as electronic invoices from April 2029. A detailed implementation roadmap and technical standards are due at Budget 2026.
PDFs and OCR won't count
The mandate means structured, machine-readable invoice data exchanged between financial systems. PDFs, Word documents, scanned images and OCR-extracted data are expressly outside the definition.
Both directions matter
It isn't only about how you issue invoices. Your suppliers will increasingly send structured e-invoices — and your finance system needs to be able to receive and process them automatically.
What it means for your system
The common thread: every one of these systems will keep running your business well past 2029 — but none of them natively speaks structured e-invoice. The gap is the layer in front.
Sage 200 / Sage 50
Built around manual entry and rigid file imports. Neither issues nor consumes structured e-invoices out of the box today — expect Sage to address issuing in cloud products first, leaving on-premise users to bridge the gap themselves.
Harold for SagePegasus Opera 3
Purchase invoices arrive as paper or PDF and get keyed in, or imported through the two-file Import Wizard. There is no native route for a structured e-invoice to land in the purchase ledger.
Harold for PegasusSyspro
Deep manufacturing functionality, strict import formats — and no built-in consumption of structured e-invoices. Anything arriving electronically still has to be transformed into the format Syspro accepts.
Harold for SysproWinMan
No built-in document capture, so supplier invoices are keyed in today. Its Zapier connectivity is an advantage: validated, structured data can already be written straight in — the pattern e-invoicing will demand.
Harold for WinManOrderWise
Flexible custom import definitions, but they expect a clean file in an agreed layout. A structured e-invoice still needs a transformation step before it can flow in.
Harold for OrderWiseWhat's worth doing now (and what isn't)
Don't panic-replace your ERP
2029 is a deadline for invoice format, not a deadline for your ERP. Systems like Sage 200, Opera and Syspro will still be running fine — they just need a layer in front of them that handles structured data.
Fix the manual entry problem now
The firms for whom 2029 will be a non-event are the ones whose supplier invoices already arrive, get validated and land in the ERP without keying. That capability is worth money today — the mandate just makes it unavoidable later.
Watch Budget 2026
The implementation roadmap, accepted formats and transmission standards are due then. That's when 'be aware' becomes 'plan' — and when software vendors will show their hands.
Ask your ERP vendor the question
Specifically: will your version — not the newest cloud edition — be able to receive and process structured e-invoices? For most legacy installs the honest answer is no, and the fix will be a bridge, not an upgrade.
Where Harold fits
Harold is the validation and transformation layer that sits in front of your ERP. Today, it takes the supplier invoices you already receive — PDFs, emails — and turns them into validated, code-matched, import-ready data your system accepts, whether that's straight in via Zapier or as a file built to your ERP's exact format. That's the same layer the e-invoicing era requires: structured data in, ERP-ready data out. Firms that put it in place now save the keying-in cost today — and arrive at 2029 with nothing to scramble for.
Honest note: the final UK technical standards land at Budget 2026. Nobody can sell you "2029 compliance" yet — anyone who claims to is guessing. What you can fix now is the manual AP work, on the same architecture the mandate will reward.
Try Harold free