What Does the Bank of Latvia Market-Participant Collection Show?

Short answer

Legalcode's LV_BANK collection can identify a financial-service provider and show its Bank of Latvia listing segments, country of origin, Latvian registration number where available, legal address, licence or EEA passport category, licence number, valid-from dates, permitted activities, cross-border service territories and sanctions attached to the official profile.

The collection is broad. Production MCP Discovery reports 3,920 LV_BANK guidance-source records: 3,849 classified as reference material and 71 as guidelines. The reference-material records are dominated by Bank of Latvia financial-market participant profiles, together with some external register references. The guidelines cover separate supervisory, licensing, customer-protection and operational topics.

The most important limitation is that status: ACTIVE in MCP metadata describes the indexed page, not necessarily the provider's authorization or operations. One sampled profile is marked active as a document while its body says the bank's licence was withdrawn and liquidation began. A current-authorisation conclusion therefore requires the licence and status text inside the profile—and, for a consequential decision, confirmation at the underlying official register.

How the collection is organized

The Bank of Latvia material sits under Legalcode's guidance source type and source code LV_BANK. That source combines two different research surfaces. Ordinary Bank pages are classified as GUIDELINE; market-participant and external-register records are generally REFERENCE_MATERIAL.

That distinction is operationally useful. A source filter alone returns both participant profiles and pages about subjects such as cyber risk, crypto-asset licensing or critical financial services. Adding documentType: REFERENCE_MATERIAL narrows toward register entries. It does not, however, create a clean legal-entity table: the participant data remains largely embedded in each record's text.

The profiles cover more than Latvian banks. Sampled results include Latvian credit institutions and cooperative credit unions, foreign EEA institutions providing services into Latvia, payment and investment-service providers, insurers, pension and investment entities, intermediaries, and references to external European registers.

Provider identity and register context

A typical profile starts with the provider's name, official source URL and listing segment. For a Latvian entity it may then provide country of origin, registration number and legal address. The sampled Swedbank AS profile states:

Listing segments: Credit institutions; Investment service providers; Payment service providers.

— Bank of Latvia participant register, Swedbank AS

Its fetched record also identifies Latvia as the country of origin, registration number 40003074764 and a Riga legal address. These fields support entity matching, particularly where a name has changed or a group contains similarly named companies.

Identifiers are not uniform. The Latvian SKOLU KRĀJAIZDEVU SABIEDRĪBA profile contains registration number 40003372253. The French CREDIT MUTUEL ARKEA profile exposes a page slug rather than a legal registration number in Legalcode's sourceNumber field. A foreign record therefore cannot always be joined to another dataset by treating sourceNumber as a company identifier.

Licences, passports and permitted activities

The richest profiles contain a nested authorization tree. Swedbank's record identifies a credit-institution licence, its number and validity date, then lists deposits, lending, guarantees, payment services, investment services and ancillary activities. The lending line expressly includes consumer credit, credit secured on immovable property, factoring and commercial-transaction financing.

Payment and investment permissions can be more granular. The profile distinguishes account operation, cash withdrawals, card transactions, credit transfers, acquiring, payment initiation, account information, order transmission, dealing on own account, portfolio management and investment advice. It also lists countries for freedom-of-services permissions where the profile provides them.

The cooperative credit-union sample is shorter and shows how category affects content. Its licence is number 151, valid from 4 December 1997, and its listed activities are attracting member deposits and other repayable funds and lending to members, including financial lease.

The French CREDIT MUTUEL ARKEA record illustrates EEA passporting rather than a Latvian domestic licence. It identifies the country of origin and says the institution uses the freedom to provide services from 3 March 2017. A listing of that kind should be described as a cross-border permission or notification in the terms given by the register, not casually restated as a Latvian-incorporated bank licence.

Sanctions attached to a participant profile

Some profiles also carry sanctions. The fetched Baltic International Bank SE profile lists breach descriptions, dates, whether a measure is appealed or in force, the affected former board member where relevant, and the sanction or procedural outcome.

