Start with a resolved company
Attach monitoring to the identifier and resolved company evidence selected during onboarding, not to a free-text name.
SCHEDULED COMPANY MONITORING
Supplier monitoring after company onboarding.
Monitor supplier and customer company records after onboarding. Review changes to names, addresses, company status and tax identifiers on a chosen cadence.
START WITHPreviously resolved company recordREVIEWChange events + review evidence
Design the control around your systems and policy.Define countries, inputs, match rules, exceptions, evidence and delivery before integration.
Reviewed
THE PRACTICAL ANSWER
What should supplier monitoring cover after onboarding?
Supplier monitoring should revisit the company facts your approval relied on, such as legal name, registered address, company status and tax-identifier association. VATFind company monitoring compares supported fields on a configured cadence and exposes events for review. Link each monitor to the originally resolved entity, assign an event owner and define which changes require a fresh onboarding or payment check.
- Approved suppliers remain active for long periods without being re-onboarded.
- Customer or merchant risk policies require event-driven or periodic review.
- Material registry changes need to trigger an ERP, KYB or case-management workflow.
THE WORKFLOW
Set up supplier monitoring
Define material changes
Choose which supported company-status, legal-name, address, registration-number or VAT-number changes matter to the policy.
Receive and classify events
Review changes in the workspace or deliver them through the documented REST, MCP or webhook route.
Record the disposition
Keep the event, source, review outcome and resulting action in the customer or supplier record.
WHAT VATFIND DOES
VATFind rechecks the company evidence behind the original verification.
Monitoring starts from a resolved legal entity and its VAT number, EIN or company-registration evidence. VATFind records supported company-record changes and routes them for review; authority-backed VAT-status monitoring remains a separate result where that coverage is available.
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.
- 01Company status changes
- Updates to the source-reported legal-company status when available.
- 02Identity changes
- Supported legal-name, registration-number or VAT-number changes linked to the monitored evidence.
- 03Address changes
- New registered-address information that may require review.
- 04Event context
- The previous and current values with source and timing information.
- 05Workflow outcome
- The internal review, escalation or record update triggered by the event.
CHOOSE THE RIGHT APPROACH
Company monitoring, risk monitoring and VAT status
Company-record changes
Track supported identity fields and route changes to the team maintaining the supplier or customer record.
Wider supplier risk
Use separate evidence for credit, operational performance, sanctions, ownership and other risks outside the monitored identity fields.
VAT-registration status
Assess authority-backed status monitoring separately by country and source. Company-record monitoring does not establish live tax-registration status.
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.
Third-party risk
Define which company changes require re-review and by when.
Vendor or customer operations
Investigate events and update operating records.
Compliance governance
Record the disposition and ensure consequential decisions remain controlled.
DECISION DESIGN
Define the evidence and action at each stage.
| Stage | Evidence to retain | Controlled action |
|---|---|---|
| Baseline | Approved legal entity, identifiers, address, status, source and verification time. | Create the monitored record from a resolved company—not a free-text name. |
| Change detection | New source value, prior value, event type and observed time. | Deduplicate and classify changes by policy relevance. |
| Re-review | Event context, refreshed company evidence and reviewer decision. | Update, request information, suspend or take no action with a recorded reason. |
EXAMPLE WORKFLOW
An approved vendor changes its legal name
A scheduled check returns a new legal name for a monitored company. Compare the retained registration identifiers and available tax-ID evidence with the original baseline. If the legal entity is unchanged, the vendor-data team can review a name update. If the identifiers conflict, reopen entity verification before changing the master record. The workflow should record its conclusion and retain the earlier snapshot, so the next user understands why the record changed.
Set up company monitoringIMPLEMENTATION CHECKLIST
Supplier monitoring checklist
- Define material events separately from ordinary data refreshes.
- Set severity and response time by event type and counterparty risk tier.
- Link every event to the original resolved company evidence and downstream case.
- Suppress duplicate notifications without hiding repeated unresolved risk.
- Version the evidence used after each material re-review.
WHAT TO MEASURE
Prove the control is useful.
Track operating quality rather than claiming that a company match guarantees the downstream outcome.
- Material events reviewed within policy SLA
- False-positive and duplicate-event rate
- Monitored records still linked to an active canonical entity
READ THE RESULT CORRECTLY
Monitoring coverage depends on source and configured events.
The public lookup does not automatically monitor every result. Monitoring must be explicitly activated with a daily, weekly, or monthly target cadence and selected fields. It tracks source-labelled company-record evidence, not live tax-authority status, and each alert still needs an accountable review process.
Review data and limitationsFREQUENTLY ASKED QUESTIONS
Company monitoring questions
Why monitor after onboarding?
Company details can change after the original check. Monitoring helps identify events that may affect vendor, customer, merchant or compliance records.
Which changes should trigger review?
Typical triggers include status, legal-name, address and identifier changes. The correct set depends on the organisation’s risk and operating policy.
Does every change indicate risk?
No. Many registry changes are routine. Monitoring should route events for proportionate review rather than treating every update as adverse.
Can events be delivered through an API?
Yes. Configured monitors expose events through the workspace, REST API, MCP tools and signed webhooks.
How often should supplier records be rechecked?
Choose a cadence based on the relationship and your policy. VATFind offers daily, weekly and monthly target cadences for company monitoring. Estimate usage before activation because completed monitoring checks draw from the plan allowance.
Does a monitoring event need a human review every time?
Not necessarily. Define materiality and routing rules for each event type. Routine updates may need a record change, while identity conflicts or changes affecting an active decision should enter a review queue.