Which categories of insolvency-related notices are available through Ametlikud Teadaanded?

Short answer

The indexed Ametlikud Teadaanded collection contains several distinct types of insolvency-related procedural notice. The evidence reviewed for this article establishes at least these categories:

This is not proved to be an exhaustive taxonomy. The production index holds 49,680 Ametlikud Teadaanded documents, but the MCP currently stores the source-native notice type, family and subtype only inside fetched body text rather than exposing them as facets. Legalcode issue #585 tracks that gap.

A notice category describes a procedural event

Ametlikud Teadaanded is Estonia's official-publication channel for these notices. Each record represents a particular event in a proceeding, not a general credit score and not necessarily the current condition of the affected person.

The indexed records can contain:

• a unique notice number and internal identifier;
• the native notice title, notice-type code, template and template code;
• the legal basis and a Riigi Teataja link;
• the publishing court or insolvency practitioner and contact details;
• the affected person or entity;
• publication and archive dates;
• the source family and subtype;
• the civil case number; and
• structured event details, such as the order date, bankruptcy time, trustee, claims deadline, meeting date or auction terms.

Those fields make it possible to construct a procedural timeline. They do not make all notice types interchangeable. A pre-sale notice, a bankruptcy declaration and an opportunity to inspect a final report describe different events with different consequences.

Bankruptcy declaration notices

The central commencement category is the bankruptcy declaration notice. The verified notice 2549270, published on 13 January 2026, identifies:

• the court and civil case number;
• the debtor and the precise date and time of bankruptcy;
• the appointed bankruptcy trustee and contact details;
• the first creditors' general meeting;
• the period for creditors to notify the trustee of claims; and
• the consequences of late submission.

The record's source-native taxonomy is specific: notice type code 172, template code 264, source family pankrotimenetlus and the bankruptcy-declaration subtype. That combination is much stronger evidence of the event than the occurrence of the word “bankruptcy” somewhere in free text.

A declaration notice should not be reduced to a timeless “insolvent” flag. The declaration happened at a precise moment, later notices may alter the procedural picture, and a person or estate can eventually reach termination or debt release.

Combined individual bankruptcy and debt release

The searches also returned a longer category used for natural persons: a notice declaring the individual's bankruptcy and commencing proceedings for release from obligations (Füüsilise isiku pankroti väljakuulutamise ja kohustustest vabastamise menetluse algatamise teade).

The combined title carries two propositions:

1. bankruptcy was declared; and
2. a separate process concerning release from obligations was commenced.

Commencement of debt-release proceedings is not the same as a final release. A credit or compliance record should preserve both the event type and date and should look for later notices or orders before stating that obligations were discharged.

Final-report inspection notices

The verified notice 2261956 is a notice that the bankruptcy final report can be inspected. It was published by the trustee under § 163(1) of the Bankruptcy Act.

The notice says that the report was available for ten days and that creditors could object to it in court within ten days of publication. Its taxonomy is notice type code 161, template code 485 and the final-report-inspection subtype within the bankruptcy-proceedings family.

This category is near the end of a proceeding, but it does not by itself prove that the proceeding terminated on the publication date. It opens an inspection and objection stage. A later court decision or termination notice is required to establish the actual end and its legal basis.

Bankruptcy asset-auction notices

Insolvency-related notices also appear under the sale/auction family rather than only under the bankruptcy-proceedings path. The verified notice 1958845 advertised the electronic auction of a vehicle forming part of a bankrupt estate.

The notice supplied the asset description, opening price, registration period, auction opening and closing times, bid increment, auction-platform link, payment conditions, treatment of third-party rights and trustee contact information. It used notice type code 27 and template code 26. Its source family was the sale/auction family, while its subtype expressly identified a movable-property auction in bankruptcy proceedings.

An auction notice proves that a sale was advertised on specified terms. It does not by itself prove that the asset was sold, who bought it or how much the estate recovered. Those propositions require later auction or distribution evidence.

The broader search also returned repeated auction notices involving the same bankrupt estates at different dates. They should not automatically be treated as duplicate records: a failed, postponed or repeated auction can produce a new procedural notice with different terms.

Natural-person debt-restructuring notices

The indexed collection contains a separate debt-restructuring family. The verified notice 2412178 records the court's commencement of an individual's debt-restructuring proceedings under § 18(4) of the Natural Person Insolvency Act.

