France BODACC Monitor: Insolvency & Company Changes avatar

France BODACC Monitor: Insolvency & Company Changes

Pricing

from $5.00 / 1,000 notices

Go to Apify Store
France BODACC Monitor: Insolvency & Company Changes

France BODACC Monitor: Insolvency & Company Changes

Know the day a French customer or supplier enters insolvency, changes management, moves or is struck off. Official BODACC notices by SIREN with risk flags, officers, address and capital. Schedule it: each run delivers only new notices, never repeats.

Pricing

from $5.00 / 1,000 notices

Rating

0.0

(0)

Developer

Philip Kirkbride

Philip Kirkbride

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Features

Limited permissions

Share

France BODACC Business Events Monitor

Know the day a French customer, supplier or borrower goes into insolvency, changes its management, moves its registered office, files its accounts or is struck off. This Actor turns France's official commercial gazette (BODACC) into one clean row per published notice, with the company's SIREN, the event, a risk flag and a link to the official notice.

Built for trade-credit, supplier-risk, KYB and corporate-finance teams who check the same companies every day:

  • Only what is new, every day. Schedule it with your list of up to 2,000 companies. Each run delivers only the notices you have not received yet, never the same notice twice.
  • Bad news stands out. Every row carries isAdverse and a riskSignal such as insolvency_opening, insolvency_conversion or deregistration, plus the proceeding (liquidation, receivership or safeguard) and the date payments stopped, when the court states it.
  • See what changed. Change notices list the officers who left or joined, the new registered office, the new share capital and what the change is about (changeTopics).
  • Amendments come back as updates. A corrected notice is linked to the one it corrects, and a notice the gazette edits later is delivered once more as changeType: "updated".
  • Quiet days cost almost nothing. A run with nothing new delivers zero rows and costs only the start fee.
  • Alerts where you work. Send each run's new notices to Slack, email or your own system with Apify integrations and webhooks.

Try it now: run it with {} for the 10 newest collective-proceeding notices (insolvencies, safeguard and liquidation judgments). The prefilled Console input does the same.

What you get

  • Every BODACC event family: collective proceedings (collective), company creations (creation), registrations (immatriculation), changes (modification), removals from the register (radiation), account filings (dpc), sales and transfers (vente), conciliation and more.
  • Company identity on every row: companyId (SIREN), companyName, tradeName, companyLegalForm, registeredAddress, city, postalCode, departmentCode, shareCapital and court.
  • Risk routing: isAdverse, riskSignal, insolvencyProceeding and cessationOfPaymentsDate for insolvency notices; dissolutions, cessations of activity and deregistrations are flagged too.
  • The legal substance: judgmentDate, proceedingType, eventSubtype and the published description.
  • Company changes: management (appointments and departures as published), changeTopics (management, registered office, capital, name, legal form, activity, dissolution and more), activity and activityStartDate.
  • Account filings: accountsClosingDate, accountsFilingType and accountsConfidential (filed with a confidentiality declaration).
  • Corrections you can trust: noticeType tells an original notice (annonce) from a correction (rectificatif) or a cancellation (annulation), and previousNoticeId links the notice it corrects.
  • Ready for your systems: stable noticeId, ISO dates, sourceUrl to the official notice, plus changeType, changedFields and idempotencyKey for scheduled feeds.

Output example

A real notice published on 2026-11-13: a liquidation opened by the Bourg-en-Bresse commercial court.

