UBL / Peppol Invoice Validator BIS 3.0 & EN 16931
This free tool validates UBL 2.1 invoices and credit notes for XSD schema compliance and Peppol BIS Billing 3.0 business rules (EN 16931 standard). It is designed for developers, accountants, and finance teams who need to verify their e-invoices before submitting them through the Peppol network.
XRechnung & Peppol BIS 3.0 Validator for German Companies
Germany mandates XRechnung (UBL-based) for B2G since 2020 and structured e-invoicing for B2B from 2027. Validate your XRechnung or Peppol BIS 3.0 invoices for EN 16931 compliance — free, no upload.
Open XRechnung ValidatorXRechnung and UBL in Germany: B2G and B2B obligations
XRechnung is Germany's national e-invoicing standard for public procurement (B2G), defined by KoSIT. It is based on two syntaxes: UBL 2.1 (CIUS DE) and UN/CEFACT CII. All federal suppliers must submit XRechnung invoices via the ZRE (Zentrale Rechnungseingangsplattform) or OZG-RE platforms since November 2020.
For B2B transactions, the Wachstumschancengesetz establishes mandatory structured e-invoicing from 2027. XRechnung and Peppol BIS Billing 3.0 are both accepted formats. Companies must be able to receive structured e-invoices since January 2025. ValidateFin validates the UBL syntax of XRechnung invoices against EN 16931 and Peppol BIS 3.0 rules.
Compliance timeline
B2G (federal): XRechnung mandatory for all federal public procurement. Submission via ZRE or OZG-RE platforms.
B2B: all German VAT-registered companies must be technically capable of RECEIVING structured e-invoices (EN 16931).
B2B: mandatory EMISSION of structured e-invoices for companies with annual turnover >800,000€.
B2B: mandatory emission extended to all German VAT-registered companies including micro-enterprises.
What ValidateFin checks in your XRechnung / UBL invoice
Before submitting to ZRE or a buyer system, verify your XRechnung / UBL invoice passes these checks:
- UBL 2.1 schema validation against XRechnung CIUS DE and Peppol BIS Billing 3.0 specification
- EN 16931 mandatory fields: seller/buyer VAT (USt-IdNr. DE format), invoice number, delivery date, tax breakdown
- Leitweg-ID (BT-10): buyer reference mandatory for all B2G XRechnung invoices submitted to ZRE
- German VAT number format: DE + 9 digits (Umsatzsteuer-Identifikationsnummer)
- XRechnung profile identifier: CIUS-DE conformance level in cbc:CustomizationID
Common XRechnung errors causing ZRE rejection
Missing or invalid Leitweg-ID (BT-10)
The Leitweg-ID is the routing identifier of the German public entity. It must appear in cbc:BuyerReference. Without it, ZRE cannot route the invoice to the correct recipient — immediate rejection.
Wrong cbc:CustomizationID for XRechnung
XRechnung invoices must declare the CIUS-DE profile in cbc:CustomizationID (e.g. urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_2.3). Mismatches fail ZRE validation.
Invalid German VAT number format
German Umsatzsteuer-Identifikationsnummer must follow the format DE + 9 digits (e.g. DE123456789). Missing DE prefix or wrong digit count causes EN 16931 rule failure BR-DE-01.
Frequently asked questions
Is XRechnung the same as Peppol BIS 3.0?
XRechnung and Peppol BIS Billing 3.0 are both UBL 2.1-based formats implementing EN 16931, but they are different CIUS (Core Invoice Usage Specifications). XRechnung (CIUS-DE) adds German-specific mandatory fields (Leitweg-ID, specific VAT rules). Peppol BIS 3.0 is the pan-European standard used on the Peppol network. Both are accepted for German B2B e-invoicing from 2027.
Can ValidateFin validate XRechnung invoices?
ValidateFin validates the UBL 2.1 structure and EN 16931 / Peppol BIS 3.0 business rules of your invoice. For XRechnung-specific CIUS-DE rules, the core validation (Leitweg-ID presence, German VAT format, mandatory fields) is included. Full KoSIT XRechnung rule set support is being extended progressively.
My company must receive e-invoices since January 2025 — what does that mean technically?
Since January 2025, your accounting system or ERP must be able to import and process structured e-invoices in at least one EN 16931-compliant format (XRechnung UBL, XRechnung CII, ZUGFeRD 2.x, or Peppol BIS 3.0). ValidateFin helps you inspect and validate any received UBL invoice to ensure it is correctly structured.
E-invoicing guides by country
Validate your XRechnung or Peppol invoice before submission
Check UBL 2.1 structure, EN 16931 rules, and XRechnung compliance instantly. No file uploaded.
About the UBL / Peppol Invoice Validator
This free tool validates UBL 2.1 invoices and credit notes for XSD schema compliance and Peppol BIS Billing 3.0 business rules (EN 16931 standard). It is designed for developers, accountants, and finance teams who need to verify their e-invoices before submitting them through the Peppol network.
The validator checks structure, mandatory fields, VAT consistency, line item totals, and dozens of business rules defined in the European e-invoicing standard. All processing is done locally — no invoice data is ever sent to a server.
UBL (Universal Business Language) 2.1 is an OASIS standard that defines XML schemas for common business documents including invoices, credit notes, and orders. Within Europe, the Peppol network uses UBL as its primary invoice format, governed by the BIS Billing 3.0 specification which implements the EN 16931 European standard. As EU member states roll out mandatory e-invoicing (France in 2026, Germany in 2025 for B2B, Belgium via Peppol from January 2026), the ability to validate UBL invoices before transmission becomes essential for compliance.
The validation covers two layers: structural validation against the UBL 2.1 XSD schema (checking element names, data types, and cardinality) and semantic validation against Peppol business rules (checking that tax calculations are consistent, that mandatory supplier and buyer identifiers are present, and that document totals are mathematically correct). A single failed business rule can cause invoice rejection on the Peppol network, leading to delayed payments and reconciliation issues.
What is UBL?
UBL (Universal Business Language) 2.1 is an OASIS open standard that defines XML schemas for common business documents such as invoices and credit notes. In Europe, UBL is the primary format used on the Peppol network for e-invoicing, governed by the BIS Billing 3.0 specification which implements the EN 16931 European e-invoicing standard.
Key Takeaways
- UBL 2.1 is the primary invoice format for the Peppol network across Europe
- Peppol BIS Billing 3.0 enforces ~150 business rules on top of the UBL XML schema
- Tax calculations must be mathematically consistent — even 0.01€ difference causes rejection
- Mandatory fields include seller/buyer VAT, invoice number, tax breakdown, and monetary totals
- ValidateFin validates both UBL schema and Peppol business rules entirely in your browser
European e-invoicing formats compared
| Format | Syntax | Primary markets | Use case |
|---|---|---|---|
| UBL 2.1 (Peppol BIS 3.0) | XML | All EU via Peppol | B2B/B2G e-invoicing network |
| Factur-X / ZUGFeRD | PDF/A-3 + XML | France, Germany, Belgium | Hybrid human+machine invoices |
| CII (Cross Industry Invoice) | XML | Germany (XRechnung) | Government invoicing (B2G) |
| FatturaPA | XML (SDI) | Italy | Mandatory B2B since 2019 |
All formats implement EN 16931. Peppol BIS 3.0 uses UBL syntax and is the most widely adopted across the EU.
Frequently Asked Questions
Which UBL invoice versions are supported?
The validator supports UBL 2.1 invoices and credit notes, with Peppol BIS Billing 3.0 business rule validation (EN 16931 standard). See our UBL/Peppol invoicing guide for details.
What is the difference between XSD validation and Peppol rules?
XSD validation checks the document structure and data types. Peppol BIS 3.0 rules add business logic checks such as VAT consistency, mandatory supplier fields, and line item totals.
Is this tool suitable for e-invoicing compliance in Europe?
Yes. The tool validates against EN 16931, the European standard for electronic invoicing, making it suitable for compliance checks in all EU member states. Read more about upcoming requirements in our e-invoicing in Europe 2026 article.
Do I need to install any software?
No installation required. The validator runs entirely in your browser with no plugins or extensions needed.
What is Peppol BIS Billing 3.0?
Peppol BIS Billing 3.0 (Business Interoperability Specification) is the standard specification for electronic invoices exchanged over the Peppol network. It implements the EN 16931 European standard and defines specific business rules around VAT, payment terms, allowances, charges, and document totals. It is used across all EU member states and many international partners.
Why does my UBL invoice pass XSD validation but fail Peppol rules?
XSD validation only checks structure and data types — it cannot verify business logic. Peppol BIS 3.0 rules include checks like: the sum of line amounts must equal the document taxable amount, each tax subtotal must have a matching VAT category, and certain fields are conditionally mandatory based on document type. An invoice can be structurally valid but still violate these business rules.
What is the EN 16931 standard?
EN 16931 is the European standard for electronic invoicing, published in 2017 and mandatory for all public sector e-invoicing in EU member states. It defines a semantic data model for invoice content. UBL 2.1 and UN/CEFACT CII are the two XML syntaxes that implement this standard. Peppol BIS 3.0 is a profile built on top of EN 16931.
Can I validate a credit note with this tool?
Yes. The validator supports both UBL 2.1 Invoice and UBL 2.1 Credit Note document types. The same Peppol BIS 3.0 and EN 16931 rules apply to both, with some specific rules activated only for credit notes (e.g. a CreditedQuantity or PayableAmount with a negative sign). For hybrid PDF invoices, see the Factur-X / ZUGFeRD Viewer.
Which VAT categories are supported?
The validator supports all standard EN 16931 VAT categories: S (standard rate), Z (zero rate), E (exempt), AE (reverse charge), K (intra-EU supply), G (export outside EU), O (outside scope), and IGIC/IPSI for Canary Islands and Ceuta/Melilla. Each category has specific mandatory field requirements checked by the Peppol rules.
Is my invoice data safe when using this tool?
Yes. The entire validation process runs locally in your browser using JavaScript. Your invoice XML file is never uploaded to any server, transmitted over the network, or stored anywhere. This makes the tool fully compliant with GDPR and safe to use with real supplier and customer data. See our GDPR compliance page for details.