Odoo e-invoicing in United Kingdom
The United Kingdom e-invoicing picture in full: the scheme, the authority behind it, who it binds, and every requirement we map before a build is quoted.
Mandatory e-invoicing for VAT invoices, run over Peppol (no local-language name, the UK operates in English)
Authority: HM Revenue and Customs (HMRC), jointly with the Department for Business and Trade (DBT)
No B2B e-invoicing mandate is in force. Public-sector obligations already exist: UK contracting authorities must be able to receive and process EN 16931-compliant e-invoices, and NHS England requires Peppol.
Businesses are not obliged to issue e-invoices to each other. If you sell to the public sector, your buyer is already required to be able to receive a compliant e-invoice, so Peppol capability is a practical requirement on B2G contracts.
Every requirement, in full
4 requirements. Each one has to end up as a field, a document layout, a stored response, or an API call in your Odoo build. This is the list an e-invoicing project in United Kingdom gets costed against.
- 1 Structured, machine-readable invoice data that the recipient's system can process, not a PDF.
- 2 Peppol as the core interoperability network, so a four-corner exchange through an access point rather than a filing to a government portal.
- 3 No real-time reporting to HMRC at launch. The consultation response says real-time reporting will not be implemented in 2029 and would only follow once e-invoicing use is well established.
- 4 Format choice, phasing and the treatment of legacy EDI are still open. Nothing firm until the Budget 2026 roadmap.
Checked Localization notes on this page checked on 22 August 2026.
Rates, formats, thresholds and submission windows change. We configure against the rules in force at build time and confirm every figure with your accountant or tax advisor before sign-off. If a rule moves after go-live, it is a support ticket, not a rebuild. Read more on our Odoo localization service.
How we build e-invoicing for United Kingdom
The delivery method behind the list above. The same four steps on a 10-user rollout and on a multi-company programme, with the depth scaled to the scope.
- 1 Requirements first, code second. Each line above becomes a field, a report, or an API call on a written mapping sheet. Anything with no home in Odoo is quoted as a build before the project starts.
- 2 Numbering is settled on day one. Invoice sequences are the part that breaks quietly and costs the most to unwind after go-live, so they are signed off before the first test document.
- 3 Submission runs from a queue. Retries, idempotency keys, stored responses and an audit trail. A failed send becomes a ticket with evidence, not a missing invoice you find at month end.
- 4 Your finance team signs it off. Real documents, in a test database, checked with your accountant or tax advisor before cutover, with a rollback plan in writing.
What we need from you to quote it
Bring these to the first call and you get a scoped, priced e-invoicing plan for United Kingdom instead of a range.
- โ Your tax registration details and the entity each one belongs to.
- โ A sample of every document type you issue: invoice, credit note, debit note, self-billing if you use it.
- โ Any registration, certificate or portal credential the authority has already issued you.
Services behind this work
The rest of the United Kingdom localization detail
Each topic has its own page with the full item list, the same way this one does.
Full detail, printed as checked.
Payroll in United KingdomFull detail, printed as checked.
Payments in United KingdomFull detail, printed as checked.
Shipping in United KingdomFull detail, printed as checked.
United Kingdom country overviewServices, modules, client work and delivery for United Kingdom.
E-invoicing in other markets we cover
Running the same rollout across borders? These pages carry the same depth for each market, so you can compare before scoping a multi-country phase.
Scope e-invoicing for your United Kingdom rollout.
Send us the list above with your answers against it. We come back with what is configuration, what is a connector, and what is a build, priced before the project starts.