EU B2B SaaS sellers should re-check a customer's VAT ID at every renewal, a vatnode.dev post argues, because each invoice is a new supply. It hooks the check to the renewal event and sends failures to a person, since a VIES miss can mean an outage.
Reality
- Evidence40
- Adoption
- Insufficient
- Hype gap+10
- Incentives65
- Confidence45
The European Commission's VAT status endpoint answers only in the present tense and stores nothing, so one operator started keeping every sample. Five days of history is enough to show the member states do not fail together.
Reality
- Evidence58
- Adoption18
- Hype gap−12
- Incentives55
- Confidence52
Running the lookup is trivial. The work is deciding which lifecycle moments re-run it, and keeping a dated record that still means something six months later.
Reality
- Evidence54
- Adoption
- Insufficient
- Hype gap+6
- Incentives74
- Confidence44
A 2019 reissue gave roughly 1.3 million Dutch sole traders new btw-ids. One Node.js validation guide argues the offline mod-11 test every pipeline copied no longer holds for them.
Reality
- Evidence45
- Adoption28
- Hype gap+15
- Incentives65
- Confidence40
A dev.to post makes the case for splitting the customer VAT identifier from an append-only log of validation events, each carrying the consultation number it produced.
Reality
- Evidence38
- Adoption
- Insufficient
- Hype gap+18
- Incentives65
- Confidence45
Receiving becomes mandatory for VAT-liable French firms on 1 September 2026. The older problem: supplier records carry a SIREN, VAT number and IBAN that nothing has checked against a live authority.
Reality
- Evidence30
- Adoption
- Insufficient
- Hype gap+34
- Incentives88
- Confidence42