TREADSTONE LAW · ONTARIO · DIGITAL LEGAL SERVICES · EST. MMXXI ·TSL
№ 249 Case Study — Tax

Catching a Filing Mistake Before It Ever Reached a Return

Jacek walked into the office with a draft separation agreement he had not yet signed and a question he almost did not think to ask. That one question changed how the whole document was written.

Tax8 min readCambridge, OntarioChild support and filing
All Tax case studies
ClientJacek, an auto body technician recently returned to Canada, negotiating child support with Lesia, a security guard
The issueA draft separation agreement bundled child support with an unrelated reimbursement, risking the reimbursement's own tax treatment
ServiceReviewed and redrafted the support terms so the payments stayed non-taxable and non-deductible as intended
ResolutionThe problem never reached a filed return, and both parents kept the tax treatment they had actually agreed to

The situation

Jacek called the office on a Thursday and asked if he could come in the next morning, before his shift at the auto body shop started. He arrived with a folder of papers and a question that, by his own account, he had almost decided not to bother asking because it seemed too small compared to everything else going on. He and Lesia, the mother of his son Taras, had spent the last two years working out a separation after Jacek had spent nearly three years living and working outside Canada, a stretch that had complicated everything from his residency status to how their finances were untangled once he came back.

Jacek and Lesia had never married, but they had lived together for six years before he left, and Taras had stayed in Cambridge with Lesia the whole time Jacek was away, seeing his father mainly through video calls and two visits home. Since Jacek's return, the two of them had been working, mostly without lawyers, on a separation agreement that would set out parenting time and a monthly child support amount based on Jacek's income as an auto body technician and Lesia's income as a security guard at a shopping plaza.

They had largely agreed on the substance: a monthly amount, a schedule for adjusting it if either of their incomes changed materially, and a parenting time arrangement that reflected the fact that Jacek was still rebuilding a routine with Taras after being away so long. What they had not agreed on, because neither of them had thought to discuss it, was exactly how the agreement described the payment itself. A relative who worked in bookkeeping had glanced at their draft and mentioned, almost in passing, that the wording looked a little unusual to her, and suggested Jacek get it checked before either of them signed anything.

That offhand comment was the reason Jacek was sitting in our office on a Friday morning with an unsigned draft, asking a question he was not sure was even worth our time. He kept saying, almost apologetically, that he did not want to waste an appointment over what was probably nothing, and that he and Lesia had already put so much work into getting the numbers right between them that he half expected to be told the wording did not matter at all.

What was actually at stake

It was worth the time. The draft agreement, in an effort to be thorough, had bundled the monthly child support payment together with a separate reimbursement Jacek had agreed to make toward some of Lesia's moving costs from when she and Taras had relocated to a smaller unit during his absence, describing both amounts under a single combined monthly figure without distinguishing which portion was support for Taras and which was something else entirely.

That distinction matters for how the payment gets treated on both parents' tax returns, though perhaps not in the direction it first seems. Child support payments, when an agreement clearly identifies them as support for a child, are not taxed as income to the parent receiving them and are not deductible by the parent paying them, a rule that has applied for years specifically because lawmakers wanted child support kept simple and untouched by the tax system on either side. Being specific in the agreement matters, but not because vague wording would make Lesia's support taxable to her: where a single combined amount is not broken out, the whole payment is generally read as child support regardless, so it stays tax-free to Lesia and non-deductible to Jacek either way. What blending the two payments actually put at risk was the other side of it, the reimbursement: an unallocated figure defaults to child support treatment, so Jacek stood to lose any ability to have the reimbursement recognized as something separate from support once the two were folded into one line.

Had the agreement been signed as drafted, Lesia would not have owed tax on the payments; bundled or not, the amount would still have been treated as child support and stayed tax-free to her, which is what she and Jacek both intended for that part of it. The exposure sat on Jacek's side instead. Without a separate clause on paper, he would have had nothing to point to later showing that part of the monthly figure was a reimbursement rather than support, which is exactly the kind of gap a reviewing tax officer, or Lesia herself in a future dispute, could read the way that suited them rather than the way Jacek and Lesia had actually meant it.

The stakes were not enormous in absolute dollar terms, somewhere in the fifteen to fifty thousand dollar range across the years the agreement would likely run, but for two people rebuilding their finances after a long separation, an unexpected tax bill of that size would have landed hard, particularly on Jacek's side of the ledger. And because both of them had drafted the agreement without a lawyer up to that point, working from a template one of them had found online and adjusting the numbers themselves, there was nothing in the document's history that would have flagged the problem to either parent before a reviewing tax officer eventually did.

