Europe's e-invoicing mandates in plain language: what a POS actually has to do

If you trade in the European Union, you have probably been told that e-invoicing is coming, usually by an accountant, a software vendor, or a letter you did not entirely read. The subject has an unhelpful reputation: it sounds like an accounting department problem, it is described in acronyms, and every country is doing it slightly differently. It is worth understanding properly, because the parts that affect a retailer or a restaurant are fewer and more concrete than the noise suggests.

What a mandate actually requires

Strip away the acronyms and almost every European regime asks for the same three things. First, that the invoice is a structured data file - XML, not a PDF of a picture of an invoice. Second, that it follows a common semantic standard, EN 16931, so that a Polish system and a Dutch system agree on what 'net amount' means. Third, that it travels through a specific channel: a shared network, or a government portal that inspects it.

The third part is where countries diverge, and it is the part that matters most operationally. Some regimes are post-audit: you issue the invoice, and it is reported afterwards. Others are clearance models: the government sees the invoice and approves it before it is legally valid. Clearance is the demanding one, because it puts a network call between you and a valid document.

Who is doing what, and when

These are the dates our customers are planning around at the time of writing. Treat them as a map rather than a legal reference, and check your own before you build a plan on them.

The pattern is worth noticing. Nothing here gets simpler over the next decade, and a business with sites in three countries is not managing one compliance project - it is managing three, on three timetables, forever.

Why this is a point of sale problem, not an accounting one

The instinctive response is to treat e-invoicing as something the finance system handles at month end. That works right up until the moment the format demands data your till never captured - a buyer's VAT identifier, a structured reference, a line-level tax category, a unit of measure code. Then somebody is retyping invoices, and the whole exercise has become manual data entry with extra steps.

The clean answer is that the document is assembled correctly at the point the sale happens, because that is the only moment when all the information genuinely exists. Everything downstream is then just transmission.

The question everyone should ask: what if the server is down?

This is the right question, and it separates serious implementations from box-ticking ones. Under a clearance model you are asking a government platform for permission. That is fine at nine on a Tuesday morning. It is a catastrophe at seven on a Friday evening if your till waits for an answer that is not coming.

• Ask the vendor to show you the queue. If there is no visible queue, there is probably no real queue.
• Ask what happens when the government platform itself is unavailable for several hours. It is not hypothetical - every clearance system has had outages.
• Ask for a reconciliation report: invoices recorded versus invoices transmitted, for any date range.
• Ask whether the till keeps selling. If the honest answer is no, keep looking.

What changes at the counter

For consumer sales, usually very little visibly - most current mandates target B2B first. Where it does reach retail, expect a structured reference on the receipt and, in some regimes, a verification QR code. The bigger change is behind the counter: your product data needs tax categories, your customer records need VAT identifiers for business buyers, and someone needs to watch a transmission queue for the first few weeks.

A short checklist before you sign anything

1. 1Which specific regimes does the vendor support today - not on a roadmap, today?
2. 2Is e-invoicing included in the price, or an add-on with its own recurring fee per site?
3. 3Does the product generate EN 16931 structured documents itself, or hand off to a third party you will also pay?
4. 4Can it route through Peppol as well as national portals, since you may need both?
5. 5Does the till keep selling when the platform is unreachable, and can you inspect the queue?
6. 6Who runs the sandbox testing and the onboarding - you or them?
7. 7How do they track mandate changes, and will they tell you when a date affects you?
8. 8If you already use a Peppol access point, can you keep it?

None of this is difficult to evaluate. It is just rarely asked, because e-invoicing sounds like somebody else's department right up until the week it becomes yours.