INVOICE REVIEW

Invoice verification: check the supplier's VAT number.

Verify the company behind an invoice VAT number or EIN. Compare supplier names, registration details and tax identifiers during accounts payable review.

START WITHInvoice tax ID + supplier countryREVIEWMatched company + invoice comparison points
Design the control around your systems and policy.Define countries, inputs, match rules, exceptions, evidence and delivery before integration.
Discuss an enterprise workflow Try an individual lookup

THE PRACTICAL ANSWER

How do you verify the supplier identity on an invoice?

Compare the invoice's legal supplier name, VAT number or EIN and address with the approved vendor and the company record returned by VATFind. Use a registration number where available to distinguish similarly named entities. Keep this identity check alongside your purchase-order, receipt, amount and payment checks. Matching the company behind an invoice is one part of invoice verification, not confirmation that the invoice is authentic or payable.

  • The invoice supplier name differs from the vendor-master name.
  • A new or changed VAT number appears on an invoice.
  • An accounts-payable reviewer needs to identify the legal company behind the number.

THE WORKFLOW

The invoice verification workflow

Explore API access
01

Take the number from the invoice

Copy the VAT or tax ID carefully and select the supplier’s legal registration country.

02

Run the company-record check

VATFind searches the available company-data source for a record linked to the submitted identifier.

03

Compare the invoice party

Review the legal name, registration number, and address beside the invoice and your vendor record.

04

Use the right authority for tax status

If VAT treatment depends on current registration, complete the separate official validation required for that jurisdiction.

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.

01Submitted tax ID
The number used for the search, normalised for matching.
02Matched legal company
The entity linked to the number in the returned company record.
03Company registration number
A separate identifier to compare with the vendor master.
04Address and company status
Additional context when returned by the source.
05Source and retrieval time
The evidence context of the VATFind result.

CHOOSE THE RIGHT APPROACH

Three checks in an invoice verification process

Supplier identity

Match the invoicing entity and tax number to the vendor record. Investigate differences between a parent, subsidiary and trading name.

Invoice and order

Reconcile the document with the purchase order, goods or service receipt, and your duplicate-invoice controls.

Tax and payment

Confirm the tax treatment and bank details through the appropriate separate process before releasing funds.

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.

Accounts payable

Compare the invoice party with the approved vendor and company record.

Tax operations

Run any separate authority or tax-treatment control required by the transaction.

Vendor master team

Investigate new or changed tax identifiers before updating core data.

DECISION DESIGN

Define the evidence and action at each stage.

Keep company identity separate from the final policy outcome
Evidence and action design for Invoice verification: check the supplier's VAT number.
StageEvidence to retainControlled action
Invoice intakeSupplier name, invoice country and the VAT or tax ID printed on the document.Extract the fields without assuming the trading name is the legal entity.
Company comparisonMatched legal name, registration number, address and source-reported status.Compare invoice, vendor-master and company-record identities side by side.
Tax decisionSeparate authority response and transaction facts where required.Determine tax treatment outside the company-record match and retain both evidence sets.

EXAMPLE WORKFLOW

A familiar supplier invoices through another group company

The vendor master names a UK company, but a new invoice carries another entity's tax number. Search that number and compare the returned company with the contract and purchase order. Ask whether the contracting entity has changed or whether the invoice needs correction. Preserve the original invoice and the lookup evidence in the exception case. Do not silently change the vendor record merely to make the invoice pass matching.

See the API requests and responses

IMPLEMENTATION CHECKLIST

Invoice verification checklist

  • Trigger review when an invoice introduces a VAT number not present in the approved vendor record.
  • Keep group-company identifiers from being treated as interchangeable.
  • Distinguish data-entry formatting differences from substantive entity mismatches.
  • Record the reviewer decision and any supplier explanation.
  • Do not let a VAT match override duplicate-invoice, bank or approval controls.

WHAT TO MEASURE

Prove the control is useful.

Track operating quality rather than claiming that a company match guarantees the downstream outcome.

  • Invoices with entity discrepancies detected before posting
  • New tax IDs reviewed before master-data change
  • Average time to resolve invoice identity exceptions

READ THE RESULT CORRECTLY

Do not use a company match as a VAT-treatment decision.

Reverse-charge, input-tax, invoicing, and evidence requirements depend on the relevant rules and authority response. VATFind helps identify the company behind the number; it does not determine the tax treatment of an invoice.

Review data and limitations

FREQUENTLY ASKED QUESTIONS

Invoice verification questions

What should match between the invoice and company record?

Compare the VAT or tax ID, legal company name, registration country, registration number, and address. A trading name may differ, but the legal entity should be explainable.

Does a matched number mean the invoice is correct?

No. The result does not assess invoice arithmetic, supply, tax rate, bank details, duplicate invoices, or authorisation. It addresses only the company-record match.

What if the invoice VAT number belongs to another group company?

Ask the supplier to explain which entity supplied the goods or services and issue corrected documentation when required. Do not assume group affiliation makes the number interchangeable.

Can I download the matched company result?

Yes. Open the company details after a match and use the available save, print, or CSV controls. Keep any separate authority validation with the same review record.

Does checking the VAT number confirm VAT invoice requirements?

No. A company association does not assess every invoice requirement or the correct tax treatment. It identifies the company linked to the number. Review the applicable invoicing rules and any required authority response separately.

When should accounts payable repeat a supplier VAT check?

Useful triggers include a first invoice, a changed legal name or tax ID, a new invoicing entity and reactivation of a dormant vendor. Apply the review cadence your organisation sets for existing suppliers.

Sources and further reading

EU: VAT invoicing requirements Reference for interpreting the registration and identifier evidence.