Czech Insolvency Register / ISIR / Insolvenční rejstřík IČO

Monitor Czech companies in the ISIR insolvency register — the official insolvenční rejstřík at isir.justice.cz — by IČO, and get only the newly published insolvency events. Run it on a schedule for daily insolvency alerts on your debtors, clients, suppliers, or counterparties.

Sleduje český insolvenční rejstřík (ISIR) podle IČO a hlásí jen nové insolvenční události — ideální pro každodenní monitoring obchodních partnerů.

What does the Czech Insolvency Register Monitor do?

You give it a watchlist of Czech company IČO numbers. On every run it looks each company up in the official insolvenční rejstřík (ISIR) and returns the insolvency-proceeding events for those companies — the insolvency petition (insolvenční návrh), the decision on bankruptcy (úpadek), declared bankruptcy (konkurs), reorganization (reorganizace), published court documents, and more.

In its new-only mode it remembers what it already reported and returns only events that are new since the last run. That makes it a true change monitor for the Czech insolvency register, not a one-off export: schedule it daily and each run gives you just the fresh filings — ideal for credit-risk, receivables, factoring, legal, and compliance teams who need to know the moment a business partner enters insolvency.

• Official source, no API key required — reads the public ISIR register (insolvenční rejstřík) directly.
• Watchlist by IČO — track many companies (subjekty) in one run.
• New-events-only deduplication across scheduled runs.
• Built-in spend caps — hard per-run and per-proceeding limits so a big case can't surprise you with a large bill.
• No wasted cost — companies with no insolvency history return nothing and are not charged.

Why use it?

• Early warning on debtors. Learn about a customer's insolvency the day it is published in the insolvenční rejstřík, not when the receivable defaults.
• Portfolio monitoring. Watch an entire book of counterparties (podle IČO) with one scheduled Actor.
• Feed your systems. Push events straight into a spreadsheet, CRM, or database via the Apify API and integrations (Make, Zapier, webhooks, Slack, Google Drive…).
• Cheap and fast. Static HTML parsing (Cheerio) — see the pricing section.

How to use it

1. Open the Actor and go to the Input tab.
2. Paste your company IČO numbers into Company IČO watchlist (8 digits each).
3. Leave Mode on New events only (monitor) for alerts, or switch to All events (full snapshot) for a one-time export.
4. (Optional) Set Only events since (date) to backfill just a recent window on your first run instead of an entire multi-year proceeding.
5. Click Start. For daily alerts, open the Schedule tab and add a schedule (see below).

Input

Field	Key	Type	Default	Description
Company IČO watchlist	icoList	array of strings	– (required)	Czech company IČO numbers to monitor in the insolvency register.
Mode	mode	new-only | all	all	all returns every event (great for a first run); switch to new-only for scheduled monitoring — it returns only events unseen within the dedup window.
Dedup window (days)	dedupWindowDays	integer	30	In new-only mode, an event already reported within this many days is skipped and not charged.
Only events since (date)	sinceDate	string (ISO YYYY-MM-DD)	– (off)	Drop events published before this date before dedup and before charging. Use it to backfill a sensible window (e.g. last 90 days) on the first run.
Register sections	sections	array of A/B/C/D/P	["A","B"]	Which ISIR sections (oddíly) to include. A = up to bankruptcy (do úpadku), B = after bankruptcy (po úpadku), C = incidental disputes, D = other, P = creditor claims (přihlášky).
Max results (spend cap)	maxResults	integer	200	Hard cap on events returned and charged per run, so you control spend. At $4.00 / 1,000 events the default caps a run at ≈ $0.80. 0 = unlimited.
Max events per proceeding (spend cap)	maxEventsPerSubject	integer	50	Cap on events charged per single proceeding, so one large multi-year case can't consume the whole run budget and starve the rest of your watchlist. 0 = unlimited.
Dedup state store name	stateKvsName	string	isir-monitor-state	Named key-value store holding the "already-alerted" IDs between runs. Use different names to run independent watchlists on one account.
Proxy configuration	proxyConfiguration	object	proxy off	ISIR is public and works without a proxy; enable Apify Proxy only if you hit rate limits.

Example input

{
    "icoList": ["25083325", "26863154"],
    "mode": "new-only",
    "sections": ["A", "B"],
    "sinceDate": "2024-01-01",
    "dedupWindowDays": 30,
    "maxResults": 200,
    "maxEventsPerSubject": 50
}

Output

Each pushed item is a single insolvency event. You can download the dataset in JSON, CSV, Excel, HTML, or XML, or fetch it via the API.

Output fields

