Turn an Estonian e-arve 1.11 / 1.2 invoice into a PEPPOL BIS 3.0 UBL e-invoice — the format the PEPPOL network and the EN 16931 mandates across Europe expect. Invoices and credit notes are both supported; parties, lines, VAT breakdown and totals are mapped automatically, and Estonian registry codes become PEPPOL endpoint identifiers. Free, no signup.
Drop the e-arve XML — the version is read from the document itself, so both 1.11 (the long-stable bank-channel version) and 1.2 (the newer EN 16931-aligned release) convert without any settings. Credit notes (type CRE) become UBL credit note values automatically.
2
Automatic EN 16931 mapping
Seller and buyer with their registry codes and VAT numbers, invoice lines with quantities and prices, the VAT breakdown per rate, payment details with IBAN and payment reference, and the totals chain are mapped to their EN 16931 UBL equivalents. Estonian registry codes are emitted as PEPPOL endpoint IDs with the EAS 0191 scheme, so the output is routable on the network.
3
Download PEPPOL BIS 3.0 UBL
You get a UBL invoice with the PEPPOL BIS 3.0 CustomizationID, ready for any PEPPOL Access Point or EN 16931-based national mandate. Conversion caveats — like a dropped attachment or a file marked as a test invoice — are reported so nothing disappears silently.
Why convert e-arve to UBL?
E-arve is Estonia's domestic format: banks and operators like Finbite, Omniva and Telema understand it, but the PEPPOL network and the EN 16931 mandates spreading across Europe (Germany, France, Belgium, Poland, Romania…) do not. The typical case is an Estonian supplier invoicing an EU customer: your accounting software exports e-arve, and the customer — or their government portal — needs a PEPPOL invoice. Re-keying it is error-prone; the converter maps it field by field.
What carries over — and what cannot
Carried over: parties with registry codes and VAT numbers, invoice and credit-note type, lines with quantities and prices, the VAT breakdown per rate, document totals, due date, IBAN, payment description and payment reference number.
Registry codes become endpoints: the Estonian 8-digit registry code maps to the PEPPOL endpoint identifier with EAS scheme 0191 (the standard Estonian participant scheme); when only a VAT number is present, the EE VAT scheme 9931 is used instead.
Embedded attachments (AttachmentFile in 1.2) are not carried over — the UBL output is a clean new document and the converter warns you when an attachment was dropped.
Multi-invoice files — an e-arve file is a batch container that can hold several invoices; files with more than one are rejected with a clear message. Convert one invoice at a time.
Validate the result, both ways
The converted UBL follows the PEPPOL BIS 3.0 rules — you can drop it into the free PEPPOL validator to see the rule-by-rule report before sending. And if the conversion complains about your source file, run the original through the e-arve validator to find the exact EA-R rule that's broken.
e-arve to UBL: FAQ
Why would I convert an e-arve invoice to UBL?
E-arve is only understood inside Estonia — banks and operators route it domestically, but the PEPPOL network and the EN 16931 mandates across Europe expect UBL or CII. The typical case is an Estonian supplier invoicing an EU customer: your software exports e-arve, the customer needs a PEPPOL invoice. Converting is far safer than re-typing the invoice.
Which e-arve versions are supported?
Both production versions: 1.11 (the long-stable bank-channel version) and 1.2 (the newer EN 16931-aligned release). The converter reads the version from the document Header and applies the right mapping automatically — no settings needed. Credit notes (type CRE) convert to UBL credit note semantics.
How are Estonian registry codes mapped to PEPPOL identifiers?
The 8-digit Estonian registry code becomes the PEPPOL endpoint and PartyLegalEntity identifier with the EAS 0191 scheme — the standard scheme for Estonian PEPPOL participants. If a party only carries a VAT number, the EE VAT scheme 9931 is used instead. That makes the converted invoice routable on the PEPPOL network.
What does not carry over in the conversion?
Embedded attachments (AttachmentFile in e-arve 1.2) are dropped — the UBL output is a clean new document — and the converter reports a warning when that happens. Files marked as test invoices are converted with a warning too. Multi-invoice e-arve files are rejected with a clear message: convert one invoice at a time.
Is the converted UBL actually PEPPOL-compliant?
The output carries the PEPPOL BIS 3.0 CustomizationID, registry codes are mapped to EAS 0191 endpoint identifiers, amounts are normalised to two decimals, and the totals chain is kept arithmetically consistent. You can verify any result in the free PEPPOL validator — same uploader, full rule-by-rule report.
Is the e-arve to UBL converter free?
Yes — upload the e-arve, download the PEPPOL UBL, no account needed for the free daily quota.