{
"noticeId": "A202602185114",
"companyId": "823261003",
"companyName": "BRESS'SNACK",
"tradeName": null,
"companyLegalForm": "Société à Responsabilité Limitée",
"eventFamily": "collective",
"eventFamilyLabel": "Procédures collectives",
"eventSubtype": "Jugement d'ouverture",
"noticeType": "annonce",
"isAdverse": true,
"riskSignal": "insolvency_opening",
"insolvencyProceeding": "liquidation",
"publicationSeries": "A",
"publicationDate": "2026-11-13",
"announcementNumber": 5114,
"court": "Greffe du Tribunal de Commerce de Bourg-en-Bresse",
"departmentCode": "01",
"city": "Bourg-en-Bresse",
"postalCode": "01000",
"registeredAddress": "49 b avenue Jean Jaurès, 01000 Bourg-en-Bresse",
"shareCapital": null,
"shareCapitalCurrency": null,
"activity": "toutes activités de restauration sur place et à emporter",
"judgmentDate": "2026-11-04",
"cessationOfPaymentsDate": "2026-08-31",
"proceedingType": "Jugement d'ouverture de liquidation judiciaire",
"description": "Jugement prononçant la liquidation judiciaire, date de cessation des paiements le 31 août 2026, désignant liquidateur Selarl Mj Synergie, Prise en la Personne de Me Desprat cs 30107 22 rue du Cordier 01003 Bourg-en-Bresse. Les déclarations des créances sont à adresser au liquidateur judiciaire ou sur le portail électronique prévu par les articles L. 814-2 et L. 814-13 du code de commerce dans les deux mois à compter de la présente publication.",
"management": null,
"changeTopics": null,
"activityStartDate": null,
"accountsClosingDate": null,
"accountsFilingType": null,
"accountsConfidential": null,
"previousNoticeId": null,
"sourceUrl": "https://www.bodacc.fr/pages/annonces-commerciales-detail/?q.id=id:A202602185114",
"country": "FR",
"sourceName": "BODACC — DILA",
"scrapedAt": "2026-11-14T23:38:31.767370Z",
"idempotencyKey": "44e32665ef13199c41d1b7beb5290ea4b61617d07debda6f58b404ce97c57b1a",
"changeType": "new",
"changedFields": []
}

Also available

The company registry suite: pick the job.

ActorUse when
France BODACC Monitor (this Actor)French insolvency and company-change alerts
France Company RegistryFrench companies with legal notices
Norway Company RegistryNorwegian companies and registry changes
UK Companies HouseUK company profiles, officers and filings
BORME Spain Corporate ActsSpanish incorporations, appointments and capital changes
Sanctions & AML ScreenerScreen names and wallets against sanctions lists

Choose your notices

Filter by company, event, place and date. Values inside one list are alternatives (OR); different filters combine (AND).

{
"sirenNumbers": ["503 833 162", "FR51440808947", "https://www.pappers.fr/entreprise/ramenshop-opera-952325439"],
"eventFamilies": ["collective", "radiation", "modification", "dpc"],
"publishedFrom": "2026-11-07",
"publishedTo": "2026-11-13",
"maxItems": 100
}
InputWhat it does
sirenNumbersUp to 2,000 companies: SIRENs with or without spaces, 14-digit SIRETs, FR VAT numbers, or Pappers, Societe.com and Annuaire des Entreprises links
companyNameCompany-name keywords, e.g. CANARDISES
eventFamiliesOne or more event families; empty means collective proceedings
departmentsDepartment codes such as 75, 13, 2A, 971; empty means all of France
publishedFrom, publishedToPublication dates, inclusive, up to 31 days; empty means the last seven days
onlyAdverseDeliver only notices flagged isAdverse; the rest are skipped and not charged
includeDetailsJudgment, description, management and filing details; on by default
maxItemsNotices per run, 1–5,000; 25 if empty (10 for the quick sample)

Empty fields behave as if you left them out. A mistyped company number is skipped with a note in the run status; unknown input fields are ignored and named. If nothing valid is left to search, such as reversed dates or only invalid company numbers, the run ends at once with a message naming the field, and nothing is charged beyond the start.

Watch companies on a schedule

Set onlyNewSinceLastRun to true and give the watch a name. Schedule it daily: the first run delivers the last seven days, and every later run delivers only new notices and genuine amendments to notices you already have.

