← Back to catalogue
Published

Legal Entity Registration

vr.wm-org-010 · wm-org-010-legal-entity-registration

Model the legal identity of an organization as constituted and recorded by an authoritative register or registration authority in a jurisdiction, so that an agent can identify, verify, monitor and operate on registered legal persons without conflating them with the organizations, groups or statistical units they relate to.

World Models Society, people and institutions SOC.ORG.REG

Bundle → Layer → Finding → Questions Filled

7 bundles · 15 layers · 29 findings · 118 questions

Legal identity and designation What the registered legal person is called, how it is identified across schemes, and how it is classified by legal form and activity.

Identity and identifiers

The authoritative register-assigned identity and the qualified alternate identifiers that denote the same legal person.

Register-anchored legal entity identity

The master identity of the registered legal person is the pair (registration authority, identifier assigned by that authority). Locally assigned surrogate keys are subordinate and must be flagged as such. LEI reference data models this explicitly as RegistrationAuthorityID plus RegistrationAuthorityEntityID, and the governed authority list exists precisely because a bare registration number is ambiguous across 232 jurisdictions.

  1. Which register or registration authority holds the authoritative record for this entity, and what identifier does it assign? identity
  2. Is the register-assigned identifier stable, reused after dissolution, or changed on conversion or migration? identity
  3. When no register-assigned identifier exists, which fallback identity is used and how is it qualified? identity
  4. How is the identifier syntactically validated before acceptance? validation

Cross-scheme identifier alignment

Additional identifier schemes attached to the same legal person (LEI, EUID, VAT or tax number, D-U-N-S, GLN, national scheme numbers) together with the scheme qualification that keeps them unambiguous, and the precedence rules when they disagree. ISO/IEC 6523 exists because an organization identifier without its issuing scheme cannot be interpreted.

  1. Which additional identifier schemes are recorded for this entity and which authority issues each? interoperability
  2. Does each alternate identifier denote the same legal person, or a different unit such as an establishment, VAT group or branch? relationship
  3. What is the precedence order when alternate identifiers disagree with the authoritative register record? decision
  4. How is a global identifier's own registration status reconciled with the underlying register record? state

Names and designations

The registered legal name, its variants across scripts and uses, and its dated history.

Legal name, variants and name history

The legal name exactly as recorded by the authoritative register, plus typed variants (transliterations, trading names, abbreviations, previous legal names) each with dated validity and an evidencing filing. Reference-data formats keep other names and transliterated names in separate typed containers because collapsing them destroys the distinction between the legally operative name and a convenience label.

  1. What is the legal name exactly as recorded by the authoritative register, including script, diacritics and legal-form suffix? definition
  2. Which other names are recorded and how is each typed? classification
  3. When did each name become effective, when did it cease, and what filing evidences the change? temporal
  4. Does the register enforce name uniqueness, and is the name reserved or in dispute? constraint

Legal form and classification

The constitutive legal form and jurisdiction, and the categorical and activity classifications applied to the record.

Entity legal form and jurisdiction of formation

The legal form under which the entity exists and the jurisdiction whose law constitutes it. These are interdependent: a legal form has meaning only under local legislation, which is why the governed code list carries local-language names and why a Dutch BV must not be normalised into a German GmbH. Sub-national formation jurisdictions are the norm in federal states.

  1. Under which jurisdiction's law was the entity formed, at what sub-national level, and how is that coded? spatial
  2. What is the entity's legal form, expressed both as a local-language name and as a governed code? classification
  3. Has the legal form changed over time, and what conversion event caused the change? lifecycle
  4. If no governed code exists for the form, which placeholder and free-text value are used? exception

Entity category and economic activity classification

The structural category of the registration record (general entity, branch, fund, sole proprietor, resident government entity, international organization) and the declared economic activity codes. Category is not cosmetic: it changes which registration rules apply and how other fields must be read, and public-authority policy has repeatedly added categories rather than treating them as free text.

  1. What category and sub-category does this registration record fall into? classification
  2. Which economic activity classification codes are recorded, under which scheme and version? classification
  3. Is the declared activity self-reported or verified, and how often is it refreshed? evidence
  4. Does the category change the applicable registration rules or the meaning of other fields? constraint

Legal personality and capacity

A registered legal person is a juristic person distinct from its members, able to acquire rights and assume obligations in its own name. UNCITRAL treats this as affirmative asset partitioning and recommends that members are not personally liable solely by reason of membership. UNCITRAL insolvency guidance adds that a corporation obtains personality by a legal process and enjoys perpetuity independent of changing members. ISO 17442 requires the party to have the legal right in its jurisdiction to enter independently into legal contracts.

  1. Does this subject have legal personality distinct from its members or controllers under the law of the formation jurisdiction? definition
  2. Which capacities does the law confer on this legal person, and are any of them restricted by statute, objects or duration? constraint
  3. Are members or shareholders shielded from the entity's debts solely by reason of membership, and under which legal form rule? classification
  4. At what event time did legal personality attach, and is registration constitutive or merely declaratory in this jurisdiction? lifecycle
Register and registration authority The authority that keeps the register, what the register legally accomplishes, and the dated act of registration with its ongoing filing obligations.

Registration authority and register scope

Identification of the authority and register instance, and the legal effect of entry.

Registration authority identification

