getregdata
Home / Blog / Article
Article · 2026-11-01

How to monitor French company insolvencies (procédures collectives) in BODACC

france · insolvency · bodacc · credit risk · kyb · 12 min read

Every French insolvency judgment - sauvegarde, redressement judiciaire, liquidation judiciaire, plans and closures - is published in BODACC, the official bulletin run by DILA, and BODACC data is free to search and free to download as open data. To check one company, search its 9-digit SIREN on bodacc.fr and read the “Procédures collectives” notices. To monitor a portfolio, run the same SIREN check on a schedule and alert on any notice you have not seen before. The France Insolvency Check actor does that and returns one JSON row per judgment.

This guide covers what BODACC publishes, how to check a company by hand, what the free open-data API gives you, and how to set up a weekly watchlist with code you can copy.

What BODACC is and what it covers

BODACC (Bulletin officiel des annonces civiles et commerciales) is the official French bulletin for legal notices about businesses. It is published by DILA (Direction de l’information légale et administrative), the government body that also publishes the Journal officiel. Commercial court registries send it the notices they are required to publish: registrations, changes, removals, filed accounts, and the one this guide is about, procédures collectives (collective insolvency proceedings).

French insolvency law, in Book VI of the Code de commerce, has three main proceedings:

ProceedingWhat it means for a counterparty
SauvegardeThe company asked for court protection before it stopped paying. It keeps trading while a plan is prepared.
Redressement judiciaireThe company has stopped paying its debts (cessation des paiements) and the court looks for a recovery plan or a sale.
Liquidation judiciaireRecovery is not possible. The business is wound up and its assets are sold.

The court also issues other judgments in a proceeding: conversion of a redressement into a liquidation, approval of a continuation or sale plan, changes to a plan, and closure of the proceeding (often for lack of assets). Each is published as a separate BODACC notice, so a company’s insolvency history in BODACC is a sequence of notices read in order.

There are two practical reasons to watch BODACC rather than wait for news:

  • Claim deadlines run from the BODACC notice. Creditors have two months from the publication of the opening judgment in BODACC to declare their claims to the court-appointed representative (four months for creditors based outside metropolitan France). If a customer who owes you money enters redressement and you learn about it three months later, you have missed the deadline.
  • It is the primary source. Commercial databases that show a “procédure collective” flag get it from these notices. Reading BODACC directly removes that step and its lag.

BODACC covers companies and individual traders (commerçants, artisans, entrepreneurs individuels) registered in France. It does not cover personal over-indebtedness cases (surendettement), which go through a separate consumer procedure.

The manual way: bodacc.fr

For a single company, the free official site is enough.

  1. Get the company’s SIREN (9 digits). If you have a SIRET (14 digits, one per establishment), the first 9 digits are the SIREN.
  2. Go to bodacc.fr and open the search for commercial notices (annonces commerciales).
  3. Enter the SIREN and limit the notice type to “Procédures collectives”.
  4. Read the results from newest to oldest. Each notice names the court, the judgment (“Jugement d’ouverture d’une procédure de redressement judiciaire”, “Jugement de clôture pour insuffisance d’actif”), the judgment date, and the names of the court-appointed administrators or liquidators.

No result means BODACC holds no published insolvency judgment for that SIREN. That is a meaningful answer, but only for the period the search covers (see the limits section).

The manual check stops working when:

  • you have more than a handful of companies and need to repeat the check every week;
  • you need the answer inside another system (an onboarding flow, a CRM, a credit-limit tool) rather than on a screen;
  • the people reading the result do not read French legal wording. “Jugement arrêtant le plan de cession” and “Jugement prononçant la résolution du plan” need translating before a credit analyst can act on them.

The free open-data API

BODACC is also published as open data under the Licence Ouverte 2.0 (Etalab), on data.gouv.fr and through an Opendatasoft API at bodacc-datadila.opendatasoft.com (dataset annonces-commerciales). It needs no key and costs nothing. For a developer who wants raw notices, it is the place to start, and worth knowing about before paying for anything.

