BCE monitoring: track company arrivals and departures at your addresses in real time

In brief

BCE monitoring allows business centers, fiduciaries and building managers to automatically detect every company arrival or departure at their critical addresses. Company Belgium compares the BCE delta every night and triggers email alerts, a filterable dashboard and HMAC webhooks for CRM integration, ensuring detection within 24 hours.

Why monitoring the BCE has become strategic

If you manage a shared address — business center, domiciliation building, notary's office, fiduciary lending its address to clients in transition — you know that every new company registered at your address engages your responsibility. Conversely, every undetected departure means a client record to close, a contract to terminate and, where applicable, a notice to send to the SPF Economie.

The Crossroads Bank for Enterprises (BCE/KBO) publishes these movements daily, but exporting them, filtering by address and turning them into actionable alerts is a project of its own. That's what Company Belgium automates.

How monitoring works

You declare one or more watched addresses in your workspace. For each address, you specify the matching granularity:

• Strict — street, number, postcode, municipality — useful for a single building

• Wide — at street level — useful for multi-building business centers

• Postcode — for fiduciaries covering an area

Every night, the engine compares the latest BCE export (Open Data + daily delta) with the previous day's snapshot. Any movement hitting a watched address triggers a typed event:

• Arrival — new registered office or establishment address for an existing company

• Registration — new company registered at the address

• Departure — registered office transferred elsewhere

• Cessation — company struck off or bankrupt

• Director change — modification of legal representation

Events are dated using the official BCE date (not the detection date) and kept without expiry.

Three channels so you don't miss a thing

1. Near-real-time dashboard. Filterable by address, event type, period. Each row links to the full company record: legal form, NACE, directors, history. CSV export in one click.

2. Email alerts. You pick a cadence: immediate, daily digest (8 a.m.) or weekly. The email lists the period's movements with a deep link to each record. One address = one possible distribution list (manager + accountant + compliance officer).

3. Webhooks. For CRM or ERP integrations, each event can be pushed to an HMAC-SHA256-signed HTTP endpoint. Normalized JSON payload, exponential retry, delivery log. Ideal to auto-create a client record on arrival or archive it on departure. See our guide on webhooks and real-time notifications for the full protocol.

Concrete case: a Brussels business center

A partner in the European quarter monitors 4 buildings totaling ~180 active domiciliations. Before monitoring was switched on, the team discovered newcomers only at invoicing time, sometimes 6 weeks after registration. Today:

• The daily digest arrives at 8 a.m. for the sales team

• Each new registration triggers a webhook that creates an opportunity in their CRM with the director's contact details

• Departures show up the next day, allowing immediate contract closure and avoiding the AML risk of a ghost domiciliation — a topic covered in detail in our guide on AML compliance for Belgian domiciliation centers

Result over 6 months: 100% of movements detected within 24 hours, ~12 hours/month of manual entry avoided, zero ghost addresses at quarterly close.

API side: what the endpoint exposes

For engineering teams, monitoring is also controllable via API:

1
2
3
4
5
6
7
8
9

# List your watched addresses
curl https://companybelgium.be/api/v2/monitoring/addresses \
  -H "X-API-Key: pk_live_..." \
  -H "X-API-Secret: sk_live_..."

# Fetch events for a date range
curl "https://companybelgium.be/api/v2/monitoring/events?addressId=adr_xxx&from=2026-04-01&to=2026-04-30" \
  -H "X-API-Key: pk_live_..." \
  -H "X-API-Secret: sk_live_..."

Events follow the schema { id, type, occurredAt, address, enterprise, payload } — payload contains the before/after state for changes (director, NACE, name).

How to enable monitoring

From your workspace: BCE Monitoring → Watched addresses → Add. The first address is free, higher plans lift the limits and enable webhooks. BCE history is replayed since 1 January 2024 on first activation — you immediately see the past of your address, not only the future. Developers can find the full data structure in our BCE KBO REST API endpoints reference guide.