Production-grade UBL 2.1 XML
Every issued invoice and credit note can be exported as a fully structured UBL 2.1 XML document with correct PEPPOL BIS Billing 3.0 identifiers.
EN 16931 e-invoicing, generated and compliant
Invoxo generates EN 16931 compliant structured invoices in UBL 2.1 format, conforming to PEPPOL BIS Billing 3.0. Download production-grade XML for every issued invoice and credit note—ready for buyers, public sector procurement, and ViDA 2030.
View pricing
14-day free trial. No charges until trial ends.
UBL 2.1 XML output ✅
PEPPOL BIS 3.0 profile ✅
Invoices + credit notes ✅
Tamper-evident export ✅
What Invoxo generates
Compliant structured invoices, not just "ready" data
Invoxo produces real EN 16931 compliant UBL 2.1 XML documents. Each export includes the correct PEPPOL BIS Billing 3.0 CustomizationID and ProfileID, full tax breakdowns, payment means, and postal addresses.
Included in the export
- ✅ Standard invoices (type code 380)
- ✅ Credit notes (type code 381)
- ✅ Tax category codes + exemption reasons
- ✅ IBAN/BIC payment means
What is EN 16931?
EN 16931 is the European standard for the semantic data model of electronic invoices. Established under EU Directive 2014/55/EU, it defines the required fields and structure that make invoices machine-readable—independent of file format.
The standard was originally mandated for public procurement. Now, with the EU's VAT in the Digital Age (ViDA) directive—formally adopted on 11 March 2025 and in force since 14 April 2025—EN 16931 becomes the mandated format for all intra-EU B2B e-invoicing from 1 July 2030. Under ViDA, Member States may require that holding a valid structured e-invoice is a substantive condition for exercising the right to VAT deduction. Multiple EU member states already have live or confirmed domestic mandates ahead of that deadline.
The standards stack
EN 16931
→
UBL 2.1 syntax
→
PEPPOL BIS 3.0
→
Compliant XML
Why it matters
EN 16931 is the semantic foundation. UBL 2.1 is the XML syntax. PEPPOL BIS Billing 3.0 adds the business profile constraints. Invoxo implements all three.
Tax integrity verified before export
The tax payload is hash-verified and totals are reconciled against canonical columns before any XML is generated. Corrupted or tampered data is caught.
Built on immutable snapshots
Structured invoices are generated from the exact buyer, seller, payment, and tax state recorded at issuance—never from mutable company or client data.
What Invoxo generates
Invoxo produces EN 16931 compliant structured invoices in UBL 2.1 format. This is not a data export or a "structured-ready" template. It is a fully formed XML document that conforms to PEPPOL BIS Billing 3.0 and can be submitted to any system that accepts that profile.
UBL 2.1 format with PEPPOL BIS 3.0 profile
Each XML document includes the correct PEPPOL BIS Billing 3.0 CustomizationID and ProfileID. The output follows the UBL 2.1 schema and satisfies the constraints defined by the PEPPOL Business Interoperability Specification.
- ✅ Correct CustomizationID and ProfileID
- ✅ Override support per invoice when needed
Both invoices and credit notes
Standard invoices use document type code 380. Credit notes use type code 381. Both are generated with the same level of compliance and structural completeness, including the billing reference on credit notes.
- ✅ Invoice type code 380
- ✅ Credit note type code 381
Complete tax breakdown mapping
Tax breakdowns from the invoice's tax payload are mapped to proper UBL TaxSubtotal elements. Each subtotal includes the correct tax category code, rate, taxable amount, and tax amount. Where applicable, exemption reasons are included—for reverse charge, out-of-scope, and other zero-rate treatments.
- ✅ Tax category codes per subtotal
- ✅ Exemption reasons where required
- ✅ Reverse charge and out-of-scope handling
Payment means and party details
The generated XML includes full seller and buyer postal addresses, VAT identification numbers, contact information, and payment means (IBAN and BIC). These are sourced from the immutable snapshot fields stored at issuance, not from current company or client records.
- ✅ IBAN/BIC payment means
- ✅ Full postal addresses
- ✅ VAT IDs and contact info
Audit integrity by design
Your structured invoice reflects the exact tax state at issuance—verified, reconciled, and tamper-evident. These are not optional safeguards. They run on every export.
Immutable snapshots
Once an invoice is issued, Invoxo freezes the seller details, buyer details, payment information, and tax payload into immutable snapshot fields. The EN 16931 export reads exclusively from these snapshots. If your company address or bank details change after issuance, the structured invoice still reflects the original state. This is how audit integrity works: the document matches what was true at the time, not what's true now.
Tax payload hash verification
Every issued invoice stores a cryptographic hash of its tax payload. Before generating the UBL XML, Invoxo recalculates this hash and compares it to the stored value. If they don't match—due to corruption, database inconsistency, or any form of tampering—the export is blocked. You cannot accidentally generate a structured invoice from compromised tax data.
Totals reconciliation
Before export, Invoxo reconciles the totals stored in the tax payload against the invoice's canonical total columns. This catches edge cases where payload data and invoice totals diverge—something that could produce a technically valid XML document with incorrect amounts. The reconciliation runs automatically. If it fails, the export is blocked with a clear error.
EN 16931-1:2025 — the revised standard
EN 16931 is being updated. The revised version, EN 16931-1:2025, received CEN formal approval on 13 February 2026 and is expected to be published by 31 May 2026. It supersedes the original EN 16931-1:2017+A1:2019, adding fields specifically needed for B2B transactions under ViDA.
Key additions in EN 16931-1:2025
The revised standard expands the semantic data model to support B2B requirements that were not necessary in the original B2G-focused version:
IBAN made mandatory
Payment account identifier becomes a required field.
Goods/services indicator
New field to distinguish between supplies of goods and services.
Invoice issuance time
Time of issuance, not just date — supports DRR reporting timelines.
Triangulation simplification
Indicator field for triangular transaction simplification.
Multiple orders and deliveries
Support for referencing multiple purchase orders and delivery locations per invoice.
Payment terms as structured data
Early payment discounts and late payment charges expressed in structured fields.
Expanded VAT codes
New VAT category codes, exemption reasons, and margin scheme support.
Corrective invoice numbering
Sequential numbering for corrective invoices and XML attachment support.
Syntaxes remain unchanged
UBL 2.1 and UN/CEFACT CII remain the two mandatory syntaxes under the revised standard. Peppol BIS 4.0 has been announced to align with EN 16931-1:2025, though a release date has not yet been confirmed. No formal transition period has been defined between the 2017 and 2025 versions of the standard — this is a known industry concern.
Invoxo and the revised standard
Invoxo's structured invoices are generated in UBL 2.1 format conforming to PEPPOL BIS Billing 3.0 — the same standard foundation that EN 16931-1:2025 builds upon. As the revised standard is published, Invoxo will track updates to ensure continued compliance.
Countries already mandating this format
Invoxo generates UBL 2.1 with the PEPPOL BIS Billing 3.0 profile. This is not a theoretical choice — it is the exact format stack that multiple EU member states are actively mandating for their domestic e-invoicing requirements.
Live
Belgium
Mandatory B2B e-invoicing since January 2026. Explicitly requires Peppol BIS Billing 3.0, UBL 2.1, and EN 16931.
B2G
Croatia
Accepts EN 16931 / UBL 2.1 / Peppol BIS Billing 3.0 for B2G e-invoicing.
Live
Germany
EN 16931 mandatory for B2B (phased: receive from Jan 2025, issue from Jan 2027/2028). Accepts XRechnung, ZUGFeRD, and Peppol BIS Billing 3.0.
2027
Slovenia
UBL 2.1 / Peppol BIS Billing 3.0 accepted for upcoming domestic mandate.
2030
Ireland
EN 16931 / Peppol expected as part of ViDA 2030 implementation.
2030
All EU member states
EN 16931 mandatory for all intra-EU B2B transactions under ViDA from 1 July 2030.
ViDA 2030 and what's coming
The EU's VAT in the Digital Age (ViDA) directive was formally adopted on 11 March 2025, published in the Official Journal on 25 March 2025, and entered into force on 14 April 2025. It mandates structured e-invoicing for all intra-EU B2B transactions from 1 July 2030. Under ViDA, Member States may require that holding a valid structured e-invoice is a substantive condition for exercising the right to VAT deduction.
Multiple EU member states already have live or confirmed domestic mandates ahead of the 2030 deadline. Belgium explicitly requires Peppol BIS Billing 3.0 / UBL 2.1 / EN 16931 — the exact format stack Invoxo generates. The direction is clear: structured invoicing is becoming the default, not the exception.
If your invoicing platform already generates EN 16931 compliant documents, the transition is a delivery question, not a data quality question. You're already producing the right output.
Current state
Generation: available now
Invoxo generates EN 16931 compliant UBL 2.1 XML documents today. You can download the structured invoice for any issued invoice or credit note from the invoice detail page. Available on the Business plan.
Coming next
Peppol network delivery
Sending structured invoices directly over the Peppol network is planned. Generation is the standards-compliant part—it requires correct data, validated tax payloads, and schema conformance. Network delivery is the transport layer that connects your output to the buyer's access point.
How it works in Invoxo
Three steps from invoice creation to structured XML download.
1) Issue your invoice
Create an invoice as you normally would. Add your client, line items, and any notes. Invoxo automatically determines the correct VAT treatment—domestic, reverse charge, or out-of-scope—and validates the client's VAT ID via VIES where applicable.
When you issue the invoice, Invoxo snapshots all seller details, buyer details, payment information, and the computed tax payload. These become the immutable source for the structured export.
2) Integrity checks run
When you request the EN 16931 export, Invoxo verifies the tax payload hash and reconciles totals against the invoice's canonical columns. If anything is inconsistent, the export is blocked with a clear error message. This happens automatically—you don't need to trigger or configure it.
3) Download the XML
From the invoice detail page, download the EN 16931 XML file. The document is a complete UBL 2.1 invoice (or credit note) with the PEPPOL BIS Billing 3.0 profile. Send it to your buyer, upload it to a procurement portal, or archive it for your records.
Available on the Business plan. Works for both standard invoices and credit notes.
EU VAT compliance
Correct VAT treatment is a prerequisite for compliant structured invoices. Invoxo handles this automatically.
Free VAT tools
Check VAT numbers or determine the correct treatment—no account required.
Available on the Business plan
EN 16931 structured export is included in the Business plan. VAT compliance features are included on every plan.
Why service businesses choose Invoxo for e-invoicing
Compliant generation, not just readiness
Invoxo generates real EN 16931 UBL 2.1 XML documents. This is not a "structured-ready" label on a PDF. It is a production-grade structured invoice generator.
Integrity you can verify
Hash verification and totals reconciliation run before every export. If something is wrong, the export is blocked. You will never send a structurally valid document with incorrect amounts.
Built on correct VAT logic
EN 16931 defines how VAT information is represented, but the underlying tax logic must be correct first. Invoxo handles both: correct VAT determination and compliant structured representation.
The format countries are mandating
Belgium, Croatia, Germany, and Slovenia already mandate or plan to mandate UBL 2.1 / Peppol BIS / EN 16931 — the exact format stack Invoxo generates. By 2030, all intra-EU B2B transactions will require it under ViDA.
EN 16931 – Common questions
What is EN 16931? ⌄
EN 16931 is the European standard for the semantic data model of electronic invoices, established under EU Directive 2014/55/EU. It defines which fields must exist in a structured invoice and how they relate to each other. It does not prescribe a single file format—UBL 2.1 and CII are both conformant syntaxes. Invoxo uses UBL 2.1 with the PEPPOL BIS Billing 3.0 profile.
Does Invoxo support Peppol? ⌄
Invoxo generates structured invoices that conform to the PEPPOL BIS Billing 3.0 profile, including the correct CustomizationID and ProfileID. You can download these as XML files today. Direct delivery over the Peppol network (via an access point) is planned but not yet available. Generation is the standards-compliant part; network delivery is the transport layer.
What format does Invoxo use for e-invoices? ⌄
UBL 2.1 (Universal Business Language). Each exported document conforms to the PEPPOL BIS Billing 3.0 specification, which is the dominant profile used across EU public procurement and increasingly in the private sector.
Do I need EN 16931 invoices for my business? ⌄
If you invoice public sector buyers in the EU, you likely need to provide EN 16931 compliant invoices. Many large corporate buyers also require structured invoices for automated processing. With ViDA 2030, structured e-invoicing will become mandatory for intra-EU B2B transactions across all member states.
What is ViDA and how does it affect invoicing? ⌄
VAT in the Digital Age (ViDA) is an EU directive that will require structured e-invoicing for intra-EU B2B transactions, with obligations phasing in through 2030. Several member states (France, Germany, Spain, Poland, Romania, Belgium) are implementing their own mandates on accelerated timelines. Businesses that already generate EN 16931 compliant invoices will have the least to change.
Can I send credit notes as structured invoices? ⌄
Yes. Invoxo generates EN 16931 compliant XML for both standard invoices (document type code 380) and credit notes (document type code 381), with the same level of compliance, integrity checks, and structural completeness.
Is EN 16931 being updated? ⌄
Yes. EN 16931-1:2025 received CEN formal approval on 13 February 2026 and is expected to be published by 31 May 2026. It adds B2B-specific fields including mandatory IBAN, goods/services indicator, invoice issuance time, expanded VAT codes, and structured payment terms. UBL 2.1 and CII remain the two mandatory syntaxes. Invoxo will track the revised standard to ensure continued compliance.
Which EU countries require EN 16931 invoices? ⌄
Belgium, Croatia, and Germany already mandate or accept EN 16931 format for B2B e-invoicing, with Belgium specifically requiring Peppol BIS Billing 3.0 / UBL 2.1. Slovenia has an upcoming mandate expected from 2027. Ireland is preparing for the ViDA 2030 deadline. By July 2030, all intra-EU B2B transactions will require EN 16931 compliant structured invoices under the ViDA directive.
Disclaimer: Invoxo provides tooling to support invoice structure and semantics. For regulatory and filing requirements, confirm with your accountant.
Compliant structured invoices, generated today
EN 16931 UBL 2.1 export with PEPPOL BIS Billing 3.0 profile. Integrity-verified, snapshot-based, and ready for ViDA 2030.
See pricing
14-day free trial. No charges until trial ends.