# France BODACC Monitor: Insolvency & Company Changes (`automatic/france-bodacc-monitor`) Actor

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.

- **URL**: https://apify.com/automatic/france-bodacc-monitor.md
- **Developed by:** [Philip Kirkbride](https://apify.com/automatic) (community)
- **Categories:** Business, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 notices

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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.

```json
{
  "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.

| Actor | Use when |
|---|---|
| **France BODACC Monitor (this Actor)** | French insolvency and company-change alerts |
| [France Company Registry](https://apify.com/automatic/france-company-registry-scraper) | French companies with legal notices |
| [Norway Company Registry](https://apify.com/automatic/norway-company-changes-monitor) | Norwegian companies and registry changes |
| [UK Companies House](https://apify.com/automatic/companies-house-scraper) | UK company profiles, officers and filings |
| [BORME Spain Corporate Acts](https://apify.com/automatic/borme-es-scraper) | Spanish incorporations, appointments and capital changes |
| [Sanctions & AML Screener](https://apify.com/automatic/opensanctions-screener) | Screen 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).

```json
{
  "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
}
```

| Input | What it does |
| --- | --- |
| `sirenNumbers` | Up to 2,000 companies: SIRENs with or without spaces, 14-digit SIRETs, FR VAT numbers, or Pappers, Societe.com and Annuaire des Entreprises links |
| `companyName` | Company-name keywords, e.g. `CANARDISES` |
| `eventFamilies` | One or more event families; empty means collective proceedings |
| `departments` | Department codes such as `75`, `13`, `2A`, `971`; empty means all of France |
| `publishedFrom`, `publishedTo` | Publication dates, inclusive, up to 31 days; empty means the last seven days |
| `onlyAdverse` | Deliver only notices flagged `isAdverse`; the rest are skipped and not charged |
| `includeDetails` | Judgment, description, management and filing details; on by default |
| `maxItems` | Notices 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.

```json
{
  "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 MB | Notices | Cost |
| --- | ---: | ---: |
| Console prefill | 10 | $0.055 |
| `{}` sample | 10 | $0.055 |
| Daily monitor of one department, nothing new | 0 | $0.005 |
| Daily monitor of one department, about 50 new notices | 50 | $0.255 |
| 1,000 notices in one run | 1,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](https://www.bodacc.fr/), published by DILA and reusable under the [Licence Ouverte 2.0](https://www.data.gouv.fr/dataservices/api-bulletin-officiel-des-annonces-civiles-et-commerciales-bodacc). 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 `ledgerName`s.
- 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.

# Actor input Schema

## `sirenNumbers` (type: `array`):

French companies, e.g. 503833162, 503 833 162, a 14-digit SIRET, an FR VAT number or a Pappers / Societe.com / Annuaire des Entreprises link. Up to 2,000; duplicates collapse and invalid entries are skipped with a note. Omit for a bounded family/date sample.

## `companyName` (type: `string`):

Source full-text company-name search, e.g. TAXI CAILLON. Combined with supplied SIRENs using AND. Omit or leave empty for the bounded sample.

## `eventFamilies` (type: `array`):

Native BODACC codes verified from source facets. OR within this list; AND with company, geography and date filters. Empty or omitted means collective proceedings.

## `departments` (type: `array`):

French department codes, e.g. 75, 69, 2A, 971 (1 is read as 01). OR within this list. An omitted or empty list selects all departments.

## `publishedFrom` (type: `string`):

Europe/Paris calendar date YYYY-MM-DD, e.g. 2026-11-07. Omit for six days before the end date. At most 31 days. For an ongoing monitor, omit both dates; a monitor with a start date also needs an end date.

## `publishedTo` (type: `string`):

Europe/Paris calendar date YYYY-MM-DD, e.g. 2026-11-13. Omit for today. Future dates are rejected.

## `maxItems` (type: `integer`):

1–5,000 notices. Omitted means 25, or 10 for the quick sample with no company, place or date filter. Monitor caps retain pending work for the next run.

## `includeDetails` (type: `boolean`):

Include judgment date, proceeding type and description, when available. Omitted means true. No documents are downloaded.

## `onlyAdverse` (type: `boolean`):

Deliver only notices flagged isAdverse: collective proceedings (insolvency), conciliation, deregistrations, and changes announcing dissolution or cessation of activity. Other notices are skipped and not charged. Example: true with eventFamilies collective, modification, radiation.

## `mode` (type: `string`):

full returns matching notices; monitor returns new or materially changed notices using a persistent named ledger. Omitted means full unless onlyNewSinceLastRun is true.

## `onlyNewSinceLastRun` (type: `boolean`):

true alone is an alias for mode: monitor. Conflicts with an explicit mode: full. Example: true with ledgerName: supplier-watch.

## `ledgerName` (type: `string`):

Delivery history name for a schedule, e.g. supplier-watch. Omitted means daily. Keep the same filters for one name; one run at a time per name. 1–64 printable characters.

## `bootstrapMode` (type: `string`):

emit delivers the initial bounded window. baseline stores inspected notices without delivery; maxItems bounds each baseline run. Monitor only for baseline.

## `overlapHours` (type: `integer`):

Rescan completed publication days covering at least this overlap; rounded up to whole Paris calendar days. Default 48; 24–168. Example: 72.

## `resetLedger` (type: `boolean`):

Explicitly discard this named ledger and its history, then inspect a new bounded window. Example: true after intentionally changing filters. Set back to false afterward. Corrupt ledgers require inspection or a new name.

## Actor input object example

```json
{
  "eventFamilies": [
    "collective"
  ],
  "maxItems": 10,
  "includeDetails": true
}
```

# Actor output Schema

## `notices` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "eventFamilies": [
        "collective"
    ],
    "maxItems": 10,
    "includeDetails": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("automatic/france-bodacc-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "eventFamilies": ["collective"],
    "maxItems": 10,
    "includeDetails": True,
}

# Run the Actor and wait for it to finish
run = client.actor("automatic/france-bodacc-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "eventFamilies": [
    "collective"
  ],
  "maxItems": 10,
  "includeDetails": true
}' |
apify call automatic/france-bodacc-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,automatic/france-bodacc-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/LboeO9Gy5EGs8KD9Q/builds/A1bpkLu1XzHBNeDxI/openapi.json
