Company Registration Number vs VAT Number

A company registration number and a VAT number answer different questions. The first identifies a business within a particular register; the second relates to tax registration. For supplier onboarding, keep both the identifier type and its country, validate each through the relevant source, and establish that the results concern the entity you intend to contract with. A valid VAT result alone does not complete a company identity check.

This distinction matters when preparing an Apiosk company verification request. If the question is who the counterparty is, a tax-validation result should not silently replace the company record you meant to obtain. If the question concerns a VAT identifier, a registry match should not be reported as a successful VAT check.

Choose the source for the question

Start by stating the fact you need to establish. “Does this supplier number work?” is too ambiguous to guide a reliable lookup. “Which business is registered under this number in this country?” and “What does the VAT validation service return for this VAT ID?” are separate, useful questions.

The Dutch example makes the distinction concrete. Business.gov.nl explains the different Dutch business numbers, including the KVK number used for registration in the Business Register and the numbers used for VAT. The tax authority assesses whether a business is an entrepreneur for VAT purposes. A business-register entry should therefore not be used as a shortcut to a tax-registration conclusion.

Outside the Netherlands, check the relevant register and tax authority rather than applying Dutch naming conventions to another country. Your internal record should say which authority and identifier type were checked, not merely that a number was “validated.”

Keep the Dutch VAT ID distinct from the tax-office number

The Dutch Tax Administration distinguishes the btw-id from the ob-nummer. The btw-id is used with customers and suppliers. The ob-nummer is used when communicating with the tax authority. For a sole trader, the ob-nummer incorporates the citizen service number; the public-facing VAT ID does not.

For a supplier form, ask for the identifier needed for the stated business purpose. Do not ask someone to upload every tax letter simply because your form has a generic “tax number” field. Clear labels make the request easier to understand and reduce the chance of collecting an irrelevant personal identifier.

Keep the original value separately from any formatting changes made for a lookup. If a service expects a country code in a separate field, record that transformation. Do not overwrite the submitted value or try to manufacture one type of identifier from another based on a pattern that happens to fit a previous supplier.

Read a VIES result within its scope

The European Commission's VIES guidance describes a service for checking registration for cross-border EU trade. It queries national VAT databases. An invalid result can mean the number does not exist, has not been activated for intra-EU transactions, or has an unfinished registration. Updates can also take time to appear. A service-unavailable error calls for a later retry rather than an invalid classification.

For your review process, keep the returned status and the interpretation in separate fields. That lets someone distinguish the source's response from your conclusion about it. If a result needs follow-up, record the unresolved question instead of replacing it with a broad label such as “bad supplier.”

Likewise, preserve any limitation on identity information returned by a source. If the response does not provide a name or address, do not infer those fields from a neighbouring spreadsheet row. State which identity link remains to be established.

Record two checks without merging their meaning

Use a record that makes each lookup understandable on its own. The following is a suggested structure for your team's notes, not a claim about fields in an Apiosk export:

• Supplier reference: your internal identifier for the onboarding file.
• Expected counterparty: the name from the agreement or quotation under review.
• Identifier type: company registration number or VAT identification number.
• Issuing country and source: the jurisdiction and service used for this lookup.
• Submitted and queried values: the original identifier and any documented formatting change.
• Result and retrieval time: the source response, when it was obtained and any available reference.
• Identity comparison: which returned details agree with the intended counterparty and which remain unconfirmed.
• Follow-up owner: the person responsible for resolving an outstanding question.

Store identifiers as text when preparing a spreadsheet or import. This avoids accidentally dropping leading zeros or letting a spreadsheet turn a number into a different display format. Preserve distinctions such as a missing input, an unavailable source and an explicit negative response; they require different next steps.

This extends the evidence record in our supplier identity verification guide. That guide addresses identifying the contracting entity; the additional discipline here is keeping company and VAT evidence attached to their own questions.

A fictional mismatch worth resolving

Imagine a fictional supplier whose quotation names Harbour Loom B.V. A registry lookup agrees with the supplied company registration details. The onboarding file also contains a VAT ID copied from a different document, and the reviewer has not established that it belongs to the same counterparty.

Even if a VAT lookup returns a valid result, the reviewer still has an identity question. The appropriate next step is to ask the supplier to explain the document and identifier, then compare the evidence through the relevant source. It would be premature either to approve the whole file or to accuse the supplier of misconduct.

A useful note says what is known: company details matched; the VAT identifier was checked separately; its connection to the contracting entity remains unresolved. Keep the original documents and the explanation together so a colleague can follow the reasoning. This example represents no real business, identifier or customer result.

Where Apiosk fits

Apiosk presents identifier validation separately from company verification. Use that distinction when describing the task you want help with. Specify the identifier, its country and the question, and review the available source coverage rather than assuming every jurisdiction returns the same information.

At publication on 5 November 2026, the public Apiosk website marks app access as “Soon available.” Contact the Apiosk team to confirm access and coverage for your intended check.

The practical outcome is a clearer handoff: a person or agent can see which identifier was checked, what the source returned and which question remains open. The checks provide evidence for your process; they do not decide the supplier relationship or the tax treatment of a transaction.

This article was prepared with AI assistance using the official sources linked above and Apiosk's public product pages. The example is fictional. The guidance concerns organising and interpreting source data, not determining legal obligations or tax treatment.