Disclaimer

Last updated 2026-08-22

The general part

The Clearance Model publishes general information about mandatory electronic invoicing and the reporting obligations attached to it. It is not legal, tax or accounting advice, it is not tailored to your circumstances, and reading it creates no relationship of adviser and client.

The publisher is not a lawyer, a tax adviser or an accountant, does not hold a professional qualification in any of those fields, and carries no professional indemnity insurance. This is stated plainly on the about page and it is the reason every article is written to be checked against its sources rather than taken on trust.

Before acting on anything here, take advice from somebody qualified and insured to give it in the jurisdiction that applies to you.

The specific part

A general warning tells you nothing about how an article might actually mislead you. These are the real failure modes in this subject, and they are worth knowing.

1. Scope is decided by facts this site does not have

Whether a mandate catches a particular transaction turns on things only you know: where each party is established, whether either has a fixed establishment for VAT purposes in the country concerned, the nature of the supply, the place of supply, the sector, group structure and turnover. An article can tell you how the scope test is drawn. It cannot tell you which side of it you fall on.

2. Dates move, and drafts are not law

Every date on this site is labelled in force, adopted or proposed. A proposal is a statement of intent by a government, and governments postpone e-invoicing mandates routinely — several have already been postponed more than once. A date labelled proposed is not a planning assumption. A date labelled adopted can still be amended before it applies.

3. The standard is not the specification you will be validated against

An invoice can conform to the European semantic standard and still be rejected, because the receiver validates against a national profile, and sometimes against its own additional rules on top of that. Where an article describes what the standard requires, that is the floor, not the whole of what you must satisfy.

4. National implementations differ in ways summaries flatten

Two Member States can implement the same European instrument with different thresholds, different definitions of an established business, different treatment of simplified invoices, and different retention periods. An article covering several countries is necessarily a summary, and a summary is where those differences go missing. Where a decision depends on one of them, read the national source that the article links to.

5. Figures that illustrate are not figures that measure

Some diagrams on this site show proportions — where implementation cost tends to land, for example. Those proportions are drawn to show the shape of a problem and are labelled as such. They are not benchmarks, they are not research findings, and they must not be pasted into a business case.

6. Translation is not neutral

Much of the primary material in this field exists in an official language other than English, and the English version — where one exists at all — is often a courtesy translation with no legal standing. Where an article relies on such a text it links to the original. If your decision rests on a precise wording, the original is the wording that counts.

7. Nothing here is a certification

No article, checklist or table on this site certifies anything. If you need assurance that an implementation is compliant, that assurance has to come from somebody who has looked at your implementation and is willing to be liable for the answer.

Third parties

Software, networks, service providers and standards bodies are named where naming them is necessary to explain something. Naming is not endorsement, and the publisher has no commercial relationship with any of them. See the advertising disclosure for how the site is funded.

Reporting an error

If something here is wrong, the contact page is the fastest route to it being fixed. Corrections are made and recorded; that is set out in the editorial policy.

Liability

The limits of the publisher's liability are set out in the terms of use and apply to everything on this page.