Short answer
Yes. A Latvian Saeima proposal can be followed into enacted law, but only through a status-gated chain: identify the exact parliamentary matter, inspect its document chronology, confirm enactment and promulgation, identify the discrete amendment act, and then fetch the current consolidated version of the law that was amended.
The proposal remains legislative history. It may explain the problem, purpose and first drafting choice, but it is not current law. Committee work can alter the wording; the enacted amendment can differ from the original bill; and later amendments can change the consolidated act again.
Saeima matter demonstrates the method. Its original February 2023 proposal would have added a short power to obtain debtor information from credit bureaus. The enacted text instead created a detailed new Section 5.1. The amendment was adopted on 19 October 2023, proclaimed on 2 November and took effect on 16 November. The operative wording must now be read in the current consolidated , not copied from the first proposal.
The five records that should not be collapsed
A reliable trace separates five legal objects:
- the Saeima flow or dossier, which records the progress of matter 176/Lp14;
- the original bill and annotation, which record the government's initial proposal and reasons;
- later parliamentary materials, including proposal tables and the text prepared for promulgation;
- the discrete , which legally changed the base act; and
- the current consolidated version of the base act, which states the rule in force on the research date.
These objects answer different questions. The annotation explains policy. A proposal table shows drafting evolution. The promulgated amendment proves what the legislature enacted. The consolidated law answers what the rule says now.
Step 1: resolve the exact parliamentary matter
The production Legalcode MCP was searched with the structured matter number 176/Lp14 and the Saeima pre-law source. That produced one exact flow: pre_law/LV/LV_SAEIMA_PRELAW:176/Lp14, titled Grozījumi Uzturlīdzekļu garantiju fonda likumā—Amendments to the Maintenance Guarantee Fund Law.
Structured identification matters. A free-text search for 176/Lp14 returned many candidates and did not put the exact matter first. That does not make the corpus unusable; it means an identifier should be placed in its identifier field instead of treated as ordinary words.
The exact flow reported ENACTED, enacted: true and a promulgation date of 2 November 2023. Those fields are a threshold, not the end of the inquiry. A flow may also be pending, withdrawn or failed, and its mere connection to an existing law does not prove enactment.
Step 2: inspect the document chronology
The flow has ten physical attachment records. They include document no. 500, the ; a first-reading committee report; second- and third-reading proposal tables; text prepared for promulgation; and promulgated document no. 179L/14.
The original bill proposed adding a new point 3.1 to Section 5(1):
bez maksas pieprasīt un iegūt informāciju par parādniekiem no kredītinformācijas birojiem
—
In English, the Fund Administration would have been entitled to request and obtain information about debtors from credit bureaus free of charge. The annotation explained the intended use: assessing asserted repayment capacity, choosing recovery measures and detecting new financial commitments inconsistent with a debtor's claim that only a small maintenance-debt payment was affordable.
That is valuable evidence of purpose. It is still not the final rule.
Step 3: identify what changed in Parliament
The second-reading material replaced the short insertion with a more structured provision. Instead of merely granting a broad acquisition power, it proposed a new Section 5.1 specifying the data, purposes and subordinate-rule authority.
This is the practical reason to inspect the whole dossier. If a researcher stopped at the original bill, the resulting legal statement would omit the limits and functions added during parliamentary consideration.
The document chronology should be read as a sequence, not as ten equally authoritative versions. A proposal rejected at second reading is not rescued by appearing in the corpus. A committee-supported proposal is still not law until the final text is adopted and promulgated.
Step 4: verify the discrete enacted amendment
The corresponding Likumi.lv amendment is . The MCP identifies it as an amendment act, adopted on 19 October 2023, proclaimed in Riga on 2 November and effective from 16 November 2023.
Its first amendment inserted Section 5.1. The enacted provision says that the Fund Administration receives from credit bureaus information about the amount of a debtor's payment obligations to other creditors and the dates for performing those obligations.
It then defines why:
Ziņas par parādnieku no kredītinformācijas birojiem tiek iegūtas, lai izvērtētu, vai Fonda administrācijas noteiktie uzturlīdzekļu parāda atmaksas nosacījumi atbilst parādnieka mantiskajam stāvoklim un maksātspējai …
—
The remainder of the paragraph adds detection of cases in which newly assumed obligations may indicate avoidance of child maintenance. A third paragraph authorises Cabinet rules governing receipt, storage and updating in the register.
The enacted architecture is therefore materially more precise than the original one-line proposal.
Step 5: finish at the current consolidated law
Even the amendment act is not automatically the last word. The final step is the current version of the amended base act.
On 13 September 2026, the MCP identified the current consolidated version of the as effective from 1 April 2026 and valid until 1 January 2029. Its Section 5.1 retains the three-part structure enacted in 2023 and attributes it to the law of 19 October 2023, effective 16 November 2023.
The current text confirms three points:
- the data concern amounts owed to other creditors and performance terms;
- the statutory purposes are repayment-condition assessment and identifying possible maintenance avoidance; and
- Cabinet rules govern how the bureau information is received, stored and updated in the Fund register.
This current-version check is indispensable because the base law has multiple historical versions and several related parliamentary flows after 176/Lp14. A statement correct on 16 November 2023 could later be amended, delayed or repealed.
How to treat pending and failed linked bills
Tracing the base law in the MCP returned seven Saeima flows. They included enacted matters 176/Lp14, 610/Lp14 and 1090/Lp14, a pending matter, and three failed matters.
That is useful legislative history, but a relationship edge does not answer legal status. Each linked flow must be read with its own status and enactment flag. Pending or failed text may reveal policy direction or rejected alternatives; it cannot be merged into the consolidated rule.
A defensible research record therefore preserves, for each proposition:
- the exact source reference and official URL;
- document role and parliamentary stage;
- whether the matter was enacted;
- adoption, promulgation and effective dates where applicable;
- the amendment act that carries legal force; and
- the consolidated version date used for the current-law conclusion.
What the proposal can still prove
Keeping the proposal in its proper category does not make it unimportant. The annotation can support a careful account of the mischief addressed, the information thought necessary, the expected administrative process and the government's view of the legal basis. Proposal tables can explain why the wording became narrower, more detailed or differently structured.
Those materials can assist interpretation when the legal system permits, but they cannot override enacted wording. They also cannot establish that a planned safeguard, implementation measure or factual assumption remains true. Any such claim needs its own current authority.
MCP source-quality findings
The production MCP successfully connected the bill dossier, its readable attachments, the amended law family and the current consolidated text. It also exposed two cautions.
First, exact Search reports the flow's current stage as Izsludināts—promulgated—while Fetch labels it Nodošana komisijām—referral to committees. Fetch's own source-derived status sections say Izsludināts. This cross-surface contradiction is tracked in .
Second, paired rendered and electronically signed attachments are represented as separate physical records, and the EDOC variants are not Fetchable. A corresponding rendered document preserved the content for this matter. Logical-document counting, unsupported formats and pre-law relation semantics are already tracked in .
These defects do not prevent this trace, but they reinforce why a researcher should compare metadata with fetched source text and should not infer legal effect from a relationship label alone.
Conclusion
The safe route is proposal dossier → document chronology → promulgated text → discrete amendment act → current consolidated law. For 176/Lp14, that route shows a real drafting change: a broad proposed power in Section 5 became a detailed enacted Section 5.1 defining the information, purposes and implementation mechanism.
The proposal explains the journey. The promulgated amendment proves the 2023 legal change. The dated consolidated Likumi.lv text supplies the current rule.
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.