It returns the notice as published: one record per BODACC announcement, across all notice families, with the judgment details as French text and several sub-fields packed as text inside the record. To turn that into a yes/no insolvency check you have to filter to collective proceedings, match the SIREN, tell real judgments apart from procedural filings published in the same section, handle corrections and cancellations, map dozens of judgment wordings to something your system understands, and schedule and diff the whole thing yourself.

The actor does that work. For ten checks a year, bodacc.fr is enough. For a monitoring pipeline without a BODACC parser to maintain, use the actor described below.

The automated way: France Insolvency Check on Apify

The France Insolvency Check (BODACC) actor takes SIRENs, SIRETs or names and returns one structured record per insolvency judgment, newest first. Compared with the raw notices, it:

  • validates each SIREN and SIRET with its check digit, and reduces a SIRET to its SIREN;
  • sorts every judgment into one of five eventType values, so you can filter without reading French;
  • keeps only judgments: procedural filings inside an existing proceeding (claims lists, distribution plans), sanctions against directors (management bans, personal bankruptcy) and cancelled notices are left out;
  • marks corrected notices (isCorrection: true) and says which notice they replace;
  • accepts a watchlist of up to 100 mixed SIRENs and names per run;
  • writes a machine-readable outcome for every entry, so “no proceeding found” is never confused with “not checked”.

It needs no login and no BODACC account. The field list is also on our site: France insolvency check (BODACC).

Input

Check one company by SIREN, the most precise check:

{ "siren": ["345086177"] }

Monitor a list. Entries of 9 or 14 digits are treated as identifiers, anything else as a name. Spaces inside numbers are fine:

{
  "watchlist": ["345086177", "542 051 180", "552032534"],
  "dateFrom": "2026-10-01"
}

The input fields:

FieldTypeWhat it does
sirenarraySIREN (9 digits) or SIRET (14 digits), up to 100
namestringCompany or trader name, word search on the debtor name. Ignored when watchlist is set
watchlistarrayUp to 100 entries, numbers and names mixed
exactMatchbooleanFor names: keep only debtors whose name equals the query, ignoring case, accents and punctuation
dateFrom / dateTostringPublication date window, YYYY-MM-DD. Empty means the full history
maxResultsintegerMost judgments per SIREN or name. Defaults: 100 per SIREN, 20 per name

Output

One record per judgment. This is the conversion of Camaïeu International into liquidation in 2021:

{
  "matchedQuery": "345086177",
  "publicationDate": "2021-04-25",
  "caseNumber": null,
  "court": "Tribunal de Commerce de Lille Métropole",
  "debtorName": "CAMAIEU INTERNATIONAL",
  "debtorType": "company",
  "siren": "345086177",
  "legalForm": "Société par actions simplifiée",
  "seat": "59100 Roubaix",
  "eventType": "bankruptcy_opened",
  "judgmentNature": "Jugement de conversion en liquidation judiciaire",
  "judgmentDate": "2021-04-14",
  "judgmentText": "Jugement de conversion en liquidation judiciaire désignant liquidateur ...",
  "noticeId": "A202100812603",
  "isCorrection": false,
  "correctsNoticeId": null,
  "sourceUrl": "https://www.bodacc.fr/pages/annonces-commerciales-detail/?q.id=id:A202100812603",
  "source": "BODACC (DILA), Licence Ouverte 2.0",
  "retrievedAt": "2026-10-31T00:00:00.000Z"
}

The main fields:

  • eventType - the decision in five values:
eventTypeMeaning
bankruptcy_openedLiquidation judiciaire opened, or a proceeding converted into liquidation
restructuring_openedRedressement judiciaire or sauvegarde opened
plan_confirmedThe court approved a continuation, restructuring or sale plan
proceeding_closedThe proceeding was closed, for example for lack of assets
otherAny other judgment in the proceeding: plan changes, a new payment-stop date, orders
  • judgmentNature and judgmentText - the original French wording, kept for audit and for cases where you need the detail (names of the liquidator, the payment-stop date, the claims deadline).
  • judgmentDate vs publicationDate - the court decides first, BODACC publishes later. Use publicationDate for “what is new since my last run” and judgmentDate for “when did this happen”.
  • debtorType - company or individual (sole traders).
  • noticeId - BODACC’s own id for the notice. Use it as the unique key when you store results.
  • sourceUrl - the notice on bodacc.fr, so a person can open the official text.

