Short answer
Legalcode indexes 30 catalogue pages from the Latvijas Republikas Uzņēmumu reģistrs open-data collection. They describe the core register of legal entities; historical names; officers, owners and capital; insolvency, liquidation, reorganization and restrictions; annual-report financial data; business and organizational activities; and specialist lists such as arbitration courts, political parties and interest representatives.
Each indexed record is reference material about a data.gov.lv package. Fetch can provide the package and resource identifiers, description, licence, update frequency, resource URLs, reported row counts and datastore fields. It does not make the underlying hundreds of thousands—or, for financial resources, millions—of rows searchable as Legalcode entity records.
That distinction is essential. ACTIVE is the catalogue document's status, not a company's legal status. The displayed publication date commonly reflects a catalogue metadata refresh, not the original dataset issuance. A zero Legalcode result for a company name or registration number therefore does not prove that the company is absent from the official open data. The metadata-only scope and its classification/date limitations remain tracked in issue #310.
What the indexed collection actually contains
Production MCP Discovery reports exactly 30 LV_ENTERPRISE_REGISTER records. All are Latvian-language REFERENCE_MATERIAL documents classified under the guidance source type. Search returned the complete set over two pages.
The records are catalogue descriptions. They identify a dataset package and its resources, often including CSV, XLSX or JSON links, declared CC0 licensing, update frequency, row count and field list. This makes the collection useful for source discovery and data-model planning. It is not a company lookup service inside Legalcode.
Entity identity, status and lifecycle datasets
Twelve catalogue entries describe identity and changes over an entity's life:
- the core Enterprise Register;
- historical legal-entity names;
- the registered duration of a legal entity;
- the date of the founding decision recorded in its file;
- reorganizations;
- current liquidation processes;
- activity prohibitions, suspensions and restorations;
- securing measures registered in entity files;
- national-significance special status;
- sanctions-risk information;
- insolvency and legal-protection proceedings; and
- expanded data on branches of foreign merchants.
The says the data cover all registered subjects and are updated daily. Its description states:
Uzņēmumu reģistrs piedāvātos datus aktualizē katru dienu.
—
The fetched schema includes registration code, current name, entity type, registration and termination dates, address and a closed field. Its source-reported CSV count was 485,729 on 4 July 2026.
Ownership, governance and capital datasets
Five entries focus on who controls or represents an entity:
- officers, board members and other authorized representatives;
- members of limited-liability companies;
- shareholders of joint-stock companies;
- beneficial owners; and
- share-capital and investment information.
The reports 280,882 rows and exposes entity registration number, position, governing body, representative name, a masked Latvian identity number, birth date, representation rights and registration/last-modified timestamps.
These schemas show how records can be joined, but the join must be performed against the official data resources. Legalcode currently indexes the package description, not each officer or owner as a separately retrievable entity fact.
Financial and activity datasets
Five more entries cover reporting and activities:
- annual-report financial data;
- objectives and activity types of legal entities;
- fields of activity of associations and foundations;
- farm land area and location; and
- the list of interest representatives.
The is the largest and most internally structured example. It separates statement basics, balance sheets, income statements and cash-flow statements. The catalogue reports 1,974,432 statement-basic rows, 1,851,891 balance-sheet rows, 1,743,299 income-statement rows and 180,029 cash-flow rows as of the reviewed resource metadata.
Its description explains that the package draws on annual reports submitted to the State Revenue Service and transferred to the Enterprise Register for publication. The fields include year, employees, currency, assets, liabilities, equity, turnover, expenses, income and cash-flow components. Those figures are available in the linked source files; they are not four million Legalcode guidance documents.
Institutional and specialist lists
The final eight entries describe:
- political parties and alliances;
- public persons and institutions;
- arbitration courts;
- arbitration founders;
- registration of amendments to arbitration rules;
- property-investment appraisers;
- religious organizations' affiliation and territory; and
- RAIM data.
These datasets broaden the catalogue beyond commercial companies. A credit-risk user should not assume that every entry is a debtor-status source. Some are public-sector or specialist registries whose relevance depends on the precise research purpose.
Insolvency and liquidation are separate datasets
The catalogue distinguishes insolvency from liquidation. The describes insolvency and legal-protection proceedings recorded in the Insolvency Register. Its CSV resource reported 17,929 rows and fields for debtor identity, proceeding dates and type, resolution, court, creditor deadline and legislation.
The source describes its scope as:
Maksātnespējas reģistrā ierakstīto maksātnespējas un tiesiskās aizsardzības procesu informācija.
—
The separately reports current liquidation processes. Its 9,757-row CSV schema includes the entity registration number, liquidation type, start date, grounds and modification time.
A liquidation flag is therefore not automatically an insolvency finding, and an insolvency proceeding may have its own start, end and resolution fields. Any risk report should retrieve the relevant row and date from the correct official resource instead of relying only on the catalogue title.
Registration number is the principal join key
The datasets repeatedly expose a registration-number field: regcode, legal_entity_registration_number, debtor_registration_number or a similarly named variant. That is the safer cross-dataset key. Names can change, be formatted differently or collide.
The makes this explicit by pairing regcode with the former name and the date until which it applied. Its fetched catalogue reported 90,974 CSV rows, while an older XLSX resource showed 80,907. Those resource counts have different freshness and should not be silently treated as equivalent snapshots.
Dates, counts and ACTIVE status
Most MCP records have a displayed publication date of 4 July 2026. Fetch shows that many packages were issued and modified on 1 July 2024, while their catalogue metadata or resources were updated in 2026. The MCP date is therefore useful as a captured metadata-refresh signal, but it is not necessarily the original publication date or the date of every underlying row.
Likewise, status: ACTIVE applies to the indexed reference document. It does not say that an entity is trading, solvent, licensed or free of restrictions. Those conclusions require the relevant current row and its field semantics.
The source-reported counts also describe resources, not Legalcode's record count. CSV and XLSX versions may differ because they were generated at different times. Counts should always be paired with format and last-modified date.
MCP source-quality finding
The audit reproduced the behavior already recorded in : 30 catalogue pages are exposed as guidance/reference material, entity rows are not searchable, document status can be mistaken for entity status, and catalogue-refresh dates can be mistaken for issuance dates. That issue also records unexplained resource-count differences and the absence of structured cross-dataset joins.
No duplicate issue was filed. Until #310 is resolved, the collection should be described as source-surface metadata. It is valuable for discovering official resources and schemas, but a failed name or registration-number search is not negative evidence about the underlying register.
Conclusion
The indexed Enterprise Register collection describes 30 open-data packages spanning entity identity and history, governance and ownership, financial statements, insolvency and liquidation, restrictions, activities and specialist institutional lists. It exposes enough catalogue metadata to identify formats, row counts, fields, licences and update signals. The actual entity and proceeding rows remain in the linked official resources. Reliable use therefore requires the correct dataset, a registration-number join, the resource's own modification date and careful separation of catalogue-document status from the legal or financial status of an entity.
Sources
This article provides general legal information, not advice for a specific matter. Laws, facts and procedural deadlines may change the result. Follow the linked primary sources and obtain local advice before acting.