Free 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 Validator for Spanish Companies
Spain mandates B2G e-invoicing via FACe (UBL-based) and is implementing mandatory B2B e-invoicing via VERI*FACTU from 2025. Validate your UBL / Peppol invoices for EN 16931 compliance — free, no upload.
Open UBL ValidatorSpanish e-invoicing: FACe, TicketBAI and VERI*FACTU
Spain has mandated B2G electronic invoicing via FACe (Punto General de Entrada de Facturas Electrónicas) since 2015, using the Factura-e format (UBL 2.1-based). The Ley Crea y Crece (Law 18/2022) extends mandatory e-invoicing to B2B transactions: companies with turnover above 8M€/year must comply from 2025, all others from 2027.
The Spanish VERI*FACTU system introduces real-time invoice reporting to the Agencia Tributaria (AEAT). TicketBAI applies in the Basque Country, Navarre, and other regions, requiring digitally signed invoices submitted to regional tax authorities. ValidateFin validates UBL 2.1 invoices against EN 16931 and Peppol BIS 3.0, covering the cross-border and FACe compliance aspects.
Spanish e-invoicing compliance timeline
B2G: FACe platform mandatory for invoices to central government entities. Factura-e (UBL-based) format required.
B2B mandatory for large companies (turnover >8M€/year). VERI*FACTU real-time reporting system activated.
TicketBAI extended compliance: Basque Country and Navarre regions complete implementation of signed invoice reporting.
B2B mandatory for all Spanish VAT-registered companies regardless of turnover. Full VERI*FACTU coverage.
What ValidateFin checks in your UBL invoice for Spain
For Spanish companies using UBL/Peppol for B2G (FACe) or cross-border invoicing, verify your invoice passes these checks:
- UBL 2.1 schema validation against EN 16931 and Peppol BIS Billing 3.0 specification
- Spanish VAT number format: ES + NIF/CIF (9 characters: letter + 7 digits + control character)
- EN 16931 mandatory fields: seller/buyer identifiers, invoice number, issue date, tax breakdown
- FACe-specific: supplier identifier (DIR3 code) for B2G invoices to Spanish public entities
- VAT consistency: Spanish rates (21%, 10%, 4%) and exempt categories correctly applied
Common UBL errors for Spanish e-invoicing
Invalid Spanish VAT/NIF format
Spanish tax identifiers (NIF for individuals, CIF for companies) must be prefixed with ES in EN 16931. Format: ES + letter + 7 digits + control character (e.g. ESA12345674).
Missing DIR3 code for FACe B2G invoices
Invoices submitted to Spanish public entities via FACe must include the DIR3 administrative unit codes (Órgano Gestor, Unidad Tramitadora, Oficina Contable) in the buyer reference fields.
Wrong VAT rate for Spanish reduced/super-reduced categories
Spain's tax system has three positive rates (21%, 10%, 4%) plus exempt categories. Mixing up rates or category codes causes EN 16931 BR-S-08 and related rule failures.
Frequently asked questions
What is FACe and how does it use UBL?
FACe (Punto General de Entrada de Facturas Electrónicas de la Administración General del Estado) is Spain's central platform for electronic invoices to government entities. It accepts the Factura-e format, which is based on UBL 2.1 with Spanish-specific extensions. ValidateFin validates the UBL/Peppol aspect of your invoice.
Is VERI*FACTU the same as B2B mandatory e-invoicing?
VERI*FACTU is a real-time reporting system where invoice data is transmitted to AEAT (Spanish tax authority) at the time of issuance. It is different from mandatory e-invoicing: VERI*FACTU is about tax reporting, while the Ley Crea y Crece mandate is about exchanging structured invoices with buyers. Both obligations apply from 2025.
Can ValidateFin validate Factura-e invoices?
ValidateFin validates UBL 2.1 invoices against EN 16931 and Peppol BIS 3.0 rules. The core Factura-e structure is UBL 2.1-based. For Spanish-specific Factura-e extensions (DIR3 codes, specific tax categories), the base EN 16931 validation covers the core requirements. Use the AEAT tools for full VERI*FACTU compliance testing.
E-invoicing guides by country
Validate your UBL invoice for Spanish e-invoicing
Check FACe UBL structure 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.