Request a quote
Emergency SectorsCareers About us Blog Get in touch
Two developers at a desk with two monitors full of code; the standing colleague points at a line

E-invoicing is coming: what changes on the IT side

E-invoicing sounds like a tax matter, and the rules are. The work, though, sits somewhere else: in the mailbox where invoices arrive today, in the ERP that produces them, in the integration between the two and in the archive. This is what IT needs to have in place before a mandate reaches your organisation.

7 min read Written by the ITproposal team
Short answer

A PDF attached to an email is not an e-invoice. An e-invoice is a structured file that a system reads without anyone retyping it.

Receiving comes first: as soon as one customer, supplier or country requires it, your organisation has to be able to accept, process and keep these invoices.

The tax rules and dates per country are for HMRC or the relevant tax authority and your adviser; IT makes sure the systems can handle the format.

What e-invoicing is, and what it is not

With e-invoicing an invoice travels as a structured file from the supplier’s system to the buyer’s. Fields such as VAT number, invoice lines, amounts and purchase order number sit in a fixed place, so the finance system can read them without anyone retyping them or a scanner guessing what is there.

That is different from what most organisations call “digital invoicing” today. A PDF you email is a picture of an invoice, not an e-invoice in the sense of the new rules. That distinction is the heart of the change: a PDF needs a person to read it, an e-invoice a machine.

  • The standard: the European standard EN 16931 defines what data an e-invoice contains. Formats such as UBL implement it.
  • The network: Peppol is the network over which these invoices travel between organisations. You connect through a service provider known as an access point.
  • What it means for IT: the file no longer necessarily arrives in a mailbox, and it has to be picked up, checked and stored by a system.

Where e-invoicing is becoming mandatory, and where to check

The direction across Europe is the same; the pace differs by country. What is settled at the time of writing:

  • The EU: under the ViDA package (VAT in the Digital Age), e-invoicing becomes the norm for VAT-registered trade between businesses in different member states, and member states may introduce their own domestic mandate.
  • Belgium: since 1 January 2026, structured e-invoicing between Belgian VAT-registered businesses has been mandatory, with Peppol as the standard network.
  • Germany: since 1 January 2025, every domestic business must be able to receive e-invoices; transitional rules apply to sending.
  • The UK: there is no general business-to-business mandate in force as we write this, but the direction of travel is clear. Check HMRC guidance for the current position rather than relying on an article.

Two questions decide when it reaches you: where you are VAT-registered, and where your customers and suppliers are. A UK organisation with a Belgian subsidiary or German customers may be affected well before any UK rule applies. Which rule applies to your situation, and from when, is a question for your tax adviser or accountant and the tax authority of that country; we do not answer it.

Receiving is the first job

You can plan sending; you cannot plan receiving. As soon as a supplier is required to send an e-invoice, it arrives, ready or not. So start on the inbound side.

  • Map where invoices arrive today. A shared mailbox, a scanning service, a supplier portal, one colleague’s inbox. There are usually more routes than anyone thought.
  • Decide where e-invoices land. In the finance system itself, through a module from its vendor, or through a separate service that passes them on. The choice belongs to finance; IT makes sure the route works and that no second, forgotten entrance is left open.
  • Register on the network. A Peppol ID in your organisation’s name, one per legal entity if you have several, with a named owner.
  • Test with a real invoice. Ask a friendly supplier to send one and follow it until it is posted and archived. An integration that only works on paper otherwise shows itself at the first payment reminder.

Sending: your master data becomes visible

A PDF tolerates sloppiness; an e-invoice does not. The recipient’s system checks mandatory fields and can reject an invoice. What used to be a query from accounts payable becomes a rejected file.

What to get in order first:

  • Customer data: VAT numbers, company registration numbers, addresses and the Peppol ID of every customer who invoices this way.
  • References: purchase order numbers and cost centres that large customers insist on. Without the reference, your invoice stops.
  • Error handling: who sees a rejected invoice, how quickly, and who corrects it. Without a named owner, a rejection sits for weeks in a queue nobody opens.

