A comprehensive technical manual for finance teams, software developers, and accountants navigating European Union B2G/B2B e-invoicing mandates. Learn OASIS UBL 2.1 XML elements, OpenPeppol specifications, EAS schemes, and 4-corner network routing.
Directive 2014/55/EU established the mandatory acceptance of electronic invoices by public contracting authorities across the European Union. To achieve interoperability across disparate national accounting systems, the European Committee for Standardization (CEN) published EN 16931, defining a semantic data model for electronic invoices.
Peppol BIS Billing 3.0 (Business Interoperability Specification) is OpenPeppol's legal and technical implementation of EN 16931. It uses OASIS Universal Business Language (UBL 2.1) XML as its core syntax, establishing strict schemas for data structure, mandatory tags, business rules, and validation checks.
urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0urn:fdc:peppol.eu:2017:poacc:billing:01:1.0urn:oasis:names:specification:ubl:schema:xsd:Invoice-2Whether you are preparing for the Belgian mandate using Peppol BIS 3.0 or ensuring your ERP can generate XRechnung or ZUGFeRD output for Germany, our tool ensures your structured e-invoices align perfectly with the EN16931 European standard. The EN16931 semantic data model serves as the foundation for all national Core Invoice Usage Specifications (CIUS), making compliant data mapping crucial for seamless cross-border B2B trade. By utilizing client-side UBL XML generation to validate syntax against official OASIS and OpenPeppol schemas, finance and development teams can establish interoperability before connecting to a certified Peppol Access Point.
A major friction point for enterprise compliance teams is ERP system integration. Many legacy ERP systems (such as SAP, Oracle, or Microsoft Dynamics) alone cannot guarantee EN16931 validation or provide certified Peppol network access. Missing VAT numbers, malformed endpoint identifiers, or incomplete legal entity master data will cause invoice rejection at the Access Point level. Use our client-side UBL XML generation tool to quickly create and validate compliant output before attempting a test transmission through your Peppol Access Point. This positions our generator as a vital emergency utility for AP (Accounts Payable) teams and developers to execute master data validation and test payload creation prior to live transmission.
Unlike traditional e-invoicing where buyers and sellers maintain direct bilateral integrations, Peppol utilizes an open, decentralized network known as the 4-Corner Model:
The billing entity that originates the invoice data using our client-side XML generator or ERP software.
A certified Peppol service provider that validates, signs, and transmits the XML payload into the network.
The certified service provider receiving messages on behalf of the buyer using SML and SMP routing lookups.
The government agency or commercial buyer that processes the invoice into their ERP or accounts payable ledger.
Peppol BIS Billing 3.0 maps every business term to exact OASIS UBL 2.1 schema elements:
| Business Term (BT) | UBL 2.1 XPath Element | Card. | Description |
|---|---|---|---|
| BT-1 | /Invoice/cbc:ID | 1..1 | Unique invoice sequential identifier |
| BT-2 | /Invoice/cbc:IssueDate | 1..1 | Invoice issue date (YYYY-MM-DD) |
| BT-3 | /Invoice/cbc:InvoiceTypeCode | 1..1 | Commercial invoice code: 380 |
| BT-5 | /Invoice/cbc:DocumentCurrencyCode | 1..1 | ISO 4217 currency code (EUR, USD, GBP) |
| BT-34 / BT-49 | .../cac:Party/cbc:EndpointID | 1..1 | Participant ID with schemeID attribute |
| BT-106 | /Invoice/cac:LegalMonetaryTotal/cbc:LineExtensionAmount | 1..1 | Sum of net amounts of all invoice lines |
| BT-110 | /Invoice/cac:TaxTotal/cbc:TaxAmount | 1..1 | Total VAT amount for the invoice |
| BT-115 | /Invoice/cac:LegalMonetaryTotal/cbc:PayableAmount | 1..1 | Final total amount due for payment |
The schemeID attribute in cbc:EndpointID indicates the registering authority. Below are official ISO 6523 ICD codes used in Peppol:
Swedish companies & public bodies
French businesses & administration
International GS1 global location numbers
Dutch Chamber of Commerce
Danish business registry
Dutch government organization number
Italian Public Administration registry
Italian commercial VAT-registered businesses
The rollout of B2B electronic invoicing in Europe is accelerating rapidly. 2026 and 2027 mark a tipping point, with mandates going live in countries like Belgium (January 2026), France (September 2026), and Croatia (Fiskalizacija 2.0). Germany is also introducing a phased obligation leading up to 2027 and 2028.
B2B structured e-invoicing mandatory from January 1, 2026 for all VAT-registered entities using Peppol BIS 3.0.
Mandatory receipt of electronic invoices for all businesses starts September 2026, with mandatory issuance phased for large/mid caps.
Phased B2B mandate transition from 2025 leading into full compliance obligation for companies in 2027 and 2028 using XRechnung and ZUGFeRD formats.
Comprehensive B2B e-invoicing framework rollout integrating real-time reporting with Peppol and EU EN16931 standards.
Mandatory implementation of the National e-Invoicing System (KSeF) for VAT-registered businesses.
Mandatory B2B structured e-invoicing rollout for companies with annual turnover exceeding €8 million.
Peppol Business Interoperability Specification (BIS) Billing 3.0 is a standardized profile of the OASIS Universal Business Language (UBL 2.1) XML standard. It mandates exact XML element structures, data types, and business rules required for cross-border and domestic e-invoicing across European Union member states and participating international jurisdictions.
The Peppol network operates on a decentralized four-corner architecture: Corner 1 (Supplier/Invoice Generator), Corner 2 (Certified Sender Access Point), Corner 3 (Certified Receiver Access Point), and Corner 4 (Buyer/Accounting System). Corner 2 transmits the XML payload securely to Corner 3 after identifying the destination Access Point via the Service Metadata Locator (SML) and Service Metadata Publisher (SMP).
The exact XML element string for cbc:CustomizationID is: urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0. This indicates full compliance with European Standard EN 16931 and the Peppol BIS 3.0 specification.
EAS codes identify the scheme used for participant Endpoint Identifiers in the Peppol network. Examples include scheme 0088 (Global Location Number / GLN), scheme 0007 (Swedish Organization Number), scheme 0009 (French SIRET), scheme 0184 (Danish CVR), scheme 0201 (Italian IPA Code), and scheme 9925 (Italian VAT number).
The XML document generated by our tool strictly conforms to the UBL 2.1 and Peppol BIS 3.0 schema specifications. However, to submit an e-invoice to public sector buyers or tax authorities, the XML file must be transmitted through a certified Peppol Access Point provider (Corner 2 service).
E-invoicing is mandatory for Business-to-Government (B2G) transactions in all 27 EU member states under Directive 2014/55/EU. Countries including Italy, France, Germany (XRechnung), Spain, Belgium, Poland (KSeF), Romania (RO e-Factura), Denmark, Sweden, Norway, Australia, New Zealand, and Singapore have enacted or expanding B2G and B2B mandatory e-invoicing frameworks.
Create validated UBL 2.1 e-invoices with dynamic line items and instant file download. 100% client-side, zero data retention.