The situation
'If we fall behind on a payment, can he take our car?' Zainab asked, sliding a stapled set of pages across the table. She and Yohannes had been saving for four years, she working shifts at a gas station and he working nights as a security guard, toward a single goal: owning a small business instead of working for someone else. They had found it in a variety store in Dundas that a longtime owner named Selam was ready to retire from.
The purchase price sat in the low six figures, just under $200,000, and like a lot of small business sales, the deal was not a straightforward cash transaction. Zainab and Yohannes had enough saved for a down payment, but not the full price. Selam agreed to carry the balance himself, financing the rest of the sale over several years while the couple paid him back out of the store's earnings. This kind of arrangement, sometimes called vendor take-back financing, is common in small business sales precisely because banks are often reluctant to lend against an unproven independent operator's future income.
To protect that loan, Selam's lawyer had drafted a security agreement, the document that gives a lender the legal right to seize specific property if the borrower stops paying. In principle this is routine and expected. Sellers who finance part of a sale are entitled to security for what they are owed. The couple was not objecting to the idea of security. What worried Zainab, reading the draft on her own before bringing it to us, was how the property being secured was described.
The clause did not list the store's fridges, shelving, cash register and inventory, the things actually being purchased. It described the collateral in much broader terms, language that on its face could reach the couple's personal vehicle, their bank accounts and any other property they came to own after closing, whether or not it had anything to do with the store. Zainab could not tell from the wording whether that reading was intentional or simply careless drafting carried over from a template. Either way, before signing a document that could put everything they had worked for on the line, she wanted someone to look at it who was not related to either side of the deal. Yohannes agreed the wording made him uneasy too, though he had been more inclined to trust Selam's lawyer simply because Selam had always dealt with them fairly in the years they had known him.
Why this was harder than it looked
On paper, fixing an overly broad security clause is a fairly mechanical piece of drafting. The harder part of this file was that Selam was not a stranger. He had known Yohannes's family for years, had encouraged the couple to make an offer on the store in the first place, and viewed the sale as much as a personal transition into retirement as a business transaction. When we raised the scope of the security agreement with the couple, their first instinct was worry that questioning it would look like an accusation, or worse, jeopardize a deal they had waited years for.
That reaction is common and understandable, but it is also exactly the situation where a badly worded agreement causes the most damage later. Personal relationships between buyer and seller can make it harder, not easier, to negotiate terms cleanly, because both sides are managing the deal and the relationship at the same time. Selam's own lawyer, it turned out, had used a precedent from a much larger commercial financing file and had not tailored the collateral description down to a small retail purchase. Nobody on either side had set out to overreach. The clause was simply broader than either party actually intended, and broader than it needed to be to protect Selam's real interest, which was getting paid back for the store he was selling.
Under Ontario's personal property security law, the wording of the agreement sets what the lender can reach, but the statute fills gaps in the lender's favour. A security interest carries through to the proceeds of the collateral, such as insurance money or the money from selling it, even where the agreement says nothing about proceeds, and language like 'all present and after-acquired property' captures assets the borrower did not own when it signed. Once an agreement is signed and registered, unwinding an overly broad description later is far harder and far more expensive than fixing it before signing. If Zainab and Yohannes had defaulted on even one payment years down the road, a broadly worded agreement could have given Selam, or anyone he later assigned the debt to, a plausible argument for reaching well beyond the store.
We also had to manage the emotional side of the file directly. Before any redrafting happened, we spent time with Zainab and Yohannes talking through what a normal, properly scoped vendor security agreement looks like, so they could see the difference between a reasonable request and an unreasonable one, and raise it with Selam calmly rather than defensively. That groundwork mattered as much as the legal fix itself, because a legally sound revision presented clumsily could still have derailed a deal that depended on trust between two families as much as on paper.
What we did
- Reviewed the draft security agreement line by line against the assets actually described in the purchase agreement, comparing what Selam was entitled to secure with what the collateral clause actually claimed, to identify exactly where the two documents diverged and by how much, and how far the broader wording could realistically be stretched if it were ever tested by a court asked to interpret it against the couple rather than in their favour.
- Explained the gap in plain terms to Zainab and Yohannes so they understood this was a drafting problem rather than bad faith on Selam's part, which lowered the temperature before any conversation with the other side and helped them approach the fix as a shared correction rather than a confrontation neither of them wanted to have, particularly given how much the friendship with Selam mattered to both of them.
- Prepared a coaching conversation, not just a legal letter, walking the couple through how to raise the issue with Selam directly and respectfully, since the relationship between the parties meant a purely formal letter risked reading as an accusation and straining a deal both sides still wanted to complete on the original timeline, without losing sight of the substance of what actually needed to change in the wording.
- Explained how a registered security interest actually works under Ontario's personal property security regime, so the couple understood why the wording mattered beyond the paper it was written on, and why a public registration matching an overly broad clause could complicate their ability to get other financing later, since any future lender checking the registry would see a claim that looked far larger than the debt it was meant to secure.
- Drafted a revised collateral description that limited the security interest to the specific fixtures, equipment and inventory transferred as part of the store, matching the scope of the loan to the scope of what was actually purchased with that loan and nothing beyond it, using language specific enough that neither side would need to guess at its meaning if a dispute ever arose years down the road.
- Negotiated the revised wording directly with Selam's lawyer, explaining that a narrower, accurately scoped agreement protected Selam's real interest just as effectively while removing any risk of a later dispute over what the security actually covered if a payment was ever missed, and pointing out that the original wording had likely been copied from a larger commercial file rather than drafted specifically for this sale.
- Confirmed the registration details that would be filed once the agreement was signed, so the public record of the loan matched the narrowed clause and would not itself become a source of confusion for either party, a future lender, or a future buyer of the store, since a registration broader than the underlying agreement can create exactly the kind of doubt the redraft was meant to eliminate.
- Reviewed the final documents with the couple before signing, confirming in plain language exactly what property Selam could claim if a payment was missed, what was permanently outside his reach regardless of what happened with the store, and how the loan balance would decline with each payment they made, so they left the meeting able to explain the arrangement to each other without needing to reread the agreement.
- Set out a short written summary of the loan terms in plain language for the couple to keep alongside the signed agreement, so that years into the loan, without needing to reread the full legal document, they could quickly remind themselves exactly what property was and was not at risk if a payment was ever missed, and hand that summary to a future lender or advisor without confusion.
The outcome
Selam's lawyer accepted the narrowed collateral description without resistance once the comparison between the two documents was laid out. The final security agreement gave Selam exactly what a vendor take-back loan is meant to provide: a real claim against the business assets if the couple defaulted, and nothing reaching into their personal property or future, unrelated income.
The sale closed on the timeline the parties had originally planned, with no delay caused by the correction. Because the issue was caught and resolved before signing, there was no dispute to litigate, no strained renegotiation after the fact, and no lasting friction between Zainab, Yohannes and Selam, who remained on good terms through the transition and afterward. Selam even stayed on informally for a few weeks after closing to help the couple settle into supplier relationships and the store's ordering routines, a transition that would have been far more awkward had the security agreement dispute turned adversarial.
Nothing about this file involved a payment default, a court filing or a breakdown between the parties. The entire value of the work was in what did not happen. A poorly scoped security agreement, left unexamined, would have sat quietly in the background of the couple's new business for years, a risk they carried without knowing its full size until the day, if ever, they missed a payment and found out how far it actually reached.
For Zainab and Yohannes, the practical result was a loan they understood completely, secured against the store they were actually buying and nothing else. Their car, their savings and anything they might come to own later stayed entirely outside Selam's reach, whatever happened with the business in the years the loan remained outstanding. That clarity, more than any single clause, was what let them treat the purchase as a fresh start rather than an open-ended risk hanging over everything else they owned.
What you can learn from this
- If a seller is financing part of your purchase, read the security agreement as carefully as the purchase agreement itself. It defines what you could lose, not just what you are buying.
- A security agreement should describe collateral that matches what is actually being financed. If the wording reaches further than the loan, ask why before you sign, not after a default.
- Personal or family relationships between buyer and seller do not make careless drafting less risky. They make it harder to raise concerns, so raise them earlier rather than later.
- Templates carried over from unrelated deals are a common source of overly broad clauses. A document reused from a larger transaction rarely fits a smaller one without adjustment.
- Catching a scoping problem before signing costs a conversation and a redraft. Catching it after a default costs a dispute, and possibly property you never expected to lose.
This is a buying & selling a business problem we handle
Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.