ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

Mandatory e-arve B2G since 1 July 2017

Estonia made structured electronic invoicing (e-arve) mandatory across its entire public sector on 1 July 2017, after a pilot phase from 1 January 2017 covering the Riigikantselei (State Chancellery) and major central agencies. The country thus became one of the very first states worldwide to enforce a universal B2G e-invoicing mandate — seven years ahead of most Member States' transposition of Directive 2014/55/EU.

History — from Riigikantselei 2017 to the universal mandate

The story starts in 2005 with the first e-arve schema published by Eesti E-arvelduskeskus (a clearing operator owned by Itella / Omniva), for domestic interbank flows. The XML e-arve format is already widely used B2B in the 2010s, driven by banks (SEB, Swedbank, LHV) that push it through their accounting interfaces.

In 2016 the Estonian Parliament (Riigikogu) amends the Raamatupidamise seadus to insert a new § 7-1 "Masinloetav arve" ("Machine-readable invoice") that makes structured e-invoicing mandatory for every public entity. The Riigikantselei (State Chancellery, which coordinates ministries) switches on 1 January 2017, followed by the universal B2G mandate on 1 July 2017.

text estonia-b2g-timeline.txt
2005       | First e-arve XML schema published by Eesti E-arvelduskeskus
           | (Itella / Omniva clearing operator), inherently banking-driven.
           |
2014       | Directive 2014/55/EU adopted — B2G mandate to be transposed by 2019.
           | Estonia decides to anticipate massively.
           |
2016       | Amendment to Raamatupidamise seadus (Estonian Accounting Act)
           | introduces a new § 7-1 "Masinloetav arve" — machine-readable
           | invoice. Target: universal B2G mandate.
           |
2017-01-01 | Phase 1: Riigikantselei (State Chancellery) and major central
           | public bodies accept only e-arve.
           |
2017-07-01 | Universal B2G mandate — every Estonian public-sector entity
           | (KOV local authorities, ministries, agencies, universities,
           | hospitals) must receive and process only structured e-arve
           | XML invoices.
           |
2019       | Update: alignment with EN 16931 + PEPPOL BIS Billing 3.0
           | alongside the historical e-arve XML format. RIK + EMTA
           | accredit operators.
           |
2020-2022  | B2B connector roll-out across local ERPs (Merit, Standard
           | Books, SimplBooks) — same e-arve rail.
           |
2024-2026  | ViDA 2028 preparation + progressive B2B extension. Riigikogu
           | debates a universal B2B mandate by 2027-2028.

Governance — Rahandusministeerium + EMTA + RIA

The B2G e-arve mandate has tripartite governance:

  • Rahandusministeerium (Ministry of Finance) — owns the Raamatupidamise seadus and defines policy and scope.
  • EMTA — Maksu- ja Tolliamet (Estonian Tax and Customs Board) — handles VAT conformance and the link with KMD INF SAF-T reporting.
  • RIA — Riigi Infosusteemi Amet (Information System Authority) — operates X-Road / X-tee, the cross-agency data bus that acts as the routing backbone for e-arve between public agencies.

Accredited operators (Omniva, Telema, Fitek, Unifiedpost, Pagero) are required to provide a connector compatible with e-arve XML + EN 16931 + PEPPOL BIS 3.0.

Schema — e-arve XML + EN 16931 + PEPPOL BIS 3.0

The historical e-arve XML 1.2 format is still accepted by every Estonian administration. Since 2019, EN 16931 and PEPPOL BIS Billing 3.0 are accepted too — operators usually convert in both directions. Public-sector routing uses national identifiers:

  • registrikood — unique entity identifier (8 digits) held by RIK / Ariregister.
  • isikukood — national personal identifier (11 digits), used by FIE (sole traders) and e-residents.
  • ICD 0191 — PEPPOL code for the Estonian registrikood.
xml e-arve-1.2-sample.xml
<?xml version="1.0" encoding="UTF-8"?>
<E_Invoice xmlns="urn:eestiarve:invoice"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           version="1.2">
  <Header>
    <Date>2026-06-15</Date>
    <FileId>EE-2026-09182</FileId>
    <Version>1.2</Version>
  </Header>
  <Invoice invoiceId="2026/00917" regNumber="12345678">
    <InvoiceParties>
      <SellerParty>
        <Name>Tallinna Insenerituru OU</Name>
        <RegNumber>12345678</RegNumber>
        <VATRegNumber>EE100123456</VATRegNumber>
        <ContactData>
          <ContactName>Mari Tamm</ContactName>
          <Email>arved@tallinna-insener.ee</Email>
        </ContactData>
      </SellerParty>
      <BuyerParty>
        <Name>Tartu Linnavalitsus</Name>
        <RegNumber>75006546</RegNumber>
        <VATRegNumber>EE100098765</VATRegNumber>
      </BuyerParty>
    </InvoiceParties>
    <InvoiceInformation>
      <Type type="DEB"/>
      <DocumentName>e-arve</DocumentName>
      <InvoiceNumber>2026/00917</InvoiceNumber>
      <InvoiceDate>2026-06-15</InvoiceDate>
      <DueDate>2026-07-15</DueDate>
      <TotalSum>2440.00</TotalSum>
      <Currency>EUR</Currency>
    </InvoiceInformation>
  </Invoice>
</E_Invoice>

Comparison — Estonia vs Italy vs France

DimensionEstoniaItaly (SdI)France (Chorus Pro)
B2G mandatory1 July 20176 June 20141 January 2020
B2B mandatoryNot yet (~2027-2028 ?)1 January 2019Postponed to 2026-2027
Formate-arve XML + EN 16931 + PEPPOL BIS 3.0FatturaPA XMLFactur-X / UBL / CII
Model4-corner (accredited operators)5-corner (clearance via SdI)5-corner (PPF + PA)
Identifierregistrikood (ICD 0191)Codice Destinatario / PECSIRET (ICD 0009)
Legal basisRaamatupidamise seadus § 7-1D.lgs. 127/2015LFR 2022 + Ordonnance 2021-1190

B2G adoption — near-total coverage

  • ~99% of B2G invoices received by the Estonian public sector are structured e-arve (RIA + EMTA, 2024 figures).
  • ~70M e-arve/year flow through the Estonian ecosystem (combined B2G + B2B), per Statistikaamet + Tieke Nordic reports.
  • ~6 main operators — Omniva (Eesti Post), Telema, Fitek (Unifiedpost group), Pagero, Maventa (Visma group), Liaison.
  • ~12% PEPPOL BIS 3.0 on cross-border flows, especially to Finland (Tieke), Sweden (Bolagsverket) and Germany (XRechnung).

Common pitfalls

  • Confusing e-arve XML and EN 16931. e-arve XML 1.2 remains the historical canonical schema. EN 16931 is accepted but converted by operators. A non-structured PDF (even signed) is rejected by the public sector since 2017.
  • Wrong registrikood. The registrikood is an 8-digit identifier maintained by RIK / Ariregister. Confusing it with the isikukood (11 digits) or with the EE VAT number causes immediate routing rejection.
  • Forgetting ICD 0191. In PEPPOL, ICD 0191 is required for Estonian recipients. Without this code, SMP routing fails.
  • Assuming B2B is mandatory. The mandate is strictly B2G as of 2026. B2B is massively adopted on a voluntary basis (~70% of companies) but not yet legally enforced.
  • Thinking Directive 2014/55/EU is enough. The directive mandates reception by contracting authorities. The Estonian mandate goes further: it also mandates issuance by every supplier.