One entry includes the decisive status warning:

The bank's licence for the operation of a credit institution has been withdrawn and liquidation proceedings have been initiated.

— Bank of Latvia participant register, Baltic International Bank SE

The same fetched profile includes sanctions concerning internal controls, lending and investment controls, anti-money-laundering risk management and delayed audited reporting. A participant page can therefore provide useful links between identity, licence history and enforcement events.

It should not be used to collapse different legal subjects into one finding. Some sanctions on a profile concern named former board members; others concern the institution. Procedural status also matters: “Appealed” is not equivalent to “In force”, and a cancelled fine is not an outstanding penalty.

What the metadata does—and does not—mean

Legalcode's top-level participant metadata reliably supplies a versioned source reference, official URL, source code, document type, language and a source number or slug. Those fields are useful for retrieval and provenance.

The generic status: ACTIVE field is different. It indicates that the indexed reference document is active in the corpus. It does not mean that every licence shown in its body remains valid, that the provider currently offers every listed service, or even that the provider remains operational. The Baltic International Bank example proves why the distinction matters.

The profile date is also contextual, not universal. Depending on the record, it may reflect the beginning of a licence, a passport notification, a sanction or another page event. It is not automatically the company's incorporation date, the most recent verification date or the date on which all permissions became current.

Search and matching cautions

A provider name alone can be ambiguous. Searching “Swedbank” returned a Latvian bank, several foreign banks and payment entities, insurance and pension entities, an investment manager and a holding company. The correct match depends on registration number, country, segment and source URL.

Names can also be misleading. A company containing “credit” in its name need not be a credit institution; the register segment and actual authorization text control. Conversely, a foreign bank may have no Latvian registration number even though the profile documents its freedom to provide services in Latvia.

Large records can be noisy. The Swedbank body repeats the same licence and activity hierarchy multiple times and exceeds 8,000 estimated tokens. Researchers should extract the distinct permissions and dates, retain the exact profile URL, and avoid counting duplicated body blocks as separate licences.

MCP source-quality finding

The production MCP returned exact, fetchable participant records and exposed enough body text to answer the question. The split between 3,849 reference-material records and 71 guidelines also makes the mixed source easier to navigate.

The key structural weakness remains unresolved. Licence type, licence status, activities, listing segment, country, validity dates and cross-border territory are not structured fields. They cannot be reliably filtered or aggregated without reading record bodies. The document-level active status can be mistaken for provider authorization, and identifiers vary between registration numbers and slugs. These limitations are tracked in Legalcode issue #309; the current audit reproduced them, so no duplicate issue was filed.

A defensible provider check

For a practical provider review:

1. filter LV_BANK to reference material before searching the entity;
2. match the exact name with country, registration number and official profile URL;
3. identify the listing segment and whether the route is a domestic licence, branch or freedom to provide services;
4. read each licence/activity line and its valid-from date rather than relying on the page status;
5. review attached sanctions and preserve their subject and procedural status;
6. check for withdrawal, liquidation, expiry or other limiting text in the body; and
7. confirm consequential current-status conclusions in the official Bank of Latvia register.

Conclusion

The indexed Bank of Latvia market-participant collection is a useful regulatory profile library. It can show who a provider is, how it is listed, where it originates, which registration and licence identifiers are available, what activities and territories appear on the profile, and which sanctions are attached. It is not yet a structured current-authorisation database. Its document status, mixed identifiers, embedded licence fields and repeated body content require record-by-record verification before stating that a provider is presently authorized for a particular service.

Sources

• Bank of Latvia participant register — Swedbank AS
• Bank of Latvia participant register — SKOLU KRĀJAIZDEVU SABIEDRĪBA
• Bank of Latvia participant register — CREDIT MUTUEL ARKEA
• Bank of Latvia participant register — Baltic International Bank SE
• Legalcode issue #309 — missing structured participant status and licence fields