What Proves the Publication and Date of a Latvijas Vēstnesis Notice?

Short answer

For an individual Latvijas Vēstnesis notice, the best publication evidence is the exact OP publication number, the publication date, the stable canonical /op/ URL, the notice type and group, the identified entity and registration number, and the exact notice text fetched from that record.

The worked example is notice 2026/125.KM1, published on 3 July 2026. It concerns the association Mamskie budni, registration number 40008253671. The notice says that the association is terminating its activity and beginning liquidation, and invites creditors to submit claims within three months after publication in Latvijas Vēstnesis. The date and OP number appear in both the MCP metadata and the rendered source record, while the fetched text supplies the event and deadline trigger.

That proves publication of the stated notice on that date. It does not prove that liquidation later finished, that the entity's present register status is unchanged, or that a claim was accepted. Those propositions require later official evidence.

The worked notice

The selected record is Latvijas Vēstnesis publication 2026/125.KM1. Its Latvian title is Paziņojums par darbības izbeigšanu, or notice of termination of activity. It belongs to the group Paziņojumi kreditoriem un ieinteresētajām personām, meaning notices to creditors and interested persons.

The MCP record gives:

The exact OP number is the strongest notice-level identifier. Company names can change, be transliterated differently or collide. A registration number identifies the entity, while the OP number identifies the publication event.

What the source text says

The fetched notice begins with the event statement:

Biedrība “Mamskie budni”, reģ. Nr. 40008253671, paziņo par darbības izbeigšanu un likvidācijas procesa uzsākšanu.

— Latvijas Vēstnesis, 2026/125.KM1

In English, the association announces termination of its activity and commencement of the liquidation process. The next sentence supplies the creditor instruction and, importantly, defines the time trigger:

Kreditori tiek aicināti pieteikt savus prasījumus trīs mēnešu laikā pēc paziņojuma publicēšanas oficiālajā izdevumā “Latvijas Vēstnesis”.

— Latvijas Vēstnesis, 2026/125.KM1

Creditors are invited to submit claims within three months after publication in the official publication Latvijas Vēstnesis. The relevant event in this text is publication, not private receipt of the notice.

The full notice also contains contact details. They are part of the public source, but they are unnecessary for explaining publication evidence and are deliberately not repeated here.

How the date is corroborated

The date is not inferred from only one place. Exact-source Fetch exposes Publication date: 2026-07-03 in record metadata. The rendered source body repeats Publication date: 2026-07-03. It also associates the date with OP number 2026/125.KM1 and the canonical notice URL.

This gives three mutually reinforcing elements:

1. a machine-readable date field;
2. a date rendered inside the fetched source record; and
3. a stable OP identifier that resolves to the individual official notice.

The parameterized PDF URL is useful provenance, but the canonical /op/2026/125.KM1 address is clearer for citation. A research file should preserve both if available: the OP page for stable identification and the PDF endpoint for the published artifact.

What the OP number tells the reader

The identifier 2026/125.KM1 is more than a convenient label. It binds the citation to the 2026 official-publication sequence and the KM notice group. It avoids relying on a vague description such as “a liquidation notice in July.”

The number should be copied exactly, including slash, period and suffix. A digit or suffix change points to a different publication. In the MCP, the same value appears as both sourceNumber and sourceRegister metadata, and an exact sourceNumber filter returns one record.

The year and issue-like segment should not be used to invent a calendar date. The authoritative date for this record is the separately stated 3 July 2026 date.

Publication evidence is not current-status evidence

An official notice is evidence that specified words were published at a specified time. It is not a live register snapshot.

From this notice alone, a researcher can safely report that:

• the association identified by registration number 40008253671 published a termination-and-liquidation notice;
• the publication occurred under OP number 2026/125.KM1 on 3 July 2026; and
• the notice invited creditor claims within three months after publication.

The same notice does not establish that:

• the liquidation was later completed;
• the association is currently dissolved or deleted from the register;
• all creditor claims were allowed or paid;
• no correction or later notice exists; or
• the deadline calculation is unaffected by governing procedural rules.

Those questions require later Enterprise Register information, subsequent Vēstnesis publications, the governing legislation and, where relevant, a court or administrator record.

How to use a notice in credit-risk work

A credit report should represent the publication as a dated event, not convert it automatically into a timeless adverse status. A defensible record would retain at least:

• the entity registration number;
• the exact OP number and canonical URL;
• the publication date;
• the Latvian notice type;
• a restrained description of what the notice itself states;
• the retrieval or verification date; and
• a field for later status or superseding evidence.

The report should avoid asserting “insolvent,” “dissolved” or “defaulting” unless the notice and governing source actually establish that proposition. Termination and liquidation are not synonyms for insolvency, and an invitation to creditors does not adjudicate a debt.

If a score uses the event, the model should account for age and later outcomes. A July 2026 publication may be relevant to a September 2026 review, but the continuing weight depends on what occurred after publication.

Distinguish three dates

Official-notice research commonly creates three dates that should not be merged:

1. Event date. A decision, registration entry or other underlying event may precede publication.
2. Publication date. Here, 3 July 2026 is the date the notice was published and the date from which its own creditor invitation is framed.
3. Research or retrieval date. This article was reviewed on 13 September 2026. That date records when the evidence was checked, not when the notice occurred.

Keeping them separate prevents a database refresh or research timestamp from being mistaken for legal publication.

MCP source-quality finding

The production Legalcode MCP exact sourceNumber Search returned one candidate, and Fetch returned the complete notice with the OP number, publication date, entity registration number, canonical URL and source text. That part of the workflow worked well.

The known Vēstnesis modeling defects remain. The notice is exposed under source type guidance; the entity name is labeled as an administrative case name; status: ACTIVE can be mistaken for the entity's status; and dedicated public-notice event and relationship fields are missing. Search also exposes the parameterized PDF URL while the stable canonical OP URL is visible only after Fetch. These defects are tracked in GitHub issue #311. No new duplicate issue was filed.

Conclusion

Notice 2026/125.KM1 can be cited as proof that a termination-and-liquidation notice for the identified association was published in Latvijas Vēstnesis on 3 July 2026 and that creditors were invited to act within three months after publication. The OP number, date, canonical URL, registration number and exact text form the evidence packet. Any claim about present status or later legal effect requires additional official material.

Sources

• Latvijas Vēstnesis — publication 2026/125.KM1