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.
UBL / Peppol Invoice Validator for French Companies
France's 2026 e-invoicing reform accepts UBL 2.1 invoices via Peppol-accredited ODP (Opérateur de Dématérialisation Partenaire) platforms and Chorus Pro. Validate your UBL invoices for EN 16931 compliance — free, no file uploaded.
Open UBL ValidatorUBL invoicing in France: Chorus Pro & ODP platforms
France's e-invoicing reform (Ordonnance n°2021-1190) mandates structured electronic invoicing for all VAT-registered companies from 2026. While Factur-X is the most widely discussed format, UBL 2.1 is equally accepted — provided it conforms to the EN 16931 semantic data model.
UBL invoices can be exchanged via Chorus Pro (the state platform managed by AIFE) or through an ODP (Opérateur de Dématérialisation Partenaire), a private certified platform connected to the national e-invoicing ecosystem. ODPs typically support Peppol BIS Billing 3.0 (UBL 2.1) as their primary format.
Compliance timeline
Large enterprises (>5,000 employees or >1.5B€ turnover): mandatory emission and reception of e-invoices via Chorus Pro or ODP.
All companies: mandatory reception of e-invoices from large enterprises. Must accept UBL, Factur-X, and CII formats.
Mid-size companies (250–5,000 employees): mandatory emission of e-invoices via Chorus Pro or ODP.
Small businesses and micro-enterprises: mandatory reception. Emission mandate from 2027.
What ValidateFin checks in your UBL invoice
Before submitting to Chorus Pro or your ODP, verify your UBL invoice passes these checks:
- UBL 2.1 schema validation: the XML structure conforms to the UBL 2.1 Invoice or CreditNote schema
- EN 16931 mandatory fields: seller VAT (FR format), buyer SIRET or VAT, invoice number, issue date, tax breakdown
- Peppol BIS 3.0 business rules: PEPPOL-EN16931-R* rules for amounts, VAT, and payment terms
- French VAT number format: FR + 2 alphanumeric chars + SIREN (11 digits total)
- Tax category codes: S (standard 20%), AA (reduced 10/5.5%), E (exempt) — French VAT rates validated
Common UBL errors causing ODP / Chorus Pro rejection
Invalid French VAT number format
French VAT (TVA intracommunautaire) follows the format FR + 2 alphanumeric characters + 9-digit SIREN. The 2-char key is computed from the SIREN and is frequently wrong in automated systems.
Missing SIRET or buyer identification
For B2B invoices in France, the buyer must be identified by their SIRET (14 digits) or VAT number in cac:AccountingCustomerParty. Its absence causes ODP routing failure.
Peppol BIS 3.0 rule PEPPOL-EN16931-R004 failure
The invoice currency (cbc:DocumentCurrencyCode) must match the currency in all monetary amounts. EUR is mandatory for French domestic invoices.
Frequently asked questions
Can I use UBL instead of Factur-X for French e-invoicing?
Yes. The French reform accepts three structured formats: Factur-X (PDF/A-3 + XML), UBL 2.1, and UN/CEFACT CII. All must implement the EN 16931 semantic data model. UBL is particularly common when exchanging invoices via an ODP (private certified platform) or via a Peppol access point.
What is an ODP and how is it different from Chorus Pro?
Chorus Pro is the state-managed platform for public procurement (B2G) and serves as the central hub for the reform. An ODP (Opérateur de Dématérialisation Partenaire) is a certified private platform (e.g. a software vendor or EDI provider) that can exchange invoices between private companies (B2B) and relay them to Chorus Pro. ODPs typically support Peppol BIS 3.0 (UBL 2.1).
Does ValidateFin validate French-specific UBL rules?
ValidateFin validates your UBL 2.1 invoice against the Peppol BIS Billing 3.0 specification and EN 16931 rules, which are the required standards for French e-invoicing. It also checks French VAT number format and tax category codes. No file is ever sent to a server — 100% browser-based.
E-invoicing guides by country
Validate your UBL invoice before submitting to Chorus Pro or your ODP
Check UBL 2.1 structure, Peppol BIS 3.0 rules, and EN 16931 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.