Identification of the organization operating the register, the specific register instance, its statutory mandate and its territorial or sectoral coverage, distinguishing a constitutive registration authority from a validation-only source. The existence of a governed list of more than a thousand registers across 232 jurisdictions shows that 'the register' is never inferable from the country alone.

  1. Which organization operates the register, and under what statutory mandate? authority
  2. Which coded entry from a governed registration-authority list applies, and at what list version? identity
  3. Does the register cover the whole jurisdiction, or only a sub-national or sectoral segment? spatial
  4. Is this source constitutive for registration, or is it consulted only to validate? authority

Register legal effect: constitutive versus declaratory

What entry on the register legally accomplishes: whether legal personality arises from registration or is merely recorded, from when disclosed particulars are opposable to third parties, what liability or warranty the register accepts, and whether parallel registers can conflict. This distinction determines whether absence from a register is evidence of non-existence or merely of non-disclosure.

  1. Does registration create legal personality, or record an entity that already exists? definition
  2. Which particulars are opposable to third parties once disclosed, and from when? authority
  3. What is the register's liability regime for inaccurate entries, and is the data warranted? constraint
  4. Are there parallel registers in the same jurisdiction whose entries could conflict? exception

Registration act and filings

The dated act of registration, the currency of the record, and the recurring disclosure obligations that maintain it.

Registration act dates and record currency

The dated act of registration and how current the record is: entity creation date, the register's own initial registration date, last update, next renewal or confirmation date, and — critically — the separation of event time, register-recorded time and our observation time. Reference-data formats keep creation date and initial registration date as distinct fields precisely because they routinely differ.

  1. What is the entity creation date, and how does it differ from the register's initial registration date? temporal
  2. When was the register record last updated, and when did we last observe or retrieve it? provenance
  3. What periodic confirmation or renewal obligation applies, and when is it next due? process
  4. How are date-only register values reconciled with timestamped ingestion records? temporal

Mandatory disclosure particulars and filing obligations

The particulars and documents the entity must disclose to the register at formation and on a recurring basis, the consequence of default, and the disclosure level applied to each. EU company law makes disclosure through national registers compulsory and interconnects it cross-border, while registry guidance treats the minimum registration dataset as a deliberate policy choice rather than a technical accident.

  1. Which particulars must be disclosed at registration under the applicable law? requirement
  2. Which documents must be filed and how frequently? process
  3. What happens when a filing is late or missing, and how is that reflected in the record? exception
  4. Which filings are publicly disclosed in full and which only as metadata? access
Lifecycle, status and events The state of the entity and of its record, the dated events that change them, and the end and possible restoration of registered existence.

Status and standing

The two independent status axes and the softer signals of standing that precede a formal status change.

Registration status and entity status

Two distinct axes that must not be conflated: the legal state of the entity in the register (active, dissolved, in liquidation, converted), and the state of the registration record as a data object (published, pending, lapsed, retired, duplicate). An entity can be perfectly alive while its identifier record has lapsed, and a record can remain published after the entity is dissolved.

  1. What is the entity's status in the authoritative register and which code list defines it? state
  2. What is the status of the registration record as a data object, independent of the entity's legal state? state
  3. Which status transitions are legally possible, and which are terminal? lifecycle
  4. What supplementary status detail qualifies the headline status? state

Compliance standing and involuntary removal risk

Signals of standing short of a formal status change: overdue filings, published proposals to strike off or dissolve, disputed registered office, insolvency-history and charges flags, and administrative penalties. These are leading indicators an operating agent must act on before the status field changes.

  1. Are there active proposals to strike off, dissolve or suspend the entity, and when were they published? state
  2. Which filings are currently overdue and by how long? measurement
  3. Does the record carry flags for insolvency history, registered charges, or a disputed registered office? quality
  4. What remediation restores good standing, and by when? process

Legal entity events and succession

Dated typed events that change registered facts, including those that create, absorb, transform or end legal persons.

Legal entity event record and effective dating

Discrete typed events recorded with an effective date in the legal jurisdiction, a date recorded by the register, a completion status and supporting validation documents. Public-authority policy explicitly separates events that alter reference data from those that retire or create identifiers, and prioritises frequent events such as name changes and mergers over rare ones such as reverse takeovers.

  1. What type of legal entity event occurred, per a governed event type list? event
  2. What is the event's effective date in the jurisdiction, the date the register recorded it, and the time we ingested it? temporal
  3. What is the event's completion status? state
  4. Which documents validate the event and which fields does it change? evidence

Succession: merger, division and conversion

Events that create, absorb or transform legal persons and the predecessor/successor links they generate, including cross-border operations where two registers must notify each other. Organization vocabularies model this as change events with original and resulting organizations rather than as an in-place update, which is the only representation that survives later audit.

  1. Which predecessor and successor entities are linked by this event, and by which identifiers? relationship
  2. Is the operation a merger by absorption, a merger by formation, a division, a spin-off or a conversion? classification
  3. Does the operation cross jurisdictions, and which registers must notify each other? interoperability
  4. Does the entity's identifier survive the operation, or is a new one assigned and the old one retired? identity

Dissolution, liquidation and restoration

The end and possible reinstatement of registered existence: voluntary and compulsory dissolution, liquidation and insolvency proceedings with appointed office-holders, deregistration, and restoration to the register. Restoration is a genuine counterexample to naive terminal-state modelling: a dissolved entity can be brought back, so 'dissolved' is not always absorbing.

  1. On what date and on what ground did registered existence end? lifecycle
  2. Which insolvency or liquidation proceeding is open, who is the appointed office-holder, and what are its dates? process
  3. Can the entity be restored or reinstated, under what conditions and within what period? exception
  4. What happens to the record and its identifiers after dissolution? retention
