Turn a PDF invoice into valid Estonian e-arve XML — the Eesti Pangaliit format your internet bank and operators like Finbite, Omniva and Telema accept. AI OCR extracts the seller, buyer, registry codes, lines and VAT; you review the data and download a schema-valid e-arve 1.2 file, ready to upload to your bank or operator channel. No watermarks on the XML.
Drag and drop the PDF — or a scan or phone photo. AI OCR (Azure Document Intelligence with an e-invoicing-tuned post-processing layer) extracts the seller and buyer details, registry codes, invoice lines, VAT breakdown and totals into a structured form.
2
Review and pick the e-arve profile
Check the extracted fields — every value is editable before export. Select Estonia e-arve 1.2 as the output profile. Estonian specifics are handled automatically: 8-digit registry codes for seller and buyer, the VAT breakdown per rate, and the PaymentInfo block with IBAN, payment description and due date that banking channels rely on.
3
Download and upload to your channel
You get a valid e-arve 1.2 XML, checked against the official Eesti Pangaliit schema and the Estonian business rules (EA-R001…R008). Upload it through your internet bank (LHV, SEB, Swedbank) or hand it to your e-invoicing operator — Finbite, Omniva or Telema — for delivery.
What you get
Valid e-arve 1.2
The generator emits e-arve version 1.2 — the newer, EN 16931-aligned release of the Pangaliit schema — and self-validates the result against the official XSD plus the EA-R business rules: line arithmetic, VAT calculation and the invoice totals always add up.
Estonian specifics handled
Seller and buyer registry codes are checked to the Estonian 8-digit format before anything is generated; VAT numbers land in VATRegNumber; the IBAN is verified with the MOD-97 checksum and written into PaymentInfo together with the payment description and due date — the fields banks use to pre-fill the payment order.
Credit notes supported
The e-arve format distinguishes debit and credit invoices, and so does the generator: switch the form to a credit note and the output carries the CRE type marker your bank and operator expect — no separate tool needed.
No PDF? Start from the form
The same generator works without a PDF: fill in the invoice form manually (or reuse saved customers and products) and export e-arve 1.2 directly. You can also generate PEPPOL BIS 3.0, XRechnung or Factur-X from the same data — one form, several output formats.
Why convert PDFs to e-arve?
Most domestic invoicing in Estonia flows as structured e-arve XML through banking channels and operators — a PDF attached to an email is neither machine-readable for your customer's accounting software nor payable with one click in their internet bank. Estonian public-sector buyers have required e-invoices since 2019, and registered private-sector buyers can demand them too. If your billing tool only produces PDFs, you need the same data as e-arve XML: parties with valid 8-digit registry codes, itemised lines, the VAT breakdown and the payment details banks pre-fill from. Re-typing that into an operator portal is slow and error-prone; the AI converter extracts it from the PDF you already have.
E-arve also coexists with PEPPOL in Estonia: domestic traffic largely runs over the banking rails, while cross-border EU invoices use PEPPOL BIS 3.0. aiDoks generates both from the same form — pick e-arve for the Estonian customer, PEPPOL UBL for the EU one — and converts between them when a document arrives in the wrong format.
Current limitations
Version 1.2 output — the generator emits e-arve 1.2. If your channel still insists on 1.11, the validator and the e-arve → UBL converter accept both versions, but generation targets 1.2.
Single invoice per file — each download contains one invoice (the format's batch container is emitted with exactly one document), which is what bank-upload flows use.
Download, then upload yourself — direct submission to Finbite, Omniva or Telema APIs is not built in yet; you download the XML and deliver it through your bank or operator portal.
The recommended workflow
Convert the PDF, review the extracted data (pay attention to the registry codes — an Excel-eaten leading zero in an 8-digit code is the most common rejection), download the e-arve XML, and run it through the free e-arve validator if you edited anything by hand. Then upload through your bank or operator channel.
PDF to e-arve: FAQ
How do I convert a PDF invoice to Estonian e-arve?
Upload the PDF (or a scan/photo) — AI OCR extracts the seller, buyer, registry codes, invoice lines, VAT breakdown and totals into an editable form. Review the fields, select the "Estonia e-arve 1.2" output profile and download the generated XML. Then upload the file through your internet bank (LHV, SEB, Swedbank) or hand it to your e-invoicing operator (Finbite, Omniva, Telema).
Which e-arve version is generated?
Version 1.2 — the newer, EN 16931-aligned release of the Eesti Pangaliit schema. The output is self-validated against the official 1.2 XSD and the Estonian business rules (8-digit registry codes, VAT arithmetic, totals consistency, IBAN MOD-97) before you download it. If you need to check a 1.11 file, the free e-arve validator accepts both versions.
Can I create credit notes as e-arve?
Yes. The e-arve format marks credit invoices with a CRE type, and the generator supports it: switch the form to a credit note and the downloaded XML carries the credit marker your bank or operator expects.
Is the generated e-arve accepted by banks and operators?
The output conforms to the official Pangaliit 1.2 schema and passes the Estonian business rules, which is what bank and operator channels validate against. Delivery itself happens through your own channel — upload the XML in your internet bank or operator portal; direct API submission to Finbite, Omniva or Telema is not built in yet.
Is the PDF to e-arve conversion free?
Generating and downloading e-arve XML from the form is free. The AI OCR step for PDF extraction requires a free aiDoks account (no credit card) and includes 4 daily operations on the free tier; a Pro plan unlocks unlimited conversions. You can also skip the PDF entirely and fill the form manually for free.
What about PEPPOL — should I send e-arve or a PEPPOL invoice?
For domestic Estonian customers, e-arve over the banking channel remains the most widely supported route. For cross-border EU customers, PEPPOL BIS 3.0 is the standard. aiDoks generates both from the same form data, and the e-arve to UBL converter re-expresses an existing e-arve as a PEPPOL invoice when needed.