Treadstone Associates
Case File · Representations & Warranties

A Guarantee For An Affiliate Was Never A Liability The Balance Sheet Had To Show

Anonymised, illustrative composite. An Ontario share purchase, a $340,000 guarantee for a related company, and the gap between a representation about what the books show and a representation about what the seller actually knows.

Treadstone Associates · Updated 2026

At a glance

  • • An Ontario share purchase of a family-owned logistics company. The “no undisclosed liabilities” representation covered liabilities “required to be reflected or reserved against on a balance sheet prepared in accordance with ASPE.”
  • • Post-closing, the buyer learned the target had guaranteed a $340,000 line of credit for an affiliated company owned by the seller’s family, current and undrawn beyond its limit at closing.
  • • Under the accounting framework the representation itself was pegged to, a guarantee is a contingency — disclosed in notes only where a future payment is both likely and estimable, and recognised as a balance-sheet liability only where it already is. A current, undrawn guarantee met neither test.
  • • The buyer's claim under the no-undisclosed-liabilities representation failed on the representation's own words: the guarantee was never a liability the balance sheet had to show, so it was never a liability the representation covered.
  • • The financial-statements representation, sitting right next to it, is a different promise entirely — and this is the file where the difference between the two decided everything.

The situation

A buyer acquired 100% of the shares of an Ontario logistics company from a family that had owned and operated it, alongside two related businesses, for eighteen years. The share purchase agreement carried both of the standard financial representations: a financial-statements representation, stating the target’s financial statements fairly presented its financial position in accordance with the accounting framework the company used, and a separate no-undisclosed-liabilities representation, stating that the target “has no liability or obligation of any nature required to be reflected or reserved against on a balance sheet prepared in accordance with ASPE, other than liabilities reflected in the Financial Statements or incurred in the ordinary course of business since that date.”

The problem

Four months after closing, the buyer's lender, running its own diligence on a refinancing, discovered that the target had guaranteed a $340,000 revolving line of credit extended to a separate company owned by the seller's family — a related trucking business that shared a yard with the target but was never part of the deal. The guarantee did not appear anywhere in the disclosure schedule, the financial statements, or the data room. The affiliate's line was current at closing and remained current afterward; nothing had been drawn beyond its ordinary operating limit, and no payment had ever been demanded of the target under the guarantee.

The buyer sued for breach of the no-undisclosed-liabilities representation, on the straightforward theory that a $340,000 contingent exposure, never disclosed, was exactly the kind of undisclosed liability the representation existed to catch.

The numbers

$340,000 was the full guaranteed amount — the buyer's worst-case exposure if the affiliate defaulted and the lender called on the guarantee. Nothing had been called, and the affiliate's own financial position, reviewed after the fact, showed no indication a call was likely in the near term. The dispute was never about whether $340,000 mattered if it came due; it was about whether an exposure that had not come due, and was not expected to, was a “liability” the representation covered at all.

The rule that decided it

No statute governs the drafting or scope of a no-undisclosed-liabilities representation in a Canadian share purchase agreement; its reach is set entirely by its own words, and this file turns on a distinction the representation's drafting made without anyone appearing to intend it.

A no-undisclosed-liabilities representation can be drafted two different ways, and they are not stylistic variants of the same promise. One version reaches every liability of the company, known or contingent, disclosed or not, whatever an accounting framework would do with it — a broad, catch-all promise. The other — the version in this agreement — is pegged specifically to what the applicable accounting framework would require to be reflected or reserved against on the balance sheet. That is a narrower, technical standard, and it does real work: under Canadian private-company accounting standards, a guarantee of another entity's debt is ordinarily treated as a contingency, not an existing liability. A contingency is recognised — entered as a liability on the balance sheet itself — only once a future payment is both likely and reasonably estimable. Short of that, it is, at most, a matter for note disclosure, not balance-sheet recognition, and note disclosure is a different thing than being “reflected or reserved against on a balance sheet.”

The affiliate's line of credit was current. No default had occurred and nothing in its financial position suggested a call was probable. On the accounting standard the representation itself invoked, the guarantee was, at most, a note-disclosure item — and arguably not even that, absent a probable and estimable future payment. It was never a liability “required to be reflected or reserved against on a balance sheet,” the only category this representation promised was complete.

The financial-statements representation, sitting in the same article, is a different promise. It says the statements themselves fairly present the company's financial position under the framework used to prepare them — and if the framework did not require the guarantee to be recognised or even disclosed, the statements were not false for omitting it. Both representations were, on their own narrow terms, true. Neither reached a guarantee that a broader, catch-all no-undisclosed-liabilities representation — one written to cover any obligation, contingent or otherwise, whether or not an accounting standard would require it to appear anywhere — would have caught without difficulty.

The outcome

The buyer's claim failed. Neither financial representation, as drafted, reached a contingent guarantee that had not crossed the recognition or probable-disclosure threshold both representations were pegged to. The guarantee itself remained live, and was eventually addressed commercially, outside the indemnity process, once the buyer's lender required it released as a refinancing condition.

What it would have cost otherwise

Had the representation instead covered “any liability, whether accrued, absolute, contingent or otherwise, and whether or not required to be reflected on a balance sheet,” the guarantee would have fallen squarely within it regardless of accounting treatment, because that drafting borrows no scope from an accounting framework at all. The recognition-based version is not defective; it is narrower, and the buyer's diligence process never priced the difference.

The tell

The tell was in the due diligence request list: the buyer's checklist asked for “all guarantees, suretyships and contingent obligations of the Company” — a broader ask than the representation, as drafted, actually promised. The list and the representation were drafted by different people at different stages, and nobody checked that one backstopped the other.

Takeaways

  • • A no-undisclosed-liabilities representation pegged to what an accounting framework requires to be “reflected or reserved against on a balance sheet” is narrower than a representation covering every liability regardless of accounting treatment. The two are drafted to look similar and are not.
  • • A guarantee, suretyship or other contingent obligation is frequently a note-disclosure item at most under Canadian private-company accounting standards, not a recognised balance-sheet liability — which means a recognition-pegged representation can systematically miss exactly this category of risk.
  • • The financial-statements representation and the no-undisclosed-liabilities representation are drafted to look like they overlap. They fail in different places, by reference to the same accounting framework, and a buyer relying on one to backstop a gap in the other is relying on nothing.
  • • If diligence specifically asks for guarantees and contingent obligations, the representations need a clause that reaches them regardless of accounting recognition — not a representation borrowed from a balance-sheet standard that was never built to answer that question.

Sources

  • • No statute governs the drafting or scope of a no-undisclosed-liabilities representation in a Canadian share purchase agreement; its reach depends entirely on its own wording. The accounting treatment of a contingency such as a guarantee is a matter of the applicable private-company accounting framework (ASPE), not of statute, and no specific ASPE provision is quoted here because its text was not fetched from a primary source in this session.
  • • Glossary: disclosure schedule.
  • • Treadstone Law — seller representations in an Ontario business purchase agreement — adjacent, not on point: a general overview of the seller representation package; it does not address the recognition-versus-disclosure gap this file turns on.

See where AI pays off first in your business.

A 30-minute call is enough to tell you whether AI pays for itself here.

The Canadian benchmark

What do businesses like this one actually sell for?

Canadian small-business transaction data is not published anywhere, so most valuations in this country quote an American benchmark. The Deavo–Treadstone Acquisition Index is a daily record of Canadian listings built to replace that: asking-price distributions by province and city are published now, and days on market, departure rates and asking-to-sale spreads follow as the series lengthens. Leave an email and we will tell you as each measure lands.

No pitch, no listings. One email when the first report lands.