Short answer
A Latvijas Banka sanctions-register entry is an administrative enforcement event; a court judgment is a judicial decision in a defined case. The same bank name can appear in both without the documents addressing the same conduct, legal question or outcome.
AS “PrivatBank” provides a concrete example. A 23 May 2022 sanctions-register summary identifies the bank as the sanctioned party, records AML/CFT/proliferation-financing breaches, and reports a EUR 893,986 fine reduced through an administrative agreement. By contrast, Supreme Court judgment SKC-644/2013 concerns the bank's civil debt-recovery claim against an individual. There, the bank was claimant and cassation appellant, not an enforcement target; the legal issue was whether contractual interest and penalty continued after early termination.
A responsible report separates decision-maker, document type, proceeding, party role, legal subject, date, status, remedy and evidentiary depth. It should not infer that the court confirmed the regulatory breach—or that the sanction decided the private debt—merely because the same institution name appears.
The name match is only the starting point
Production Legalcode MCP Search for AS PrivatBank in the Bank of Latvia sanctions collection returned two records. One sanctions the bank itself. The other warns an individual, Inga Rumba, while naming AS “PrivatBank” only as the related institution.
The same search within the selected Supreme Court archive returned seven decisions mentioning the bank. They include civil debt cases and administrative proceedings. A text match therefore answers only “which records mention this name?” It does not establish:
- that the bank is the respondent or sanctioned person;
- that two records concern the same event;
- that the legal entity is identical across name changes or reorganisations;
- that a finding in one proceeding transfers to another; or
- that both records have the same finality or evidential weight.
Cross-source reporting must resolve those questions before combining events into an institution timeline.
The 2022 sanction: regulatory enforcement
The is dated 23 May 2022. Legalcode classifies it as a regulatory decision in a regulatory-enforcement posture, with the bank as sanctioned party.
The public summary records:
Breaches of the anti-money laundering and counter terrorism and proliferation financing regulatory requirements.
—
It identifies a EUR 893,986 fine, register status “In force,” decision outcome SANCTION_IMPOSED, final outcome SANCTION_REDUCED, and binding status BINDING. The reduction followed contesting and appealing the original board decision and entering an administrative agreement.
Those structured fields make the event reportable, but the document has a firm limit: it is a PUBLIC_REGISTER_SUMMARY and expressly says Full decision available: No. The indexed text does not supply the complete factual file, the bank's submissions, all provisions applied or the proportionality analysis behind the original and reduced amounts.
A report may say that the official register records the breach category and reduced fine. It should not invent which customers, transactions or control failures produced the sanction.
SKC-644/2013: private civil adjudication
, decided on 30 January 2013, is a full Supreme Court judgment. It arose from AS “PrivatBank”'s small debt-recovery claim against an individual. The bank challenged a lower court's treatment of principal, contractual interest and contractual penalty after the bank terminated the credit agreement early.
The Senate's Civil Cases Department held:
Līgumiskie procenti un līgumsods … ir atlīdzināmi līdz brīdim, kad līgums beidz pastāvēt.
—
Contractual interest and penalty accrued only until the contract ended. The principal and valid accrued amounts remained due, while statutory interest could apply after termination.
This judgment does not sanction the bank for AML failures. The institution appears as a civil claimant and cassation appellant. The court resolves a private-law calculation and states an interpretive rule. Even an adverse ruling on one component of the claim is not interchangeable with a regulatory finding of institutional misconduct.
Eight fields that keep the records separate
1. Decision-maker
A court judgment comes from an identified court and judicial panel. A sanction comes from a supervisory authority exercising administrative powers. “Official decision” is too broad a label to describe both.
2. Document nature
SKC-644/2013 contains facts, submissions, reasoning and an operative order. The sanction record is a compact public-register summary without the full decision. The latter cannot support the same depth of factual reconstruction.
3. Procedural posture
The court matter is civil debt litigation followed by cassation. The sanctions record is regulatory enforcement followed by contest/appeal and an administrative agreement. Procedural routes determine who bears what burden, which remedies are available and what finality means.
4. Party role
In the court case, AS “PrivatBank” sought money from a debtor. In the sanction record, the bank is the sanctioned party. A database should encode these roles rather than expose an undifferentiated “mentioned entity.”
The related Inga Rumba register entry illustrates the point. The individual—not the bank—was warned. Describing it as “a sanction against PrivatBank” would change the subject of the decision.
5. Legal question
The 2022 record concerns compliance with AML/CFT/proliferation-financing regulation. SKC-644/2013 concerns the contractual basis for interest and penalty after termination. Neither decides the other's legal issue.
6. Date and historical context
The events are more than nine years apart. A later sanction cannot retroactively become evidence of the bank's conduct in the 2013 debt case. The earlier judgment cannot decide whether 2022 compliance systems met later supervisory requirements.
7. Outcome and remedy
The regulator imposed a monetary fine later reduced by agreement. The court adjusted a civil debt claim and declared rights concerning interest. A fine, a civil award, a dismissal of part of a claim and an interpretive holding are different outcome types.
8. Identity evidence
The name string is strongly suggestive but not the safest entity key. The fetched sanction summary does not expose a registration number, and the court record identifies the bank through party text. Before building a long-run entity profile, a researcher should verify a stable registration identifier and preserve decision-time names, later names and corporate continuity.
How status should be written
The sanction should be described with both stages: an enforcement fine was imposed, and the amount was later reduced through an administrative agreement. Reporting only the initial action overstates the current consequence; reporting only the reduction hides the enforcement event.
For a court judgment, status concerns judicial disposition, appeal history and whether the decision is final or precedential. SKC-644/2013 is significant because an expanded Senate panel expressly clarified prior case law. That does not make every factual statement in the judgment a general rule.
A compact report can use parallel but distinct language:
- Regulatory event: “The official sanctions register records an AML-related fine against AS ‘PrivatBank’ dated 23 May 2022; the fine was reduced to EUR 893,986 through an administrative agreement. The indexed record is a summary, not the full decision.”
- Judicial event: “In SKC-644/2013, the Supreme Court decided AS ‘PrivatBank’'s civil debt claim and held that contractual interest and penalty stop when lawful early termination ends the contract.”
Nothing in either sentence implies that one proceeding adjudicated the other.
When the court case actually reviews a sanction
Sometimes a financial institution challenges supervisory action in an administrative court. Even then, the regulator's decision and the judicial review judgment remain separate records.
The regulator record states the initial finding, measure and administrative lifecycle. The court record states what was challenged, the review standard, the court's reasoning and the judicial disposition. A report should link the records through an explicit appeal/review relationship, preserve both dates, and update the sanction's final status. It should not replace the original regulator event with the later judgment or assume that filing an appeal suspended or annulled the sanction.
That relationship does not exist between the two examples above: SKC-644/2013 is unrelated private debt litigation.
MCP source-quality findings
The production MCP correctly kept LV_BANK_SANCTIONS in the agency-decision source family and LV_SUPREME_COURT in court cases. It exposed sanction-native fields for the 2022 record and full judicial text for SKC-644/2013. This supports reliable separation by source, body type, posture, party role and outcome.
One historical-attribution defect emerged. The 2022 record labels decisionBody as Latvijas Banka, but its own outcome text attributes the contested board decision and reducing administrative agreement to the Financial and Capital Market Commission (FCMC). The current register host/successor authority should not overwrite the historical decision-maker. This is tracked in .
The record's explicit public-summary limitation and structured sanction fields reflect the repairs previously tracked in . Entity-name and participant-status limitations remain relevant under and .
Conclusion
The shared institution name is an entity clue, not a legal bridge. The 2022 AS “PrivatBank” sanction is a regulator-enforcement summary about AML-related obligations and a reduced fine. SKC-644/2013 is a full Supreme Court judgment in the bank's private debt claim, producing a rule about contractual accrual after termination.
Keeping decision-maker, party role, subject, procedure, status, remedy, date and evidentiary depth separate prevents a report from turning mere co-occurrence into a false finding.
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.