WATCHED FIELD
Registry association
See when the identifier-to-company match changes between usable snapshots.
VAT RECORD MONITORING
Monitor the company record
behind the VAT number.
Create a baseline for a VAT number, then recheck its company-record evidence on a daily, weekly, or monthly cadence. Review material changes in VATFind or deliver them to a signed webhook.
WATCHED FIELD
Company legal status
Track changes to the source-reported legal-company status without treating it as tax status.
WATCHED FIELD
Identity details
Compare legal name, registration number, returned VAT identifiers, and registered address.
A DEFINED LIFECYCLE
Baseline, recheck, compare, alert.
Monitoring starts only when you activate it. A saved result remains a point-in-time snapshot.
- 1. Establish a baseline
- Run one live company-record check and keep its supported watched fields as the last usable snapshot.
- 2. Recheck on cadence
- Choose a daily, weekly, or monthly target schedule for each identifier.
- 3. Compare known values
- Ignore case, whitespace, punctuation, source ordering, and unavailable intermediate values.
- 4. Route events
- Review changes in the workspace, read them through REST or deliver them to a signed HTTPS webhook.
ONE MONITORING CONTRACT
Operate it in the workspace, REST API, MCP, or webhooks.
WORKSPACE
Create monitors and review events.
Run, pause, resume, archive, acknowledge changes, and inspect last-known snapshots.
Open monitoringMCP TOOLS
Manage the lifecycle from an AI client.
Use OAuth-scoped monitor and event tools with idempotent creation, updates, and manual runs.
Read the MCP workflowSIGNED WEBHOOKS
Push material changes downstream.
Verify timestamped HMAC signatures and deduplicate at-least-once deliveries by event ID.
Review webhook deliveryIMPORTANT BOUNDARY
Company-record monitoring is not tax-authority validation.
VATFind monitors company-record evidence associated with the identifier. It does not monitor live VAT-registration status through VIES, HMRC, the IRS, or another tax authority, and it does not establish tax compliance. Source unavailability remains an operational state and never overwrites the last successful snapshot.
CHECK USAGE
Predictable usage per identifier.
Monitoring uses the same paid checks as one-off lookups. The monitor slot itself does not add a separate event fee.
- Daily
- Approximately 30 checks per monitor per month.
- Weekly
- Approximately 5 checks per monitor per month.
- Monthly
- Approximately 1 check per monitor per month.
- Source failure
- No check consumed; the prior successful snapshot remains in place.
MONITORING QUESTIONS
Know exactly what will run.
Baseline, cadence, watched fields, source health, billing, delivery, and lifecycle controls.
What is VAT number monitoring?
VATFind monitoring creates a baseline for the company-record evidence associated with a VAT number and rechecks selected fields on a target cadence. It reports material change and operational health events.
Does VATFind monitor live VAT-registration status?
No. VATFind monitors company-record evidence associated with the identifier, not live status through VIES, HMRC, the IRS, or another authority. It does not establish tax compliance.
How often can a VAT record be monitored?
Choose a daily, weekly, or monthly target cadence. A cadence is a scheduled service interval rather than a real-time source-freshness guarantee, and runs depend on service and source availability.
Which VAT and company-record changes can trigger an event?
Watched fields can include registry association, source-reported company legal status, legal name, registration number, returned VAT identifiers, and registered address. VATFind normalizes non-material formatting differences before comparison.
What happens when a monitoring source is unavailable?
VATFind records an operational health event, preserves the last successful snapshot, and retries on a later interval. A source outage does not become a company-change event and does not consume a check.
How is VAT monitoring charged?
Baseline creation and each successful scheduled or manual recheck use one live check. Daily, weekly, and monthly cadences are estimated at 30, 5, and 1 checks per monitor per month, while source failures consume no check.
START WITH ONE IDENTIFIER
Establish the baseline, then keep watch.
Activate monitoring in your workspace or create the first monitor through the REST API.