An e-invoice is not a PDF of your invoice

You already send invoices electronically. You raise the document, save it as a PDF, attach it to an email. Done, surely, whatever this e-invoicing noise is about.

Unfortunately no, and the distinction has stopped being pedantic. Belgium's tax administration put it about as bluntly as a government website can: "Sending a PDF invoice by e-mail or via a platform will no longer be enough." That sentence became law there in January. Understanding why is worth ten minutes of any contractor's time, because the same logic is now working its way toward the UK with a date attached.

What counts as an e-invoice — and why a PDF doesn't

An e-invoice is structured data. Buyer, seller, every line, every VAT rate, every total, each sitting in a named field that software can read directly, the way your bank reads a sort code. The number £1,461.00 is not a shape on a page that a human recognises as a total; it is a field called "total" containing 1461.00.

A PDF, for all its convenience, is the opposite: a picture of an invoice. A human reads it effortlessly. A machine has to guess at it, which is why the receiving end of most invoices is still someone retyping figures into an accounts package, or OCR software doing the same thing with more confidence and similar accuracy. Figures cited by HMRC and the Department for Business and Trade put manual entry at 80% of businesses globally, with around 10% of entered data carrying some form of error. Every one of those errors is a query, and every query is a delay to you being paid.

There is a European standard for what the structured version must contain, called EN 16931. You do not need to remember the number. You only need to know that when Germany, France, Belgium or the EU institutions say "e-invoice", they mean data conforming to that standard, and a PDF on its own conforms to nothing.

The clever compromise: one file, two readers

The obvious objection is that humans still need to read invoices, and nobody wants to open raw XML to find out what they owe. The answer the French and Germans settled on jointly is called Factur-X: an ordinary PDF with the structured data file embedded inside it. One file. Your client opens it and sees a normal invoice. Their accounts software opens the same file and finds the machine-readable version tucked within. The Germans call the identical specification ZUGFeRD; it is one standard wearing two national badges.

Germany's Ministry of Finance accepts these hybrid invoices at their fuller profiles, and its rules contain a detail worth pausing on: in a hybrid invoice, the embedded data is the legally governing part. If the PDF says one number and the XML says another, the XML wins. Which means the era of "the PDF is the invoice and the data is a nice extra" is already over in the largest economy in Europe. The data is the invoice now. The PDF is the courtesy copy.

Why tax authorities suddenly care

Two reasons, and neither is love of technology.

The first is the errors above. HMRC's own analysis attributes 22% of the VAT gap in 2022-23 to error and failure to take reasonable care, not fraud. Structured invoices attack that directly: data that is never retyped is never mistyped.

The second is fraud, and here the European Commission estimates the stakes at up to €11 billion a year in reduced VAT fraud, alongside over €4 billion a year in lower compliance costs. Those are the Commission's projections rather than measured results, but they explain the legislative energy. In April 2025 the EU removed the two legal brakes that had held everything back: member states no longer need Brussels' permission to mandate e-invoicing, and your customer no longer has a right to refuse one. The dominoes you can watch falling across Europe — Belgium in January, France this September, Germany's issuing rules from 2027 — all trace back to that change.

Where the UK actually stands

Further along than most contractors realise. The government consulted on e-invoicing in early 2025, and the consultation response landed alongside a decision at Budget 2025: e-invoicing becomes mandatory for UK VAT invoices from April 2029, covering business-to-business and business-to-government alike. In June 2026 the government confirmed the network it will run on (a system called Peppol, if you collect names), with the detailed roadmap promised at the autumn Budget.

So nothing is mandatory here today, and the technical fine print is genuinely unwritten. But "voluntary" and "distant" are different things. April 2029 is two customer contracts away, and the adjacent machinery is already running: Making Tax Digital began pulling sole traders over £50,000 into quarterly digital reporting this April. The direction of travel only points one way.

There is a nearer-term version of this too. If any of your clients are European — a facilities group with a Paris head office, a German-owned manufacturer's UK sites — the request for a structured invoice will arrive from their procurement department long before it arrives from HMRC. Their side is already being rebuilt around ingesting data, and suppliers who still send pictures of invoices become the awkward manual step in an automated process. That is rarely a conversation about compliance. It is a conversation about staying easy to buy from.

What an e-invoice is not

One honest boundary, because vendor marketing in this area is fog. Producing a valid e-invoice file is not the same as being connected to a country's invoicing network. France, for instance, will require domestic businesses to exchange invoices through approved platforms; Italy clears everything through a state system; the UK's future network is its own machinery. A file format cannot plug you into any of that, and anyone who implies their PDF workflow "complies with the French mandate" is selling something. What the file format does do is carry your invoice data in the shape all of those systems speak, which is the part that lasts.

For our part, we built this in rather than selling it as a module. Every invoice issued in BlueWave goes out as a Factur-X e-invoice at the EN 16931 profile: the branded PDF your client reads, with the structured data embedded inside, checked against the official European rulebook invoice by invoice before the PDF is even built. There is nothing to switch on and no per-invoice fee — it is simply what an invoice is here. The data half of your invoices is the half that can't be retrofitted later, so we'd rather you were accumulating it now.

And if the regulatory angle leaves you cold, the operational one still stands: the same structured data that satisfies a tax authority is what lets an invoice be raised from completed work instead of retyped from it, and the retyping was always the expensive part.