Capture the legal details
Collect the supplier’s legal name, registration country, tax ID, registration number, and registered address.
SUPPLIER ONBOARDING
Supplier onboarding: verify company and tax details.
Build a supplier onboarding checklist for legal names, VAT numbers, EINs and company records. Resolve vendor identity before creating an ERP supplier record.
START WITHSupplier country + submitted tax IDREVIEWResolved entity + onboarding exceptions
Design the control around your systems and policy.Define countries, inputs, match rules, exceptions, evidence and delivery before integration.
Reviewed
THE PRACTICAL ANSWER
What belongs in a supplier onboarding checklist?
A supplier onboarding checklist should collect the contracting legal name, registration country, company number, registered address and relevant VAT number or EIN. Compare those details before creating the vendor master record. VATFind supplies the company and tax-ID association for this step; procurement can then continue its document, bank-detail, screening and approval process against the same supplier entity.
- A new supplier submits a VAT number or EIN with its onboarding form.
- The commercial brand does not clearly identify the contracting legal entity.
- Procurement and accounts payable need one consistent company identity in the vendor master.
THE WORKFLOW
The supplier onboarding process
Resolve the submitted identity
Match the tax ID and legal name to the most likely source-labelled company record.
Apply onboarding rules
Compare legal name, identifiers, address, status and source context against the onboarding form.
Route exceptions
Send mismatches, ambiguous entities and incomplete records to review instead of silently overwriting data.
WHAT VATFIND DOES
VATFind verifies which legal company is associated with the VAT number or EIN.
VATFind takes the submitted identifier and country, matches it to a source-labelled company record, and returns the legal name, registration number, address, company context, source and retrieval time. The workflow receives an explicit match, discrepancy, ambiguity, no-match or unavailable state instead of a generic pass/fail answer.
Evidence meaning: a verified association means the submitted VAT number or EIN is linked to the returned company record. It is not, by itself, confirmation of current tax-registration status, tax compliance or approval of the wider transaction.
For API checks, use vat_number outside the US and tax_identifier for US EINs. Optional fields can be absent when a source does not provide them.
- 01Legal-name match
- Does the company record identify the supplier you expected?
- 02Tax-ID association
- Is the submitted number linked to the returned company record?
- 03Registration details
- Separate company number, legal form, status, and incorporation date when supplied.
- 04Registered address
- Useful for resolving entities with a common or trading name.
- 05Source context
- The source label and time VATFind retrieved the record.
CHOOSE THE RIGHT APPROACH
Separate supplier onboarding from later vendor controls
New supplier setup
Establish the contracting entity and resolve missing or conflicting identifiers before creating the supplier record.
Vendor data cleansing
Repair existing records, duplicates and inconsistent tax IDs using a documented process for proposed changes.
Supplier monitoring
Recheck approved entities after onboarding and route relevant company changes to the responsible team.
CONTROL OWNERSHIP
Give each team one clear responsibility.
A reliable workflow names who owns the input, who interprets the company evidence and who makes the wider decision. That separation prevents a data result from becoming an unexplained approval.
Procurement operations
Define the legal supplier record required before vendor approval.
Accounts payable
Ensure the invoicing entity and vendor master use consistent identifiers.
Third-party risk
Set escalation rules and initiate the independent controls required by policy.
DECISION DESIGN
Define the evidence and action at each stage.
| Stage | Evidence to retain | Controlled action |
|---|---|---|
| Application | Legal name, country, registration number, tax ID and registered address. | Block incomplete submissions from becoming an approved vendor record. |
| Entity resolution | Source-labelled company match and any discrepancies with submitted fields. | Create one governed legal-entity record or route the case to review. |
| Approval handoff | Resolved identifiers, source, timestamp and reviewer disposition. | Start ownership, sanctions, bank and risk checks against the correct entity. |
EXAMPLE WORKFLOW
Procurement and finance receive different company details
Procurement approves a supplier using its group brand, while finance receives an invoice from a local legal company. Establish which entity is signing the contract, then compare its VAT number or EIN, registration number and address. Record the brand as a business alias without replacing the legal supplier. Assign the final entity selection to the vendor-data owner so the purchase order, invoice and payment workflow use a consistent record.
See the API requests and responsesIMPLEMENTATION CHECKLIST
Supplier onboarding checklist
- Collect legal name and trading name in separate fields.
- Make country and identifier type mandatory before matching.
- Define which discrepancies can be accepted automatically and which require evidence.
- Prevent reviewers from overwriting the original supplier submission.
- Trigger re-verification when the legal entity or tax details change.
WHAT TO MEASURE
Prove the control is useful.
Track operating quality rather than claiming that a company match guarantees the downstream outcome.
- Suppliers resolved before ERP creation
- Median time to clear identity exceptions
- Duplicate or wrong-entity vendor records prevented
READ THE RESULT CORRECTLY
Tax-ID matching is one onboarding control, not complete KYB.
The lookup does not verify bank ownership, sanctions, beneficial ownership, tax compliance, or the authority of the person submitting the form. Apply the other controls required by your risk policy separately.
Review data and limitationsFREQUENTLY ASKED QUESTIONS
Supplier onboarding questions
When should the supplier tax ID be checked?
Check it before the vendor record is approved and again when the legal entity or tax details change. The correct cadence depends on your internal policy and jurisdiction.
Should I approve a supplier when the number matches?
A match resolves only the company-record association. Approval should still follow your required document, bank, sanctions, ownership, and risk checks.
What should happen when the legal name does not match?
Pause the record creation and ask the supplier for clarification or corrected documents. Similar group-company names and trading names are common sources of error.
Can this page process a vendor file in bulk?
No. The public VATFind tool is for individual lookups. Use the API request route to discuss a scaled workflow.
What is the difference between supplier onboarding and vendor onboarding?
The terms usually describe bringing a new business into procurement and payment systems. The practical requirement is the same: collect its details, resolve the legal entity, complete your checks and assign ownership of the approved record.
How can supplier verification be added to an ERP workflow?
Your application can call the VATFind REST API with the supplier's name or tax identifier and country, compare the result with the submitted fields, and route exceptions before creating or changing an ERP vendor. The integration must define its own field mapping and approval rules.