E-invoicing is not something we invented to sell you. It is how invoices are increasingly required to be exchanged across Europe — as structured data rather than as a PDF. This page explains what that means, how the rules differ per country, and how we get you ready.
A PDF emailed to a customer is not an e-invoice. It is a picture of an invoice that a person still has to read and retype. An electronic invoice is the same commercial information in an agreed structured format — fields the receiving system can validate, post and pay without anyone opening it.
That is the whole shift, and everything else follows from it. Once the invoice is data, it can be checked against tax rules automatically, matched to a purchase order automatically, and delivered without either side agreeing on a file layout first.
It also explains why governments care. Structured invoices are what make VAT reporting verifiable at scale — which is why e-invoicing is moving from good practice to legal requirement across Europe.
Structured invoices travel over shared infrastructure rather than bilateral links. You join through an accredited provider, providers exchange with each other, and one connection is enough to reach everyone else who is connected. In most of Europe that infrastructure is the Peppol network; some countries run their own regime alongside it.
The document is created where it was always created — in your ERP, as a normal sales invoice, order or dispatch advice.
It is converted into the structured format the destination country requires, validated against that country's rules, and handed over for transport.
The receiver's provider takes delivery. Sender and receiver never need a bilateral agreement or a shared file format.
The document arrives as data in the recipient's software, ready to be processed — no PDF, no scanning, no re-keying.
This is why it scales where point-to-point EDI does not: connect once, reach everyone who is also connected.
Plenty of organisations would have got to structured invoicing eventually. What changed is that governments across Europe are making it mandatory, on dates that are already published.
We do not sell the rules. What we sell is the thing that gets your Dynamics environment compliant and keeps it there while the rules keep moving.
Infivex works with B2Brouter, a certified Peppol Access Point. That is the accredited doorway onto the network — the piece you cannot build yourself and should not try to.
SLinkHub is our own platform, and it is how customers get their Dynamics environment — Business Central, NAV, BC - On Premise, Finance & Operations — sending and receiving electronically. It handles the formats, the validation and the country rules so your ERP does not have to.
Explore SLinkHubNo — and this is the single most common misunderstanding. A PDF, even a signed one emailed automatically, is an image of an invoice that a person still has to read and retype. An e-invoice is structured data the receiving system can process on its own. Under the incoming mandates, emailing PDFs will not count as compliant.
Not quite. Peppol is the network most of Europe uses to move e-invoices around, and it is a public one — not owned by us or by any vendor. But it is the delivery mechanism, not the obligation, and not every country uses it. France in particular runs its own regime through government-registered platforms. So the question to answer is "are we compliant in the countries we invoice in", and the route follows from that.
Delivery goes through an accredited provider that exchanges documents with other providers on your behalf. Infivex works with B2Brouter, a certified Peppol Access Point. You do not interact with it directly — SLinkHub sits in front of it, and your ERP talks to SLinkHub.
Business documents in an agreed structured format — invoices most visibly, but also orders and dispatch advices. The point is that they arrive as machine-readable data in the receiver's system rather than as a document a person has to read and retype.
That is when the French DGFIP reform lands. Note that France is not simply "switching on Peppol" — it runs its own regime, with its own registered platforms and its own formats, which is why we talk about e-invoicing readiness per country rather than about one network. It is worth treating as a project rather than a switch: identification, ERP readiness across every entity, and testing before the date rather than during it. The French requirements are built into SLinkHub ahead of the deadline, so the conversation is about your rollout, not about whether the platform will be ready.
Not because of e-invoicing. SLinkHub has interfaces for Dynamics NAV and Business Central - On Premise alongside current Business Central and Finance & Operations, precisely so a compliance date does not force an ERP migration on you. If you want to modernise, that stays a decision you make on business grounds.
Tell us which countries you invoice in and which Dynamics versions you run. We will tell you what your obligation looks like and what getting compliant would involve.