Integrations: which system creates the invoice

In many organisations it is not one system that creates invoices but three or four: the ERP, the web shop, the timesheet tool, the till system, sometimes a spreadsheet. Each of those sources has to deliver the right format, or hand its data to a system that can.

  • List the sources and for each one note what it invoices, to whom, and whether the software vendor supports e-invoicing or only promises to.
  • Agree who owns each integration. The software vendor, the e-invoicing service or your own IT. In an outage that is the first question, and you do not want to be searching for the answer then.
  • Monitor the integrations. An integration that stops does not put an error on your screen; it simply sends nothing. Agree who notices, and how.

Archiving: keep the file, not just the view

Record-keeping rules apply to e-invoices as well; in the UK, VAT records are generally kept for six years. The difference from before: the original is the structured file, not the readable PDF your system renders from it. Keep the file as it arrived or left.

  • Unalterable and findable: an archive in which nobody can change an invoice afterwards, and in which you can find a five-year-old invoice in minutes.
  • Backup and exit: if your invoices sit with a service, find out how you get them out when you switch. Ask before you sign.
  • Email separately: an invoice that still arrives by email falls under your email archive. How that works is covered in our article on email archiving.

Access rights and invoice fraud

E-invoicing makes it harder to send a forged PDF, but it does not remove the best-known fraud: a “supplier” announcing that their bank details have changed. That message still comes by email or phone, and the money still goes wherever the master data says.

  • Rights in the portal and finance system: who may change supplier details, who may pay, and are those different people.
  • MFA on every account that can view, approve or forward invoices.
  • A fixed check on changed bank details: call back on a number you already had, never the one in the message.

How to protect the email side of this is covered under endpoint and email security.

Where our work stops

What we do. We make sure your systems can receive and send e-invoices: the route from mailbox or network to the finance system, the integrations with your ERP and other sources, access rights and MFA, monitoring, the archive and backup. We are ISO/IEC 27001 certified, and that is how we handle that data.

What we do not do. We are not tax advisers, accountants or lawyers: we do not tell you when a mandate applies to your organisation or what must appear on an invoice for tax purposes. Check that with HMRC or the tax authority of the country you invoice in, and with your adviser. Nor are we an e-invoicing platform or a Peppol service provider; that service comes from a third party, and we make sure your environment connects to it.

Frequently asked

Questions we get about this

The five that come up most often.

What is e-invoicing?

E-invoicing is sending and receiving invoices as a structured file that a system can read automatically. The data sits in fixed places according to the European standard EN 16931, and the invoice usually travels over the Peppol network from system to system. Nobody has to retype anything.

Is a PDF invoice an e-invoice?

No. A PDF is a readable rendering that a person has to process. An e-invoice in the sense of the new rules is a structured file, for example in UBL, that a system reads. Many packages send both, but the structured file is the original.

Is e-invoicing mandatory in the UK?

There is no general business-to-business mandate in force as we write this, though the direction is clear. Check HMRC guidance for the current position. If you have customers or entities in EU countries such as Belgium or Germany, look at their rules too, because those already apply.

What is Peppol?

Peppol is a network and a set of agreements through which organisations exchange e-invoices and other documents. You connect through a service provider called an access point and receive a Peppol ID under which others can reach you. In Belgium, among others, it is the standard route for e-invoicing.

Are you an e-invoicing platform or a tax adviser?

No, neither. We make sure your systems can receive and send e-invoices: integrations, access rights, monitoring, archive and backup. The service that carries invoices over the network comes from a third party, and the tax question of when and how you must invoice is for your adviser and the tax authority.

Related services

Further reading

Where e-invoicing connects.

Shall we map your invoice flows?

We go through where invoices arrive and leave today, which systems create them and where they are kept, and tell you what has to happen technically. The tax questions stay with your adviser.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call