Field	Description
ico	Company IČO the event belongs to.
nazev	Debtor name (název) as recorded in ISIR.
spisovaZnacka	Case reference (spisová značka), e.g. KSOS 25 INS 10525 / 2016.
court	Court conducting the proceeding (soud).
stavRizeni	Current state of the proceeding (stav řízení), e.g. Povolena reorganizace.
section	ISIR section (oddíl): A, B, C, D, or P.
datePublished	When the event was published in ISIR (local time).
popis	Event description (in Czech, as published).
idUdalosti	Event ID within the proceeding.
documentUrl	Direct link to the published PDF document, when available.
datumPravniMoci	Date the document became legally effective (nabytí právní moci), when available.
detailUrl	Link to the full proceeding on isir.justice.cz.
scrapedAt	ISO timestamp of the run.

Example output records

The insolvency petition (insolvenční návrh) that opened the OKD reorganization — a real record from a run:

{
    "ico": "26863154",
    "nazev": "Správa pohledávek OKD, a.s.",
    "spisovaZnacka": "KSOS 25 INS 10525 / 2016",
    "court": "Krajského soudu v Ostravě",
    "stavRizeni": "Povolena reorganizace",
    "section": "A",
    "datePublished": "2016-05-03T14:32",
    "popis": "Insolvenční návrh spojený s návrhem na povolení reorganizace",
    "idUdalosti": "I_7",
    "documentUrl": "https://isir.justice.cz/isir/doc/dokument.PDF?id=23076275",
    "datumPravniMoci": null,
    "detailUrl": "https://isir.justice.cz/isir/ueu/evidence_upadcu_detail.do?id=3BD92F3EAA724B37ACCEDD86B31BE055",
    "scrapedAt": "2026-08-24T12:20:26.238Z"
}

A later section-B ruling from the same proceeding, showing a populated datumPravniMoci:

{
    "ico": "26863154",
    "nazev": "Správa pohledávek OKD, a.s.",
    "spisovaZnacka": "KSOS 25 INS 10525 / 2016",
    "court": "Krajského soudu v Ostravě",
    "stavRizeni": "Povolena reorganizace",
    "section": "B",
    "datePublished": "2016-05-11T11:05",
    "popis": "Usnesení o vydání předběžného opatření",
    "idUdalosti": "I_85",
    "documentUrl": "https://isir.justice.cz/isir/doc/dokument.PDF?id=23383505",
    "datumPravniMoci": "2016-06-08",
    "detailUrl": "https://isir.justice.cz/isir/ueu/evidence_upadcu_detail.do?id=3BD92F3EAA724B37ACCEDD86B31BE055",
    "scrapedAt": "2026-08-24T12:20:26.238Z"
}

Pricing

This Actor uses pay-per-event pricing: you are charged only for each new insolvency event returned.

What you pay for	Price
Each insolvency event returned	$0.004 per event ($4.00 per 1,000 events)

Because it monitors changes, healthy companies on your watchlist cost effectively nothing — no insolvency record means no events and no per-event charge. A typical daily run over a watchlist yields only the handful of genuinely new filings, so ongoing monitoring stays cheap. The built-in Max results and Max events per proceeding caps mean a first run — or a single huge historical case — can never bill more than you expect. Underlying platform compute is minimal: a run producing 1,000 events uses about 0.0023 compute units.

Run it on a schedule (recommended)

Scheduled monitoring is the whole point — this Actor is designed to be run daily so each run reports only what changed:

1. Open the Actor's Schedule tab (or Schedules in the Console).
2. Create a schedule, e.g. every day at 07:00, pointing at this Actor with your saved input.
3. Add a notification: connect a webhook, Slack, email, or Make/Zapier integration so new events reach your inbox or systems automatically.

Keep Mode on new-only and set Dedup window (days) to at least your schedule interval (30 days is a safe default). The dedup state persists between scheduled runs, so you never get the same alert twice. On the first run, set Only events since (date) to backfill just a recent window instead of an entire proceeding's history.

FAQ & notes

• Where does the data come from? The public ISIR insolvency register (insolvenční rejstřík) at isir.justice.cz. This Actor only reads publicly available register data.
• Which sections should I monitor? A (proceedings up to bankruptcy / do úpadku) and B (after bankruptcy / po úpadku) cover what most creditors care about. Section P (creditor claims / přihlášky pohledávek) can be very large; enable it only if you need it — and note the per-proceeding cap.
• How do I avoid a big first bill? Leave the Max results and Max events per proceeding caps in place, and use Only events since (date) to limit history on the first run.
• Do I need a proxy? No. ISIR is public; leave the proxy off unless you monitor very large watchlists and hit rate limits.
• Feedback / bugs? Use the Issues tab on the Actor page.

Disclaimer: this Actor extracts publicly available information from the official Czech insolvency register (ISIR / insolvenční rejstřík) for legitimate monitoring purposes. You are responsible for using the data in compliance with applicable law.