VAT Validation vs KYB: What Each Actually Checks

The short answer

VAT validation checks whether a VAT ID is currently registered, and sometimes hands back a name or address from the underlying registry. KYB (Know Your Business) checks who owns and controls the business and whether it’s clean of sanctions and regulatory flags. One is an input the other can use – neither is a substitute for the other.

That distinction matters because it’s easy to build an onboarding flow where ‘the VAT number checked out’ quietly becomes the whole risk decision. It isn’t one, and it was never meant to be.

What VAT validation actually checks

A VAT validation call answers one question: does this VAT ID exist in the system of record right now. Under the hood, vatnode’s GET /v1/vat/:vatId calls VIES (the EU Commission’s lookup service) and, where VIES is unavailable, a national tax-authority or company-registry fallback.

The response is a valid boolean plus, where the source provides them, registry fields: companyName, companyAddress, companyRegistrationDate, companyForm, industryDescription, registryCode, taxId, and a few others. None of these are guaranteed – coverage depends on what the member state’s VIES endpoint or national registry chooses to expose, and that varies by country. A valid: true result with every enrichment field null is a normal response.

Two things valid: true does not mean:

• It doesn’t mean the business is legitimate, solvent, or safe to deal with. VIES confirms registration status, nothing about conduct or risk.
• It doesn’t mean the data is current. The registration status comes from the source at check time; the enrichment fields, where present, are only as fresh as the registry behind them.

For the full field-by-field breakdown of what’s in the response and when each one is populated, see what a VAT check returns beyond valid or invalid – this post stays at the conceptual level: what the check is for, not every field in it.

What KYB checks that VAT validation doesn’t

KYB is a risk and compliance process, not a single API call. Depending on the regime a business sits in, it typically covers:

• Beneficial ownership (UBO). Who ultimately owns or controls the entity – the natural persons behind layers of holding companies, not just the registered legal name.
• Sanctions and PEP screening. Checking the entity and its known owners/directors against sanctions lists and politically-exposed-persons registers, and keeping that screening current as lists change.
• Incorporation and supporting documents. Certificates of incorporation, articles of association, proof of address, and signatory authority – verified against the document itself, not inferred from a lookup.
• Ongoing monitoring. A one-time pass at onboarding isn’t enough for most regimes; KYB programs re-screen periodically and react to triggering events.

A VAT validation response contains none of this. There’s no ownership field, no sanctions flag, no document reference – VIES and national VAT registries exist to confirm tax registration, not to run AML programs.

Whether a given business needs any or all of the above depends on its own regulatory regime – this post doesn’t tell you which obligations apply to you. What it says is narrower: don’t expect a VAT check to answer that question.

Where the two overlap

The overlap is real, just smaller than ‘VAT check = KYB’:

• Identity fields. Company name, address, and sometimes registration date or legal form overlap with what a KYB process also wants to confirm about an entity – VAT validation can supply or cross-check those fields rather than asking the user to type them in. See the enrichment field reference for exactly which fields and when they’re populated.
• Ongoing monitoring, narrowly. KYB programs re-screen over time; vatnode’s own VAT monitoring and webhooks (paid plans – see pricing) do the equivalent for VAT status specifically – a subscription that fires a webhook when a VAT ID becomes invalid or its registry details change. That covers the ‘did this number stop being valid’ trigger, not sanctions or ownership changes.
• Audit evidence. A VIES consultation number is evidence that a VAT check was made against VIES at a given date and time (it’s only issued when the check includes a requester VAT ID). That’s useful audit evidence for the VAT-specific part of a file, the same way a document hash or screening log is evidence for the rest of it – consultation numbers for finance teams covers how that’s typically retained.

Past that, the two diverge. KYB owns ownership, screening and documents; VAT validation owns registration status and, where available, registry metadata.

A practical pattern: VAT validation as the first gate

The combination that actually works in production is sequential, not substitutive: VAT validation runs first and cheaply, KYB runs after and only where it’s needed.

curl https://api.vatnode.dev/v1/vat/FR12345678901 \
  -H "Authorization: Bearer $VATNODE_API_KEY"

{
  "valid": true,
  "vatId": "FR12345678901",
  "countryCode": "FR",
  "countryName": "France",
  "companyName": "EXAMPLE SAS",
  "companyAddress": "1 RUE EXEMPLE 75001 PARIS",
  "companyRegistrationDate": null,
  "companyForm": null,
  "industryDescription": null,
  "registryCode": null,
  "registryCodeName": null,
  "taxId": null,
  "taxIdName": null,
  "commercialName": null,
  "companyStatus": null,
  "secondaryActivities": [],
  "companyAgeYears": null,
  "registryPrivacy": false,
  "checkId": "a1b2c3d4-5678-4e9f-9a1b-2c3d4e5f6a7b",
  "verifiedAt": "2026-10-05T09:00:00.000Z",
  "source": "VIES",
  "consultationNumber": null,
  "specialTerritory": null
}

Nothing in that response touches ownership, sanctions or document data – there’s no field for it. A workflow that uses this as the first gate typically:

1. Calls /v1/vat/:vatId when a business enters its VAT ID at signup.
2. Blocks or flags on valid: false before any heavier check runs.
3. Pre-fills what’s available (companyName, companyAddress) to cut manual entry.
4. Routes accounts that pass into whatever UBO, sanctions and document checks your own KYB process requires – the VAT result doesn’t decide which accounts can skip them.

Step 2 is where a VAT check earns its place: a fast, inexpensive filter that catches obviously bad input before anyone spends time on a full KYB check. It’s not a replacement for step 4.

This is general information about VAT validation and KYB concepts, not legal or compliance advice – which obligations apply to a given business is a question for counsel, not an API response.

Start with the free plan – 100 requests/month, no card required – and read the full API reference for the exact fields the endpoint returns. For teams running this at volume, pricing covers the paid tiers.

FAQ

Does VAT validation satisfy KYB requirements?

No. VAT validation confirms a VAT ID is currently registered, and sometimes returns registry fields like company name or address. It does not check beneficial ownership, sanctions or PEP status, or incorporation documents, so it cannot stand in for a KYB process on its own – it can only feed one.

What’s the difference between KYB and KYC?

KYC (Know Your Customer) verifies an individual’s identity. KYB (Know Your Business) verifies a legal entity – its registration, structure, beneficial owners, and whether it or the people behind it appear on sanctions or PEP lists. Where a KYB obligation applies, it usually extends to identifying and verifying the people who own or control the business.

What data does a vatnode VAT check return?

A boolean validity result plus, where the source provides them, registry fields such as company name, address, registration date, legal form and industry. It does not return ownership structure, sanctions or PEP matches, or any document data.

Can VAT validation be automated as part of a KYB workflow?

Yes. Calling the validation endpoint at signup and gating or flagging on the result is a common first step in an automated KYB pipeline – before routing to UBO, sanctions and document checks.