The required fields, each party's registration numbers, the exact statutory wording for every tax treatment and the currency the tax must be shown in — for 43 countries, each line cited to the statute or the tax authority it came from.
These pages aren't a summary someone wrote once and forgot. They're generated from the rule set Invoice by Juros-AI uses to build invoices — so every requirement here is one the software already knows how to satisfy.
The wording for each tax treatment links to the statute or the tax authority it was read from — no practitioner blogs, no paraphrase passed off as law.
Invoice by Juros-AI lifts clean data off any invoice, and is adding compliant creation — the market's legal format, generated and validated on your own machine.
Both directions run on-premise: no cloud, nothing uploaded, and a deterministic engine that never invents a figure.
43 countries, grouped by region. Each page carries that market's fields, identifiers, statutory wordings and sources.
Invoice by Juros-AI reads any invoice into clean data — any vendor, any layout, PDF or scan — and is adding compliant invoice creation: it builds each market's legal e-invoice (UBL/Peppol BIS, XRechnung, Factur-X, FatturaPA, KSeF FA(3), Peppol PINT) and validates it against the official schema, entirely on your own hardware.
Validation runs on your machine against the official artefacts — OASIS UBL/CII, the CEN EN 16931 schematron, Peppol BIS 3.0, KoSIT XRechnung, FatturaPA, KSeF FA(3) and the Peppol PINT packages. These pages are a reference for build scoping, not legal or tax advice.
Invoice