Free tier

← All guides · Peppol

Peppol vs national platforms: network countries and portal countries compared

By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Convert an invoice free

Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.

Short answer

Europe's mandates run on two architectures. Network countries — Belgium above all — deliver invoices between private access points over Peppol, addressed by Peppol ID. Platform countries — Poland's KSeF, Italy's SdI, France's PDP/PPF system — route invoices through a national or approved platform that validates and holds the operative copy. For suppliers the delivery mechanics differ; the invoice discipline — validated EN 16931 data — is identical.

Network model vs platform model: the difference

In this product's mandate table the two models appear as channel values: Peppol for Belgium (and voluntarily elsewhere); KSeF for Poland; 'PDP / PPF (Factur-X accepted)' for France; 'SdI (FatturaPA)' for Italy; 'EN 16931 (XRechnung / ZUGFeRD)' for Germany's document-based approach; 'VeriFactu / EN 16931' for Spain. The checker names the channel in every verdict, because the channel decides how a structured invoice travels — not whether it must exist.

The network model: Peppol's four corners

In the network model there is no centre. Your access point looks up the recipient's Peppol ID, finds their access point, and delivers the document across; confirmations flow back along the same path. The state's role is to mandate the rails and the rules, not to touch each invoice. Belgium chose this model for its January 2026 B2B mandate, and the voluntary Peppol countries (Netherlands, Austria, Sweden) show the same rails carrying traffic without a mandate at all.

For suppliers, the network model's signature experiences are identity and addressing: you hold an account with your chosen access point (here, Qvalia free), your Peppol ID is your address, your clients' IDs are your address book, and delivery evidence lives with your carrier. Onboarding a new country often means nothing more than a new address in the book — the network already spans the border.

The platform model: KSeF and SdI

In the platform model, invoices pass through a national system that validates them and becomes the point of truth: Poland's KSeF, through which structured invoices are issued under the 2026 phases; Italy's SdI, routing FatturaPA invoices since 2019. France's design is a hybrid — approved private platforms (PDP) plus the public platform (PPF) — but the family resemblance holds: a defined platform layer sits in the invoice's path, with its own intake rules and its own record of the document.

For suppliers, the platform model's signature is specification: each platform has its format expectations and its process for issuance and correction, which your client — the party inside that system — will specify. Your leverage is the same as everywhere: invoice data so clean that any platform's intake is a formality. Platforms reject bad data with codes, just as validators do; the discipline that passes one passes the other.

Germany and Spain: the document-model middle

Germany's channel is named by its documents — EN 16931 as XRechnung or ZUGFeRD — with receiving and issuing duties but no single national portal in the table's model: invoices travel between the parties' systems in the specified formats. Spain's 'VeriFactu / EN 16931' pairing similarly joins a national verification ecosystem to the European standard. These middle models remind suppliers that 'structured' is the invariant and the plumbing varies by jurisdiction and era.

The practical reading: never ask 'what is Europe's system?' — ask 'what is this client's channel?', a question with a one-line answer per client, recorded in the client file at onboarding. The mandate table in this product is organised exactly that way — per country, a channel — and the checker reports the channel with every verdict so the answer is never separated from the obligation.

What differs for you, concretely

Three things differ by model. Addressing: Peppol IDs in network countries; platform accounts, recipient codes or client-specified routes in platform countries. Evidence: delivery confirmations from your access point versus platform acknowledgements and statuses. Setup: an access point account you open once (with its verification wait) versus per-client route agreements as platform clients onboard you into their process.

Three things never differ. The invoice data must be complete and rule-valid. Cross-border identifier discipline (seller's VAT ID always; buyer's for reverse charge) applies in both worlds. And the readable copy for humans — the Factur-X PDF — remains useful everywhere, because every model still employs people who approve invoices by reading them. Suppliers who internalise the constants find each new country's variable part small.

Planning a mixed portfolio

Most EU-facing suppliers end up mixed: a Belgian Peppol client, a Polish KSeF client, an Italian SdI client, German document-model clients. The portfolio strategy that survives this variety is to industrialise the constant and administrate the variables: one conversion-and-validation process producing the artefact set; a client record per relationship carrying its channel, identifiers and dates; monitored clients watching the verdicts; and channel mechanics treated as address-book entries rather than as separate crafts.

That is, in the end, the architecture of this product itself: one engine, one mandate table, channels named per country, and guided sending where the network model applies. Learn the constant deeply once, and the map's variety reduces to a column in a spreadsheet you already keep.

Working across both models in 5 steps

  1. Record each client's channel at onboarding: Peppol network, national platform, or document route — from the mandate table's channel for their country.
  2. For Peppol clients, collect Peppol IDs; for platform clients, record the route and recipient details their process specifies.
  3. Keep one conversion process for all: validated EN 16931 data is the constant every channel consumes.
  4. File evidence per model: access point confirmations for network sends, platform acknowledgements for platform routes.
  5. Let the checker name the channel with each verdict — never separate the obligation from its delivery route.

Worked example: two invoices, two architectures, one morning

A firm's Monday run includes a EUR 2,400.00 invoice to a Belgian agency and a EUR 1,500.00 invoice to a Polish manufacturer. Both are converted and validated identically — reverse charge AE, identifiers present, totals reconciled. Then the paths fork: the Belgian UBL is uploaded in the firm's Qvalia account and sent to the agency's Peppol ID, confirmation filed from Qvalia. The Polish invoice follows the route the manufacturer's process specifies for their KSeF world, its data equally platform-ready.

Same data discipline, same morning, two architectures — and the firm's effort difference between them is measured in minutes of routing, because everything expensive (correct data, proven totals, complete identifiers) was shared. That ratio is the whole strategy for multi-country suppliers.

Frequently asked questions

Which countries use Peppol as the mandate channel?

Belgium is the mandate case in the table (from January 2026). The Netherlands, Austria and Sweden show voluntary Peppol use; Ireland uses Peppol for B2G.

Which countries use national platforms?

Poland (KSeF, phasing through 2026) and Italy (SdI, since 2019); France routes through approved platforms (PDP) or the public platform (PPF).

Does the channel change the invoice format I produce?

The artefact is the validated EN 16931 invoice (UBL XML, plus the Factur-X PDF) in both worlds. Platforms add their own format and process layer, which your client specifies; the data discipline is unchanged.

Where does delivery proof live in each model?

Network model: your access point's confirmation (in Qvalia, on the guided route). Platform model: the platform's acknowledgement and statuses, per that platform's process.

Can one supplier really serve both models with one process?

Yes — that is the design premise of this product: one engine and mandate table, channels named per country, and per-client records carrying the variable parts.

Keep going

Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides

Related guides

← Back