How Do Latvia's Supreme and Constitutional Court Collections Differ?

Short answer

The two indexed collections answer different legal questions. LV_SUPREME_COURT is a selected jurisprudence archive from Latvia's Supreme Court. Its 5,395 records concern precedent from the Senate's civil, criminal and administrative departments. The material is curated rather than a claim to contain every Supreme Court decision, and a record may combine a legal headnote with the judgment or provide only a compact jurisprudence summary.

LV_CONSTITUTIONAL_COURT contains 990 Constitutional Court case records. It follows constitutional review rather than ordinary civil, criminal or administrative appeals. Crucially, 581 rows are classified as court decisions and 409 as case-status records. A status record may contain an order initiating constitutional proceedings; it does not prove that the challenged rule has been held unconstitutional.

Researchers should therefore choose the source by institutional function and procedural stage. Use the selected Supreme archive for Senate precedent. Use the Constitutional Court collection to identify constitutional challenges, then distinguish initiated review from a final judgment. Production QA also found one Supreme archive summary with a substantive 2002 cutoff date misused as the decision date for a 2016 judgment; issue #595 tracks that cross-source date and identity defect.

Two courts, two functions

The Supreme Court of Latvia sits at the apex of the ordinary court system. Its Senate departments decide civil, criminal and administrative questions reaching the cassation level. The indexed archive is designed around selected jurisprudence: decisions chosen for their legal significance, often with a concise proposition explaining why the case matters.

The Constitutional Court performs constitutional review. Its records concern challenges to legislation, regulations, local rules or other norms against the Constitution or another rule of higher legal force. It does not operate as another cassation department correcting ordinary errors in individual litigation.

That institutional difference is more important than the shared MCP source type court_case. Both collections contain court material, but the legal effect and research use are not interchangeable.

The selected Supreme Court archive

Production Discovery names LV_SUPREME_COURT as the “Supreme Court of Latvia selected case-law archive” and reports exactly 5,395 indexed rows. Its records identify the relevant Senate department, decision date, case number, normalized citation variants and ECLI where available, together with the official at.gov.lv document link.

The latest source-scoped record reviewed was , a Senate Civil Department judgment dated 10 June 2026. The indexed document begins with a jurisprudence headnote on termination of employment during probation and expressly marks a change in case law before reproducing the judgment.

One headnote states:

Darbiniekam nav prasības tiesības … par pārbaudes laikā izdarīta uzteikuma atzīšanu par spēkā neesošu.

—

This editorial layer is a defining feature of a jurisprudence archive. It helps a researcher locate a legal proposition, but it must still be read with the operative judgment and its procedural context. Not every archive row has the same depth: the audit found both full decisions with headnotes and short summary-only records.

“Selected” is the essential limitation. The archive is not evidence that an absent decision was never issued. A comprehensive search may also require the much larger LV_ALL_COURTS portal collection, with cross-source grouping where identifiers support it.

The Constitutional Court collection

Production Discovery describes LV_CONSTITUTIONAL_COURT as “initiated and reviewed cases” and reports exactly 990 rows. All belong to Latvijas Republikas Satversmes tiesa, with court type CONSTITUTIONAL.

The collection contains two procedurally different classes:

581 COURT_DECISION records; and
409 CASE_STATUS records.

The classes sum to the full 990-record collection. The distinction prevents a pending or newly opened constitutional case from masquerading as a final merits ruling.

The fetched record for is headed LĒMUMS PAR LIETAS IEROSINĀŠANU—an order to initiate a case. Its operative part says:

Ierosināt Satversmes tiesā lietu … pēc sabiedrības ar ierobežotu atbildību “KORS N” pieteikuma.

—

That proves that constitutional review began concerning a VAT rule. It does not establish how the Court will decide the compatibility question.

What a final Constitutional Court record adds

A final judgment supplies reasoning and an operative determination about the challenged norm. In , decided on 12 May 2026, the Court found part of a Jūrmala local plan inconsistent with Article 115 of the Constitution and invalid from its entry into force.

The fetched judgment closes with an explicit finality rule:

Spriedums ir galīgs un nepārsūdzams. Spriedums stājas spēkā tā publicēšanas dienā.

—

That is categorically different from an initiation order. A policy or legal opinion should state whether the cited item merely opened a case, terminated one procedurally, or finally resolved constitutionality. The case number alone does not answer that question.

Different identifiers and document presentation

Supreme archive records commonly use department-specific case numbers such as SKC, SKA and SKK, representing civil, administrative and criminal Senate work. Many recent records also expose an ECLI. Their official documents are served through the Supreme Court's jurisprudence archive.

Constitutional Court records use constitutional case numbers such as 2025-11-03 or 2026-09-01 and link to a case page on satversmestiesa.lv. The page may assemble the procedural life of constitutional review. A pending record may select an initiation document because no final judgment yet exists.

For both sources, the exact Legalcode sourceRef returned by Search should be passed to Fetch. A researcher should not construct references from a case number or assume that similar docket formatting means the sources describe the same institutional process.

Cross-source overlap and the SKA-993/2016 defect

The Supreme archive and all-courts portal can contain representations of the same Senate judgment. Ideally, normalized identifiers let Legalcode treat them as one decision with multiple sources. Question 7 testing found a case where that has not happened.

Exact Search for SKA-993/2016 returns both the full all-courts judgment and a selected Supreme archive summary. The full judgment is dated 19 December 2016. The summary is incorrectly dated 1 January 2002—the cutoff date discussed in its pension-law holding—and the two rows have separate canonical decision identities despite both exposing the equivalent citations SKA-993/2016 and SKA-0993-16.

records the exact Search and Fetch reproduction. The error can distort chronological searches and double-count one decision. Until corrected, researchers should prefer the date in the fetched full judgment and treat the archive summary as another representation of that case, not an independent 2002 decision.

A practical source-selection rule

Use the collections in this order:

For a Senate precedent question, search LV_SUPREME_COURT for curated jurisprudence and fetch the selected record.
If completeness or the underlying document matters, search LV_ALL_COURTS by ECLI and normalized case-number variants.
For constitutional validity, search LV_CONSTITUTIONAL_COURT.
Filter or inspect decisionKind so that CASE_STATUS is not reported as a final judgment.
Confirm the decision date and operative part in Fetch, especially where a compact headnote mentions other dates.

This workflow preserves both the value of curation and the procedural limits of each source.

Conclusion

The indexed Supreme Court archive is a 5,395-record selected jurisprudence collection for Senate civil, criminal and administrative precedent. The 990-record Constitutional Court collection follows constitutional review and deliberately mixes 581 court-decision records with 409 case-status records. The first source helps identify legally significant cassation rulings; the second shows both initiated constitutional challenges and final validity judgments. They should not be merged conceptually, and an initiation order should never be described as a final constitutional holding. Exact sourceRefs, fetched operative text and cross-source identity checks are necessary where the same Supreme decision appears in more than one collection.

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.