{
"onlyNewSinceLastRun": true,
"ledgerName": "supplier-watch",
"sirenNumbers": ["503833162", "440808947"],
"eventFamilies": ["collective", "radiation", "modification", "dpc"],
"maxItems": 500
}
  • No repeats, no double charges: a notice you already received is never delivered again under the same ledgerName. An amended notice comes back once, as changeType: "updated" with the changed fields listed.
  • Nothing silently skipped: if a run stops at maxItems or at your spending limit, the next run picks up exactly where it stopped. Recent days are re-checked each run, so late notices and corrections still arrive.
  • Quiet days cost only the start fee: a run with nothing new delivers zero rows.
  • Only the bad news: add "onlyAdverse": true to a watch to receive insolvency, dissolution, cessation and deregistration notices only.
  • Prefer a silent first run? Set bootstrapMode to baseline to record the current notices without delivering them, then receive only what is published next.

Use one ledgerName per watch list and keep its filters the same. To change a watch, use a new name or set resetLedger to true once.

Get alerts in Slack, email or your own system

In Apify Console, open the schedule's Actor task, go to Integrations and connect Slack, email, Zapier, Make or a webhook to "run succeeded". Each daily run then pushes its new notices to you; idempotencyKey lets your system ignore any repeat.

Pricing

$0.005 per delivered notice ($5.00 per 1,000) plus $0.005 per run start. One result is one notice row in your dataset. Unchanged notices you already received, and notices that are not delivered, are not charged. The start fee is charged per GB of memory, with a minimum of one; the default 512 MB run is one start event.

Example at 512 MBNoticesCost
Console prefill10$0.055
{} sample10$0.055
Daily monitor of one department, nothing new0$0.005
Daily monitor of one department, about 50 new notices50$0.255
1,000 notices in one run1,000$5.005

Use maxItems and the run's spending limit to cap the cost. When the limit stops a run, the status says how many notices it allowed, and a scheduled watch delivers the rest next time.

Good to know

  • Data comes from BODACC, published by DILA and reusable under the Licence Ouverte 2.0. Missing values are null; coverage and detail vary by notice.
  • Only notices about legal entities are delivered. Notices naming individuals, such as sole traders (entrepreneurs individuels), are excluded for privacy, and the run status says how many were excluded. A watched SIREN that belongs to a sole trader returns no rows.
  • Contact emails and phone numbers in notice text are removed. Names of directors or court officers can appear in descriptions exactly as BODACC publishes them.
  • A notice that names several companies gives one row, for the company with the lowest SIREN.
  • An account-filing notice (dpc) records that accounts were filed; it does not contain the accounts. PDFs, financial statements and archive-wide backfills are not included.
  • Each run covers up to 31 days of publications and stops collecting after about four minutes; a scheduled watch continues from there next run. Very large one-off searches (thousands of SIRENs over a full month) are best split by date.
  • Late amendments are caught for recent days (two days by default, up to seven with overlapHours).
  • A watch keeps up to 10,000 notices from its recent days. Nationwide watches of very busy families, such as all account filings in France, exceed this: narrow them by department or company, or split them across several ledgerNames.
  • Only one run per ledgerName at a time. A second run that starts while the first is still working stops at once with a clear message and no charge beyond the start. After a crash, the name is free again within 15 minutes.
  • In the rare case a run is interrupted while saving rows, those notices are not re-sent (you are never charged twice); the next run lists their IDs in OUTPUT.previousRunInFlight.
  • The OUTPUT record of each run summarises what was delivered, what was unchanged and what is still pending.
  • isAdverse, riskSignal, insolvencyProceeding and changeTopics are read from the published wording of each notice. They help you route alerts; they are not a credit score. Notices whose wording is generic get insolvency_other.
  • management, registeredAddress and shareCapital are the values published in that notice; BODACC usually states the new value only, so keep your previous row to compare. Management text lists officers by name exactly as published.
  • There is no court or industry-sector filter: use departments and sirenNumbers to narrow a watch.
  • This is a data feed, not a credit opinion. Do not treat an absent notice as proof that a company is healthy.