Capture the claimed payee
Collect the beneficiary name, supplier legal name, country and business identifiers.
PAYMENT & SUPPLIER FRAUD CONTROLS
Supplier fraud controls before payment.
Add supplier company checks to payment fraud controls. Compare VAT numbers, EINs and legal entities when beneficiary details or invoicing instructions change.
START WITHPayee identity + country + tax IDREVIEWResolved company + discrepancy signals
Design the control around your systems and policy.Define countries, inputs, match rules, exceptions, evidence and delivery before integration.
Reviewed
THE PRACTICAL ANSWER
How can company verification support supplier fraud controls?
Check whether the business named in a payment request is consistent with the approved supplier and the company associated with its tax identifier. VATFind helps identify company discrepancies during new supplier setup, beneficiary changes and dormant-vendor reactivation. Use those findings alongside bank-account verification and independent approval. A fraudster can reuse genuine company details, so a matching VAT number or EIN cannot establish that payment instructions are authentic.
- A new supplier or beneficiary is being approved for payment.
- Bank details or the invoicing legal entity have changed.
- A payment-review team needs evidence about the company behind the submitted tax ID.
THE WORKFLOW
Check supplier identity before payment
Resolve the company identity
Match the submitted tax ID or company name to the registered legal entity.
Surface discrepancies
Highlight differences in legal name, country, registration details, address or company status.
Combine independent controls
Use the identity result beside bank-account verification, sanctions, invoice and approval checks.
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.
- 01Registered legal entity
- The company associated with the submitted business identifier.
- 02Identifier consistency
- Whether tax and registration fields align with the resolved entity.
- 03Company status context
- Source-reported status and incorporation information when available.
- 04Address context
- Evidence for resolving similarly named suppliers or unexpected jurisdictions.
- 05Review evidence
- Source and retrieval context for the payment-control record.
CHOOSE THE RIGHT APPROACH
Different fraud checks answer different questions
Company identity
Does the request refer to the legal business already approved? Compare identifiers and explain changes in entity.
Payment destination
Does the destination account belong to the intended payee? Use a separate bank-verification process.
Instruction authenticity
Did an authorised person request the change? Confirm sensitive instructions through a trusted channel already on file.
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.
Treasury and payment operations
Define the evidence required before releasing or changing a payment.
Accounts payable
Compare invoice, vendor, beneficiary and legal-company identities.
Fraud and compliance
Combine independent bank, sanctions, identity and behavioural signals.
DECISION DESIGN
Define the evidence and action at each stage.
| Stage | Evidence to retain | Controlled action |
|---|---|---|
| Change trigger | New beneficiary, changed bank details, legal-name change or dormant-vendor reactivation. | Pause automatic release until the required checks complete. |
| Company identity | Registered entity, identifiers, address, status context, source and time. | Surface discrepancies with the claimed payee rather than producing a safe-to-pay label. |
| Independent approval | Bank ownership, invoice, sanctions, internal authorisation and reviewer disposition. | Release, reject or escalate under the organisation's payment policy. |
EXAMPLE WORKFLOW
An email asks finance to replace bank details
A message uses a known supplier's legal name and VAT number but requests a new beneficiary account. A VATFind match can confirm the company association; it cannot authenticate the sender or the account. Keep the proposed change pending while the payment team verifies the account and contacts the supplier using established details. Retain the company lookup with the independent checks and final reviewer decision so the evidence trail shows what was actually verified.
See the API requests and responsesIMPLEMENTATION CHECKLIST
Supplier fraud control checklist
- Trigger controls on material supplier and payment-detail changes, not only at first onboarding.
- Verify bank-account ownership separately from company identity.
- Require out-of-band confirmation for sensitive beneficiary changes.
- Retain the exact inputs and result from every independent control.
- Prevent one positive signal from overriding an unresolved conflict elsewhere.
WHAT TO MEASURE
Prove the control is useful.
Track operating quality rather than claiming that a company match guarantees the downstream outcome.
- Sensitive changes reviewed before payment
- Identity discrepancies caught before release
- Exceptions with complete reviewer and evidence trails
READ THE RESULT CORRECTLY
A company match is not a safe-to-pay decision.
VATFind does not verify ownership of the destination bank account, invoice authenticity, sanctions clearance, internal authorisation or whether payment instructions were compromised. Company identity is one independent signal in the wider payment-control framework.
Review data and limitationsFREQUENTLY ASKED QUESTIONS
Supplier and payment fraud questions
Does a company match prove the bank account is safe?
No. Bank-account ownership must be verified through a separate account-name or bank-verification control.
When should company identity be rechecked?
Common triggers include new supplier setup, bank-detail changes, legal-name changes, reactivation of dormant vendors and risk-based periodic review.
Should every mismatch stop payment?
Not automatically. Route mismatches according to policy because trading names, group entities and legitimate company changes can create explainable differences.
What evidence should be retained?
Keep the submitted inputs, resolved company fields, source, retrieval time, discrepancies and the reviewer’s final disposition.
Can a genuine VAT number appear on a fraudulent invoice?
Yes. A person can copy real company details. Verify the document, payment destination and authority behind the instruction as separate checks, even if the tax number returns the expected company.
Which changes should trigger a supplier payment review?
Useful triggers include a new beneficiary account, a new contracting company, a changed tax identifier, unexpected jurisdiction and reactivation of a dormant vendor. Define escalation rules for each trigger instead of treating every change alike.