Jurisdiction, place and cross-border presence Addresses recorded by the register, and the entity's registered footprint beyond its jurisdiction of formation.

Registered addresses

Addresses of record and their legal roles.

Registered office and address set

The addresses attached to the registration record: the legal or registered address that has legal effect for service of documents, the headquarters address, and other recorded addresses — all distinguished from operating sites. Registers publish an explicit flag when a registered office is in dispute, which shows the address is a contested legal fact rather than descriptive metadata.

  1. What is the legal or registered address of record and which components does the register mandate? spatial
  2. How does the registered address differ from the headquarters address and from operating sites? composition
  3. Is the address usable for legal service, and is it a third-party or agent address? authority
  4. Is the recorded address disputed, unverified or subject to change proceedings? quality

Cross-border presence

Branch registration, seat transfer and authorization to operate outside the jurisdiction of formation.

Branch and establishment registration

Registration records for branches and establishments that are not separate legal persons but carry their own register entries, identifiers and disclosure duties in a host jurisdiction. Relationship data recognises an international branch relationship as a distinct type, and national registers hold explicit branch and foreign-company sub-structures pointing back to the home register.

  1. Is this record a branch or establishment rather than an autonomous legal person, and which head office does it belong to? classification
  2. Which host-jurisdiction register holds the branch record and what identifier does it assign? identity
  3. Which particulars must the branch disclose locally versus rely on from the head office register? requirement
  4. How is closure or dissolution of the head office propagated to the branch record? event

Redomiciliation and foreign qualification

Transfer of the registered seat between jurisdictions, and authorization to do business in jurisdictions other than that of formation, with or without continuity of legal personality. Register status vocabularies carry values for transfer out of the jurisdiction, confirming that jurisdiction of formation is a dated fact rather than a constant.

  1. Has the entity transferred its registered seat, from which jurisdiction to which, and on what date? lifecycle
  2. Is legal personality continuous across the transfer, or was the entity re-formed? definition
  3. In which additional jurisdictions is the entity qualified or authorized to do business, and under what identifier? spatial
  4. Which identifiers are retired, retained or newly assigned as a result? identity
Relationships, control and representation Structural links between registered entities, the linkage to control and ownership mechanisms, and who may bind the entity.

Group and parent relationships

Reported structural links between registered entities, with periods, evidence and exceptions.

Parent, group and structural relationships

Links between registered entities as reported to registers and identifier systems: direct and ultimate accounting-consolidating parents, international branch to head office, and fund, sub-fund and feeder-to-master links. Each carries a validity period, an accounting or document-filing period, a corroboration level and, where no parent is reported, a coded reporting exception. Consolidation-based parenthood is not the same as legal ownership and must not be presented as such.

  1. Which direct and ultimate consolidating parents are reported, and by which identifiers? relationship
  2. Over what period is each relationship valid, and which accounting or filing period does the evidence cover? temporal
  3. What corroboration level supports the relationship and which documents validate it? evidence
  4. If no parent is reported, which reporting exception applies? exception
  5. How does this reported relationship differ from a statistical enterprise group? interoperability

Control, representation and ownership linkage

The pointer to control information and the registration facts about who may act for the entity.

Beneficial ownership register linkage

The pointer from the registration record to the mechanism holding beneficial ownership or persons-with-significant-control information, its holding mechanism type and its access regime — the linkage only, never the ownership content. International standards allow a registry or an alternative mechanism, and the access regime is materially narrower than for core company particulars and has been changed by litigation and by national rule changes.

  1. Which mechanism holds beneficial ownership information for this entity? composition
  2. What identifier links the registration record to the beneficial ownership record? identity
  3. Who may access the beneficial ownership record, and on what legal basis? access
  4. How current must the linked information be, and when was it last confirmed? quality

Officers and authority to represent

Registered officers and representatives and the derived question of who may validly bind the entity, recorded as dated registration facts plus evidence of authority for a specific act. Registers publish suppression regimes for officer details, so the presence of a role does not guarantee the presence of the person's particulars.

  1. Which officer or representative roles are recorded in the register, with what appointment and cessation dates? ownership
  2. What representation rule applies — sole, joint, or limited by class of act — and where is it stated? authority
  3. How is authority to act evidenced for a specific transaction, and when was it verified? evidence
  4. Are any officer details suppressed or protected, and under what regime? privacy
Evidence, verification and quality What proves each registration fact, how strongly it was corroborated, and how discrepancies are detected and resolved.

Evidence and validation

Documentary evidence for registration facts and the strength of their corroboration.

Registration evidence documents and extracts

Documents that evidence registration facts — certificates of incorporation or good standing, dated register extracts, gazette publications and cross-border company certificates — each speaking as of a point in time and each requiring authentication before reliance. Extracts age: an extract is a dated snapshot, not a standing truth, which is why an as-of timestamp and a freshness window are mandatory.

  1. Which document evidences each registration fact, and who issued it? evidence
  2. As of what date do the extract's contents speak, and how long is it treated as current? temporal
  3. Is the document authenticated, and how is authenticity checked? validation
  4. Is a translation or legalization required for cross-border use? interoperability

Validation sources and corroboration level

How each recorded fact was validated: which source was consulted, what role it plays, which validation authority and local identifier were used, and what corroboration level was achieved. Corroboration is graded, not binary, and the grade must travel with the data.

  1. Which source was consulted to validate each field, and is it the authoritative register or a secondary source? provenance
  2. What corroboration level does the record achieve? quality
  3. Which validation authority and which local identifier were used for corroboration? authority
  4. How often must validation be repeated and what triggers re-validation? process

