bce-codes-to-label
Lookup labels for Belgian Crossroads Bank for Enterprises (BCE/KBO) codes.
Covers NACE codes, legal forms, joint committees, countries, postal codes, and more — with labels in French, Dutch, German, and English (where available).
Installation
pip install bce-codes-to-label
Quick start
from bce_codes_to_label import joint_committees, countries, nace, lookup
# Each registry accepts three input forms:
joint_committees("jcc:m100") # full BCE code
joint_committees("m100") # suffix (part after ":")
joint_committees("100") # value only
# Filter by language
countries("BE", lang="fr")
# {'_key': 'BE', '_code': 'cty:mBE', 'label_fr': 'Belgique'}
# Global lookup — returns a result only if there is a unique match across all registries
lookup("jcc:m100")
# {'_registry': 'joint_committees', 'label_fr': '...', '_key': '100', '_code': 'jcc:m100'}
Available registries
| Registry | Prefix | Example | Description |
|---|---|---|---|
joint_committees |
jcc: |
joint_committees("100") |
Joint committees (commissions paritaires) |
nace |
nace: |
nace("2008:01110") |
NACE-BEL activity codes (2003 & 2008) |
currencies |
ccy: |
currencies("EUR") |
Currency codes |
countries |
cty: |
countries("BE") |
Country codes |
data_types |
met: |
data_types("am1") |
Data/metric types |
address_types |
atc: |
address_types("001") |
Address type codes |
commercial_courts |
cct: |
commercial_courts("31") |
Commercial courts |
mandate_functions |
fct: |
mandate_functions("10") |
Mandate/function labels |
legal_forms |
lgf: |
legal_forms("001") |
Legal form codes |
identifier_kinds |
nmt: |
identifier_kinds("1") |
Identifier kind-of-number labels |
sectors |
sct: |
sectors("01") |
Sector codes |
postal_codes |
pcd: |
postal_codes("1000") |
Belgian postal codes |
msca |
msca: |
msca("10/49") |
MSCA accounting codes |
rejection |
rej: |
rejection("PDF:11") |
Filing rejection codes |
models |
mod: |
models("m02-f") |
Annual accounts model types |
API
Registry call
registry(query, lang=None)
- query: full BCE code (
"jcc:m100"), suffix ("m100"), or value ("100") - lang (optional):
"fr","nl","de", or"en"— returns only that language's label - Returns a
dictwith labels and metadata, alistif multiple matches, orNoneif not found
Global lookup
lookup(query, lang=None)
Searches all registries. Returns the match only if exactly one registry produces exactly one result. Returns None if ambiguous or not found.
Utilities
registry.all_keys() # list all canonical keys
registry.get(query, lang) # alias for registry(query, lang)
NACE codes
NACE codes include a version prefix since both 2003 and 2008 versions are available:
from bce_codes_to_label import nace
nace("2008:01110") # specific version + code
nace("nace:2008:m01110") # full BCE code form
Data structure
Each data file uses an efficient keyed format:
{
"code_prefix": "jcc:",
"codes": {
"100": {
"label_fr": "Commission paritaire auxiliaire pour ouvriers",
"label_nl": "Aanvullend PC voor de werklieden",
"label_de": "die paritätische Hilfskommission für Arbeiter"
}
}
}
Rebuilding data
Source JSON files live in codes/. To regenerate the optimized data files:
python scripts/build_data.py
License
MIT
Metadata
Release files for bce-codes-to-label 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bce_codes_to_label-0.2.0.tar.gz | 1.1 MB | With provenance | Details for bce_codes_to_label-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bce_codes_to_label-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for bce_codes_to_label-0.2.0-py3-none-any.whl |
Total release size: 2.2 MB
Release files / bce_codes_to_label-0.2.0.tar.gz
| Download URL | bce_codes_to_label-0.2.0.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3c917b32cd0a81d1ad8818d47f205b195deb48d54857f798a2eba3c70153b6c
|
|
BLAKE2b-256 checksum How to use checksums |
6d8d352ec9dddd8ad3c62120d01deb7e79d83d9d7bab1d1e376cbdf32368cf21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 6, 2026.
Transparency logRelease files / bce_codes_to_label-0.2.0-py3-none-any.whl
| Download URL | bce_codes_to_label-0.2.0-py3-none-any.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f86b4abc1adeb4c6bdea29bf3ad0697bf0c66046b908863e8efff1227d5cb36
|
|
BLAKE2b-256 checksum How to use checksums |
cf2964968565cb11109876095d67b1b55266fc64a2fe3c9ed94f5d1eb859e871
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 6, 2026.
Transparency logSecurity for bce-codes-to-label 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for bce_codes_to_label-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.