Free Estonian e-arve Validator (Versions 1.11 & 1.2)

Validate Estonian e-arve XML against the official Eesti Pangaliit schema and Estonian business rules (registry codes, IBAN MOD-97, VAT consistency). Both schema versions 1.11 and 1.2 supported. Free, no signup, instant report with Estonian-specific error codes (EA-R001 to EA-R008).

Validate an e-arve XML See all supported formats

How the e-arve validator works

1

Upload your e-arve XML

Drag and drop the XML file. The root element must be <E_Invoice> with no XML namespace — the standard Eesti Pangaliit structure. The validator auto-detects e-arve and routes to the dedicated Estonian validator.

2

Schema validation + business rules

The validator reads the schema version from <Header><Version> and applies the matching XSD (1.11 or 1.2). Then it runs the EA-R001…R008 business rules covering registry codes, IBAN MOD-97 checksum, VAT consistency and amount totals.

3

Read the report

Schema errors come back with XSD line/column references; business-rule violations are reported with the Estonian rule code (EA-R001 through EA-R008) and a plain-English description.

What the e-arve validator checks

XSD schema (1.11 + 1.2)

Per-document version detection. If the file declares <Version>1.11</Version> the 1.11 XSD is used; if it declares 1.2 the newer EN 16931-aligned 1.2 schema is used. Structural errors fire with line and column numbers.

Estonian business rules (EA-R001–R008)

Invoice number presence (R001), invoice date validity (R002), Estonian 8-digit registry codes for seller and buyer (R003, R004), total amount consistency with line items (R005), VAT calculation correctness (R006), payment due date logic (R007) and IBAN MOD-97 checksum verification (R008).

Automatic format detection

The validator auto-detects e-arve from the <E_Invoice> root element. PEPPOL invoices and XRechnung invoices use different XML structures and get routed elsewhere — you never have to pick a format manually.

IBAN MOD-97 verification

Any IBAN value in PaymentInfo/PayToAccount or AccountInfo/IBAN is validated using the ISO 13616 MOD-97 checksum algorithm. Catches typo'd account numbers before the invoice goes out via banking channels.

Why a separate Estonian e-arve validator?

E-arve is the Estonian banking-channel e-invoice format published by Eesti Pangaliit (Estonian Banking Association). It predates PEPPOL adoption in Estonia and remains the dominant format for domestic B2B and B2G invoices exchanged via banking infrastructure (LHV, SEB, Swedbank) and Estonian e-invoice operators (Finbite, Omniva, Telema). The XML structure has nothing in common with PEPPOL UBL or EN 16931 CII — a different root element, different field names, no XML namespace at all. Generic PEPPOL or XRechnung validators reject e-arve documents as "invalid XML" because they don't recognise the structure.

The aiDoks validator handles e-arve as a first-class format alongside PEPPOL, XRechnung and Factur-X. Upload your e-arve XML, get the full validation report with both XSD schema errors and Estonian business-rule violations, and fix issues before submitting through your bank's e-arve channel.

Common e-arve validation errors

  • EA-R001 — Invoice number is missing or empty. The InvoiceNumber element under InvoiceInformation must be populated.
  • EA-R003 — Seller registry code is not 8 digits. Estonian company codes are always 8 digits — most often the issue is a leading-zero stripped by Excel during data entry.
  • EA-R005 — Total amount mismatch. The TotalSum in InvoiceSumGroup must equal the sum of line items within ±0.01 tolerance.
  • EA-R006 — VAT calculation inconsistent. VATSum must equal SumBeforeVAT × VATRate / 100 within ±0.01 tolerance.
  • EA-R008 — IBAN fails MOD-97 check. Usually a typo — the IBAN is structurally well-formed but the check digits don't match the rearranged account number. Banks will reject the payment outright.

For Estonian companies dealing with cross-border invoices

Many Estonian companies receive both domestic e-arve from local suppliers via banking channels AND PEPPOL invoices from cross-border EU suppliers via PEPPOL access points. Rather than running two validators, the aiDoks tool detects which format you uploaded and applies the matching pipeline. Same UI, same report structure, one less tool to maintain.

Estonian e-arve validator: FAQ

What is the Estonian e-arve format?

E-arve is the Estonian domestic e-invoice format published by Eesti Pangaliit (Estonian Banking Association). It is distinct from PEPPOL — predates PEPPOL adoption in Estonia and is still the dominant format for domestic B2B and B2G invoices exchanged via banking channels (LHV, SEB, Swedbank) and operators (Finbite, Omniva, Telema). The validator supports both schema version 1.11 (the long-stable production version) and 1.2 (newer EN 16931-compatible release).

Why do I need a separate validator for Estonian e-arve?

E-arve uses a completely different XML structure than PEPPOL UBL or CII: the root element is <E_Invoice> with no XML namespace, and the document layout follows the Estonian banking conventions rather than the EU EN 16931 model. PEPPOL or XRechnung validators do not recognise it and would reject it as "invalid XML". The aiDoks validator auto-detects the e-arve root and routes to the dedicated validator.

What does the e-arve validator check?

Two layers: XSD schema validation (against the official e-arve schema, either 1.11 or 1.2 depending on the version declared in the document Header) plus business-rule checks implemented in Java. Business rules cover invoice number presence (EA-R001), date validity (EA-R002), Estonian 8-digit registry codes for seller and buyer (EA-R003, EA-R004), amount consistency between line items and totals (EA-R005), VAT calculation correctness (EA-R006), payment due date logic (EA-R007) and IBAN MOD-97 checksum verification (EA-R008).

Does the validator handle both e-arve 1.11 and 1.2?

Yes. Each uploaded document declares its own schema version in <Header><Version>; the validator reads that and applies the matching XSD at validation time. 1.11 remains the dominant version in Estonian banking traffic; 1.2 is the newer EN 16931-aligned variant. Both pass through the same business-rule layer.

Is the Estonian e-arve validator free to use?

Yes, free and no account required. Upload your e-arve XML (E_Invoice root, no namespace) and get instant validation with both schema errors and Estonian-specific business-rule violations flagged with codes (EA-R001 through EA-R008).

Can I also validate Estonian invoices in PEPPOL or EN 16931 format?

Yes — the same aiDoks validator supports PEPPOL BIS 3.0, XRechnung, EN 16931 and Factur-X / ZUGFeRD in addition to Estonian e-arve. Many Estonian companies receive both domestic e-arve from banking partners and PEPPOL invoices from cross-border EU suppliers; one validator handles both worlds.

Related tools

PEPPOL BIS 3.0 validator

For cross-border EU invoices via PEPPOL.

XRechnung validator

For invoices to German public-sector buyers.

Free e-invoice generator

Create PEPPOL e-invoices online — no signup.

Validate your e-arve in seconds

Free, anonymous, full XSD + Estonian business rules.

Run Validator Compare formats