Poland KRS Financial Statements Scraper avatar

Poland KRS Financial Statements Scraper

Pricing

from $8.00 / 1,000 financial statement records

Go to Apify Store
Poland KRS Financial Statements Scraper

Poland KRS Financial Statements Scraper

Retrieve Polish KRS financial-document metadata, reporting periods, standardized financial fields, company identifiers, and optional source files directly from the official KRS document repository.

Pricing

from $8.00 / 1,000 financial statement records

Rating

0.0

(0)

Developer

Muhammad Afzal

Muhammad Afzal

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Free plan limit: Free-plan users can receive up to 5 result records per run. Paid-plan users retain the Actor's existing limits.

Retrieve structured records for annual financial statements and related corporate documents filed in Poland's National Court Register (Krajowy Rejestr Sądowy — KRS). The Actor scrapes directly from the official Ministry of Justice Financial Documents Repository (rdf-przegladarka.ms.gov.pl), enriched with company master data (legal name, NIP, REGON) from the official public KRS API (api-krs.ms.gov.pl).

No external API key or third-party paid subscription is required.

Features

  • Direct official repository scraping: Scrapes public corporate filings directly from rdf-przegladarka.ms.gov.pl.
  • Automatic KRS company enrichment: Fetches official legal name, NIP, and REGON from api-krs.ms.gov.pl.
  • Standardized XML financial figures: Extracts balance sheet and profit & loss figures (total assets, equity, net revenue, net profit/loss, operating profit/loss) directly from filed XML statements.
  • Source document downloading: Optionally saves source files (XML, PDF, XHTML) directly to your run Key-Value store.
  • Pay-per-event pricing: Transparent billing with tiered discounts and zero platform usage pass-through fees.

Input

  • krsNumbers: Array of 1 to 50 KRS numbers. Values may contain spaces or omit leading zeroes; each is normalized to 10 digits.
  • fromYear / toYear: Inclusive major reporting-year window (e.g. 2023 to 2025).
  • documentTypes: Document type values to keep (e.g. financial_statement, approval_resolution, activity_report, audit_report). Leave empty to include all filed documents.
  • includeStandardizedFields: Extract normalized balance-sheet and profit-and-loss values when filed XML is present (default: true).
  • includeExtractedFields: Extract all raw flattened XML tags. Enable only when exhaustive XML field mappings are required (default: false).
  • downloadFormat: Optionally save document files to the key-value store (none, original, pdf, html, all).
  • maxResults: Total document records across all companies (default: 100, max: 5,000).

Example:

{
"krsNumbers": ["0000028860", "0000005239"],
"fromYear": 2023,
"toYear": 2025,
"documentTypes": ["financial_statement"],
"includeStandardizedFields": true,
"includeExtractedFields": false,
"downloadFormat": "none",
"maxResults": 100
}

Output

Each dataset item represents one validated financial document record:

  • recordId: Unique record identifier (e.g. 0000028860-1234567).
  • krs, nip, regon: Official company identifiers.
  • companyName: Full legal name from KRS.
  • documentType: Normalized document classification (financial_statement, approval_resolution, activity_report, etc.).
  • periodMajorYear: Financial reporting year (e.g. 2023).
  • periodFromDate / periodToDate: Full reporting period dates.
  • filingDate / preparationDate: Official submission and preparation timestamps.
  • isCorrection / isIasCompliant: Correction and IAS/IFRS compliance flags.
  • standardizedFields: Normalized financial metrics (totalAssets, totalEquity, netRevenue, netProfitLoss, operatingProfitLoss).
  • savedFiles: Keys of files stored in the run Key-Value store.
  • source: "Official KRS Document Repository (RDF)".
  • sourceUrl: Link to the repository search page.
  • scrapedAt: ISO 8601 scraping timestamp.

The run summary and diagnostics are saved in OUTPUT in the default Key-Value store.

Pricing

This Actor uses Pay-Per-Event (PPE) pricing with volume-based discount tiers:

EventDescriptionFREE TierBRONZE (2.5% off)SILVER (5% off)GOLD (20% off)
apify-actor-startActor start (one-time synthetic initialization)$0.005$0.005$0.005$0.005
financial-statement-recordOne validated financial-document record in default dataset$0.010$0.00975$0.0095$0.008
document-fileOne saved document file (PDF, XML, XHTML) in Key-Value store$0.005$0.004875$0.00475$0.004

Platform compute and proxy costs are bundled into event prices; platform-usage pass-through is disabled (isPPEPlatformUsagePaidByUser = false).

Cost Examples

  • 10 company statements (metadata & standardized figures, no files): $0.005 (start) + 10 × $0.010 = $0.105
  • 50 company statements with original PDF downloads: $0.005 (start) + 50 × $0.010 + 50 × $0.005 = $0.755

Local Development & Testing

npm ci
npm test
npm run preflight
apify run -p