Data provenance

Sources and identifiers

The engine collects data from multiple public, regulatory, and market sources. Financial statements include ESEF/XBRL filings and SEC disclosures for supported cross-listed issuers; other datasets have their own source coverage.

Use the returned source, company identifier, report_period, and currency to keep a result attached to its context. Fields and source links differ across datasets.

Verify a number

1. Resolve the company using its ticker, ISIN, or LEI.
2. Check the reporting period and statement currency.
3. Preserve the source and filing date when returned.
4. Follow a source document URL when available and compare the relevant line item.
5. Keep missing values as missing and identify any currency conversion you requested.

Check freshness

The get_data_freshness tool reports per-source recency and status. Use it to distinguish a current source, a stale dataset, and an ingestion error.

get_data_freshness(stale_only=true)

Inspect automatically_refreshed, refresh_job_status, refresh_blocked_reason, last_success_at, latest_data_date, freshness_state and filing_backlog. A successful scheduled run does not prove exhaustive discovery or that a newer report exists.

The profile configured on 6 October 2026 contains 75 bounded jobs: all 27 ESEF countries, ECB rates, official regulatory disclosures, GLEIF/ESMA work, and macro, insurance and ownership registers. Country imports process up to 25 reports from three index pages per run; new reports take priority over historical catch-up. Per-report checkpoints advance segment, APM and KPI extraction. Check actual job outcomes: a scheduled source may still be pending or failed. Prices and other feeds requiring permission or credentials remain skipped.

A financial reporting period, filing publication date, ingestion time, and request time describe different events. Keep those distinctions in your analysis.