Supplier Identity Verification Before Onboarding

Supplier identity verification starts with a simple question: which business are you actually about to onboard? Before interpreting a company profile or attaching screening results to a supplier, match the proposed counterparty to the right official record. A useful starting set is the entity name, country of registration and registration number. Keep the source and retrieval date with the result, and leave unresolved differences visible.

This is the identity question behind Apiosk company verification. Getting it right gives subsequent research a consistent subject. Getting it wrong can produce a detailed file about a business that has nothing to do with the contract in front of you.

Start with the entity on the contract

A supplier may introduce itself using a brand, a trading name or a group name. Those labels are useful context, but the first task is to identify the entity expected to sign the agreement and issue the invoice. Ask for that information explicitly instead of assuming that the best-known group company is the counterparty.

Create a short identity record before searching. Preserve the supplier's original wording alongside any normalized version used for lookup. That allows a reviewer to see whether a difference came from the supplier, a source or your own data entry.

• Record the proposed contracting entity's name exactly as supplied.
• Record the country of registration, separately from the delivery location.
• Record the registration number and the register it belongs to, if known.
• Keep the trading name and invoice name as separate fields when they differ.
• Note which document or communication supplied each detail.
• Mark missing information as missing rather than filling it with a guess.

Treat this as a proposed evidence record for your onboarding process. It is not a claim that every field appears automatically in an Apiosk export.

Use identifiers in their proper context

A registration number is more useful when it travels with its jurisdiction and source. An isolated string in a spreadsheet does not tell the next reviewer which register to consult. Store it as text so software does not silently remove leading zeros or change its formatting.

For a Dutch business, KVK explains that a KVK number has eight digits and can be used to look up a customer or supplier in the Business Register. The practical implication is straightforward: keep the KVK number beside the supplier's name, then compare the retrieved details with the information you received. A number copied from an invoice still needs that comparison.

Another identifier you may encounter is the Legal Entity Identifier. GLEIF describes the LEI as a 20-character alphanumeric code linked to reference information identifying a legal entity. Record an LEI as an LEI, rather than putting it into a generic company-number field and assuming every downstream system interprets it correctly.

The purpose of collecting identifiers is to make the subject of the check explicit. Adding more identifiers is useful only when you know what each one represents and how it relates to the same counterparty.

Compare the record before drawing conclusions

Once you have a candidate record, compare the fields that answer your identity question. Does the name correspond to the proposed contracting entity? Does the jurisdiction match? Does the registration number agree with the one supplied? If an address differs, establish whether you are comparing the same type of address before treating the difference as resolved or problematic.

Avoid compressing this review into an unexplained pass label. A more useful note states the fields checked, the source used and any discrepancy. For example, a reviewer can understand “registration number and legal name match; invoice address still requires explanation” without having to reconstruct what a green indicator meant.

If multiple businesses match a name, keep them as candidates until additional evidence distinguishes them. Do not choose the first result simply because it appears first. If no usable record is returned, document the search inputs and source limitation. A failed lookup and a verified negative finding are different outcomes.

A fictional onboarding example

Consider a fictional supplier that introduces itself as North Quay Studio. Its quotation names North Quay Services B.V. as the contracting entity and supplies a Dutch registration number. The brand and entity names differ, so the onboarding reviewer records both rather than overwriting one with the other.

The reviewer looks up the supplied number in the relevant register and compares the returned name with the quotation. If they agree, that supports the specific identity link under review. The reviewer then requests clarification for any unexplained difference, such as an invoice naming another entity. No actual company, registration number or customer result is represented in this example.

The resulting note can be brief: the documents examined, the entity selected, the source and date of the lookup, the matching fields and the open questions. That is more useful to a colleague than a broad statement that the supplier has been “verified” without saying what was checked.

Keep identity evidence separate from the decision

A company record should be used for the facts it contains. Registration alone does not establish that a supplier can deliver the proposed work, controls a particular bank account or meets every requirement in your onboarding policy. Those are separate questions with their own evidence needs.

The same discipline applies when an AI agent helps assemble the file. Ask it to preserve the entity identifier, sources and unresolved questions. A fluent summary should not turn a missing field into a fact or silently merge records for similarly named businesses. Apiosk for agents explains the product's approach to connecting agents to checks with spending limits and approval rules.

Decide which additional questions are relevant to the actual relationship. The Apiosk use-case overview describes company records, ownership information, screening and other checks. Their relevance and coverage should be reviewed individually; a list of available categories is not a universal onboarding requirement.

Where Apiosk fits

Apiosk's company verification page describes a check using a company name or registration number and a country, with official record details such as name, registered address, status and directors. Before relying on a particular field or country, confirm the available source coverage. The pricing page explains that the sources and maximum cost are shown before a check runs; this article does not assume a fixed price.

At publication on 4 November 2026, the public website marks app access as “Soon available.” Contact the Apiosk team to confirm access and coverage for your intended company check. The checklist above can still help you prepare the identity information and the questions a reviewer needs to resolve.

This guide was prepared with AI assistance using the official sources linked above and Apiosk's public product pages. The worked example is fictional; the checklist is practical data-review guidance, not a statement of jurisdiction-specific legal duties.