Trade Register Data Structure for PKI and Subject Verification

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

Naming Standardization in the Trade Register

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.

Rules

Logging is not sufficient; historical values shall be stored using explicit from/to date-time fields.
If only one trade name exists, it is automatically primary.
Where multiple trade names exist, exactly one shall be primary at any given time.
For an eenmanszaak, at least one trade name shall exist and exactly one shall be primary.
For a BV or NV without a registered trade name, legalized_name serves as the primary trade name.
Optional attributes such as IBAN are clearly optional and may require explicit consent.
A subject identifier references a registered subject only.
It does not indicate or imply whether the subject is a natural person, a business, a legal entity, or any particular legal or organisational form.
Such characteristics are determined from the associated registration data and may change over time.
A subject identifier shall begin with the ISO 3166-1 alpha-2 country code and shall contain two check digits.
Field names should be globally distinguishable wherever practical, allowing database structures and code to be read almost like a book, reducing ambiguity and facilitating data exchange and software development.