Quality and conflict management

Detecting, reporting and resolving divergence between the register record and other sources.

Data quality, discrepancies and challenge process

Detection, reporting and resolution of divergence between the register record and other authoritative or self-reported sources, including statutory discrepancy-reporting duties on obliged entities and the register's own correction or challenge procedure. Unresolved conflicts must be represented explicitly rather than silently resolved by picking a value.

  1. Which discrepancies exist between the register record and other sources? quality
  2. Is there a duty to report the discrepancy, to whom, and within what deadline? requirement
  3. What process corrects an erroneous register entry, and who may initiate it? process
  4. Which quality checks run automatically and at what thresholds? validation
  5. How is an unresolved conflict represented so downstream consumers are not misled? decision
Governance, access, provenance and retention Who may see what, how personal data in register records is handled, how every assertion is attributed, and how long records must survive.

Access, publicity and privacy

Disclosure tiers and the handling of personal data within registration records.

Public disclosure tiers and access conditions

Who may see what: the free-to-all core that registry guidance says should be available to everyone without discrimination and at low or zero cost, versus fee-bearing, registration-gated, legitimate-interest and competent-authority-only tiers. Reuse licence conditions attach to disclosed data and constrain redistribution.

  1. Which fields and documents are public without restriction, and which require registration, fee or a legitimate-interest test? access
  2. Which categories of requester are recognised and how are they authenticated? security
  3. What licence or reuse conditions attach to the disclosed data? ownership
  4. What must be logged when restricted content is accessed? evidence

Personal data in registration records

Personal data unavoidably present in registration records — officers, agents, and registered addresses that are also private residences — and the constraints that follow. Settled case law holds there is no general right to erasure from a companies register even after the company ceases to exist, because no suitable maximum retention period can be identified, while a case-by-case right to object may exist; suppression regimes operate as the practical remedy.

  1. Which fields in the registration record contain personal data, and whose? privacy
  2. Which suppression, protection or redaction regimes are available, and how are they flagged? exception
  3. Can a data subject obtain erasure or restriction, and what is the settled position? retention
  4. How is personal data handled when the record is redistributed or cached downstream? security

Provenance, retention and interoperability

Attribution of every fact to its source and time, survival of the record over time, and alignment to external vocabularies and exchange protocols.

Provenance, source attribution and observation time

Full attribution of every recorded fact to its source, retrieval method, retrieving agent and time, keeping three clocks separate: when the event took legal effect, when the register recorded it, and when we observed it. Collapsing these makes it impossible to reconstruct what was knowable at a past decision point.

  1. From which source system, endpoint or file was each fact obtained, and at which version? provenance
  2. What are the event time, the register's recorded time and our observation time for each fact? temporal
  3. Which agent performed the retrieval and under what authorization? authority
  4. How is the retrieved payload preserved so the assertion can be re-checked later? evidence

Record history, retention and deletion constraints

How prior states are kept, how long records survive dissolution, and where deletion is constrained. Public-authority policy for the global identifier system requires data history alongside events, and case law establishes that no single maximum retention period can be identified for register data, so retention must be declared per jurisdiction rather than assumed.

  1. Which historical versions of the record are retained and at what granularity? retention
  2. For how long after dissolution must the record be retained, and by whom? retention
  3. Under what circumstances may data be deleted or de-published, and what tombstone remains? exception
  4. How are retention conflicts between register duties and privacy demands resolved? decision

Interoperability mappings and exchange projections

Alignment of this model to external vocabularies and exchange protocols, recorded as version-pinned mappings with explicit conflicts rather than conformance claims. Register-to-register exchange uses service-based electronic communication with standard protocols and defined message types, which the model must be able to feed without becoming coupled to any one of them.

  1. Which external vocabularies and schemas is this model aligned to, and at which versions? interoperability
  2. Which fields map cleanly, which map with loss, and which have no counterpart? validation
  3. Which register-to-register or downstream exchange protocols must be supported, and what message types do they define? process
  4. Where do external models conflict semantically, and how is the conflict recorded rather than hidden? decision

Classifiers Filled

Family
World Models
Category
Society, people and institutions
Entry kind
entity
Navigation path
NAV.SOC.ORG.REG
Domain
SOC.ORG.REG
Industry
Cross-industry
Tags
legalentityregistrationsoc.org.reg

What it is Filled

In scope is the registration record of a legal person (and of branches that carry their own register entries): the authoritative register and its assigned identifier, legal name and name history, legal form and jurisdiction of formation, registered addresses, registration and entity status, dated legal entity events including succession and dissolution, structural relationships as reported to registers, evidence and validation of those facts, cross-scheme identifier alignment, and the governance of the record (provenance, access tiers, retention, interoperability). Out of scope is anything that is a fact about the organization's operation, ownership content, finances or authorizations rather than about its registered legal existence.

