UBL Validator
Validator
🇪🇪 Validate UBL Invoices for Estonia
UBLB2G MandatoryPeppol
UBL 2.1 is required for B2G in Estonia. Estonia has mandatory B2G e-invoicing since July 2019 and introduced a "buyer's choice" model from July 2025 — buyers registered in the Commercial Register can demand e-invoices from any supplier, who must comply.
Quick Facts
Format
UBL 2.1
Standard
EN 16931
Mandate
B2G Only
Peppol
Connected
What We Validate
UBL 2.1 XML schema validation
EN 16931 business rules
Namespace and element structure
Code list validation
Party and address structure
Tax calculation rules
Invoice line consistency
Common UBL Errors
Estonia E-Invoicing Requirements
Phase
Status
Scope
B2G
Live (Jul 2019)
All public sector suppliers
Buyer's choice
Live (Jul 2025)
Registered buyers can demand e-invoices from any supplier
Full B2B mandate
2027
Expected — legislation being drafted
Required CIUSEN 16931 (default from Jul 2025); Estonian e-arve EVS 923 (legacy)
Routing identifierRegistrikood (registry code) in e-Business Register
PeppolYes — connected to Peppol for cross-border
Buyer's choice model. From July 2025, buyers registered as e-invoice recipients in the Estonian Commercial Register can legally demand e-invoices from any supplier. The default format is EN 16931 unless otherwise agreed. The legacy Estonian e-arve (EVS 923) format is still accepted but declining. Exchange occurs via private operators (Billberry, E-arveldaja, Finbite, Telema, Unifiedpost) with no central government platform.
FAQ
What is UBL 2.1?
UBL (Universal Business Language) 2.1 is an open XML standard for business documents developed by OASIS. It defines schemas for invoices, orders, and 60+ other document types.
Is UBL the same as Peppol?
No. UBL is the document format; Peppol is the network. Peppol BIS Billing is built on UBL 2.1 with additional business rules.
Should I use UBL or CII for EN 16931?
Both are valid syntaxes for EN 16931. UBL is more common internationally (Peppol uses it), while CII is used in hybrid formats like ZUGFeRD.
What are cbc: and cac: prefixes?
These are UBL namespace prefixes. cbc: (Common Basic Components) contains simple values, cac: (Common Aggregate Components) contains complex structures.
Which standards are built on UBL?
Peppol BIS Billing 3.0, XRechnung (UBL variant), A-NZ PEPPOL (Australia/New Zealand), and Singapore InvoiceNow all use UBL 2.1 as their base syntax. Our validator checks generic UBL compliance—use format-specific validators for additional business rules.
Validate your Estonia UBL invoices
Upload and validate instantly. Auto-fix common errors.
Try the Validator