E-invoicing go-live playbook

Switching to electronic invoicing is not like onboarding a bilateral EDI partner. Your “counterparty” is often the State (a clearance model) or a network (PEPPOL), not a single company. Here is the path, from zero to go-live, in seven steps.

Why it's different from classic EDI

• The obligation comes from the law, not from a customer: the timeline and format are imposed.
• A common semantic format (EN 16931) rather than a map negotiated partner by partner.
• A trusted third party or the State on the path: clearance (Italy, Poland…) or a four-corner network (PEPPOL).

Step 1 — Map your obligation

Before any technology: where and when are you obliged? List your issuing and receiving countries, the scope (B2G, B2B, B2C) and the entry-into-force date. The European e-invoicing roadmap and the country pages give the timeline. The model varies a lot: real-time clearance, a post-audit network, or a public portal.

Step 2 — Choose the channel

The channel depends on the country and model:

• PEPPOL access point: for the four-corner network (EU, Australia, Singapore…). You go through a certified access point.
• PDP / public portal: in France, a PDP (partner dematerialisation platform) or the public portal (PPF) as concentrator/directory.
• Clearance platform: Italy's SdI, Poland's KSeF — a mandatory State gateway.

You either operate an access point yourself or — most commonly — go through a provider (see the software comparison).

Step 3 — The identifiers

An invoice must identify its parties unambiguously and know where to be delivered:

• Legal identifier: SIREN/SIRET (France), VAT, LEI, national organisation number.
• Electronic address (EndpointID + EAS / ICD scheme): this is what routes on PEPPOL.
• Specific routing keys: Leitweg-ID (Germany), Codice Destinatario (Italy).

Register your reception endpoint in the network directory (SMP / directory) to be reachable.

Step 4 — Choose the format

The semantic core is EN 16931, materialised in CII or UBL. Depending on the country you apply a CIUS (XRechnung, PEPPOL BIS) or a national format (FatturaPA, Facturae). In B2B the hybrid Factur-X format eases the transition (readable PDF + XML). Map your ERP onto these fields (BT-*/BG-*).

Step 5 — Validate

An invoice must pass two layers of checks: the common EN 16931 (BR-*) business rules, then the national rules (BR-DE, RO_CIUS…), expressed in Schematron. Build validation into your chain before issuance: EN 16931 validator, PEPPOL validator, Schematron runner.

Step 6 — Test

Before production: representative test data, the channel's test environment (PEPPOL test bed, SdI test, KSeF pre-production), and end-to-end tests including the receipts. See testing EDI pipelines for fixtures, mocks and CI validation.

Step 7 — Go-live and operations

E-invoicing go-live does not stop at issuance: you must handle the responses.

• Receipts: ricevuta di consegna (SdI), MLR / Invoice Response (PEPPOL), UPO (KSeF).
• Rejections: notifica di scarto (Italy) = the invoice is deemed not issued — fix and reissue.
• Monitoring: rejection rate, acknowledgement delays, queue depth. See monitoring your stack.

Common pitfalls

• Missing or wrong addressing (EndpointID, Leitweg-ID, Codice Destinatario) → non-delivery or rejection.
• Unreconciled totals (BR-CO) → the invoice fails validation.
• Inconsistent VAT category (exemption without a VATEX reason, mis-coded reverse charge).
• Confusing e-invoicing and e-reporting: these are two distinct obligations.
• Forgetting legal archiving (tamper-evident retention).

Further reading

• EDI partner onboarding playbook — the classic-EDI counterpart (AS2/AS4).
• European e-invoicing roadmap — the regulatory timeline.
• EN 16931 — the core standard, and its syntaxes CII / UBL.