In scope

  • Authoritative register identity: registration authority, register-assigned entity identifier, and qualified alternate identifiers such as LEI, EUID and ISO/IEC 6523-scoped scheme identifiers
  • Legal name, transliterations, trading and previous names with dated validity
  • Entity legal form (ISO 20275 ELF) and jurisdiction of formation at country and subdivision level
  • Registered/legal address, headquarters address and other addresses recorded by the register
  • Registration status, entity status, status detail and compliance standing signals such as strike-off proposals and overdue filings
  • Dated legal entity events: name change, legal form conversion, merger, division, spin-off, seat transfer, dissolution, liquidation, restoration, with effective and recorded dates
  • Branch and establishment registration records and their head-office linkage
  • Structural relationships as reported to registers: consolidating parents, branch/head-office, fund and feeder relationships, with validation level and reporting exceptions
  • Evidence artifacts: certificates, dated register extracts, gazette notices, filings and their authentication
  • Validation sources, corroboration levels, discrepancy detection and register correction processes
  • Access tiers, licence conditions, personal-data handling, retention and deletion constraints on register records
  • Interoperability mappings to external organization vocabularies and register-to-register exchange

Out of scope

  • Internal organizational structure, units, posts, headcount and reporting lines (parent organization model)
  • Beneficial ownership and control content, including natural-person particulars; only the linkage and access classification are in scope
  • Financial statement content, accounting figures and audit opinions, even when filed with a register
  • Sector authorizations, licences, permits and regulatory registrations that do not constitute legal existence
  • Tax assessment, returns and fiscal compliance; only the fiscal identifier as an alternate identifier is in scope
  • Statistical units (enterprise, enterprise group, local unit, kind-of-activity unit) and business demography
  • Trademarks, brands and domain names
  • Contracts, credit ratings, sanctions listings and adverse media
  • Natural-person identity records and employment relationships
  • Physical premises management, geocoding and facility operations

Why it exists Filled

Model the legal identity of an organization as constituted and recorded by an authoritative register or registration authority in a jurisdiction, so that an agent can identify, verify, monitor and operate on registered legal persons without conflating them with the organizations, groups or statistical units they relate to.

Distinguishing features Filled

  • The legal identity of an organisation as constituted by a register in a jurisdiction.
  • Unlike the organisation model, it does not model internal structure.
  • Unlike a statistical unit, it follows legal personality, not economic activity.
  • Keeps entity status and record status as distinct values.

What robots and AI may and may not do Filled

Must not

  • Store facts without a validation source and timestamp.
  • Delete records after dissolution.
  • Redistribute personal data beyond licence.
  • Merge conflicting register data silently.
  • Present record status as entity status.

Only with a human decision

  • Reporting a discrepancy to a registration authority.
  • Linking entities where identity is uncertain.

May

  • Resolve and validate registration identifiers.
  • Ingest register records with provenance.
  • Compute status as of a given time.
  • Detect and report discrepancies between registers.

Moral aspects Filled

  • Register data names directors and officers; redistribution must respect privacy rules.
  • Wrong status can block a business from trading or contracting.

Who is affected

  • Registered entities
  • Directors and officers named in registers
  • Counterparties relying on registration

Owners Filled

Steward

Name a single accountable owner package for WM-ORG-010 and declare, per jurisdiction, which register it treats as authoritative and whether that register is constitutive or declaratory.

Roles

Registration Data Steward
Own the correctness of registration records within assigned jurisdictions and adjudicate discrepancies raised against them.; Approve identity resolutions, duplicate merges and identifier retirements.; Maintain the jurisdiction coverage statement and its production or best-effort classification.
Register and Jurisdiction Liaison
Track changes to register law, fee schedules, access regimes and published code lists in covered jurisdictions.; Pin and roll forward external code-list versions, producing migration mapping tables.; Record the constitutive versus declaratory characterisation and liability regime for each register.
Evidence and Verification Officer
Define required evidence types, freshness windows and authentication methods per use case.; Verify authenticity of certificates and extracts and record verification results with timestamps.; Set and review corroboration-level thresholds for downstream reliance.
Access and Privacy Controller
Classify every field and artifact type into an access tier and keep classifications current with legal change.; Approve exceptions, evaluate legitimate-interest tests and enforce suppression regimes.; Review access audit logs and investigate bulk-extraction alerts.
Interoperability Mapping Maintainer
Maintain version-pinned mappings to external vocabularies and exchange protocols, with per-field fidelity and loss reports.; Publish and review the semantic conflict list rather than silently resolving conflicts in mappings.; Validate that projections remain regenerable from canonical assertions.
Automated Ingestion Agent
Retrieve register records and exports under authorized credentials and within licence terms.; Write assertions with full provenance and preserve snapshot artifacts with content hashes.; Halt and escalate rather than guess when a source schema, code list or access regime changes unexpectedly.

Links to other meta-models Filled

child

  • WM-ORG-001 Organization (registered parent model) - WM-ORG-010 specialises the parent organization concept to the subset that has registered legal status, mirroring the org:Organization to org:FormalOrganization to rov:RegisteredOrganization narrowing. The parent owns organization identity in general; this model owns the registration facts.

references

  • Beneficial ownership and control model (sibling) - Hold ownership and control content, including natural-person particulars, under its own access regime. This model carries only the pointer, holding-mechanism type and access tier.
  • Jurisdiction and geopolitical unit model (sibling) - Resolve country and subdivision codes, jurisdictional hierarchy and the legal systems that give legal forms their meaning; legal form and jurisdiction are interdependent and must resolve against a governed jurisdiction set.
  • Natural person and party identity model (sibling) - Resolve officers, representatives and registered agents to person records without importing person identity or employment semantics into the registration record.
  • Tax registration and fiscal identifier model (sibling) - Own fiscal registration, assessment and compliance. This model carries tax and VAT numbers only as scheme-qualified alternate identifiers and makes no inference about tax status from business-register presence.
  • Regulatory licence and authorization model (sibling) - Own sector authorizations that condition conduct rather than constitute existence, preventing licence withdrawal from being read as loss of legal personality.
  • ISO/IEC 6523 identifier scheme registry - Supply the scheme codes that qualify alternate organization identifiers, without which an identifier value cannot be interpreted or compared.

