Short answer
Four published Estonian Supreme Court decisions provide especially useful answers:
Together, the decisions reject a mechanical rule that a guarantor always owes whatever the creditor demands as soon as the borrower misses payment. The court must identify the secured principal obligation, the guarantee's type and monetary scope, enforceability, notice terms, available defences, other security, insolvency or restructuring effects, and any payments already made.
The decisions also distinguish the creditor's claim against the guarantor from the underlying claim against the principal debtor. Those claims are separate, but the guarantee remains accessory: changes to the underlying claim can affect the guarantor unless a statutory or contractual rule allocates that risk differently.
“Principal borrower” and “principal debtor” are not always identical
The Estonian judgments use põhivõlgnik—principal debtor—because a guarantee can secure more than a conventional loan.
The four reviewed disputes concerned:
- unpaid goods supplied on credit;
- a bank loan supported by a guarantee and mortgage security;
- scheduled tax debt under a guarantee; and
- two company loan agreements secured by a personal guarantee and share pledges.
For a lending policy, “principal borrower” is usually the relevant business description. For legal analysis, the broader term “principal debtor” is safer. The first task is to identify exactly which obligation the guarantor promised to secure.
3-2-1-121-10: joint liability does not wait for collection from the principal debtor
In , a supplier sold construction materials on credit. The buyer did not pay, later entered bankruptcy and was removed from the register. The supplier claimed against an individual guarantor.
The guarantee stated that the guarantor and principal debtor were jointly liable, subject to an 80,000-kroon maximum. It also allowed the creditor to demand performance from the principal debtor, the guarantor, or both.
The default rule was joint liability
The Supreme Court explained that, on breach of the secured obligation, the principal debtor and guarantor are jointly liable under VÕS §145(1) unless the guarantee provides that the guarantor is liable only when the creditor cannot obtain satisfaction from the principal debtor.
That distinction is decisive:
- under an ordinary joint-liability guarantee, the creditor need not first complete proceedings against the borrower merely because the borrower is the primary contracting party;
- under a subsidiary guarantee, the agreed or statutory precondition must be satisfied before the guarantor is liable.
The judgment does not permit the labels to be assumed. The signed guarantee must be read.
Notice did not create liability under this contract
The guarantor argued that the creditor had not given notice in the contractually specified form. The Court held that neither the law nor this agreement made receipt of a debt notice the event that created the guarantor's liability.
The Court distinguished that issue from the creditor's information duty. It stated that VÕS §146(1) required information about the principal debtor's performance at the guarantor's request. That did not transform notice into a condition precedent where the parties had not agreed one.
This is contract-specific. A different guarantee may expressly make demand, notice, expiry of a cure period or unsuccessful enforcement a condition of liability.
Default consequences can fall within the guarantee
The Court said that VÕS §145(2) made the guarantor responsible for the secured obligation in full, including consequences of breach such as default interest, contractual penalties, damages and specified termination-related costs. The actual agreement expressly covered unpaid principal, interest and breach claims, but capped the guarantor's total responsibility at 80,000 kroons.
The Court left the lower judgment in force and dismissed the guarantor's cassation appeal.
The operational lesson is to calculate both dimensions:
- which categories of principal and accessory claims the guarantee covers; and
- the contractual maximum or other limitation on the guarantor's exposure.
The principal debtor's bankruptcy defence was personal in the circumstances
Bankruptcy law stopped interest and default-interest accrual against the bankrupt debtor from the bankruptcy declaration for purposes of the claim in that proceeding. The Court held that the guarantor could not ordinarily invoke that particular defence.
The guarantee's purpose was to protect the creditor against the principal debtor's insolvency. Under the rule applied by the Court, a defence arising from liquidation or bankruptcy and tied to the principal debtor's person did not automatically reduce the guarantor's obligation. The parties could have agreed otherwise, but this guarantor had not alleged such an agreement.
That point must not be generalized into “bankruptcy never affects a guarantee.” The relevant insolvency rule, guarantee wording and nature of the defence must be identified.
3-2-1-69-14: the creditor's handling of other security can reduce liability
In , the principal debtor failed to perform a bank loan and was later removed from the register. The loan was also supported by security over a third party's property. The bank and that pledgor reached a compromise after the pledged property was realized, and the bank pursued the remaining claim against the guarantor.
Settlement with a pledgor did not automatically end the guarantee
The Supreme Court agreed that a compromise ending the relationship between the creditor and the third-party pledgor did not by itself terminate the separate relationship between creditor and guarantor. The creditor could still pursue the portion of the principal obligation that remained unsatisfied after realization of the pledge.
But that did not answer how large the guarantor's remaining liability was.
Impairment of other security may reduce the guarantee
The Court applied VÕS §145(5): if the creditor's conduct reduces other security that existed when the guarantee was made and secured the same claim, the guarantor's liability falls by the corresponding amount unless the creditor proves that the guarantor's loss was smaller.
Crucially, the rule was not limited to security supplied by the principal debtor. The guarantor could rely on it where a third party had granted the mortgage or pledge.
The inquiry is therefore causal and financial:
- what other security existed when the guarantee was concluded;
- what the creditor did or omitted;
- how that conduct reduced the security;
- the value of the reduction; and
- whether the creditor can prove that the guarantor suffered less harm.
The Supreme Court set aside the circuit-court judgment and remanded the case because those matters and the calculation of the claim had not been properly assessed. It did not finally declare that the entire guarantee was discharged.
Payment transfers the claim and normally its security
The decision also addressed what happens after a guarantor pays. The creditor's claim against the debtor transfers to the guarantor under VÕS §152(1), and associated securities generally follow the transferred claim under the rules discussed by the Court.
For a mortgage held by the former creditor, the paying guarantor may have a contractual claim requiring transfer of that mortgage, with the former creditor obliged to assist with registration.
This explains why careless release or impairment of collateral can prejudice the guarantor: it may destroy part of the recovery package the guarantor expected to obtain after paying.
3-2-1-4-16: restructuring the principal debtor did not release the guarantor
In , the guarantor secured a company's scheduled tax debt up to €670,000 and agreed to joint liability. The principal debtor failed to follow the payment schedule. A later restructuring plan altered the company's obligation.
The restructuring change applied only to the principal debtor
The Supreme Court applied SanS §45(4), under which a restructuring plan did not release a person jointly liable for the restructured company's obligation. The Court held that alteration of the principal debtor's obligations under the plan affected only that debtor, not the guarantor's obligation to the creditor.
The Court therefore rejected the argument that reducing the creditor's plan claim to 10% necessarily reduced the guarantee to the same extent. It upheld the result below and dismissed the guarantor's cassation appeal.
This is a statutory risk-allocation rule specific to the restructuring context reviewed in the judgment. It does not eliminate the accessory nature of guarantees generally.
The guarantor could not require realization of blocked collateral
The claim was secured by mortgages and a commercial pledge. Ordinarily, VÕS §149(5) may allow a guarantor to require the creditor to seek satisfaction from pledged property.
The Court held that the restructuring provisions applied as special rules. Once the plan prevented the creditor from realizing the collateral, the guarantor could not use the ordinary pledge-first rule to bar the claim.
Recourse against the debtor remained limited by the plan
After a guarantor performs, the creditor's claim transfers only to the extent for which the restructured principal debtor remains liable under the plan. The Court noted that this recourse issue was not the dispute before it and declined to decide the constitutional challenge directed at that limitation.
That creates a deliberate asymmetry: the guarantor may owe the creditor more than it can later recover from the restructured debtor. A guarantee risk model should not assume that full payment always produces an equal-value recourse asset.
2-19-15672/125: the guarantor may use the principal claim's limitation defence
In , a lender sued an individual guarantor for €500,000 under guarantees supporting two company loans. The lower courts awarded €400,000. During the appeal proceedings, the guarantor raised limitation.
Separate claims, accessory liability
The Supreme Court emphasized two propositions that must be held together:
- the guarantor's obligation is separate from the principal debtor's obligation to the creditor; but
- it is accessory to the secured obligation, so its creation, duration, content, enforceability and defences depend on the principal obligation.
Under VÕS §149(1), the guarantor may generally raise defences the principal debtor could have raised unless they are directly personal to that debtor. The Court said this includes limitation of both the claim arising from the guarantee and the claim arising from the creditor's contract with the principal debtor.
A suit against the guarantor did not stop the principal claim's limitation period
Because the two claims are distinct, filing the action against the guarantor could stop limitation on the guarantee claim without stopping limitation on the creditor's claim against the principal debtor.
The result can be counterintuitive: the claim against the guarantor may not itself have expired, while the underlying claim against the borrower has. If the principal debtor could then invoke limitation, the guarantor may use the same defence under VÕS §149(1).
This makes defendant identity and procedural history essential. A docket entry saying “action filed” is not enough; the analyst must identify against whom it was filed and which claim's limitation it affected.
The limitation issue was remanded, not finally resolved
The Supreme Court held that the guarantor raised limitation on time when responding within the deadline to the lender's appeal. The circuit court had wrongly refused to consider it.
The Supreme Court did not finally decide whether the principal claim had expired. It set aside the judgment and remanded for the circuit court to assess the defence on its merits after allowing the lender to respond and produce evidence.
The decision therefore establishes the availability and procedural admissibility of the defence, not the final outcome of the underlying monetary dispute.
How the decisions fit together
The judgments can appear to point in opposite directions unless their rules are separated.
The key is not to treat “accessory” as meaning that every event affects borrower and guarantor identically. Accessory liability supplies the baseline connection. Contractual terms, personal defences and special insolvency or restructuring rules determine where the two claims diverge.
A case-review checklist
Before relying on a guarantee after non-payment, preserve evidence for:
- the principal agreement and exact secured obligations;
- proof of drawdown, delivery or other creditor performance;
- the principal debtor's due date and breach;
- the signed guarantee, amendments and applicable form requirements;
- whether liability is joint or subsidiary;
- every condition for demand, notice or cure;
- the monetary ceiling and covered principal, interest, penalties, damages and costs;
- payments, set-off, settlements and debt calculations;
- limitation separately for the principal and guarantee claims;
- bankruptcy, liquidation or restructuring events and the version of the applicable law;
- other guarantees, mortgages and pledges existing when the guarantee was made;
- any creditor act that released, impaired or undervalued another security;
- defences available to the principal debtor and whether any are personal;
- the guarantor's recourse and transferred security after payment; and
- each judgment's procedural outcome, including whether it remanded the case.
A credit file should not reduce this analysis to a single “guarantee called” flag. The amount ultimately recoverable can depend on evidence and legal events that occur after the borrower's initial missed payment.
Authority and chronology limits
All four decisions are judgments of the Estonian Supreme Court's Civil Chamber. They are stronger interpretive authorities than a party's allegation or a lower court's reasoning reproduced in their procedural histories.
The article attributes each proposition to the Supreme Court's own reasoning section and distinguishes a judgment left in force from one remanded. That distinction matters: a remand decides the legal error identified by the Supreme Court but may leave the ultimate monetary liability unresolved.
The cases span 2010 to 2024 and apply provisions and contracts relevant to their own facts. For a live dispute, the historical version of each cited statute, subsequent amendments, later case law and the exact transaction documents must be checked. The date on which Legalcode refreshed a database record is not the decision date or evidence that every cited provision remains unchanged.
MCP and source audit findings
Production research reached the seven-call cap with one Discover, two Search attempts and four exact Fetches. One Search was rejected because it used the `decision` result level advertised by Discover; it was not used as evidence. Every accepted call used the configured production bypass token and charged zero. The four exact MCP-provided full-text downloads were then retrieved with authentication and reviewed completely.
The source-language Search for `käendaja põhivõlgnik` returned a relevant first page of Supreme Court decisions and exposed court, date, case-number and citation metadata consistently. Three defects were nevertheless confirmed.
Discover advertises a result level that Search rejects
The case source profile says `resultLevels: ["decision"]`. Search rejects `resultLevel: "decision"` during schema validation and says only `auto`, `document`, `flow` or `record` are accepted. Replacing it with `record` succeeds.
requests one coherent contract across source profiles, Search input validation, documentation and tests. The issue also records the same class of incompatibility for agreement and law profiles.
One official judgment contains an impossible appellate chronology
Case 3-2-1-4-16 is dated 16 March 2016 but identifies the challenged circuit-court judgment as dated 12 October 2016. The live official Riigikohus text contains the same contradiction, so Legalcode did not introduce it during extraction.
requests preservation of the official wording, a source-quality warning, authoritative investigation of the actual lower-court date, and corpus-level appellate chronology checks. The article does not guess a corrected year.
A cited judgment paragraph became a nonexistent statutory point
Fetch metadata for case 3-2-1-69-14 includes a legal-basis key for `VÕS §145(5) point 17`. The decision actually cites §145(5) and then paragraph 17 of another Supreme Court judgment. The reference extractor appears to have carried the statutory context into the separate case-paragraph locator.
requests correction of the fabricated key, authority-context boundaries, provision-hierarchy validation and an audit for similar errors.
The malformed legal-basis child key was not used to find or interpret the judgment. The exact Search result, Fetch metadata, authenticated decision text and official URL supplied the evidence.
Conclusion
The published Supreme Court decisions show that guarantor liability after borrower default is substantial but conditional.
A jointly liable guarantor may be pursued without first exhausting the borrower and may cover default consequences within the guarantee's scope. Yet the guarantor can retain non-personal defences of the principal debtor, including limitation; the creditor's impairment of other security can reduce exposure; and payment normally transfers recourse and security rights.
Insolvency and restructuring do not produce one universal result. A defence personal to a bankrupt debtor may be unavailable to the guarantor, while a restructuring statute can preserve the creditor's full claim against the guarantor but restrict the guarantor's later recourse.
The safe conclusion is therefore case-specific: prove the principal debt and breach, classify the guarantee, calculate its scope, test every defence and security event, and read the judgment's final procedural disposition before recording guarantor liability as established.
Sources and audit issues
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.