Each run also stores an OUTCOME record in its key-value store. It has a queries list with one entry per input, each with an outcome of results, no_match, not_checked or invalid_input. results entries carry complete: false when more judgments existed than maxResults allowed.

Code

JavaScript

npm install apify-client
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });

const run = await client.actor('regdata/france-insolvency-scraper').call({
    siren: ['345086177'],
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
for (const j of items) {
    console.log(j.judgmentDate, j.eventType, j.judgmentNature, j.court);
}

// Per-entry outcome: results, no_match, not_checked or invalid_input
const outcome = await client.keyValueStore(run.defaultKeyValueStoreId).getRecord('OUTCOME');
console.log(outcome.value.queries);

Python

pip install apify-client
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])

run = client.actor("regdata/france-insolvency-scraper").call(
    run_input={"siren": ["345086177"]}
)

for j in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(j["judgmentDate"], j["eventType"], j["judgmentNature"], j["court"])

outcome = client.key_value_store(run["defaultKeyValueStoreId"]).get_record("OUTCOME")
print(outcome["value"]["queries"])

Worked example: a weekly watchlist for a credit team

Say you sell on 30-day terms to 250 French business customers and want to know within a week if one of them enters a proceeding.

1. Build the list from SIRENs, not names. Your ERP probably holds a SIRET or a VAT number. The French VAT number (FR + 2-digit key + SIREN) contains the SIREN in its last 9 digits. Names are a fallback: “Martin” matches thousands of unrelated debtors.

2. Split into runs of up to 100. 250 customers means three watchlist runs. On Apify you can save each as a task with its own input and schedule all three for Monday morning.

3. Ask only for recent notices. A weekly job does not need 2008. Pass a dateFrom about two weeks back, so a notice published late in the window is not missed, and drop the duplicates by noticeId:

import os, datetime
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
seen = load_seen_notice_ids()           # your storage: a table, a file, a sheet
since = (datetime.date.today() - datetime.timedelta(days=14)).isoformat()

for batch in chunks(customer_sirens, 100):    # your helper: lists of up to 100
    run = client.actor("regdata/france-insolvency-scraper").call(
        run_input={"watchlist": batch, "dateFrom": since}
    )
    for j in client.dataset(run["defaultDatasetId"]).iterate_items():
        if j["noticeId"] in seen:
            continue
        seen.add(j["noticeId"])
        if j["eventType"] in ("bankruptcy_opened", "restructuring_opened"):
            alert_credit_team(j)        # stop deliveries, file the claim
        else:
            log_for_review(j)

    queries = client.key_value_store(run["defaultKeyValueStoreId"]) \
                    .get_record("OUTCOME")["value"]["queries"]
    retry = [q["query"] for q in queries if q["outcome"] == "not_checked"]
    if retry:
        schedule_retry(retry)

save_seen_notice_ids(seen)

4. Route by event type. An opening (restructuring_opened, bankruptcy_opened) is the urgent one: stop shipping on credit, and get the claim to the court-appointed representative within the two-month window. A plan_confirmed tells you the payment schedule your claim will follow. A proceeding_closed after a liquidation usually means the company is gone and the account can be written off.

5. Treat not_checked as unknown. An entry BODACC did not answer is reported as not_checked, not as clean, and is not charged. Re-run those entries; do not mark the customer as clear.

The same pattern works in n8n or Make: a weekly trigger, the Apify node (in n8n, the official community node @apify/n8n-nodes-apify) running the actor with your watchlist, a filter on eventType, and a Slack or e-mail step. The dedupe on noticeId can live in a Google Sheet or a small database table.

