TREADSTONE LAW · ONTARIO · DIGITAL LEGAL SERVICES · EST. MMXXI ·TSL
Home/Case Studies/Mergers & Acquisitions
№ 377 Case Study — Mergers & Acquisitions

A cousin's payroll entry nearly derailed the sale of the family business

A minority shareholder in a Bracebridge manufacturing company noticed a payroll line that did not match any actual work, and traced it back to a relative on the payroll with no defined role before the sale could close.

Mergers & Acquisitions8 min readBracebridge, OntarioRelated-party arrangements
All Mergers & Acquisitions case studies
ClientElena, a minority shareholder in a Bracebridge manufacturing company being sold
The issueA relative of the majority owner was on the payroll with no defined role, undisclosed as a related-party arrangement ahead of the sale
ServiceReviewed the payroll and related-party disclosures, confirmed the arrangement, and negotiated its removal before the purchase agreement was signed
ResolutionThe arrangement was removed and the deal closed on clean terms, with Elena's minority position protected from a liability she had not created

The situation

Elena noticed it while reviewing the diligence binder the buyer's team had assembled for the sale of the Bracebridge manufacturing company she held a minority stake in. A payroll line, modest but recurring, paid out to Niran every month, tucked into a spreadsheet with dozens of other employee names Elena recognized without a second thought. Elena knew Niran. He was Marco's cousin, and Marco was the majority owner who had run the company for years and had negotiated the sale on behalf of all the shareholders. What Elena did not know was what Niran actually did for the company. She had never seen him at the plant, never heard his name come up in an operations meeting, and could not recall a single project or account he was associated with, despite having sat on more than her share of management updates over the years the two of them had worked together.

She raised it with Marco directly, expecting a simple explanation — a consulting arrangement, a part-time role she had simply never crossed paths with, something ordinary and easily documented. Marco's answer was vague. Niran had helped out informally over the years, Marco said, with things that were hard to itemize precisely. There was no job description on file, no defined hours, and no documentation setting out what the payments were for beyond a generic payroll category, and Marco seemed uncomfortable being pressed further on specifics.

The company was mid-size, valued in the eight to fifteen million dollar range for the pending sale, and the buyer's diligence team had flagged the payroll line as a related-party item requiring explanation, but had not yet pushed hard on it. Elena, holding a minority stake and therefore with the most to lose if the sale fell apart or closed on bad terms, could not accept the vague answer Marco had given her. If the arrangement was what it appeared to be — payments to a relative for no defined work — it was exactly the kind of undisclosed related-party transaction that could unwind the deal, trigger a working capital adjustment against the sellers, or create liability that would land disproportionately on a minority shareholder who had no control over how the company had been run and no say in who Marco chose to put on the payroll.

Elena retained our office to review the payroll records, understand what the arrangement actually was, and make sure it did not become her problem when the deal closed, before the buyer's own team pushed the question further and forced a more difficult conversation later in the process.

The gap nobody had noticed

The company's related-party disclosure schedule, prepared for the buyer's diligence process, listed several legitimate arrangements: a lease on equipment from a company Marco partly owned, a supply contract with a business run by another shareholder's spouse, both properly disclosed with terms and dollar amounts attached and both reviewed and approved by the board in years past. Niran's payroll entry was not on that schedule at all. It sat inside the general payroll ledger, coded the same as any other employee, with nothing flagging it as connected to Marco or requiring separate disclosure, which meant it had passed through years of routine bookkeeping without a single person questioning it.

This is the gap that matters in related-party reviews, and it is easy to see why nobody had caught it earlier. A related-party lease or supply contract is a discrete document that gets pulled and reviewed as a matter of course, because it looks unusual on its face and invites scrutiny. A payroll entry for a relative with no defined role is buried inside hundreds of other payroll lines, and unless someone is specifically cross-referencing employee names against the ownership and family structure of the business, it does not stand out at all. Marco's own advisors, focused on the larger and more obviously flagged related-party arrangements, had not run that cross-reference, and neither, apparently, had anyone in the years before the sale was ever contemplated.

The legal exposure was real. An undisclosed related-party payment, once discovered by a buyer after signing, can support a claim that the purchase agreement's representations about the company's arrangements and liabilities were inaccurate, potentially triggering an indemnity claim against the selling shareholders. Whether that exposure lands on the sellers as a group or only against each one for their own proportionate share turns entirely on how the purchase agreement is drafted; many agreements make each seller severally liable, capped at that seller's share of the proceeds, so a buyer cannot assume it can pursue any one of them for the whole amount. For a majority owner like Marco, that risk might be manageable, absorbed as part of doing business with a relative on informal terms over many years. For a minority shareholder like Elena, who had no involvement in hiring Niran and no knowledge of the arrangement until she found it herself in the diligence binder, the exposure was disproportionate: she stood to bear a share of any post-closing liability for a decision she had never made, never approved, and could not have prevented even if she had known about it sooner.

There was also a relationship problem layered underneath the legal one. Marco was not just the majority owner; he was someone Elena had worked alongside for years, built the company with in some real sense, and Niran was his cousin. Raising the issue meant directly challenging an arrangement Marco had set up for a family member, in the middle of a deal everyone wanted to close and after years of a working relationship neither of them wanted to damage. Elena needed the issue resolved without the conversation turning into a personal conflict that could poison the rest of the sale process for every shareholder involved, not just the two of them.

