Poland KRZ National Debtor Registry Scraper

🔎 Search Poland’s public KRZ with structured output

For compliance teams, legal researchers, finance teams, and developers, Poland KRZ Registry searches the public Krajowy Rejestr Zadłużonych (KRZ) and returns available names, identifiers, proceedings, statuses, courts, dates, announcements, estate assets, advisor contacts, and official source links. Screen a list of the same kind of subject or retrieve a specific case-related entry without supplying a KRZ account, cookie, or API key.

• Run a KRZ company search by name, KRS, NIP, or REGON for counterparty screening.
• Perform a KRZ person lookup by PESEL or NIP while keeping submitted PESEL values out of output.
• Complete a Poland debtor registry check for sole traders by name, NIP, REGON, or PESEL.
• Use KRZ court case search to find public case context from a complete case signature.
• Run a KRZ proceeding lookup by an exact proceeding identifier.
• Perform a KRZ court announcements search by date range, case signature, or proceeding identifier.
• Run a KRZ company partner search by personal-company name, KRS, NIP, or REGON.
• Use a bankruptcy estate asset search to retrieve public inventory status, asset descriptions, and valuations.
• Run a restructuring advisor search by name, licence number, or city.

📦 Data returned

Choose one Target per run. Depending on that Target, each successful match can include:

• registered names and available KRS, NIP, or REGON identifiers;
• proceeding ID, case signature, type, status, role, court, and opening or closing dates;
• proceeding summaries attached to matched companies, people, and sole traders;
• announcement ID, date, title, content, case context, and court;
• company and partner names, identifiers, partner type, and role;
• estate inventory status plus asset category, description, quantity, valuation, currency, and status;
• advisor name, licence number, city, address, phone, and email;
• checkNumber, queryComplete, rowType, and sourceUrl on every row.

queryComplete: false means KRZ capped the source query or the requested advisor limit was reached before all source matches were delivered. Do not treat it as a complete absence check. For estate inventories, confirmedAbsent means the public registry positively reported no inventory; retrieval failures are not reported this way.

A PESEL supplied for a check is never included in dataset rows or public logs.

▶️ Running the Actor

1. Choose one Target.
2. Fill in the criteria shown for that Target.
3. Set Maximum results per check to bound delivered matches and cost.
4. Start the Actor and open the default dataset.

A run can process multiple checks of the same kind. Run separately configured registry areas in separate runs. Public KRZ coverage begins on 1 December 2021.

⚙️ Input

The Target determines which fields are used:

• companies: companyQueries
• persons: personQueries
• soleTraders: traderQueries
• courtCases: caseSignatures
• proceedings: proceedingIds
• announcements: announcementFrom, announcementTo, optional announcementQueries, announcementCaseSignatures, and announcementProceedingIds
• partners: partnerCompanies
• estateAssets: assetSubjects, assetProceedingIds, assetCaseSignatures, and optional assetType
• advisors: advisorQueries and optional advisorCity

maxResults applies per submitted check or announcement search. Inputs belonging to inactive Targets are ignored.

Example company input:

{
  "target": "companies",
  "companyQueries": ["ORLEN", "KRS:0000304735"],
  "maxResults": 25
}

Natural-person criteria must be an 11-digit value prefixed with PESEL: or a 10-digit value prefixed with NIP:. Names are not supported for that Target.

🧾 Output

Successful matches are written to the default dataset. The exact row shape depends on rowType. A company row can look like this:

{
  "rowType": "company",
  "checkNumber": 1,
  "queryComplete": true,
  "name": "Example Sp. z o.o.",
  "nip": "5250001009",
  "krs": "0000123456",
  "regon": "012345678",
  "proceedings": [
    {
      "proceedingId": "example-proceeding-id",
      "caseSignature": "WA1M/GUp/12/2024",
      "status": "open",
      "court": "District Court in Warsaw",
      "openingDate": "2024-05-10"
    }
  ],
  "sourceUrl": "https://krz.ms.gov.pl/"
}

This is an illustrative schema-conforming example, not a statement about a real company. Empty checks and failures do not create dataset rows. Export saved rows through Apify as JSON, CSV, Excel, XML, RSS, or HTML.

💳 Pricing

The Actor uses pay-per-event pricing. You are charged once for each successful final public KRZ match delivered to the default dataset. Empty checks, retries, failures, and internal detail requests are not charged as matches. Use maxResults to bound the number of delivered matches for each check.

🔌 Integrations

Run the Actor through the Apify API, schedule repeat runs, or send dataset output to another system with webhooks and Apify integrations. Scheduling does not turn the Actor into a watchlist or change detector; compare outputs in your own workflow when you need change monitoring.

❓ FAQ

Can I search a natural person by name?

No. The public person Target requires either an 11-digit PESEL or a 10-digit NIP. The identifier is used for the source request; submitted PESEL values are not exported.

Does a zero-row run prove that a subject has no debt?

No. It means the completed search in the selected public KRZ area returned no match. It is not a credit score, solvency conclusion, KYC/AML decision, or legal advice.

What does an incomplete query mean?

A false queryComplete value means a source or requested limit was reached before the Actor could represent the search as complete. Narrow the search criteria or review a higher result limit where appropriate.

Does it access all Polish debtor history?

No. The Actor covers the public KRZ period beginning 1 December 2021. It does not add earlier history or data from private debtor databases.

Do I need KRZ credentials?

No user-supplied credentials are required. The Actor accesses only public KRZ material and does not retrieve authenticated or private content.

Can one run search several registry areas?

No. Choose one Target per run. You can submit multiple same-kind checks in that run, then launch separate runs for other Targets.

Can the Actor monitor subjects or provide alerts?

It does not maintain watchlists or detect changes. Use Apify schedules, webhooks, and your own comparison logic around separate runs.

📝 Changelog

• 0.1: Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

🔗 Related Actors

• GLEIF LEI Lookup — enrich counterparties with public Legal Entity Identifier, registration, address, and parent relationship data.
• Pappers Sirene Scraper — search and enrich French companies with SIREN/SIRET identifiers and official registry data.

Made with ❤️ by Maxime Dupré