Trade Register data should be stored as time-bound facts, not reconstructed from logs.
A jurisdiction-specific `subject_identifier` is proposed to identify the registered subject.
The internal subject_id remains the primary identifier within the Trade Register.
Names, legal status and optional subject attributes should be modelled using relational structures with explicit UTC date-times.
The primary trade name designation is a separate historical fact and should be maintained in its own table.
Optional attributes, such as IBAN, should be clearly identified and may require explicit consent before disclosure.
Field reference - From June 11, 2026 - Insight at janwillemstegink.nl
Abbreviations such as B.V. and N.V. should be standardized as BV and NV by introducing a legalized_name name type. Trade names must be retrievable in their original letter case for precise matching.
| Table | Field | Key | Req. | Meaning |
|---|---|---|---|---|
| registered_subject | subject_id | PK | Yes | Internal Trade Register subject identifier. |
| subject_identifier | IDX | Yes | Unique reference assigned to a registered subject and prefixed by the issuing jurisdiction. | |
| local_code | IDX | Yes | Unique local Trade Register number assigned by the registration authority. | |
| jurisdiction_code | Yes | Issuing jurisdiction code. | ||
| registration_authority | Yes | Register authority. | ||
| subject_from | Yes | UTC date-time from which this subject record applies. | ||
| subject_to | No | UTC date-time until which this subject record applied; empty means current. | ||
| subject_legal_status | legal_status_id | PK | Yes | Legal status record identifier. |
| sls_subject_id | FK | Yes | Registered subject. | |
| legal_status | Yes | Recorded legal status. | ||
| legal_status_code | No | Standardized abbreviation of the legal status. | ||
| status_from | Yes | UTC date-time from which this legal status applies. | ||
| status_to | No | UTC date-time until which this legal status applied; empty means current. | ||
| subject_name | name_id | PK | Yes | Name record identifier. |
| sn_subject_id | FK | Yes | Registered subject. | |
| name_type | Yes | legal, legalized, trade. | ||
| name_value | Yes | Recorded name value. | ||
| is_case_sensitive | Yes | Uppercase/lowercase distinction applies. | ||
| name_from | Yes | UTC date-time from which this name applies. | ||
| name_to | No | UTC date-time until which this name applied; empty means current. | ||
| primary_trade_name | primary_name_id | PK | Yes | Primary trade name designation record. |
| ptn_subject_id | FK | Yes | Registered subject. | |
| ptn_name_id | FK | Yes | Name designated as primary trade name. | |
| primary_from | Yes | UTC date-time from which this name is primary. | ||
| primary_to | No | UTC date-time until which this name was primary; empty means current. | ||
| subject_location | location_id | PK | Yes | Subject location record. |
| sl_subject_id | FK | Yes | Registered subject. | |
| sl_name_id | FK | No | Trade name associated with this location. | |
| street_address1 | No | Primary street address line. | ||
| street_address2 | No | Additional street address line. | ||
| postal_code | No | Postal or ZIP code. | ||
| city | No | City or locality. | ||
| state_region | No | State, province, or region. | ||
| country_code | No | ISO 3166-1 alpha-2 country code. | ||
| location_from | Yes | UTC date-time from which this location applies. | ||
| location_to | No | UTC date-time until which this location applied; empty means current. | ||
| optional_subject_attribute | attribute_id | PK | Yes | Optional attribute record. |
| osa_subject_id | FK | Yes | Registered subject. | |
| attribute_name | Yes | iban, bic, account_holder_name, website_url, contact_email. | ||
| attribute_value | No | Provided value; empty means not provided. | ||
| consent_required | Yes | Explicit consent required before disclosure. | ||
| attribute_from | Yes | UTC date-time from which this attribute applies. | ||
| attribute_to | No | UTC date-time until which this attribute applied; empty means current. | ||
| subject_responsible | responsible_id | PK | Yes | Responsible party record identifier. |
| sr_subject_id | FK | Yes | Registered subject. | |
| responsible_subject_code | IDX | Yes | Subject code identifying the responsible natural person. | |
| responsible_name | Yes | Recorded name of the responsible party. | ||
| responsible_role | Yes | Role of the responsible party. | ||
| authority_to_represent | No | Indicates authority to represent the subject. | ||
| responsible_from | Yes | UTC date-time from which this responsibility applies. | ||
| responsible_to | No | UTC date-time until which this responsibility applied; empty means current. | ||
| subject_relationship | relationship_id | PK | Yes | Subject relationship record identifier. |
| from_subject_id | FK | Yes | Subject from which the relationship is defined. | |
| to_subject_id | FK | Yes | Subject to which the relationship applies. | |
| relationship_type | Yes | Type of relationship between the registered subjects. | ||
| relationship_from | Yes | UTC date-time from which this relationship applies. | ||
| relationship_to | No | UTC date-time until which this relationship applied; empty means current. | ||
| subject_relationship_attribute | relationship_attribute_id | PK | Yes | Relationship attribute record identifier. |
| sra_relationship_id | FK | Yes | Subject relationship. | |
| relationship_attribute_type | Yes | Type of attribute describing the relationship. | ||
| relationship_attribute_value | Yes | Value of the relationship attribute, interpreted according to its type. | ||
| relationship_attribute_from | Yes | UTC date-time from which this attribute value applies. | ||
| relationship_attribute_to | No | UTC date-time until which this attribute value applied; empty means current. |
Private individuals should be able to use an electronic identity wallet on their own devices. This includes Linux-based phones.
Wallet functionality should therefore not depend on the use of a particular commercial mobile operating system or on registration as a Trade Register subject.
Where an authoritative register serves a public function, public access to its data may be funded from public resources rather than through charges for individual data access or retrieval.
Public funding of an authoritative register should support a proportionate organizational structure, with specialized functions introduced only where their responsibilities cannot reasonably be shared or combined with other functions.
Parts of this governance evolution have been addressed in individual countries. Different institutional, funding, and public-access models are in use. These provide practical reference points for developing authoritative public registers.
Preparing on GitHub: EU Digital Identity Wallet — Android reference implementation
| Responsibility | Generic role | Scope | Dutch implementation | Description |
|---|---|---|---|---|
| Business registration | Business Register | National | KVK / Handelsregister | Maintains authoritative business registration data. |
| Person identification | Identity Provider | EU / National | DigiD / EUDI? | Establishes trusted evidence of a natural person's identity. |
| Organisation identification | Authoritative Register | EU / National | KVK / Handelsregister | Establishes the registered identity of an organisation. |
| Relationship registration | Authoritative Register | National | KVK / Handelsregister | Records relationships between registered subjects. |
| Representation authority | Authoritative Source | EU / National | KVK / Handelsregister? | Establishes who may act for an organisation. |
| Attribute definition | Attribute Scheme Authority | EU / National | To be determined | Defines trusted attributes and their meaning. |
| Attribute issuance | Attribute Issuer | EU / National | To be determined | Issues trusted attributes from authoritative data. |
| Trust framework | Trust Framework Authority | EU / National | To be determined | Defines how trusted parties and credentials are recognised. |
| Trust services | Trust Service Provider (TSP / QTSP) | EU / National | TSPs / QTSPs | Provides regulated electronic trust services. |
| Public key infrastructure | Public Key Infrastructure (PKI) | Global / EU / National | PKIoverheid | Provides cryptographic trust infrastructure. |
| Trust lists | Trusted List Provider | EU / National | Dutch Trusted List | Publishes trusted service providers and their status. |
| Wallet provision | Wallet Provider | EU / National | NL Wallet / private wallet providers? | Provides digital identity wallets. |
| Wallet interoperability | Standards and Conformance Framework | Global / EU | EUDI / national implementation? | Enables wallets, issuers and relying parties to interoperate. |
| User platform | Platform Provider | Global / EU | Android / iOS / Linux-based platforms? | Provides the operating environment for a wallet. |
| Secure key storage | Secure Cryptographic Environment | Global / EU | To be determined | Protects cryptographic keys and operations. |
| Service verification | Relying Party | Global / EU / National | Public and private service providers | Requests and verifies trusted information. |
| Technical conformance | Conformance Authority / Test Facility | Global / EU / National | To be determined | Tests implementations against applicable requirements. |
| Issue handling | Issue Resolution Function | EU / National | To be determined | Routes technical and data issues to the responsible party. |
| Remediation | Remediation Function | EU / National | To be determined | Ensures identified problems can be corrected. |
| Escalation | Escalation Authority | EU / National | To be determined | Handles unresolved cross-party issues. |
| Supervision | Supervisory Authority | EU / National | RDI / other competent authorities? | Provides independent regulatory oversight. |
| Cross-domain coordination | Coordinator | EU / National | To be determined | Maintains alignment across all responsibilities. |
| Governance | Governance Authority | EU / National | To be determined | Assigns ownership, decisions and accountability. |