What we did

  1. Reviewed the full payroll ledger against the company's org chart and related-party disclosure schedule. We cross-referenced every payroll entry against known family and ownership connections, not just the entries Marco's advisors had already flagged, which is what surfaced Niran's payment as the only related-party item missing from the formal disclosure, a check the buyer's own diligence team had not yet completed at the point Elena raised it.
  2. Requested documentation of Niran's actual role, if any existed. We asked Marco directly for any job description, timesheet, project record, or correspondence establishing what work Niran had performed. None existed in any form beyond the payroll entry itself, which confirmed the arrangement could not be defended as an ordinary employment relationship if the buyer's team ever chose to ask the same question directly.
  3. Quantified the total historical exposure the arrangement created. We calculated the cumulative payments made to Niran over the relevant period to understand the scale of the potential indemnity exposure if the buyer discovered the arrangement independently after closing, giving Elena a concrete number to work from rather than an open-ended risk she could not size or explain to her own advisors.
  4. Advised Elena on her position as a minority shareholder facing a majority owner's undisclosed arrangement. We explained that as a minority shareholder, Elena had standing to insist the disclosure schedule be corrected before signing, and that raising the issue formally through counsel, rather than only informally through conversation, gave the concern the weight it needed without requiring Elena to personally confront Marco again.
  5. Raised the issue with the buyer's diligence team through proper channels, in coordination with Marco. Rather than letting the buyer discover the gap independently, which would have looked far worse for all the sellers, we worked with Marco to bring the corrected disclosure to the buyer proactively, framing it as a related-party item identified and resolved through the sellers' own review process.
  6. Negotiated the removal of the arrangement before the purchase agreement was signed. We worked with Marco to have Niran's payroll entry discontinued and the related-party disclosure schedule corrected to reflect that no such arrangement existed going forward, closing the gap before it could become a warranty problem at signing. We set a firm timeline for the correction to be completed, tied to the signing date, so the fix did not linger as an open item the buyer's diligence team might independently notice first.
  7. Confirmed the corrected disclosure was reflected in the final representations Elena would be bound by. Before Elena signed on to the final purchase agreement as a selling shareholder, we confirmed the related-party representations accurately reflected the corrected state of affairs, so she was not making a warranty that later turned out to be false through no fault of her own, a step that mattered as much for her peace of mind as for the legal record.

The outcome

The arrangement was removed and the sale closed on clean terms. Niran's payroll entry was discontinued before the purchase agreement was signed, the related-party disclosure schedule was corrected to reflect an accurate picture of the company's arrangements, and the buyer proceeded to closing without raising the issue as a diligence objection, since it had already been identified and resolved by the time the buyer's team would otherwise have flagged it independently, which spared the sellers the far worse position of explaining an undisclosed related-party arrangement after the buyer found it on its own.

For Elena, the outcome protected exactly what she had been worried about: she signed the final purchase agreement without warranting a related-party disclosure that she knew, before the correction, would have been inaccurate. Had the arrangement gone unaddressed and surfaced after closing, Elena's minority stake would have exposed her to a share of the resulting indemnity claim for a decision Marco had made unilaterally, years before the sale was ever contemplated, and one she would have had no realistic way to defend against once the money had already changed hands.

The relationship also came through the process intact. Because the correction was raised through proper channels and framed as a related-party item identified and resolved rather than an accusation, Marco was able to make the change without the conversation becoming a personal conflict with Elena or with Niran, and the two cousins were able to work out separately, on their own terms, how Niran's informal involvement with the company would wind down. The sale closed on schedule, and Elena's diligence in reading the payroll ledger closely, rather than accepting a vague explanation at face value, turned out to be the reason a real liability never made it into the closing documents. Her fellow shareholders, once they understood what had been at stake, were glad she had pushed the question rather than letting it pass.

What you can learn from this

  • Related-party review should cross-reference the full payroll ledger against ownership and family connections, not just the arrangements already flagged as leases or supply contracts.
  • An undefined role with no job description, timesheet, or project record is a red flag on its own, regardless of who holds the position or how the payments are labelled.
  • A minority shareholder has standing to insist a disclosure schedule be corrected before signing, even when the arrangement was set up by the majority owner without consulting them.
  • Bringing a corrected disclosure to the buyer proactively, before the buyer discovers it independently, protects the credibility of the entire selling group during diligence.
  • Do not sign a representation you know to be inaccurate just because correcting it means an uncomfortable conversation with someone you know well. The liability lands on you regardless of the relationship.
This case study is entirely fictional. It does not describe any real client, file, or matter handled by Treadstone Law, and it is not a real file with details changed. All names, people, properties, businesses, dollar amounts, dates, and events are invented, and any resemblance to a real person, business, or situation is coincidental. Fictional scenarios like this one illustrate the kinds of legal issues people in Ontario commonly face and how a lawyer can help. They are general information, not legal advice — no two matters unfold the same way, and nothing here predicts the outcome of any real case. Reading a case study does not create a lawyer-client relationship. If you are facing something similar, speak with a lawyer about your specific circumstances.

This is a mergers & acquisitions problem we handle

Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.

ContactStart a File →