What we did

  1. Read the draft agreement line by line with Jacek before anything was signed, flagging the exact clause where the combined monthly figure blended child support with the moving-cost reimbursement, and explaining in plain terms why that blending created a real tax risk rather than just an awkward phrasing choice. This gave Jacek something specific and concrete to raise with Lesia, rather than a vague sense that something in the document felt off.
  2. Separated the two payment streams into distinct clauses, one clearly labelled as child support for Taras calculated against both parents' incomes, and a second clearly labelled as a one-time reimbursement unrelated to child support, with its own separate payment schedule and its own end date. This structural change was the core fix, since it gave each dollar flowing between the two parents an unambiguous label on paper that a reviewing officer could not later reinterpret.
  3. Confirmed the child support clause used language that matched how support agreements are meant to read to preserve non-taxable, non-deductible treatment, avoiding any wording that hinted at the payment being compensation, a settlement, or anything other than support calculated for the direct benefit of the child living primarily with Lesia. Even a stray phrase borrowed from a general-purpose template can undo the clean tax treatment the rest of the clause is built to protect.
  4. Contacted Lesia directly, with Jacek's agreement, to explain the change before the revised draft went back to her, since a document arriving with unexplained edits after months of informal negotiation risked reopening trust issues that had taken real effort to rebuild between two people who were, by then, on genuinely decent terms after a difficult few years apart. A short, plain explanation up front made the change land as helpful rather than as a unilateral move by Jacek's lawyer.
  5. Adjusted the reimbursement schedule when Lesia changed her position midway through, after she initially wanted the moving-cost reimbursement folded back into a single combined payment for simplicity's sake, requiring a second round of explaining why the separation mattered and a revised schedule that kept both streams distinct while still landing on a total monthly amount close to what she had originally expected to receive.
  6. Walked both parents through a plain-language example showing what a combined, unlabelled payment could look like on a tax return versus what the properly separated version would look like, using rough numbers so neither Jacek nor Lesia had to take the risk on faith. Seeing the difference in concrete terms was what finally settled Lesia's hesitation about the separated structure.
  7. Reviewed the final signed agreement against how it would actually be reported on each parent's return, walking Jacek through exactly what he should tell his own accountant about which figures were and were not deductible, so the correct treatment would carry through consistently from the agreement itself into the actual filings each year going forward.

The outcome

The agreement Jacek and Lesia ultimately signed kept the child support payment clean, described specifically as support for Taras, calculated against both parents' income, and entirely separate from the reimbursement Jacek owed for the moving costs. Nothing about the substance of what they had already agreed to changed. The monthly amount Lesia received stayed the same, and the total Jacek paid stayed the same. What changed was the label attached to each piece of it, and that label was the entire difference between a clean filing and a reassessment neither of them would have seen coming for a year or more.

Because the fix happened before either party signed, nothing about this ever became a dispute with a tax authority. There was no reassessment to challenge and no back taxes to negotiate, because the problem never made it past the drafting stage into an actual filed return. That is the quiet, harder-to-notice kind of result this kind of review produces: nothing dramatic happened, which was exactly the point.

Lesia's mid-negotiation change of heart about the reimbursement added a few weeks to the process and required a second explanation of the same underlying tax point, but it did not change the outcome. Jacek said afterward that the part he found hardest to believe was how close they had come to signing the original version, on the strength of a bookkeeper's passing comment being the only reason anyone looked closer at all. Lesia, once she understood the difference, said much the same thing, and both of them agreed the small delay had been worth avoiding a much larger one down the road.

Taras, still young enough that none of this touched him directly, kept the benefit of a stable arrangement between his parents that neither of them had to revisit or renegotiate months later over an unplanned tax bill. For Jacek and Lesia, the agreement now sits signed and filed away, doing exactly the quiet, unremarkable job a well-drafted support agreement is supposed to do.

What you can learn from this

  • An unallocated support payment defaults to being treated as child support, tax-free to the recipient and non-deductible to the payer, whether or not it is labelled that way. The real reason to spell it out separately is to protect the tax treatment of anything else bundled into the same figure, like a reimbursement, so it is not swept into that default too.
  • A separation agreement drafted informally between two parents, however well-intentioned, can carry tax consequences neither of them meant to create. A brief legal review before signing can catch issues no accountant will see until it is too late.
  • If a payment covers more than one purpose, such as support plus a reimbursement, write each purpose into its own clause with its own label rather than folding everything into one combined monthly figure.
  • Explaining a proposed change to the other parent before sending a revised draft can prevent a document edit from being misread as bad faith, especially when trust between two co-parents is still being rebuilt.
  • Catching a structural problem before an agreement is signed is far cheaper, in both money and stress, than fixing the same problem after a return has already been filed and reassessed.
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 tax problem we handle

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

ContactStart a File →