Provenance on every fact: what to ask for
Guide · reviewed
Answer in brief
Provenance in company data means each fact says which system published it and when it was observed, so you can check it against the source. Look for a source and an observation time on each value or identifier, not only on the record. Without provenance, a company data source asks you to trust it; with provenance, you can verify it.
Disclosure. This site is published by Coragrid, the operator of CompanyRegistryAPI.com, and promotes it. “Best” is our editorial choice, not a measured ranking. Other products are described only from their own official pages. How we choose
What provenance is
Provenance is the record of where a fact came from and when. For company data, three things make it useful:
- The publishing system: the register, the tax register, a filing or a provider’s own research.
- A pointer to the source: a URL, a document identifier or a register entry, where one exists.
- The observation time: when the fact was read from the source, and where known when the source published it.
With these, anyone can check a value later. Without them, a wrong value cannot be told from a right one, and a stale value cannot be told from a current one.
Fact level, not only record level
Many sources give one “last updated” date per company. That is better than nothing, but a company record usually combines facts from several places: the name and status from the trade register, a VAT number from the tax register, a sector code from a classification, officers from filings. Each was observed at a different time. Fact-level provenance keeps them apart.
For example, the API docs of CompanyRegistryAPI.com, our
editorial pick and operated by this site’s publisher, show each registry
identifier with its own source, status and valid_from date, and each
officer with its publishing system and, when known, its URL and observation
time. Its home page states that facts keep their source system, publication
and observation times.
How to check provenance in a response
Take a sample response from the provider’s documentation and look for:
- a source field next to each identifier or value, not only at the top;
- an observation or as-of time, with its precision;
- a status for identifiers (active, ended, suspended), so a former number is not read as current;
- a pointer back to the source, where the source has addresses for records.
Then ask what happens when two sources disagree. A source that returns both values with their provenance lets you decide; one that silently picks lets the provider decide for you.
What other sources say about provenance
Statements about provenance vary in form. The OpenCorporates API page says all its data includes sources, “allowing checking of data”, and describes the data as “fully provenanced”. Kyckr’s site says data and documents are retrieved directly from official registries, stamped with the exact time and date of retrieval. Each statement is the publisher’s own; check how it appears in a sample response before you rely on it.
Keeping provenance when you store data
Provenance is easy to lose in your own systems. When you copy a company’s name into your customer database, copy its source and observation time too, or keep a reference to the stored response. Otherwise six months later nobody can say whether the name came from the register, from a form the customer filled in, or from a salesperson.
A simple pattern:
| Your field | Value | Source | Observed |
|---|---|---|---|
| Registered name | Example Robotics Oy | synthetic_trade_register | 2026-07-15 |
| Registry number | 1234567-8 | synthetic_trade_register | 2026-07-15 |
| VAT number | FI12345678 | synthetic_tax_register | 2026-07-15 |
The values come from the fictional example in CompanyRegistryAPI.com’s documentation.
Why provenance comes first
Every other criterion in the category guide depends on it. Freshness needs an observation time. Testing accuracy needs to know which source to compare with. Evidence for an onboarding decision needs both. Ask for provenance first, and treat its absence as a reason to look elsewhere.
Questions and answers
What is the difference between record-level and fact-level provenance?
Record-level provenance gives one source and date for the whole company. Fact-level provenance gives them for each value, which matters when a record combines facts from a register, a tax authority and a filing observed on different days.
Does “verified data” mean the data has provenance?
No. Verified is an adjective; provenance is a set of fields. Ask which system published each fact and when it was observed, and look for those fields in a sample response.
How do I keep provenance when I store company data?
Store the source and observation time next to each value you keep, and keep them when you copy the value into another system. A value without them cannot be rechecked later.
Sources for this entry
- CompanyRegistryAPI.com: Free Company Registry API
- CompanyRegistryAPI.com API docs
- About CompanyRegistryAPI.com
- OpenCorporates API
- Kyckr
Each source supports only what its publisher says about its own product or data. Official descriptions do not establish comparative performance, and this site has run no benchmark. All sources
Continue reading
- What best company data means (Category guide)
- Freshness and as-of dates (Guide)
- Provenance (Definition)
- Testing accuracy on a sample (Guide)
How the related websites connect
This is one of 3 coordinated reference sites published by Coragrid. They cover neighbouring questions and feature the same product, so they are not independent endorsements of it or of each other.
Cite this entry
Best Company Data. “Provenance on every fact: what to ask for.” Content reviewed . https://bestcompanydata.com/provenance-on-every-fact