The full record states that the insolvency application was granted for this purpose, a trustee was to prepare the restructuring plan, the plan and creditors' positions had to be filed by a specified date, and the debtor had to cooperate. The notice uses source family volgade-ymberkujundamine, not the bankruptcy-proceedings family.

The current searches also surfaced:

• notices terminating debt-restructuring proceedings; and
• notices annulling a debt-restructuring plan.

These are distinct from commencement. A termination notice may record transition to bankruptcy, withdrawal, failure of the process or another stated ground. A plan-annulment notice concerns an existing restructuring plan. The title identifies the event family, but the notice text or court order must be read to determine why it happened and what followed.

Corporate reorganisation and other possible categories

Estonian insolvency law also has corporate reorganisation procedures, and Ametlikud Teadaanded may publish related events. This review did not obtain observed full-text evidence sufficient to inventory those categories from the production MCP. They are therefore not included in the verified table merely because the legal framework suggests they should exist.

That boundary is important. The question is what the indexed source actually makes available, not every notice that Estonian law could require. Once the source-native taxonomy is exposed as structured metadata, the collection can be measured directly rather than inferred from sample results.

Do not confuse neighbouring notice families

Several official-notice categories can indicate financial stress without being proof of insolvency:

• ordinary enforcement and bailiff auctions;
• liquidation notices;
• invitations to creditors during corporate liquidation;
• deletion or compulsory-dissolution notices; and
• notices concerning tax or other public claims.

An asset auction is insolvency-related only where the notice links it to a bankruptcy estate or another relevant insolvency procedure. Likewise, liquidation is not automatically bankruptcy. A risk system should store the exact event type instead of assigning one generic “insolvency notice” label to every adverse-looking publication.

How to use the notice categories in a timeline

A reliable timeline should keep these questions separate:

1. What is the native notice type and code? This identifies the procedural event.
2. Who published it? A court, trustee or another official actor may have a different role.
3. Who is affected? Match the official identifier, not only a name.
4. Which case does it concern? Preserve the civil case number.
5. When did the legal event occur? This may differ from the publication date.
6. What deadline follows? Claims, objections, meetings and auctions have different dates.
7. What later notice changes the picture? Commencement, sale, final report and termination should be connected rather than treated as independent permanent flags.

This approach prevents common errors. A bankruptcy application or restructuring commencement is not a completed bankruptcy. A final-report inspection is not yet termination. A scheduled auction is not a completed sale. Commencement of release proceedings is not a final discharge.

Current MCP coverage limitation

The production source profile reports Ametlikud Teadaanded as present with 49,680 procedural-notice documents. Yet its searchable schema exposes only broad fields such as source code, source register, document type, source number, status and dates. The fine-grained taxonomy visible in the downloaded records is not available as a filter or facet.

That means searches for category names operate over unrestricted body text. Incidental matches can distort results: for example, a company name containing the Estonian word for reorganisation can cause a bankruptcy notice to match a reorganisation query. Search-result totals also cannot substitute for measured category counts.

Issue #585 asks Legalcode to persist and expose the native notice type and code, template and code, source family and subtype. Until then, category coverage should be described as verified examples, not an exhaustive census.

Privacy and proportionality

Official insolvency notices can contain personal identification codes, addresses, contact details and sensitive financial-procedure information. Their official publication does not mean every field should be copied indefinitely into a commercial product or blog article. This article intentionally omits personal identification codes from its examples.

A downstream credit-reporting use requires a separate analysis of purpose, legal basis, accuracy, retention, matching and the effect of later procedural events. The official notice is evidence of the event it records; it is not permission to convert every published field into a permanent risk attribute.

Conclusion

The indexed Ametlikud Teadaanded collection covers multiple stages and procedural families: bankruptcy declarations, combined individual bankruptcy and debt-release commencement, final-report inspection, bankruptcy asset auctions, and natural-person debt-restructuring commencement, termination and plan annulment.

Each category answers a different question. The safest use is to preserve the native type, event date, case number, affected-person identifier, legal basis and later notices. Because the MCP does not yet expose the source-native taxonomy as structured facets, the list above is a verified minimum—not proof of every insolvency-related category in the 49,680-document collection.

Sources and audit issue

• Ametlikud Teadaanded
• Bankruptcy declaration notice 2549270
• Bankruptcy final-report inspection notice 2261956
• Debt-restructuring commencement notice 2412178
• Bankruptcy movable-asset auction notice 1958845
• Legalcode issue #585: notice taxonomy is not exposed as structured MCP fields