We check EIN and VAT numbers against the issuing tax authority, then resolve the number to the legal entity in that country's company register — and keep a timestamped record of both.
Format. Authority. Registry. Evidence. In that order, on every single number.
Country-specific structure and checksum applied before any network call, so malformed input never consumes an authority query.
Live query to the issuing tax administration. Three outcomes are handled distinctly, and unavailable results are queued and retried, not failed.
The number is matched to the legal entity in the national company register — including in jurisdictions where the tax authority returns nothing but a validity flag.
An immutable record of the check: input, response, source, timestamp, consultation reference. Retrievable by counterparty or by date range.
The tax authority answers one question. The company register answers the rest. What that actually looks like, country by country.
Structure, local-language name, worked example and registration threshold for 110 jurisdictions, each verified against the issuing authority — with a format validator that runs in your browser. No account, nothing leaves the page.
Perpetual monitoring means every number you hold is re-checked against the issuing authority every day, for as long as you hold it. Here is one supplier across a single year, and the day you hear about each change.
Checked against the authority, resolved to the entity, evidence stored.
Baseline recordedRemoved from the intra-EU register while the domestic registration continues.
You are told on day 41Absorbed into a VAT group. The old number is retired.
You are told on day 96The authority cancels the registration outright.
You are told on day 173The first time anyone notices, and the VAT is already yours.
Only without monitoringVIES is the European Commission's free service for checking EU VAT numbers, and we query it too. It answers one question, for one region, one number at a time. Below is how the two compare across the seven things enterprise finance and compliance teams ask about.
Start in the platform today, integrate when volume demands it. The underlying record never changes.
Search, validate and export from the web application. Built for analysts running checks one company at a time.
Single lookup or batch. Validation, registry resolution and the evidence reference come back in one response, priced per result rather than per token.
Daily, weekly or monthly exports loaded into your own database. Send the whole vendor or seller master and get it back matched. Reseller and derivative rights available.
Check a company’s tax registration and registry entry from any website or LinkedIn profile without leaving the page.
Validation on the record your team already works in, matched on registration number rather than company name. Registry fields refresh on the same daily sync, so the account carries filed data instead of typed notes.
One-click connectors for both assistants. Ask in plain language which suppliers lost their VAT registration this quarter and get the answer with its source attached.
Validation and registry resolution exposed as tools to Claude and any other Model Context Protocol client, on the same key and the same provenance fields.
Our own model, in the platform and over the API. Ask a question that spans numbers, entities or borders and it plans which authorities and registers can answer, calls them, and hands back every value with its source, reference and timestamp. It cannot answer from training alone.
As a UK accounting and tax advisory firm, Menzies LLP integrates verified financial and registry data directly via API — the same registry-backed identifiers that underpin reliable tax ID and VAT validation.
Read the case studySend a sample from your vendor or seller master. We check each EIN and VAT number against the authority that issued it, resolve it to the legal entity in the company register, and return a count of the records where the two no longer agree. No integration, no commitment.
Because a validity flag is not the answer most teams need. The free services confirm a number is registered; the European Commission is explicit that VIES is a search engine rather than a database, and its own guidance notes the service is periodically unavailable while national databases back up. We validate against the authority, resolve the number to the legal entity in the company register, keep the evidence, and re-check daily.
There is no open IRS database to query. Validation is a match: the EIN is checked together with the legal name, and the result confirms whether the two agree. Everything a compliance or AP team needs after that — registered address, entity status, incorporation date, officers, group structure — comes from state filings, which we hold and join to the EIN.
No. Every identifier is checked against the authority that issued it, and every registry field is sourced directly from the government register that holds it. Each field carries its source and the date it was retrieved.
The check returns unavailable — explicitly, not as a rejection. The request is queued and retried on a backoff schedule, and the resolved result is delivered without you polling for it. Treating an outage as an invalid number is one of the most common and most expensive implementation errors.
Yes. Where a member state confirms validity without releasing trader name and address, we take the confirmation from the authority and resolve the entity from the national company register — the Handelsregister and the Registro Mercantil respectively. The number still lands on a named, status-checked company.
Each check produces a timestamped record containing the number submitted, the requester number, the authority queried, the response, the consultation reference where one is issued, and a snapshot of the registry data at that moment. Whether that satisfies a specific assessment is a matter for your tax advisers, but the record exists and is exportable.
Monitored numbers are re-checked against the issuing authority on a daily cycle, and the change is pushed into your systems rather than waiting for you to ask. Authorities themselves publish with a lag, so the honest answer is: as soon as the register shows it.
National tax and business identifiers including GSTIN, ABN, CNPJ, UEN, UID and organisation numbers, alongside EU and UK VAT registration numbers and US EINs. The full list, with the issuing authority and the register each is joined to, is published in the data dictionary.
Yes, under licence. Identifiers are open and there is no proprietary key locking you in — you keep the government registration numbers and can move providers without re-mapping your master data. Redistribution terms are agreed commercially.
The free trial gives you API access the same day. Bulk validation of an existing vendor or seller master is usually a single file exchange. Integration work is measured in days, not quarters.