If you are searching for e-invoicing ERP guidance, you probably want an answer to a simple question: will our finance system cope with what is coming, and what do we need to do about it? This guide separates what is already law in the UK from what is arriving through trading partners in Europe, and turns both into checks you can put to your software vendor and your integrator.
It is written for finance directors, IT leaders and owners of small and mid-sized businesses. It does not replace advice from your accountant or from the tax authority, but it should help you ask better questions.
What e-invoicing actually means
The term is used loosely, and the confusion costs money. Three things are often mixed together:
- A PDF sent by email. It is produced electronically, but a person still has to read it and key the figures into their own system. It is not e-invoicing in the regulatory sense.
- A structured e-invoice. A data file, normally XML, that the buyer's system reads directly. The supplier's ERP creates it, and the customer's ERP receives it, with no manual entry in between.
- Tax reporting. Sending transaction data, or a digital return, to the tax authority. This is a separate obligation, even if it often draws on the same invoice data.
Most of the regulatory activity in Europe concerns the second and third. In the UK, today's obligations sit mainly in the third category.
Where the UK stands
The UK has taken a different route from several European countries. Rather than a single national mandate for structured invoices, the focus so far has been Making Tax Digital, which requires digital records and digital submissions.
Two facts from the official guidance are worth knowing:
- Making Tax Digital for Income Tax has been mandatory since 6 April 2026 for self-employed people and landlords whose annual income, before expenses, is above 50,000 GBP.
- For the 2026-2027 tax year, no penalty points apply for late quarterly updates under Making Tax Digital. Late filing and late payment are still penalised.
If you run a limited company, Making Tax Digital for Income Tax does not apply to the company itself, but it may apply to directors with additional self-employment or rental income. Your VAT reporting, meanwhile, already depends on digital records and compatible software. Whatever the scheme, the principle is the same: figures should flow from your accounting records to the tax authority without being retyped.
The practical consequence for your ERP is that it must either submit data itself or hand it to a connected bridging tool, and it must keep the digital trail that links each return to the underlying transactions.
For the latest position on any wider e-invoicing plans, rely on GOV.UK rather than on commentary. Timetables in this area move, and a project plan should not be built on rumour.
Why UK companies still need to prepare
Even without a domestic mandate, three pressures are already reaching UK finance teams.
EU customers and suppliers
The EU directive known as ViDA, VAT in the Digital Age, makes structured electronic invoicing mandatory for business-to-business transactions between member states from 1 July 2030, according to the Dutch government and the Austrian Federal Economic Chamber. Several member states are also preparing or applying domestic rules that may come sooner. A UK company that sells into the EU, or has a subsidiary there, will be asked for compliant invoices by its customers.
Large customers
Large buyers, public bodies and multinational groups increasingly ask suppliers to send structured invoices through a network or portal. A supplier that cannot do so gets slower payment, manual queries or, in the end, less business.
Efficiency
Structured invoices cut re-keying, reduce disputes caused by typing errors and shorten the matching of invoices to orders and receipts. For accounts payable, the same gains apply in reverse when suppliers send you data rather than documents.
Formats, networks and platforms
Three terms recur in every e-invoicing project.
Formats. The common structured syntaxes are UBL and UN/CEFACT CII. On top of these sit profiles that define which fields are required, such as PEPPOL BIS. Different countries select different profiles, so an ERP needs to support several and be updated when they change.
Networks. Peppol is an international network in which suppliers and buyers exchange documents through accredited access points, in the same way that email travels between providers. Many countries use it, either as a mandatory channel or as a recommended one.
Platforms and intermediaries. Some countries require invoices to pass through a government-approved platform, or require data to be reported to the tax authority in near real time. These obligations are national, which is why you must ask which countries you trade with, not only where you are based.
| Concept | What it is | What it means for your ERP |
|---|---|---|
| Structured format | XML data file such as UBL or CII | The ERP must generate and read it, not only print a PDF |
| Profile | Rules on mandatory fields per country or network | Must be configurable and kept up to date |
| Access point | Provider that sends and receives on a network | Native connector, partner connector or third-party service |
| Tax reporting | Transmission of data to the authority | Often needs a certified or approved channel |
| Archiving | Retention of the original data file | The structured file, not just a PDF, may need to be stored |
What it changes inside the ERP
An e-invoicing project touches more of the system than the invoice template.
- Master data. Customer and supplier records need correct legal names, tax numbers, electronic addresses and, for public buyers, reference codes. Poor master data is the most common cause of rejected invoices.
- Tax configuration. Tax codes, exemptions, reverse-charge treatment and cross-border rules must map cleanly to the fields of the chosen format.
- Document workflow. The ERP needs a status for each invoice: created, sent, delivered, accepted or rejected. Someone must own the exceptions queue.
- Receiving invoices. Accounts payable should be able to ingest structured files, match them to purchase orders and receipts, and route exceptions. See our guide to ERP implementation for how this fits into the wider project.
- Archiving and audit trail. You must be able to show, years later, what was sent, when, and in which format.
What to check with major ERP vendors
We are not affiliated with any software vendor and take no position between them. The question is not which product is best, but how each delivers compliance and who is responsible for updates. Ask the same questions of every shortlisted system.
- Odoo is modular and has an active community. Check which e-invoicing and tax-reporting features are included in the edition and version you plan to use, and which come from additional modules. Our page on Odoo integrators explains what to expect from a project.
- Microsoft Dynamics 365 Business Central is delivered through a vendor ecosystem. Ask which localisation and which extension covers the formats and networks you need, and who supports it. Read more on Business Central.
- Sage products are widely used by UK finance teams. Confirm what is native, what depends on an add-on or connected service, and how Making Tax Digital submissions are handled. See Sage.
- Oracle NetSuite is a cloud ERP with a global footprint. Check how e-invoicing is handled for each country in which you have subsidiaries or customers, and whether it is a native feature or a bundle. See Oracle NetSuite.
- SAP Business One is aimed at smaller and growing companies. Clarify how structured invoices and tax reporting are supported in your version and who maintains the connector. See SAP Business One.
If you are still comparing systems, our ERP selection guide and the side-by-side comparisons put these questions in a wider context.
Questions to put to your vendor and integrator
The wording below is deliberately practical. Put it in your request for proposal and ask for written answers.
- Which structured formats does the ERP create and read today, and which are on the roadmap?
- Can it send and receive through an access point, and is this built in, partner-supplied or third-party?
- Which countries' rules are covered, and who updates them when rules change?
- How are Making Tax Digital submissions made: natively, through a certified bridging tool or by a separate service?
- How are invoices archived, and can you export the structured file as well as the human-readable copy?
- How are rejected or unmatched invoices handled, and who sees the exception queue?
- Is the cost of updates included in the support contract, or charged as projects?
The last question matters more than it looks. Compliance is not a one-off build. Rules, formats and interfaces change, and a system whose maintenance is nobody's job turns into a risk.
A good integrator will demonstrate these points on your own data, not on a polished sample. Our guide on choosing an ERP integrator lists what to look for.
A plan of action
You do not need to wait for a mandate. A sensible sequence is as follows.
- Map your exposure. List the countries where you sell, buy and have subsidiaries, and note the invoicing and reporting rules in each.
- Check your current ERP. Establish what it already does for formats, networks and Making Tax Digital, and where it relies on manual work.
- Clean the master data. Correct names, tax numbers and addresses before anything is automated.
- Choose the channel. Decide between a native module, a partner connector or an access-point provider, and who contracts with whom.
- Pilot with a friendly counterparty. Start with one customer or one supplier, then widen the scope.
- Document the process. Record who owns exceptions, updates and archiving.
- Review regularly. Rules change; schedule a periodic check with your integrator and your accountant.
If the check shows your current system cannot be adapted at reasonable cost, e-invoicing becomes one more factor in a migration decision. In that case, the requirements template is a useful place to record the points above so that they appear in the specification from the start. The expected budget varies with scope and number of entities, which is why the cost guide explains the main drivers rather than quoting a figure.
Common mistakes
- Treating a PDF generated by the ERP as compliance with a structured-invoice requirement.
- Buying a connector without asking who updates it when a format changes.
- Ignoring the receiving side, and then drowning accounts payable in files that do not match orders.
- Leaving tax codes inconsistent, so that valid invoices are rejected for technical reasons.
- Launching without an owner for the exception queue.
Most of these are avoidable and are described more broadly in our article on ERP project mistakes.
How we can help
ERP Integrator is a free service. You describe your project and your constraints, including e-invoicing and tax-reporting requirements, and we put you in touch with an integrator whose experience fits. The integrator carries out the project; we do not. How it works explains the process, and if you already know what you need you can go straight to the request form.
Frequently asked questions
Is e-invoicing mandatory in the UK?
There is no single UK rule that obliges every business to issue structured electronic invoices to its customers. What does apply is digital record-keeping and reporting through Making Tax Digital, which is already in force for VAT and, since 6 April 2026, for Income Tax for sole traders and landlords above the stated income threshold. Check GOV.UK for any change to the timetable before you commit to a project.
Does my ERP need to be Making Tax Digital compatible?
Yes, if the figures you report come from the ERP. Your ERP, or a bridging tool connected to it, must keep digital records and submit returns through the tax authority's interface without manual re-keying. Ask your vendor how this is delivered, who maintains it and what happens when the interface changes.
Why should a UK company care about EU e-invoicing rules?
If you sell to customers in EU member states, their rules apply to those transactions. The EU VAT in the Digital Age directive makes structured e-invoicing mandatory for cross-border B2B transactions between member states from 1 July 2030, and member states may bring in domestic requirements earlier. Your customers will increasingly ask you to send invoices in their required format.
What is the difference between a PDF invoice and a structured e-invoice?
A PDF is a picture of an invoice that a person has to read, even when it was generated by software. A structured e-invoice is a data file, usually in XML, that the receiving system reads directly. It can be matched to a purchase order and posted to the ledger without anyone typing the figures again.
How do I know whether my ERP can handle e-invoicing?
Ask your vendor or integrator to show, in a demonstration on your own data, that the ERP can create invoices in structured formats, send them through an access point or network, receive supplier invoices and keep an audit trail. Confirm who is responsible for updates when formats or tax rules change, and get this in writing in the project scope.
Sources
- GOV.UK – Sign up for Making Tax Digital for Income Tax
- Rijksoverheid – Kabinet kiest voor invoering e-facturatie en rapportage voor bedrijven
Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.