Enterprise number vs establishment unit: the difference in the BCE

In brief

In the Crossroads Bank for Enterprises (BCE/KBO), two identifiers coexist and are always distinct: the enterprise number (10 digits, starts with 0 or 1) that designates the legal entity, and the establishment unit number (10 digits, starts with 2) that designates a physical activity point. Every company has exactly one enterprise number and at least one establishment unit (often several).

The two identifiers side by side

Three typical cases

Case 1 — Small company, single location

A Brussels-based consulting BV with one office has:

• 1 enterprise number: 0735.123.456

• 1 establishment unit at the registered office: 2.260.789.012, located 12 rue de la Loi in Brussels

The enterprise number and the unit share the same address, but they are two distinct objects in the BCE.

Case 2 — Multi-site company

A pharmacy chain with 8 outlets has:

• 1 enterprise number: 0415.678.901

• 8 establishment units, each with its own number and address

• A single VAT return and a single annual accounts filing — at the enterprise number level

If you want to prospect this chain, looking only at the enterprise number gives you one prospect. Looking at the establishment units gives you eight geographically distinct contact points.

Case 3 — Foreign company with a Belgian branch

A French company opening a branch in Antwerp gets:

• 1 Belgian enterprise number for the branch (the French parent keeps its SIREN)

• 1 establishment unit for the Antwerp branch

This Belgian enterprise number is separate from the French SIREN. To identify the parent, the French register must be consulted — the BCE does not link them automatically.

Which key to store in your application

Golden rule: the enterprise number is the "accounting and legal" key; the establishment unit is the "geographic and operational" key.

Classic integration pitfalls

1. Treating VAT = enterprise number

That is almost true. A VAT-liable company has a VAT number equal to its enterprise number (BE0403170701). But not all companies are liable (non-profits, pure holdings, etc.) and some foreign companies have a Belgian VAT number without a Belgian enterprise number. Always verify VAT status via the VIES API or the Company Belgium API before assuming.

2. Mixing enterprise and unit numbers in the same column

In raw format, both have 10 digits with dots. If your database stores "0403.170.701" and "2.260.789.012" in a column bce_number, you are mixing two heterogeneous concepts. Good practice: two separate columns, or an explicit prefix ("ENT:0403170701" / "EST:2260789012").

3. Treating a unit as a "subsidiary"

An establishment unit has no legal personality. It is not a subsidiary, not a branch in the company-law sense, just a geographic activity point. A real subsidiary has its own enterprise number. For the distinction subsidiary / branch / unit, see our article on branches of foreign companies in the UBO register.

4. Ignoring the cessation date of a unit

Units can be closed independently of the enterprise number. A chain closing a store keeps its enterprise number active but marks the unit as ceased. If your prospect has only one active unit left out of 8, that is a strong distress signal. For dormant company signals, see our dedicated guide.

NACE activities: enterprise vs unit

Important subtlety: NACE codes can be attached at the enterprise number level or at each establishment unit level. A company carrying out different activities at different sites declares it this way: NACE A at unit 1, NACE B at unit 2. To exploit this data fully, see our guide on Belgian NACE codes.

The Company Belgium API

The API exposes both levels separately:

1
2
3

GET /api/companies/{enterpriseNumber}              # Legal entity
GET /api/companies/{enterpriseNumber}/establishments  # List of units
GET /api/establishments/{establishmentNumber}      # Unit detail

For geographic searches, the unit collection is queried — much more precise than filtering on the registered office address. To get started, see the BCE API documentation.