The InvoiceSnap editorial team·Researched and maintained by the team at FusionStudios·Last reviewed
This hub covers the jurisdictions listed below and no others. Legal requirements differ per country, so every rule below names the country or bloc it comes from and links to the authority that publishes it. This is general information about published requirements, not tax or legal advice. See our editorial policy and methodology.
What must appear on an invoice is set nationally, not universally. Inside the EU, article 226 of the VAT Directive sets one exhaustive list of particulars, so most EU invoices share the same core fields. Outside it the rules diverge sharply: the United States has no federal rule about invoice content at all. The table below compares 10 jurisdictions, each value linked to the authority that publishes it.
Compared side by side
The quickest way to see how far the rules actually diverge. Every cell traces to the source listed on that country's own page.
Invoice rules compared across 10 jurisdictions, each sourced from its own tax authority
"Not verified" means exactly that: we could not read the value off a primary source, so we do not state one. It is not a claim that no rule exists. Thresholds do not all work the same way: Australia's AUD 1,000 adds a requirement above it, and Canada has three tiers. The country pages explain each one.
Download the dataset
The table is also a dataset. The CSV has one row per sourced value, 131 rows across 10 jurisdictions, so every mandatory field is its own row with its publisher, source URL and retrieval date. The JSON holds the same records in the shape the API returns.
How to cite: InvoiceSnap (2026). Invoice requirements by country, version 1.2.0, updated 2026-10-19. https://invoicesnap.net/invoice-requirements. Licensed CC BY 4.0.
Building something with it? The data API documentation covers every endpoint, including one file per jurisdiction, with no key and no account.
Each country page follows the same shape so you can compare them without re-learning the layout: a direct answer, a table of mandatory fields, the numbering rule, the reverse-charge wording where one is prescribed, the retention period, and any e-invoicing obligation with its start date. Underneath sits the sources block with the exact page each value came from and the day we read it.
Two deliberate omissions. We do not tell you whether a rule applies to your business, because that depends on facts we do not have. And we do not fill gaps: where a value could not be confirmed from the authority, the row says so instead of showing a number that looks right. If you need certainty for a specific situation, take it to your tax authority or an accountant.
Once you know what your invoice needs, the invoice generator builds it in the browser, with a tax field, a discount field and a notes field for wording such as a reverse-charge statement. Nothing you type is uploaded.
Frequently asked questions
Are invoice requirements the same in every country?
No, and this is the single most common mistake in invoicing advice. Invoicing is governed nationally. Within the EU, article 226 of the VAT Directive sets one exhaustive list of particulars, so member states share most mandatory fields, while the rate, the retention period, the reverse-charge wording and the e-invoicing deadline still differ by country. Outside the EU the rules diverge much further: the United States has no federal requirement for what an invoice must contain at all.
Which country's rules apply, mine or my client's?
As a general rule you invoice under the rules of the country you are established in, which is why these pages are organised by the seller's country. Cross-border business-to-business supplies inside the EU add a second layer, because the place of supply can shift the VAT liability to the customer and change what the invoice has to say. This describes published rules and is not advice on your own situation.
Do I have to number invoices sequentially?
In much of the EU yes: the VAT Directive requires a sequential number, based on one or more series, that uniquely identifies the invoice. In the United States there is no such federal requirement, though unbroken numbering is still standard practice and makes your own records defensible. Check the page for your country, and see our guide on invoice number formats for the practical side.
Where do these rules come from?
Each one comes from the tax authority or legislature that publishes it, linked from the page it appears on, with the date we last opened that page. Nothing here is taken from an accountancy blog or a software vendor's summary. Our methodology page lists every source per country.
Can I download this data?
Yes. The comparison is published as a CSV file with one row per sourced value and as JSON, free under Creative Commons Attribution 4.0. Every row carries the publishing authority, the source URL and the date the value was read. Attribution with a link is requested.
Related guides
The practical side of getting an invoice right, once you know which rules apply.