← Supported standards

Peppol BIS 3.0

OpenPeppol · Business Interoperability Specifications for the Peppol network SIGNET support: Normative mapping — machine-verified for Billing

What it is

Peppol is the pan-European (and increasingly global) network for exchanging electronic business documents between trading partners and public authorities. The Business Interoperability Specifications (BIS) define how those documents are structured on the network: BIS Billing 3.0 is a UBL-based, EN 16931-compliant invoice profile, with companion specifications for ordering and catalogues. In many jurisdictions, Peppol is the delivery rail through which national e-invoicing mandates are met.

The network and its specifications are stewarded by OpenPeppol AISBL. Official reference →

How SIGNET supports it

Peppol BIS sits in SIGNET's normative mapping tier. The specification's mapping table binds three canonical objects to Peppol profiles: Order to Peppol BIS Ordering, Catalogue to Peppol BIS Catalogue, and Invoice to Peppol BIS Billing. A conforming implementation MUST be able to transform between the canonical objects and these profiles without loss of the mapped fields.

For Billing, the mapping is continuously proven. The reference repository ships a transform that projects a canonical SIGNET invoice into UBL 2.1 / Peppol BIS Billing 3.0, together with a verifier that parses the generated document and reconciles every mapped EN 16931 Business Term and monetary total against the source. Both run in continuous integration on every change, and the generated output is committed alongside the source example so the projection is inspectable without running anything.

Because the alignment is anchored at the EN 16931 semantic layer that BIS Billing itself profiles, a SIGNET network can emit exactly the artefact a Peppol Access Point expects — without a bespoke integration per jurisdiction. The worked examples use the peppol identifier scheme for invoice numbering, reflecting how the two systems coexist in practice.

The reference transform is a faithful projection, not a substitute for official validation: production use should additionally apply the official Peppol validation artefacts.

Where it lives in the standard