How to create a Peppol BIS 3.0 invoice in UBL XML
Structured electronic invoicing replaces PDF email attachments with machine-readable XML that buyer accounting systems ingest without manual data entry. Generating a compliant file requires exact OASIS UBL 2.1 element ordering, valid participant identifiers, and balanced VAT totals, all of which this browser-based builder checks locally before export.
According to the OpenPeppol BIS Billing 3.0 Specification, every invoice must declare the exact customization URI urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0 and process URI urn:fdc:peppol.eu:2017:poacc:billing:01:1.0. The XML writer outputs OASIS UBL 2.1 Invoice (type 380) or CreditNote (type 381) elements in strict schema sequence.
| Peppol rule ID | Checked field | Validation condition | How to fix errors |
|---|---|---|---|
| PEPPOL-R003 | Buyer or Order reference | At least one reference non-empty | Enter a BuyerReference or PO number |
| PEPPOL-R020 | Seller EndpointID | Electronic address and schemeID present | Pick scheme (e.g. 0208) and enter ID |
| PEPPOL-R010 | Buyer EndpointID | Electronic address and schemeID present | Enter buyer Peppol ID or EM email |
| BR-CO-10 to 16 | Line and document totals | Totals match within 0.01 tolerance |
Check line quantities, discounts, and VAT |
| BR-CO-25 | Due date or terms | Required when payable amount exceeds 0 | Set a due date or payment terms |
After clicking Download e-invoice XML, you can inspect generated UBL XML files in a readable viewer to verify line items, VAT breakdowns, and party tags before sending.
How do Peppol EndpointIDs and the four-corner model work?
Under the Peppol four-corner model, your business (Corner 1) hands the UBL XML invoice to your certified Access Point (Corner 2), which routes it via the EndpointID to your customer’s Access Point (Corner 3) and ERP (Corner 4). This generator builds the compliant XML document itself, leaving AS4 network delivery to your registered Access Point.
Choosing the right participant schemeID such as 0208 or 0106
The editor provides 11 common PEPPOL_SCHEMES presets so your XML tags match national registries without manual lookup errors. Select 0208 for a 10-digit Belgian enterprise number (KBO/BCE), 0106 for a Dutch KvK number, 0204 for a German Leitweg-ID, 0192 for Norway, 0007 for Sweden, or 9925 through 9932 for national VAT schemes, or fall back to EM for email-based routing.
Belgium January 2026 B2B mandate and e-facturatie
Under the FPS Finance Belgium B2B E-Invoicing Portal, Belgian VAT-registered businesses must exchange structured B2B e-invoices (e-facturatie / facture électronique) via Peppol starting January 2026, replacing plain PDF attachments between domestic businesses. When a buyer only needs a human-readable PDF copy alongside structured billing, you can also generate a Belgian VAT invoice template for PDF billing.
VAT categories, arithmetic checks, and Nordic or German peers
Every Peppol file is anchored in EU Directive 2014/55/EU on EUR-Lex, which established the European semantic model EN 16931. Misaligned VAT category codes or rounding discrepancies are the most common reasons an Access Point rejects an uploaded XML file.
Preventing BR-CO-10 to BR-CO-16 rounding and VAT category errors
The built-in checker validates line extension sums, allowances, charges, and VAT bases to a 0.01 currency tolerance while writing quantities to 4 decimal places and unit prices to 6 decimal places. It also enforces category-specific rules, requiring a VAT ID on intra-EU supplies (K) and reverse-charge (AE) lines and an exemption reason when VAT is 0 percent.
Switching between Peppol BIS 3.0, XRechnung, and Nordic workflows
If a buyer asks for a different European profile, the format selector at the top of the editor lets you switch between Peppol BIS 3.0, ZUGFeRD / Factur-X PDF, XRechnung (CII), and XRechnung (UBL) without retyping your invoice. Businesses billing Scandinavian customers outside Peppol can also create Danish invoices with CVR and 25 percent Moms locally.
Local IndexedDB storage, XML export, and compliance scope
Company tax IDs, IBAN bank accounts, and customer pricing should never sit on an unknown third-party server. All drafts, saved client profiles, and XML serialization execute inside your browser’s IndexedDB and JavaScript runtime with zero external network calls.
Keeping supplier, buyer, and IBAN details on your device
Your business profile and client address book persist locally in IndexedDB unless you disable local remembering, which protects sensitive bank accounts and customer pricing across sessions. The validator also runs an ISO 13616 modulo-97 check on your IBAN and flags typos before you export your EN 16931 XML file, and retaining exported XML archives for 7 years to 10 years satisfies most EU VAT audit rules.
Tip: Always populate Buyer reference or Order reference even on small invoices, because rule
PEPPOL-R003is strictly enforced by Peppol receiving gateways across Europe.
Full Schematron validation and tax-advice boundaries
When billing German public-sector contracting authorities that require Leitweg-ID and German-specific BR-DE contact tags, switch to our tool to generate German XRechnung XML invoices in either CII or UBL syntax.
E-invoicing mandates, national CIUS extensions, and Peppol code lists verified as of 2026 evolve periodically. This generator is an operational XML authoring tool rather than certified tax or legal advice; verify full Schematron conformance with your certified Peppol Access Point and confirm VAT treatment with a qualified accountant.