What actually changed on 1 July 2025?
The amendment adopted by the Riigikogu on 18 September 2024 did three things:
- It unified the principle. Previously a seller's duty to issue an e-invoice applied in the public sector. Now a single buyer's choice principle applies across both the public and the private sector.
- It enabled self-registration. Buyers can register themselves as e-invoice recipients in the commercial register directly; previously this was possible only through an e-invoice operator.
- It set a default format. Where the buyer requires an e-invoice, the default format is the European standard EN 16931. Other formats remain permitted by agreement.
The practical reach is limited. About 15,000 entities have registered as e-invoice recipients — roughly 7 per cent of taxable persons at the time the 2024 bill was being drafted. Most Estonian companies therefore cannot require an e-invoice at all, because they are not in the register.
Why is this so widely reported as a mandate?
Because the mechanism does not fit the categories the trackers use. Most country comparisons ask one question — is B2B e-invoicing mandatory? — and expect a yes or a no. Estonia's answer is neither. It is a conditional duty triggered by the counterparty's register entry, and a summary table has nowhere to put that.
The European Commission's own country page for Estonia illustrates the problem rather than solving it: it answers the mandate question with a yes, qualified by the buyer's choice principle applying to all accounting entities. Read carefully, that is accurate. Read as a table cell — which is how it is usually read, and how it is usually copied — it becomes Estonia: B2B mandatory, and from there it propagates.
The distinction is not pedantry, and it changes three decisions.
It changes what you build. A general mandate justifies a programme that converts every outbound invoice. A conditional duty justifies a lookup in the invoicing process and a format branch. Those are different budgets.
It changes when the duty arises. Under a mandate you know the start date years ahead. Here, the duty appears the moment a particular customer registers — a date you do not control, are not notified of, and will not discover unless the process checks.
It changes who is exposed. A general mandate exposes everyone equally. This one exposes whoever sells to the roughly 15,000 registered buyers, which for many groups is a specific and identifiable customer segment.
What counts as an e-invoice, and is a PDF one?
An e-invoice is a machine-processable structured invoice. A PDF is not an e-invoice, even when it is emailed — the criterion is machine readability, not electronic transmission. The same applies to a scanned paper invoice and to an image file.
Formats in use:
- EN 16931 — the default, in practice usually Peppol BIS Billing 3.0 (UBL)
- EVS 923:2014 — the Estonian national standard, permitted by agreement, being phased out
- UN/CEFACT CII
The middle entry deserves a note for anyone inheriting an existing Estonian integration. EVS 923:2014 is the national standard and is being phased out, but it remains permitted where the parties agree — so a legacy interface built against it is not broken, and there is no compliance date forcing its replacement. What there is, is a standard that is going away on no announced schedule. A group consolidating invoicing platforms should treat migration to EN 16931 as a planned technical decision rather than a regulatory deadline, and should not wait for one.
Estonia applies no national CIUS or extension on top of EN 16931, which simplifies cross-border integration compared with countries where a national profile is mandatory. For a group standardising one invoicing platform across several markets, this is the most useful single fact on this page: the Estonian requirement can be met with the standard European profile, so Estonia does not need its own mapping, its own validation artefacts or its own test cycle. Countries with a mandatory national profile do.
Does the public sector have to receive e-invoices?
| From | What applies |
|---|---|
| 1 March 2017 | The public sector must be able to receive e-invoices. The e-invoice recipients register was launched in the commercial register at the same time (RIK). |
| 1 July 2019 | Suppliers are obliged to send e-invoices to the public sector. |
| 1 July 2025 | The same framework was harmonised between the private and public sectors on the buyer's choice principle. |
These two dates are frequently confused. 2017 concerns receipt by the public sector; 2019 concerns sending by the supplier. A group whose Estonian entity sells to public bodies has been within a genuine issuing obligation since 2019 — which is a separate matter from the B2B position described above, and is often the source of the belief that Estonia already has a mandate.
Is a 2027 mandate coming?
In December 2024 the Ministry of Finance published a väljatöötamiskavatsus — an intention to draft legislation — envisaging:
- a general B2B e-invoicing obligation for VAT-registered persons from 2027;
- abolition of the 1,000 euro invoice reporting threshold in the VAT return annex;
- estimated additional VAT revenue of roughly 16.6 million euros a year.
No VAT Act amendment enacting this has been adopted. The most recent VAT Act amendment memorandum, of March 2026, deals with the extension of the One Stop Shop from 1 January 2027 and with transfers of own goods from 1 July 2028 under ViDA — it says nothing about an e-invoicing obligation or the 1,000 euro threshold.
So: planned, not enacted. Material describing a 1 July 2027 obligation as law in force is wrong. For planning purposes, an intention to draft is roughly two legislative stages away from a date you can put in a programme plan, and the absence of the proposal from the March 2026 memorandum is the more informative signal of the two.
What does a group finance function have to do differently?
Four things, none of which follow from a mandate-shaped mental model.
You do not control the trigger; the buyer does. When a customer registers as an e-invoice recipient, an obligation arises for you and nobody tells you. A billing process that checks the register before the document is prepared avoids the situation where the duty arose and you did not notice. Because the register is machine readable, this is a small technical change whose omission generates manual work later.
The duty attaches to the Estonian selling entity, not to the shared service centre. Where invoices are raised centrally by a European AR function, the obligation still belongs to the entity making the sale. The register check therefore has to run in the central process on behalf of the Estonian entity — the failure mode is a central platform that applies one group-wide format policy and never looks at the Estonian register at all.
Receiving capability matters more than sending capability. The absence of a mandate does not mean there is nothing to do; it means the driver is commercial rather than regulatory, and that changes the priorities. Registering your own Estonian entity as a recipient is a decision to accept structured invoices from suppliers, with the automation benefit that follows — and it is one of the few compliance-adjacent decisions here that is entirely yours to make.
Do not run one scoping rule across the region. Norway adopted a dated B2B issuing duty in June 2026, effective 1 January 2027, with a receiving duty and mandatory digital bookkeeping following in 2030. A single Nordic-Baltic e-invoicing programme that treats the two markets alike will either over-build in Estonia or under-build in Norway.
How do you establish whether you owe an e-invoice on a given sale?
Six steps, and they belong in the billing process rather than in a policy document. Confirm the sale is business to business, since the buyer's right applies to accounting entities and a consumer sale does not engage it. Query the e-invoice recipients register for that buyer, at the point the invoice is raised rather than during a periodic master data refresh. Check whether the parties have agreed otherwise, and hold that agreement against the customer master record rather than in a contract folder where the billing system cannot see it. Select the format: EN 16931 by default, in practice Peppol BIS Billing 3.0 in UBL, with other formats permitted by agreement and no national profile to accommodate. Reject a PDF as the answer, because the criterion is machine processability rather than electronic delivery. Finally, record the register status you relied on and when you checked it, alongside the issued document — the buyer can register at any time, so the defensible position is the one that shows what the register said when the invoice was raised.
What arrives regardless of Estonia's decision?
Council Directive (EU) 2025/516 introduces digital reporting for cross-border intra-EU B2B transactions from 1 July 2030. This does not depend on whether Estonia enacts a national obligation. A company with intra-EU trade is bound by that deadline in any event, and it is the fixed point around which the Estonian question should be planned — the national mandate is contingent, the ViDA date is not.
And on the cyber security side?
The NIS2 transposition — the amendment to the Estonian Cybersecurity Act — entered into force on 1 January 2026, materially later than the EU deadline of 17 October 2024. The number of covered entities rose from roughly 3,500 to about 6,500. The management board must approve the cyber risk management measures, monitor their implementation and complete mandatory training. Estonia did not adopt the optional prohibition on managers exercising management functions, so the personal exposure runs through company law rather than an administrative ban. The full analysis is under the Estonian Cybersecurity Act and NIS2.
In practice
BarzelVault applies policy and approval thresholds before an operation executes and issues a signed audit receipt for each one, which answers the question that follows the format question once invoices are raised by automated processes: who authorised this document. BarzelOps runs the cross-system workflow — register lookup, format selection, transmission — with durable state and approval checkpoints.
Frequently asked questions
Is there a B2B e-invoicing mandate in Estonia?
No. What applies is the buyer's right to require an e-invoice where the buyer is registered as an e-invoice recipient in the commercial register, unless the parties have agreed otherwise.
Is a general obligation coming in 2027?
That is a proposal in the Ministry of Finance's December 2024 intention to draft. No amending Act has been adopted, and the March 2026 VAT Act memorandum does not mention it.
Is a PDF an e-invoice?
No. The criterion is machine processability, not electronic delivery. A scanned invoice or image file fails for the same reason.
Where do you check whether a buyer is registered?
In the e-invoice recipients register held in the commercial register and administered by RIK. Since 1 July 2025 buyers can register themselves; about 15,000 entities are registered.
Does Estonia apply a national CIUS?
No. Estonia applies EN 16931 without a national profile or extension, which reduces integration work for a group running one platform across several markets.
What changed on the cyber security side?
The NIS2 transposition took effect on 1 January 2026, taking covered entities from roughly 3,500 to about 6,500, with approval, monitoring and training duties on the management board and no management ban.
Related reading
- Estonia: the Cybersecurity Act and NIS2
- Norway: mandatory e-invoicing from 1 January 2027
- Approving AI actions
- AI agent audit trails
- Workflow automation
- Glossary of Baltic and EU terms
- Corrections
In practice
The control has to run before the invoice becomes irreversible.
An accepted structured invoice can be corrected but never deleted, and from the penalty date every defect has a price. Barzel puts the approval threshold, the duplicate check and the signed record in front of submission, so the process can be defended on the day an auditor or the tax authority asks.
In forceBuyer's right to require an e-invoice since 1 July 2025
BarzelVault
The AI action firewall: decide what an agent may do before it does it.
- Approval thresholds and policy checks enforced before execution; human approvals that expire and escalate.
- Cryptographically signed audit receipts: trigger, inputs, policy version, approver, outcome.
- Credential isolation, spend and action limits, and an emergency kill switch.
Free tier: 10,000 calls a monthPaid plans from $199 a monthLive on MCPize
BarzelOps
Governed workflow automation across the systems that run the business.
- Durable, idempotent execution: a timeout is retried once, never filed twice.
- Human approval checkpoints that pause the workflow and resume it.
- Isolation per entity or client, signed evidence receipts and a portable manifest; HubSpot, Xero, Gmail, Google Drive and Slack.
Free tier: 100 calls a dayPaid plans from $19 a monthLive on MCPize
Enterprise: written quote by email within two business days. No sales call.
Sources
- Raamatupidamise seadus (Accounting Act) amendment, adopted 18 September 2024, in force 1 July 2025 — riigiteataja.ee. Left as plain text: the register is script-gated and carries several superseded consolidated redactions, so the text in force could not be identified with certainty.
- Rahandusministeerium, E-arveldamine muutub paindlikumaks — the buyer's choice principle, self-registration and EN 16931 as the default format.
- Rahandusministeerium, väljatöötamiskavatsus (intention to draft legislation), December 2024 — the 2027 proposal. No published URL verified.
- European Commission, eInvoicing in Estonia — country page, including that Estonia applies no national CIUS or extension.
- Council Directive (EU) 2025/516 (VAT in the Digital Age) — digital reporting for cross-border intra-EU B2B from 1 July 2030.
- Riigi Infosüsteemi Amet, Uuest aastast laienes küberturvalisuse seadus — the Estonian NIS2 position, in force 1 January 2026.
- Norway: LOV-2026-06-19-39 — the contrasting Nordic mandate referred to above.
This article is for information and does not constitute tax or legal advice. The Estonian text of the instruments cited is the binding one. Position as at 3 September 2026.