composes

  • Postal address and location model (sibling) - Supply the structured address type used for legal, headquarters and other recorded addresses, and own geocoding and premises identity, which are outside registration scope.
  • Document and evidence model (sibling) - Own generic document lifecycle, storage, rendering and signature verification, so that certificates, extracts, filings and gazette notices are typed evidence here rather than duplicated document machinery.
  • Provenance and observation mixin - Apply uniform source attribution, retrieving-agent identity, and the separation of event time, source-recorded time and observation time to every assertion in this model.
  • Bitemporal versioning and history mixin - Provide append-only assertion history with validity and transaction intervals, which the legal entity events and data history requirement depends on.

aligned

  • Statistical business register unit model (sibling) - Declared boundary alignment: the enterprise, enterprise group, local unit and kind-of-activity unit are constructed from legal units but are not legal units. Mapping is one-to-many in both directions and must be recorded, not assumed.
  • ISO 20275 Entity Legal Forms code list - External governed classifier for legal form, referenced with an explicit version because codes and jurisdictions are added between releases.
  • W3C Registered Organization Vocabulary and Organization Ontology - Declared alignment for export and linked-data projection. Mapping is partial: RegOrg lacks the register-authority qualification and event history this model requires, and its status remains a Working Group Note.
  • GLEIF LEI-CDF and RR-CDF reference data formats - Declared alignment for entity and relationship reference data exchange, version-pinned to LEI-CDF 3.1 and RR-CDF 2.1; alignment is not a conformance claim and holds only for entities within the identifier system's eligibility scope.

neighbor

  • WM-ORG-001 Organization (parent model) - The parent models any organization, including informal, unregistered and purely internal ones. WM-ORG-010 models only the subset that has acquired or claims registered legal status, and only the facts that the register constitutes or records. W3C ORG makes the same cut with org:FormalOrganization, which RegOrg further narrows to rov:RegisteredOrganization for entities that gained legal entity status through formal registration.
  • Statistical business register unit model (enterprise, legal unit, enterprise group) - A legal unit is not an enterprise. Statistical frameworks define the enterprise as the smallest set of legal units with autonomy in financial and investment decisions, so a single enterprise may span several registered legal persons and a registered legal person may be only part of an enterprise. WM-ORG-010 stops at the registered legal unit and delegates statistical unit construction, demography and continuity rules elsewhere.
  • Beneficial ownership register model - Beneficial ownership is held in a separate mechanism with a different legal basis and a materially different access regime; unrestricted public access to beneficial ownership data was struck down in the EU, whereas core company particulars remain publicly disclosable. Only the pointer, holding mechanism and access tier belong here.
  • Global LEI System (GLEIF/LEI issuers) - An LEI is a governed global identifier layered on top of a register record; GLEIF and its issuers are not registers of formation. LEI reference data explicitly cross-references the local business register through a registration-authority code and a local entity identifier, which confirms that the register, not the LEI, is the master identity source.
  • Tax registration and fiscal identifier model - Tax numbers, VAT numbers and employer identification numbers are usually assigned by a different authority under a different act; being on a business register does not imply tax registration and vice versa. They are carried here only as qualified alternate identifiers, scheme-tagged so they cannot be mistaken for the register identity.
  • Branch / establishment as an organization site - A branch is not a separate legal person, but in many jurisdictions it holds its own register entry, identifier and disclosure duties, and LEI relationship data recognises IS_INTERNATIONAL_BRANCH_OF as a distinct relationship. Branch registration records are therefore in scope, while branch premises and operations are not.
  • Regulatory licence and authorization model - Authorization to carry on a regulated activity is granted by a supervisor and can be withdrawn without ending legal existence. Registration constitutes or records existence; licensing conditions conduct. Conflating them makes an entity appear dissolved when it has merely lost a permission.
  • Document and evidence model - Certificates, extracts and filings are modelled here only as evidence bound to registration facts, with issuer, as-of date and authentication. Generic document lifecycle, storage and rendering belong to a composable document model.

parent

  • WM-ORG-001

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identifier assigned by the authoritative master system — the registration authority code paired with the register-assigned entity identifier, both stored with the authority-list version used to validate them.
  • Governed global identifier or IRI where one exists, such as a legal entity identifier, a cross-border register identifier, or an ISO/IEC 6523 scheme-qualified organization identifier; recorded as an alternate identity with an explicit equivalence assertion, never substituted for the register identity.
  • UUID or ULID assigned by the adopting Dimension, used only when neither of the above is obtainable, flagged as locally assigned, and replaced by an authoritative identifier as soon as one is resolved, with the local identifier retained as a historical alias.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • A registration has a registration authority, an entity identifier, a legal name, a legal form, a jurisdiction and a status.
  • Often confused with an organisation, a branch, a tax registration and a beneficial owner record.

