Skip to main content

E-invoicing with Sage 200, Sage 50 and Sage X3 in the UK

Jack
· 6 min read
In this article
  1. What has gov.uk confirmed about UK e-invoicing?
  2. What does Sage say about UK e-invoicing?
  3. What to ask Sage or your Sage partner
  4. What changes for a Sage AP team receiving e-invoices alongside PDFs?
  5. Where Stratas fits

Sage’s public UK material, checked on 16 October 2026, does not describe Sage 50 or Sage 200 receiving Peppol invoices directly, and the Sage X3 e-invoicing material Sage posted in 2026 is written for France and Belgium. Gov.uk confirms that from April 2029 businesses must issue all VAT invoices as e-invoices, with the rules due in a roadmap at the Budget on 28 October 2026, so the question for Sage or your Sage partner is how each product will send and receive them.

Below is what gov.uk has confirmed, what Sage itself says, product by product, and what receiving e-invoices alongside PDFs looks like for a Sage AP team.

What has gov.uk confirmed about UK e-invoicing?

  • The Budget 2025 document (26 November 2025) says the government will require all VAT invoices to be issued in a specified electronic format from April 2029, with an implementation roadmap to be published at Budget 2026.

  • The Tax update 2026 summary (23 June 2026) announced that Peppol will be the core interoperability network for e-invoicing in the UK.

  • HMRC’s Transformation Roadmap annex (first published 2 July 2026) says HMRC will publish full guidance, standards, technical specifications and legislation by the end of 2027 to 2028.

The Budget falls on 28 October 2026, according to the Chancellor’s letter to the Treasury Committee. For the full timeline, see our guide to the UK e-invoicing mandate.

What does Sage say about UK e-invoicing?

Sage’s UK guide to preparing for e-invoicing, first published in November 2024 and updated on 9 July 2026, explains that an e-invoice is a structured data file the recipient’s software reads automatically, and that a bill sent by email does not count. It says most of the UK detail is still open, and it suggests working with suppliers who use Peppol. It does not describe what Sage 50 or Sage 200 do with e-invoices.

Sage 50

On the Sage UK pages we checked on 16 October 2026, we found nothing that describes Sage 50 sending or receiving Peppol invoices. If you run Sage 50 and a customer such as NHS Supply Chain asks you to invoice through Peppol, ask Sage or your Sage partner which route they support today.

Sage 200

The same applies to Sage 200: we found no Sage page describing a Peppol connection or the receipt of structured e-invoices into Sage 200. That may change once the roadmap sets the UK rules, so it is worth asking Sage what it plans for Sage 200 and when it expects to say.

Sage X3

Sage X3 has an e-invoicing framework. In an announcement on Sage’s Community Hub, Sage delivered an e-invoicing pack for Sage X3 2025 R2 that brings in the e-invoicing features developed for release 2026 R1, and says e-invoicing must be activated with the EINV activity code first. A separate Sage alert points to how-to guides for e-invoicing setup in France and Belgium. We found no equivalent guide for the UK.

What to ask Sage or your Sage partner

  • Will your Sage product receive Peppol invoices itself, or through a connected service?

  • Who provides the Peppol access point, and who registers your Peppol ID?

  • Will received e-invoices post with your nominal codes, departments and VAT codes intact?

  • How will matching to purchase orders and approvals work for an e-invoice compared with a PDF?

  • When will Sage set out its plans for the UK rules once the roadmap is published?

Our explainer on whether you need a Peppol access point covers what an access point does and who needs Peppol before 2029.

What changes for a Sage AP team receiving e-invoices alongside PDFs?

E-invoicing is voluntary for most UK suppliers until April 2029, so any Sage team that starts receiving e-invoices will still receive PDFs and paper from everyone else. The work that matters is keeping both in one process:

  • One inbox for the team. E-invoices arriving through a separate service are easy to miss if PDFs still come in by email.

  • The same checks for both. An e-invoice carries its fields as data, so nothing needs keying, but supplier details, VAT, totals and order references still need checking before it posts.

  • Matching to Sage purchase orders. Structured data makes the match easier to automate, and the tolerance and approval rules should stay the same whatever the format.

  • Duplicates. During a changeover, a supplier may send the same invoice through Peppol and by email.

For the manual routes into Sage today, see our guides to importing purchase invoices into Sage 200 and importing invoices into Sage 50.

Where Stratas fits

Stratas receives Peppol, UBL and XML invoices alongside the PDFs and scans your suppliers send today, and every format is validated, approved and posted to your ERP the same way. Your team works one queue, whichever way each supplier sends. Approvals route by value, cost centre, supplier or department, the same way for a Peppol invoice as for a PDF.

Invoice number, supplier, order reference, VAT and totals map to the fields your Sage system expects, then post with the original file and a complete audit trail. See our pages on Sage 200 and Sage 50 and Sage X3, our UK e-invoicing mandate guide and e-invoicing with Stratas.

Written by Jack
Stratas
See Stratas in action

A live walkthrough with our team, built around the questions you bring.

Book a demo

Want to see this in action?

Book a demo and we'll show you how Stratas handles your specific document types.