Automating your KYC process in Belgium: architecture, steps and integration patterns
Automating KYC cuts file processing from 2-4 hours to 15-30 minutes. Target architecture, 7 steps to automate, required technical blocks (BCE, UBO, screening, signature, archiving), integration patterns and human control points to preserve.
In brief
Automating the KYC process in Belgium cuts file processing from 2-4 hours to 15-30 minutes through 7 orchestrated steps: BCE pre-fill, UBO cascade, remote identification, screening, risk assessment, electronic signature and archiving. The typical gain for a practice handling 200 files per year reaches 30 to 60 freed person-days annually.
Why automate
A manual KYC of a Belgian company typically takes 2 to 4 hours: BCE search, ID copies, mail for signature, paper filing. Multiply by 100 files/year for a mid-sized practice → 300 person-days of pure admin.
Automation brings the same file down to 15-30 minutes, without compromising on control quality, by redeploying human judgement where it truly matters.
This article describes the target architecture and the 7 steps to automate.
The target architecture in 5 layers
1 2 3 4 5 6 7 8 9
User (staff or client)
↓
Interface (web, mobile)
↓
KYC orchestration (workflow engine)
↓
Technical blocks (BCE, UBO, screening, signature, archiving)
↓
Audit trail (log + timestamp)
Three non-negotiable architectural principles:
The 7 steps to automate
Step 1 — Pre-fill from BCE number
Staff enters BCE/KBO number. The system automatically retrieves:
- Name, legal form, status (active/ceased)
- Registered office address
- Directors (with dates)
- NACE codes
- Linked establishments
- Name history
See the Python tutorial or Node.js for API integration.
Time saved: 15-25 minutes per file.
Step 2 — Automatic UBO cascade
The system identifies beneficial owners climbing 3 levels:
- Level 1: direct shareholders > 25 %
- Level 2: parent holdings up to natural person
- Level 3: default senior officers if no UBO identified
Automatic comparison with Belgian UBO register → divergences flagged. See our UBO article.
Time saved: 20-40 minutes per file.
Step 3 — Remote identification
For natural persons (directors, UBOs, self-employed clients):
- Belgian eID authentication with card reader
- itsme® for residents
- Supervised video-identification by trained operator
- OCR + liveness for European passports
See our KYC guide for accepted methods.
Time saved: 15-30 minutes per natural person.
Step 4 — Sanctions and PEP screening
The system cross-checks all identified persons (clients, directors, UBOs) with:
- International sanctions lists (EU, UN, OFAC, HMT)
- PEP lists (politically exposed)
- With fuzzy matching to tolerate spelling variations
Result tracked, dated, archived. On hit, AMLCO alert before validation.
Time saved: 10-20 minutes per file.
Step 5 — Automated risk assessment
Based on the above, the system computes a risk score:
- Legal form (recent shell company → +1)
- Geography (non-resident UBO from opaque jurisdiction → +2)
- Activity (cash-intensive business → +1)
- PEP (UBO PEP → +3)
- Sanctions (partial hit to clarify → +5)
Sum → matrix: ≤2 = low, 3-6 = standard, ≥7 = high. The matrix is configurable by the AMLCO.
Time saved: 5-10 minutes per file.
Step 6 — Electronic signature and contracting
The system generates the pre-filled business relationship contract and gets it signed via:
- Qualified electronic signature (eIDAS)
- itsme® or eID
- With TSA timestamp
The signed contract goes directly to 10-year archiving.
Time saved: 30-60 minutes (vs postal mail).
Step 7 — Automatic archiving
All produced documents (BCE extract, UBO cascade, screening, video-ID, signed contract) are:
- Converted to PDF/A (long-term archive standard)
- TSA-timestamped
- AES-256 encrypted at rest
- Indexed per client file
- Kept 10 years automatically
See our article on mandatory KYC file content.
Time saved: 15-20 minutes per file.
Human control points to preserve
Automation does not eliminate human judgement — it refocuses it on value-added decisions:
Final AMLCO validation
Before onboarding, the AMLCO validates the complete file in minutes. For high-risk files, mandatory management approval.
Monitoring alert analysis
See our article on transaction monitoring. Alert triage remains procedural human work.
CTIF reporting decision
Suspicion analysis and reporting decision remain strictly human. See the CTIF guide.
Annual file review
If automation detects a change (new director, modified UBO), a human must interpret: impact on risk? additional measure?
Integration patterns
Pattern 1 — Mono-platform
Everything in one RegTech platform. Pro: zero integration. Con: vendor lock-in.
Pattern 2 — Workflow + external blocks
Internal workflow (Camunda, Temporal, or custom orchestration) calling external APIs for each block. Maximum flexibility.
Pattern 3 — RegTech platform + extensions
Main platform covering 80 % of the journey + API calls for the 20 % specific (e.g., specialized video-ID for non-residents).
See our 2026 RegTech landscape.
Frequent mistakes
How Company Belgium automates your KYC
The Company Belgium KYC module covers the 7 steps natively:
- Integrated BCE/KBO API (automatic pre-fill)
- 3-level UBO cascade with register comparison
- eID, itsme®, video-ID connectors
- Integrated sanctions + PEP screening, dated, tracked
- AMLCO-configurable risk matrix
- Native qualified eIDAS electronic signature
- Timestamped PDF/A archiving, encrypted, 10 years
- Full audit trail (user, action, timestamp)
- Webhooks to integrate upstream systems (CRM, ERP)
To scale to high volume: see the rate-limits & caching architecture.
Bottom line
Automating KYC in Belgium rests on 7 steps orchestrated in an explicit workflow with systematic audit trail. Typical gain: 80 % time saved on repetitive tasks (BCE, UBO, screening, archiving), while preserving human judgement on critical decisions.
For a practice handling 200 files/year, automation frees 30 to 60 person-days annually. Combined with continuous training and a solid AMLCO, it is the right lever for 2026.
Frequently asked questions
How long does it take to automate KYC for a Belgian company?
With an integrated RegTech platform connected to BCE/KBO and the UBO register, pre-fill and UBO cascade are instantaneous. The full KYC file, including remote identification and electronic signature, can be completed in 15 to 30 minutes instead of 2 to 4 hours manually. Initial platform setup typically takes 4 to 6 weeks.
What technical tools are needed to automate KYC in Belgium?
At minimum you need a BCE/KBO API for pre-fill, a connector to the Belgian UBO register for the beneficial-owner cascade, a sanctions and PEP screening engine, a remote identification module (eID, itsme or video-ID), a qualified eIDAS electronic signature, and timestamped PDF/A archiving. These building blocks can be bought separately or within an all-in-one platform.
Which human controls must be kept in an automated KYC process in Belgium?
The Belgian Act of 18 September 2017 does not allow full automation without human oversight. The AMLCO must validate the final file before onboarding, analyse monitoring alerts and decide on any CTIF report. Annual review of active files and interpretation of detected changes (new director, modified UBO) also remain mandatory human tasks.
What is the ROI of KYC automation for a Belgian practice?
For a practice handling 200 AML files per year, automation typically frees 30 to 60 person-days annually, equivalent to 30,000 to 50,000 euros in full salary cost. Against a RegTech subscription of 1,000 to 10,000 euros per year depending on size, ROI is reached within a few months. The reduced risk of SPF Economy sanction, which can reach several hundred thousand euros, is an additional major benefit.
Comments
Related articles

Belgian Crossroads Bank for Enterprises (BCE/KBO) API: complete English developer documentation
English developer documentation for the Belgian Crossroads Bank for Enterprises API. Overview of the BCE/KBO registry, legal context, access options, quick start with cURL examples, and integration patterns for international developers.

Rate limits, quotas and caching to scale a BCE/KBO application: reference architecture
Your app queries the BCE/KBO API at volume — how to avoid 429s, control costs and guarantee latency? Reference architecture with multi-layer cache, request queue, observability and webhooks. Concrete patterns and target numbers.

BCE/KBO API endpoints reference: complete list of REST routes (companies, addresses, NACE, UBO, establishments, Peppol)
Comprehensive technical reference of the Company Belgium REST API endpoints: search, company record, addresses, NACE activities, establishments, directors, UBO, Peppol verification. With response schemas, parameters and error codes.