Capabilities and actions required Filled

  • Resolve registration identity: Resolve a candidate organization description to a single authoritative register record, or report that no confident resolution exists.
  • Validate identifier syntax and scheme: Check that an identifier conforms to the format and any checksum defined by its scheme, and that the scheme code itself is known.
  • Ingest register record with provenance: Retrieve a register record or bulk export and store it as timestamped assertions with full source attribution.
  • Apply legal entity event: Record a typed legal entity event and derive the field changes, identifier retirements and successor links it implies.
  • Compute current status as of a time: Return the entity status, record status and standing signals that were true as of a given instant, using the stored assertion history.
  • Request and verify registration evidence: Obtain a dated extract or certificate and verify its authenticity and freshness before it is relied on.
  • Link alternate identifier: Attach an identifier from another scheme to the registration record with an explicit equivalence assertion and evidence.
  • Detect and report discrepancy: Compare the register record with other held sources, classify divergence and discharge any statutory reporting duty.
  • Evaluate access request against tier: Decide whether a requester may read specified fields, documents or artifacts, and produce the audit record.
  • Project record to an exchange format: Render the format-neutral record into a named external vocabulary or exchange message, declaring what is lost.
  • Close or supersede a registration record: Close a record on dissolution, transfer out or supersession, retaining a tombstone and honouring retention duties.
  • Update register particulars: File and publish changes to name, registered office, representatives, capital, objects, legal form or other disclosed particulars, with event-effective time distinct from filing time.

Hazards and failure modes required Filled

  • Fraud with stale or fake entities.
  • Privacy breaches.
  • Wrong counterparty.

Standards and interfaces required Filled

  • ISO 17442 LEI.
  • ISO 20275 Entity Legal Forms.
  • GLEIF Registration Authorities List.
  • W3C Registered Organization Vocabulary.

Context of use required Filled

  • The model assumes a jurisdiction has at least one identifiable registration authority. This fails where a legal form arises without registration, and the fallback identity path exists specifically for that case.
  • EU-specific structure — cross-border register interconnection, a European unique identifier, and a cross-border company certificate — is treated as one regional realisation of register interoperability, not as the universal pattern.
  • The United States has no single national company register; formation is state-level and there is no federal equivalent to a national commercial register. The registration authority code must therefore resolve to a state office, and any model assuming one register per country will break here.
  • Sub-national jurisdiction coding is assumed necessary, not optional, because federal and devolved systems routinely register at that level; a national register's jurisdiction field with devolved values illustrates this.
  • Local-language legal form names are assumed authoritative and untranslatable; translation is a convenience layer, never a substitute for the local name and its code.
  • Restoration or reinstatement after dissolution is assumed to exist in some jurisdictions and not others; the model does not treat dissolution as universally absorbing.
  • Register access regimes are assumed to differ by jurisdiction and to change; a single global access classification is not assumed anywhere in the model.
  • Non-Latin script and transliteration handling is assumed necessary, following reference-data formats that carry separate transliterated name and address containers.
  • EU Directive 2017/1132, EUID and BRIS are a regional profile applied when the entity is an EU/EEA registered company or branch, not a global default.
  • GLEIF RA and ELF lists are globally broad (232 jurisdictions / 200+ jurisdictions) but still incomplete; absence from a list is a gap, not proof that no register or form exists.
  • Common-law registered-office-plus-registered-agent patterns and civil-law notarial constitutive deeds both map to the same address and instrument findings with different formation_theory codes.
  • FATF 'company registry' language is applied mutatis mutandis to other legal persons as INR 24 footnote 68 requires, without pretending every foundation or cooperative uses a companies house.

Sources Filled

  1. Level 1 Data: LEI-CDF Format — Common Data File Formats - Global Legal Entity Identifier Foundation (GLEIF)
  2. LEI-CDF Version 3.1 — Documentation - Global Legal Entity Identifier Foundation (GLEIF)
  3. GLEIF Registration Authorities List - Global Legal Entity Identifier Foundation (GLEIF)
  4. ISO 20275 Entity Legal Forms (ELF) Code List - Global Legal Entity Identifier Foundation (GLEIF), Maintenance Agency Secretariat for ISO/TC 68
  5. Level 2 Data: Relationship Record (RR) CDF Format - Global Legal Entity Identifier Foundation (GLEIF)
  6. The Organization Ontology - World Wide Web Consortium (W3C)
  7. Registered Organization Vocabulary - World Wide Web Consortium (W3C), from the European Commission ISA Core Business Vocabulary
  8. Companies House Public Data API — company profile resource - Companies House (United Kingdom)
  9. UNCITRAL Legislative Guide on Key Principles of a Business Registry - United Nations Commission on International Trade Law (UNCITRAL)
  10. Company law and corporate governance - European Commission
  11. ROC Policy on Level 1 Data — Legal Entity Events and Data History in the Global LEI System - Legal Entity Identifier Regulatory Oversight Committee (LEI ROC), published via GLEIF
  12. Organization — schema.org type - Schema.org Community Group (W3C)
  13. ISO 6523 ICD code list — Peppol BIS Billing 3.0 - OpenPeppol
  14. Commission Implementing Regulation (EU) 2021/1042 laying down rules for the application of Directive (EU) 2017/1132 as regards technical specifications and procedures for the system of interconnection of registers - European Union (Official Journal, via EUR-Lex)
  15. Press release No 188/22 — Judgment of the Court in Joined Cases C-37/20 and C-601/20, WM and Sovim SA v Luxembourg Business Registers - Court of Justice of the European Union
  16. Guidelines on Statistical Business Registers - United Nations Economic Commission for Europe (UNECE), Conference of European Statisticians
  17. Beneficial Ownership Information Reporting - Financial Crimes Enforcement Network (FinCEN), U.S. Department of the Treasury
  18. Guidance on Beneficial Ownership of Legal Persons (Recommendation 24) - Financial Action Task Force (FATF)
  19. CJEU — C-398/15 — Manni (case analysis) - GDPRhub (noyb-supported case-law wiki)
  20. ISO 17442-1:2020 Financial services — Legal entity identifier (LEI) — Part 1: Assignment - International Organization for Standardization
  21. LEI-CDF Version 3.1 documentation and Level 1 Data: LEI-CDF Format 3.1 - Global Legal Entity Identifier Foundation
  22. Directive (EU) 2017/1132 relating to certain aspects of company law (codified, consolidated) - European Parliament and Council of the European Union
  23. The FATF Recommendations — Recommendation 24 and Interpretive Note (Transparency and beneficial ownership of legal persons) - Financial Action Task Force
  24. UNCITRAL Legislative Guide on Limited Liability Enterprises - United Nations Commission on International Trade Law
  25. Global LEI System - Legal Entity Identifier Regulatory Oversight Committee
  26. UNCITRAL Legislative Guide on Insolvency Law - United Nations Commission on International Trade Law
  27. Commission Implementing Regulation (EU) 2020/2244 laying down technical specifications and procedures for the system of interconnection of registers - European Commission
  28. GLEIF Base Ontology - Global Legal Entity Identifier Foundation

