Skip to content

ERP ReferenceE-invoicing mandates

Method

Methodology

Every fact on this site comes from a page we actually fetched and read. Each record stores its source URLs and the date we last verified it. If we could not verify something, we show it as unknown and list the gap publicly instead of guessing.

Sources

Currently 30 of 30 country records, 15 format explainers and 58 ERP×country records are backed by fetched sources.

Status definitions

In force
The obligation applies today under law or binding regulation.
Legislated (not yet in force)
Adopted in law with a future start date.
Announced
A government has announced the obligation, but we have not seen adopted legislation.
Proposed
A draft or consultation exists; it may change or not happen.
No mandate
The sources we checked state there is no such mandate.
Unknown
We could not verify the status from an official source.

Dates that are not fixed in law are labelled "not legally fixed". When a source gives only a month or a year, we show only that. Sector-specific obligations (for example energy suppliers) do not count as a general B2B mandate.

Model classification

Post-audit: invoices go directly between the parties and the tax authority checks later. Clearance: invoices must pass through or be registered on a government platform as part of issuing them. CTC / reporting: invoice data is reported to the tax authority in real time or near real time, directly or through accredited platforms. The classification is our reading of the official description and is explained in each country's notes.

Freshness

A script re-fetches every source URL (monthly once enabled), compares the main text of the page with the last reviewed version and produces a review report. A person then checks the change and updates the data and the changes page. The "Last verified" date on each page is the date of the last human review of that record, not the date of the last automated fetch.

Limitations