For onboarding a new customer, run a single SIREN check with no dateFrom. That returns the full history since 2008: a company that went through a redressement and is now executing a plan is a different risk from one with no history at all.

How to read results, and the limits

Rows for a SIREN mean the company has been through, or is in, a collective proceeding. Read the sequence from newest to oldest. A proceeding_closed after a bankruptcy_opened usually means the company was liquidated. A proceeding_closed after a plan_confirmed usually means the plan was completed. A plan_confirmed alone means the company is trading under court supervision and repaying old debts on a schedule.

No rows means BODACC holds no published insolvency judgment for that SIREN in the window searched. It does not mean the company is healthy: BODACC only knows about proceedings a court has opened. Late payments, tax debts and a weak balance sheet do not appear here.

Other limits, all at the data level:

  • Coverage starts in January 2008. Proceedings published before that are not in BODACC’s open data, so a clean answer says nothing about earlier years.
  • Publication lags the judgment, usually by one to two weeks. A company placed in liquidation on Monday will not show up on Tuesday.
  • The case number (N° RG) is rarely published. caseNumber is null in most rows. Use noticeId and sourceUrl as references.
  • Old judgment dates can be text. Some older notices write the judgment date out in French words, and judgmentDate then keeps that text.
  • Name search matches words. “Dupont Distribution” returns every debtor with those words in its name. Use exactMatch: true, or better, the SIREN. A name query also returns only the 20 newest judgments by default; when more exist, the outcome says complete: false.
  • A new SIREN is a new company. If a business was sold out of liquidation to a buyer, the buyer usually trades under a different SIREN with no history. Checking the old SIREN tells you about the old legal entity only.
  • Sole traders are people. Notices about individuals contain personal data. Use them for a legitimate purpose such as credit risk or KYB, keep them only as long as you need them, and handle them under the GDPR. This is not a consumer credit report.

If you republish the data, cite “BODACC (DILA)” and the date. Every row carries the source and licence.

Pricing

The actor charges per check and per judgment returned: from $0.0045 per SIREN, SIRET or name that BODACC answered (a clean “no proceeding found” included) and from $0.0009 per judgment row, plus a small per-run start fee. Invalid SIRENs and entries BODACC did not answer are not charged. At those rates, a clean 100-company watchlist costs about $0.45 per run. Rates depend on your Apify plan; current figures are on the Store page. You can set a maximum cost per run: the run stops at the limit and lists the entries it did not reach as not_checked, never as clear.

The same kind of check exists for other countries, for example Germany’s insolvency register. For how insolvency checks fit into credit decisions more broadly, see insolvency and credit risk.

FAQ

Is BODACC data free?

Yes. bodacc.fr is free to search, and the data is published as open data under the Licence Ouverte 2.0, which allows reuse with attribution. A paid tool charges for filtering, structuring and scheduling; the data itself is free.

Can I check a sole trader?

Yes. Sole traders (commerçants, artisans, entrepreneurs individuels) have a SIREN and their proceedings are published in BODACC like a company’s. They come back with debtorType: "individual".

How quickly does a new insolvency appear?

A judgment appears once BODACC publishes it, usually one to two weeks after the court decision. A weekly check therefore catches most openings within two to three weeks of the judgment, well inside the two-month claims window.

Does “no proceeding found” mean the company is solvent?

No. It means no court has opened a collective proceeding that BODACC published since 2008. A company can be in serious difficulty without one, and amicable procedures such as mandat ad hoc and conciliation are confidential and never appear in BODACC.

Can I search by SIRET?

Yes. A 14-digit SIRET is reduced to its 9-digit SIREN, because insolvency proceedings apply to the legal entity, not to one establishment.

What about personal debt problems (surendettement)?

They are not part of BODACC “Procédures collectives” and are not returned. Surendettement is a consumer procedure handled outside the commercial insolvency system.


Turn this into working data. Browse the registries and use cases, or start free on Apify.