What is a VAT Number?

  • Registers & identifiers
  • Business identifiers
  • 3 min read

The short answer

A VAT number identifies a person or business registered for value-added tax in a particular tax system. It is used in tax-related processes and may help reconcile a counterparty’s records. It should be stored with its country or issuing context because formats and validation methods vary.

VAT Number: why it matters

A legal entity record and a VAT registration describe related but different things. A business can have a registration number without the VAT status expected for a particular transaction. Keeping the identifiers distinct helps finance, onboarding and data teams ask the right question rather than infer tax status from a company search.

How to assess it in practice

Collect the number as supplied and identify the relevant tax system. Check its syntax using country-specific rules, then use the appropriate official validation service where available. Reconcile any returned identity details with the counterparty’s legal entity information. Record the validation date, result and any service limitations. Review tax treatment separately when the transaction requires specialist interpretation.

Worked example

A supplier gives a company registration number in a field labelled VAT number. The buyer does not approve it simply because the company exists. The buyer asks for the correct tax identifier and validates that identifier using the appropriate service before recording the result.

Illustrative scenario

A number passes a format check but the returned business details differ from the invoice. Resolve the discrepancy before treating the tax check as a complete verification.

Distinctions that matter

A company registration number identifies the legal entity in a registry. A VAT number identifies a tax registration. Entity resolution can connect those records, but should preserve which source supports each claim.

Evidence and review output

Review these

  • Identifier namespace and issuer
  • Original value and normalisation
  • Returned identity and status scope

The review should produce

A reconciled identifier-to-entity link with the validation method and any conflict retained.

Across this family

Identifiers belong to namespaces. Retain the issuer, country context, original representation and entity scope so matching does not depend on an apparently unique string alone. Format checks are useful for input quality but do not establish current registration or entitlement to use an identifier.

A note from practice

A VAT number relates to a tax registration under a particular system. Keep the country context and distinguish structural validation, an external status check and a legal-entity match.

Limits and common mistakes

Format checking and live validation are separate steps. A temporary service error should not be recorded as proof that a number is invalid. Equally, a valid tax identifier should not be treated as confirmation of financial strength or complete ownership verification. Tax conclusions depend on the transaction and applicable rules.

Frequently asked questions

Does correct format mean valid VAT registration?

No. Syntax and live registration validation answer different questions.

Is a VAT number a company registration number?

Not necessarily. Keep the two fields separate.

What if validation is unavailable?

Record the service failure and retry or use an approved alternative; do not invent a validation result.

Continue learning

Sources & further reading

See the registry record behind every answer.

Primary, government-sourced data on 600M+ companies in 200+ countries, with full source attribution.