Open questions

  • EUID and BRIS as an explicit EU regional profile overlay (Grok SRC-003, SRC-010): EUID composition, the no-centralised-database constraint on the central platform, and the branch-disclosure and cross-border-merger notification message types — to be modelled as a jurisdiction profile bound to the base's interoperability layer, not as core structure.
  • Registered capital, subscribed versus authorised capital, share classes, bearer shares and nominee shareholder or director arrangements: confirm the split between the capital and securities sibling model and the beneficial-ownership sibling, and decide where the FATF transparency-obstacle mitigations attach.
  • Stated objects, entity duration and the notified location of the shareholder or member register: these are register-disclosed in many jurisdictions and are currently unowned by any model in the set; decide whether they belong here as registration facts or to the capital and governance siblings.
  • Administrative strike-off, restoration, reinstatement and dormancy: both providers record that global instruments do not specify these and that they are nationally common. Needs national-profile research (UK, US states, Australia) to ground the base's claim that dissolution is non-absorbing within a jurisdiction-specific window.
  • Judicial declaration of nullity of a company: primary-text grounding for its disclosure requirement, its retroactive effect on acts already performed, and whether it belongs in the event-type vocabulary as a distinct type or as a ground under termination of registered existence.
  • FATF 'sufficient links' test for foreign-created legal persons, and how it interacts with the base's foreign-qualification and redomiciliation structure — currently only partially extracted by Grok and absent from the base.
  • Register fee schedules and cost-of-access economics, declared a gap by the base: determine whether any primary source enumerates them across jurisdictions or whether the gap must remain declared.
  • Whether Vercy models the registrar role at all: the rejected formation and disclosure functions imply a second actor perspective. Decide explicitly, because accepting it later would change the model's purpose statement rather than extend it.
  • Sole traders, partnerships without legal personality and unincorporated associations are only partially addressed. They appear as an entity category and are within registry-guidance scope, but the model is built around registered legal persons, and jurisdictions differ on whether such entities register at all.
  • Trusts and other legal arrangements are deliberately excluded. They are governed by a distinct international recommendation with different transparency mechanics and would need a sibling model rather than an extension of this one.
  • Charity, cooperative, religious-body and public-body registers are acknowledged as parallel registers but their specific particulars are not enumerated; only the parallel-register conflict question captures them.
  • Fee schedules, filing costs and cost-of-access economics are not modelled beyond gating conditions, as noted in the checklist gap.
  • Registered capital, share structure and share classes are not modelled. They are register-disclosed in many jurisdictions but belong to a capital and securities model.
  • Sanctions listing, export-control designation and politically exposed status are excluded as screening concerns rather than registration facts.
  • Historical registers, pre-digitisation records and jurisdictions where the register is paper-only are not addressed; the ingestion functions assume a retrievable electronic source.
  • Verifiable-credential issuance of registration facts is referenced as an authentication method but its issuance, revocation and trust-chain semantics are not modelled.
  • UNCITRAL Guide on Key Principles of a Business Registry (2018) is cited by the LLE Guide as the dedicated registry-operations instrument but was not independently fetched; operational registry-service design may be thinner than that Guide.
  • Administrative strike-off, restoration to the register, dormancy and administrative revival are nationally common and not specified in the fetched global instruments.
  • United States state secretaries of state, registered-agent statutes, China's Unified Social Credit Code, India's CIN and similar national identifier schemes are not modelled beyond the RA-list binding.
  • Full FATF INR 24 footnotes, verification methods and foreign-person 'sufficient links' tests are only partially extracted.
  • Digital-asset organisations, DAOs and other emerging personality experiments have no primary support in ISO 17442 eligibility as fetched.
  • Islamic waqf, cooperatives, unincorporated associations and mixed public-law bodies are covered only insofar as an ELF code or RA source exists.
  • EU proposal for an 'EU Inc.' 28th-regime corporate form (2026) is not in force and is excluded.
  • ISO 5009 official organisational roles and vLEI role credentials are alignment pointers, not a modelled officer ontology.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-org-010-legal-entity-registration/spec.yaml, ver-cy/world-models/card-supplements/wm-org-010-legal-entity-registration.json