The fields, the party identifiers, the exact statutory wording for each tax treatment and the EUR rule — each cited to the statute or the tax authority, not a summary of one.
The content Estonia's rules put on the face of the document, beyond the parties, line items and totals every invoice carries.
The registration numbers and their formats the Estonia rules expect on the invoice.
When no tax is charged, the invoice has to say why — in the words the law names. Each is linked to the statute or tax authority it was read from.
Kauba ühendusesisene käive — 0 % (KMS § 15 lg 3 p 2)0 % — intra-Community supply
Ilma Eesti käibemaksuta — kaup kolmandast riigist; impordi käibemaksu tasub importija (KMS § 6)VAT not charged — supply outside the scope of Estonian VAT; import VAT is accounted for on importation by the importer (Art. 2(1)(d), 30, 70 and 201, Directive 2006/112/EC).
KMS § 37 lg 7: järjekorranumber, kuupäev, müüja nimi/aadress/KMKR number, ostja nimi/aadress (KMKR number pöördmaksustamisel), kauba nimetus/kogus, väljastamise ja võõrandamise kuupäev, hind, maksumäär, maksusumma eurodes.
A plain PDF still counts as the invoice in Estonia; a structured e-invoice is accepted where the buyer asks for it.
Invoice by Juros-AI builds the Estonia e-invoice — EN 16931 UBL (Peppol BIS 3.0) — and checks it against the official schema on your own machine before anything is sent. Invoice by Juros-AI reads any invoice into clean data and is adding compliant invoice creation — the same rules on this page, built into the engine, run entirely on your own hardware. No cloud, nothing uploaded, no figure invented.
Every generated invoice is validated on your machine against the official artefacts — the OASIS UBL/CII schemas, the CEN EN 16931 schematron, Peppol BIS 3.0, KoSIT XRechnung, FatturaPA, KSeF FA(3) and the Peppol PINT packages. This page is a reference for build scoping; it is not legal or tax advice.
Invoice