Company monitoring FAQ: data, ownership and workflows

The relevant datasets include registry details, officers, shareholders, corporate linkage and financial records. Actual fields depend on the company and source. See the selected data dictionary.

The company dataset contains 340,299,683 records, including 199,453,702 active companies, across 195 countries and territories. The separate linkage dataset contains 40,210,132 records with a global ultimate ID. Explore the country tables.

No. The datasets have different scopes and are not additive. A corporate linkage count is not a count of unique groups or proof of complete ownership coverage.

No. The source may not disclose it, the dataset may not contain it or the latest retrieval may have failed. Missing fields should remain distinct from reported zero values.

A baseline is the first successful captured record for a dataset and company. Later compatible records can be compared against it to identify changes.

Checking frequency depends on the configured schedule and the relevant source. Recurring scheduling must be activated for your workspace; a monitoring setting alone is not proof that checks are running.

The filing date records when information was filed. Detection describes when your system observed it. An effective date, if supplied, may be different from both.

Keep the prior successful record and make the failure visible. A failed or incomplete retrieval should not be shown as an unchanged company. Read the monitoring guide.

Not necessarily. The meaning of a parent relationship depends on the dataset. A shareholder record describes an interest, while a parent field describes a position in a defined hierarchy.

No. It identifies a corporate entity in the group hierarchy. Identifying natural people behind ownership or control requires additional evidence.

No. Availability varies by country, company type, period and disclosure. Check the statement types and fields available for the specific entity.

Only when the entity, period, currency, units and reporting scope are compatible. Restatements or missing fields may require analyst review. See the financial statements guide.

With the AI connection configured, it prepares a draft summary and findings from captured company evidence. A reviewer should inspect the cited records, calculations and gaps before accepting a conclusion.

No. The website demonstrations use labelled illustrative companies and records. They explain the workflow and do not claim to be live customer research.

The workspace supports roles and assigned reviews. Each person also needs access to the Site. Adding an application role does not bypass the Site’s access controls.

The workspace has API keys and read-only MCP access for saved records. External clients require appropriate scopes, configuration and a permitted Site access path. This is not a promise that every external AI client is already connected.

Not by itself. Delivery requires a configured integration, the correct field mapping and confirmation from the receiving system. Keep the approval and delivery states separate.

Choose a representative company list, inspect coverage and define the decisions your reviewers need to make. Use the pilot worksheet to agree acceptance criteria before testing.