Filings

get_financials

Annual-accounts filings for a company, normalised with period_end + document_id + source_url.

Convenience wrapper over list_filings(category='accounts'). Normalises the fiscal-period shape across registries, pre-computes download URLs, and returns period_end as the primary sort key. Good for 'pull the last 3 years of accounts'.

Parameters

NameTypeRequiredDescription
jurisdictionstringyesISO code. Currently: GB, FI, NL, KR.
company_idstringyesRegistry ID.
yearintegernoCalendar year of period_end.
period_endstringnoYYYY-MM-DD - pinpoint one period.

Supported jurisdictions (6)

Related tools

Frequently asked questions

How is this different from list_filings(category='accounts')?

Same source data, ergonomic differences. get_financials normalizes period_end across registries (so you can sort / filter on fiscal year), pre-computes source_url, and sorts by period_end DESC instead of filing_date. Use this when 'pull the last 3 years' is the question.

What format does fetch_document return for these?

Depends on the registry and the company size. GB: iXBRL (application/xhtml+xml) for medium and large, PDF or simplified XBRL for micro and small. FI: iXBRL across the board (mandatory since 2020). NL: XBRL only, no PDF. KR: PDF-only annual audit reports.

Do I get parsed numbers (revenue, profit) directly?

No — this returns the filing pointer (document_id, period_end, format). To extract figures, fetch_document then parse the XBRL / iXBRL. The XBRL tags follow IFRS or US-GAAP taxonomies depending on the company. Live case study at /docs/case-studies walks an iXBRL parse.

What's the relationship between period_end and period_start?

period_end is the fiscal year-end (always present). period_start is the start of the period (present where the registry captures it, often inferred to 365 days back if not). For abbreviated short / long accounting periods, period_start is the authoritative start — don't assume 365 days back.

Why doesn't year filter work as I expect?

year filters on period_end, not filing_date. A FY2023 annual report (period_end 2023-12-31) might have been filed in October 2024 — passing year=2024 misses it. Always think in fiscal-period-end terms when querying.

Consolidated vs unconsolidated?

Each filing returns a single set of accounts as the company filed them. Whether they are consolidated depends on the company (groups file consolidated, standalones don't). The XBRL document itself contains the disclosure under the typical taxonomy elements. Some companies file BOTH (separate consolidated and standalone filings on the same period) — both will appear.

What currency are the figures in?

Whatever the company reports in — typically the company's functional currency declared on the front of the accounts. GB filings declare currency in the iXBRL header (xbrli:unit). Cross-currency comparisons require explicit FX conversion you'd source elsewhere.

Why no accounts before YYYY?

Electronic filing mandates kick in at different dates. GB: 2001 forward. FI: 2014 forward. NL: 2012 forward. KR: 1999 forward via DART. Pre-mandate accounts may exist on paper but not via the API.

Late filings / overdue?

Late filings still appear once filed. To detect 'overdue' check get_company_profile.jurisdiction_data.accounts.next_due (GB) against today. Accounts more than 12 months overdue typically correlate with imminent dissolution proceedings.

Why does Germany not work?

DE annual accounts are filed at the Bundesanzeiger, not the Handelsregister. There is no free machine-readable feed for the Bundesanzeiger accounts dataset, so it is not part of the DE surface.