Methodology

The editorial policy says we only use primary sources. This page is the receipt: exactly which source, for which country, opened on which date.

Invoice requirements on this site are held in one structured dataset, one record per jurisdiction. Every field in a record carries its own publisher, URL and retrieval date. A field with no source is not filled in with a best guess: it is left empty, and the page simply does not show that row. The country pages, the comparison table and the free JSON API are three views of that one dataset, so they cannot disagree with each other.

How a country record is built

  1. Find the authority that actually publishes the rule for that country. For EU member states there are two layers: the VAT Directive sets the common floor and the national tax administration adds its own detail. Both get cited where both apply.
  2. Open the page and read it. Not a summary of it, not a search-result snippet describing it.
  3. Record the value together with the publisher, the exact URL and the date of reading.
  4. Anything that could not be confirmed this way is left out of the record. It is not carried over from another country, inferred from a neighbouring rule, or written from memory.

What we deliberately do not do

Review cycle

Each record carries a review date. A build check fails when any record passes twelve months without review, which means an unmaintained country page stops the site from shipping rather than sitting there looking authoritative. E-invoicing obligations move fastest and are checked first at every review.

Sources per jurisdiction

Every source below was opened on the date shown. Links go straight to the authority so you can check any claim yourself.

European Union

Netherlands

Germany

France

Belgium

United Kingdom

Ireland

United States

Australia

Canada

The same rule for the tool: check it yourself

The claim that your invoice never leaves your browser is held to the same standard as the country data: you can verify it rather than trust it. Every page is served with a Content-Security-Policy whose connect-src line allows only our own site and the endpoint of the contact form, which receives a message only when you send one yourself. The PDF is made on your device with jsPDF. The privacy page quotes the full header and shows how to check it in your browser's developer tools.

Found a mistake

Tell us through the contact form, ideally with the source. Corrections to a factual claim are made as soon as we can verify them.