Two letters to the agency later, the calendar app settled it

The situation

David had already written to the agency twice on his own before he called us, and both letters had gone nowhere. Each time, he explained the same thing: that he had stopped actively working as a self-employed IT consultant well before the date the agency's records showed, and that the special benefits he had drawn during that period should not now be treated as an overpayment. Each time, the response came back unchanged, restating the disputed date and the amount owed as if his explanation had not registered at all.

Roughly $22,000 in dispute was not a number David or his wife Emily, an HVAC technician, had budgeted for. Years earlier, while working full time as an IT support lead, David had taken on self-employed consulting work on the side, eventually registering formally and opting into the self-employed EI special benefits program, which lets self-employed people access parental, sickness, and caregiving benefits in exchange for premiums, provided they keep the arrangement active and report their self-employment income accurately. David and Emily also held a small rental duplex jointly with David's sister Giulia, bought together several years earlier as a long-term investment, and its modest monthly rent landed in the same joint account the agency's reviewers would later comb through for evidence of ongoing consulting income.

David used that access once, taking several months of family caregiver benefits to help look after his mother during a serious illness. The program requires that once someone accesses a benefit under the self-employed election, they generally cannot cancel the election going forward, and for every week a benefit is paid, the claimant's self-employment activity must have genuinely dropped by more than the threshold the program sets, compared to a normal working week. An audit of his benefit period flagged a mismatch: invoices on file showed consulting work continuing through several of the very weeks David had been paid benefits, which meant those specific weeks no longer supported the reduced-activity test the program requires.

David's first two letters argued the point in general terms — that he had simply stopped working, that the business had gone quiet, that the paperwork was outdated. Neither letter carried anything the reviewer could actually check against a specific date, and both were closed without changing the file, leaving David convinced, wrongly, that the agency simply was not listening rather than that his own evidence had never actually been strong enough to move it.

The complication

The real complication was not the rule itself. The self-employed special benefits program is genuinely structured this way: once accessed, the election stays in effect, and for each week a benefit is claimed, the claimant must be able to show their work time and income actually dropped by more than the program's threshold that week, with a repayment obligation triggered for any claimed week the records show did not really meet that test. David understood that much correctly.

The complication was proving exactly when his self-employment activity had actually stopped, as distinct from when his business registration formally closed or when his last invoice happened to be paid. David's own bookkeeping did not help him here. He had continued issuing occasional invoices for small, wind-down projects for several months after he considered himself finished, work he thought of as tying off loose ends rather than ongoing self-employment, and those invoices were exactly what the agency's income-matching system had picked up as evidence of continuing activity.

Worse, David's initial account to us was itself inconsistent with those invoices. When we first reviewed his file, his description of when he had 'really' stopped working did not match the dates on his own issued invoices, which ran later than he remembered. Building an argument on David's recollection alone would have meant building it on a version of events his own records contradicted, which is not a position that survives contact with a skeptical reviewer.

What we needed was not a better argument about intent. It was independent, dated evidence of what David was actually doing, week by week, during the disputed period — evidence that did not depend on anyone's memory of how the business had wound down.

What we did

1. Set aside David's narrative account of the wind-down as the basis for the dispute, since it was already contradicted by his own invoicing dates, and treating a contested memory as the foundation of a third letter would only have repeated the same failure as his first two attempts. What the file needed instead was something a reviewer could check against a record, not another version of events resting on David's recollection of a business that had wound down gradually rather than on a single clean date.
2. Asked David for every record that could independently date his work activity, not just invoices and bank deposits, prompting him to check sources he had not thought to offer. That search turned up the scheduling calendar app he used to book client meetings and track project hours, a record he had never considered relevant to a tax dispute because he had built it purely to manage his own workload.
3. Reviewed the calendar app's project logs against the disputed benefit weeks and found that David's actual billable activity had stopped almost three months earlier than his last invoice date, with the trailing invoices covering work completed and simply billed late. That is a common and unremarkable pattern in freelance billing, but it was exactly the kind of detail the agency's raw invoice dates could never show on their own, and it directly reframed which weeks of the claim period were genuinely still in dispute.
4. Cross-referenced the calendar records against David's bank deposits to confirm the pattern held consistently, which first meant separating out the monthly rent from the duplex David, Emily, and Giulia held together so shared rental income was not mistaken for continuing consulting revenue. Once isolated, the deposits confirmed no new client work had actually commenced after the date the calendar logs showed, ruling out the possibility that the calendar told only part of the story.
5. Prepared a submission built entirely around the calendar and deposit evidence, rather than around David's own account of events, presenting a dated, source-based timeline the reviewer could check independently instead of a narrative that simply asked to be believed. Every date in the submission traced back to a document the agency could verify on its own, which was precisely what David's first two letters had lacked.
6. Reframed the repayment calculation around the corrected activity end date, arguing that only the shorter, evidence-supported period of genuinely overlapping income and benefits should count toward the repayment, rather than the full benefit period the agency had originally assessed based on invoice dates alone. This narrowed the weeks actually in dispute from the entire claim period down to a handful the records could not fully clear.
7. Negotiated a revised repayment figure with the agency's review officer, using the corrected, evidence-based timeline as the basis for a lower assessed overlap between income and benefits paid. Securing written confirmation of the reduced amount before any collection or penalty action proceeded further meant David's file closed on agreed terms rather than staying open to further escalation while the numbers were still being argued over.

The outcome

The repayment obligation did not disappear. David had genuinely continued some self-employment activity, even if for a shorter period than the agency first assessed, and the corrected timeline still showed real income overlapping with benefits received. The final figure landed at roughly $9,000, down from the roughly $22,000 originally claimed, reflecting the narrower period the calendar and deposit records actually supported.

What the file cost David beyond the repayment itself was time and two earlier attempts that went nowhere, along with the discomfort of having to concede that his own memory of the wind-down had been wrong. The evidence that mattered was not new; it had been sitting in an ordinary scheduling app the whole time, unconnected in his mind to a tax dispute until someone asked the right question about where else his activity might be dated. Sorting the rental duplex's deposits out of the same account added an extra week of reconciliation work, but it also meant the agency's reviewer never had reason to question whether the joint account itself was hiding something, since Giulia's share of the rent was clearly documented and easy to separate from the consulting income once anyone actually looked.

David set up a payment arrangement for the reduced amount and closed the file without penalties attaching, since the corrected submission had been made before the agency escalated to collections. He now keeps a simple written log of his last billable day whenever he winds down a project, separate from his invoicing, precisely so that the next transition in his work does not depend on reconstructing dates from memory under pressure. He and Emily also asked Giulia to start routing the duplex's rent through a dedicated account rather than their shared one, a small change that will keep any future review of either income stream far simpler than this one turned out to be.

What you can learn from this