🆔Show KBO data
To comment on a FP:
Date, name: comment
Status Feature Passport
| STATUS | OWNER | DATE |
|---|---|---|
In proposal | Sofie | 20/10/2023 + 20/12/2023 |
In refinement - Design Research | ||
In refinement - Technical Research/Feedback | ||
In development | ||
In QA/ Testing | ||
In Final state |
OP-2731: Integration: show KBO data in OP
ANALYSIS
This part of the feature passport is owned by the analyst
Context
KBO = NL - Kruispuntbank van Ondernemingen = EN - Crossroadsbank for Enterprises
What is the Crossroads Bank for Enterprises?
The Crossroads Bank for Enterprises (CBE) is a database owned by the FPS Economy containing all the basic data concerning companies and their business units. The purpose of the CBE is twofold:
increasing the efficiency of public services;
and simplifying administrative procedures for companies.
De Kruispuntbank van Ondernemingen (KBO) is een databank van de FOD Economie waarin alle basisgegevens van ondernemingen en hun vestigingseenheden verzameld zijn. De KBO heeft een dubbel doel:
de werking van de overheidsdiensten efficiënter maken;
en de administratieve procedures voor ondernemingen vereenvoudigen.
Method of operation
The CBE centralises the basic data of companies and business unit and disseminates it to several competent authorities. The CBE assigns a unique identification number to each company and business unit. This identification number allows authorities to exchange information. Consequently, companies need to submit their data to the authorities only once.
De KBO centraliseert de basisgegevens van ondernemingen en vestigingseenheden en verspreidt deze naar verschillende bevoegde overheidsdiensten. Elke onderneming en vestigingseenheid krijgt van de KBO een uniek identificatienummer. Met dit identificatienummer kunnen overheden onderling gegevens uitwisselen. Zo moet de ondernemer slechts één keer dezelfde gegevens aan de overheid overmaken.
Problem:
The KBO should be the authentic source for organisation and contact information, but in reality the information is not always up-to-date.
The KBO number = ondernemingsnummer = btw nummer
Goal
Phase 1: We want to show KBO data in OP
Phase 2: We want to compare the ABB data in OP and the KBO data in OP and show the mismatches.
In both phases ABB business can check the data and
correct wrong data in OP (before edit version of the contactapp is live)
alert administrative units of incorrect data, so they can change it via the contactapp
Current state
We have no data from KBO in OP yet.
1. Data in KBO
Example: Gent (gemeente) https://kbopub.economie.fgov.be/kbopub/toonondernemingps.html?ondernemingsnummer=207451227
2. Data in Organisatieregister Wegwijs
Example: Gent (gemeente) https://wegwijs.vlaanderen.be/#/organisations/6c708abb-ffa5-4db2-ad3c-c9046a317d64/info
Pages with info for OP
Data mapping
Miro mapping (WIP): https://miro.com/app/board/o9J_l7hGn30=/?share_link_id=329979535825/?moveToWidget=3458764567549192948&cot=14
The table shows the mapping of the data of KBO, Wegwijs and OP.
The first column shows the data of KBO that we want to show in OP. We do not sync directly with KBO, but we sync with Wegwijs, so we have the corresponding fields in the d
The third column shows corresponding name and OSLO reference in OP that we have in production. I added this a reference.
Not all data that is shown in Organisatieregister Wegwijs comes from KBO.
✅ = data in Wegwijs is synct with KBO
❔ = not sure if the data comes from KBO or from an other source, please check if more information is available via API. If we are not sure that the data is synct with KBO, than we don't show it. We will ask Wegwijs at a later time how we we can solve this because we don't want to sync with KBO directly.
| KBO | OK? | Wegwijs | OP tab KBO gegevens |
|---|---|---|---|
Naam | ✅ | Formele naam volgens KBO | Naam (OSLO = wettelijke naam) = OP-2735 |
Commerciële naam | ❔ | Not available in Wegwijs? | Commerciële naam = OP-2737 |
Afgekorte naam | ❔ | Korte naam (= volgens KBO?) | Afgekorte naam (OSLO = alternatieve naam) |
Rechtsvorm | ✅ | Rechtsvorm volgens KBO | Type bestuur = OP-2735 |
Status | ✅ | Status (= volgens KBO?) | Status = OP-2735 |
Begindatum | ✅ | Formeel geldig vanaf | Begindatum = OP-2735 |
Ondernemingsnummer | ✅ | KBO nummer | Ondernemingsnummer = OP-2735 |
URL (page in KBO) | ✅ | Not available in Wegwijs |
= OP-2734 To develop (cfr Sharepoint-ID). Auto generate, URL is fixed format with the KBO number at the end https://kbopub.economie.fgov.be/kbopub/zoeknummerform.html?nummer=0207451227 |
Adres van de zetel | ✅ | Maatschappelijke zetel volgens KBO | Adres van vestiging type maatschappelijke zetel = OP-2735 |
Telefoonnummer | ❔ | Available in Wegwijs, but this is not data from KBO | Telefoonnummer = OP-2737 |
❔ | Available in Wegwijs, but this is not data from KBO | E-mail = OP-2737 | |
Website | ❔ | Available in Wegwijs, but this is not data from KBO | Website = OP-2737 |
Design for KBO data in OP
This design shows all the data we would like to show. Only develop the fields that we know that have data from KBO (✅).
Link to Figma = https://www.figma.com/file/sZ3xGevGuecXu39wQYnnTZ/OP_KBO-data?type=design&node-id=0%3A1&mode=design&t=vLUgh7gARGR2DPR5-1
🤩 Expectations
Develop the page as shown in the design.
Page kerngegevens with two tabs (to be developed = OP-2899)
ABB gegevens (is already in production)
KBO gegevens (to be develop: see data mapping tabel for the corresponding Jira tickets)
The content of the tab is the current page ‘Kerngegevens’, no changes in the content is required.
We keep the validations and field editing the way it is.
The 'bewerk' button has to be shown.
Content of the tab needs to be developed.
All the fields are not editable fields
The 'bewerk' button doesn't have to be shown, because editing is not allowed
🤔 Discussion points
How to get data from Organisatieregister Wegwijs:
OP-2732: Technical analysis: integration via OrganisatieRegister Wegwijs (MAGDA) or directly via KBO
SOLUTION
The next two parts of the FP can [sometimes] be worked on simultaneously
Design
This part of the feature passport is owned by the designer
User research
[If there is any user research preceding the wireframe mock-up stage, it needs to be documented here]
Mock-ups
[link to figma mockups + any explanation or extra documentation]
Technical
This part of the feature passport is owned by the technical team
[Information about the technical solutions for expectations that need it - e.g. using mu-search for showing all types of positions in one table.]
After the designer and/or the technical team finish their task, a meeting follows where the solutions are presented. The team exchanges feedback and amends the feature passport where necessary.
Last updated
