Company legal status and tax-registration status answer different questions. The public lookup returns company-record evidence; API and MCP clients must read the independent authority-status capability instead of inferring it.
BEFORE YOU START
Collect the inputs that prevent a false match.
- The exact business question the check must answer
- Identifier type and issuing country
- The legal company expected by the workflow
- The source and timestamp required for evidence
- A defined route for unavailable, ambiguous and disagreeing results
SOURCE MAP
Use the source that answers the actual question.
| Question | Evidence source | Retain |
|---|---|---|
| Who is the legal company? | Company record or business registry | Legal name, registration number, jurisdiction and source |
| Is this number associated with that company record? | VATFind company-record match | Submitted number, match state, company and retrieval time |
| What does the tax authority report now? | VIES, HMRC or the relevant national authority | Authority response, time and reference where supplied |
| What tax treatment applies? | Transaction facts, applicable rules and professional review | Decision rationale and the evidence actually used |
What a VAT lookup tells you
VATFind offers two ways to reach a company record. Find a VAT number starts with the legal company name; Check VAT / EIN starts with a number and shows which company-data record it matches. Useful fields include the legal name, registration number, available tax ID, address, and data source.
VATFind returns the available company information with source context and a retrieval time. Data availability differs between countries and individual records. The retrieval time shows when VATFind obtained the result, not necessarily when every underlying field was last updated.
What official validation tells you
An official authority service can return its current response for a tax registration, often with the associated registered name and address.
Authority services answer a different question from company discovery. Record their response separately from the company-record match returned by VATFind.
GOV.UK: Check a UK VAT numberRead status labels in context
A registry status describes the company record supplied by the source. A tax-registration status describes a different registration. One cannot substitute for the other.
The public lookup described in this guide displays source-reported company status when available. REST and MCP expose a separate tax_authority_status dimension; not_supported or not_checked is not an authority confirmation, and clients must use the country capability returned by the contract.
Keep the evidence for the question you asked
For entity research, retain the company identifiers and source information. For a tax-registration decision, retain the appropriate authority result and date. Label each record so another person can tell what was actually checked.
If an official service is unavailable, retain that service response as an error and retry or contact the authority. Keep it separate from the VATFind company-record result.
Read VIES and national authority responses carefully
The European Commission describes VIES as a search engine that retrieves VAT-registration information from national databases. A response can be affected by national activation, incomplete registration or temporary database availability. It is not a universal company register and it does not replace legal-entity resolution.
Some authority services return a name, address or consultation reference; others confirm only part of the submitted information. Record exactly what the service returned instead of upgrading a narrow response into a broader statement about legitimacy, ownership, solvency or fraud risk.
EU: Check a VAT number through VIESDesign a status model that preserves uncertainty
A production workflow should distinguish malformed input, unsupported capability, company matched, company not matched, ambiguity and source unavailability. Where an authority result exists, keep that in its own field. One boolean cannot explain which question was checked or why a case needs review.
This is especially important for automation. A retryable service outage should trigger a retry or review. An ambiguous company result should request more identifying information. A completed no-match should preserve the input and source context. Each state has a different operational response.
PRACTICAL QUESTIONS
Frequently asked questions
What is the difference between VAT lookup and VAT validation?
A lookup can identify a company or surface a source-reported number. An official validation service reports its current response for a submitted VAT registration. The sources, timestamps and limitations are different.
Can a company be active while its VAT status is different?
Yes. Company legal status and tax registration are different facts maintained by different systems. Neither should be inferred from the other.
What can an unavailable VIES or authority response mean?
The service or a national database may be unavailable. Preserve that service state and retry or follow the authority's guidance; do not translate an outage into a no-match or negative business conclusion.
Does a number with the right format prove registration?
No. Format logic checks structure only. Issuance, company association and current tax status require separate evidence.
Which result should an API store?
Store each dimension separately: submitted and normalised identifier, format status, company-record match, authority status where available, company legal status, sources, times and warnings.
When was this guide last reviewed?
VATFind reviewed this guide on 29 August 2026. Rules, authority services, and source coverage can change, so check the linked official reference before making a current tax or legal decision.
This guide explains the lookup and evidence process; it is not tax or legal advice. Official services, coverage and requirements can change. The review date records VATFind's content review, not a guarantee that every linked authority changed on that date.