A missed pre-authorized debit nearly cost Selam her bank account

The situation

The voicemail said Selam's payment arrangement with the Canada Revenue Agency was in default and that collections action would resume unless she called back within five business days. She had not missed a payment on purpose, had not missed one that she knew of, and had no idea what had gone wrong. She played the message twice before she called us.

Selam worked as a personal support worker, picking up shifts through two different home care agencies that each paid her as a contractor rather than an employee. Neither agency withheld tax from her pay, and for two years her income had landed in her account in full, with nothing set aside for what she would owe each spring. By the time she filed, she owed a little over eleven thousand dollars in combined income tax and Canada Pension Plan contributions, an amount that felt impossible to pay in one sum on a support worker's income. The shift work itself made budgeting harder than a fixed paycheque would have: some weeks she picked up forty hours between the two agencies, other weeks barely fifteen, and the debt had built up gradually across two tax years before either agency's paperwork made clear how little tax was being withheld along the way.

She had done the right thing about it. Rather than ignore the notices, she called the CRA's collections line herself, explained her situation, and set up a monthly pre-authorized debit that would clear the balance over roughly two years. She kept it faithfully, treating the withdrawal the same as a rent payment, something that came out first before anything else was budgeted. Her partner Tigist, a forklift operator whose pay went into the same joint account, had adjusted their own budget around the withdrawal so it never bounced, shifting grocery spending and a car payment around the date it cleared each month.

Except, according to the collections officer now assigned to her file, one payment had not gone through. Selam was certain she had seen the withdrawal in her banking app the day it was due. But the account CRA held on record showed a gap, one month with no payment posted, and under the terms she had agreed to, a single missed payment was enough to put the entire arrangement in default and reopen the door to a requirement to pay against her bank account. If that happened, the freeze would not stop at her own earnings; it would reach the shared account Tigist relied on too, at a moment neither of them had budgeted for the disruption.

The gap nobody had noticed

The collections officer, a man named Dilshan, was not unreasonable, but he worked from what his system showed him, and his system showed one missing payment. He explained that CRA's internal ledger recorded pre-authorized debits by the date they were processed on their end, not the date they left Selam's account, and that a processing delay or a bank-side hold could occasionally cause a payment to post late enough to fall outside the window and register as skipped rather than delayed. He was careful to say this was possible, not confirmed, and that the default notice would stand unless Selam could show otherwise within the five days already ticking down.

That explanation mattered, because it meant the money might not be lost at all. It might simply be sitting somewhere between Selam's bank and CRA's ledger, misfiled by timing rather than missing by substance. But proving that required evidence CRA's own system was not going to volunteer, and Selam did not have the kind of documentation that usually settles this sort of dispute: no letter, no formal payment confirmation, nothing with a CRA reference number attached to it. A pre-authorized debit does not generate a receipt the way a cheque or a wire transfer does; it simply happens quietly in the background, which is normally its advantage and, in this case, was the reason nobody had a paper trail ready.

What she did have was her banking app, open on her phone, showing an e-transfer-style pre-authorized debit dated and time-stamped for the month in question, with a confirmation number and a status marked complete. It was not evidence anyone had built for a tax dispute. It was just the ordinary transaction record her bank kept for every account holder, the kind of screen most people glance at and swipe past. Nobody on either side had thought to look at it first, because payment arrangement disputes are usually resolved by asking CRA to search their own records, not by asking the taxpayer to produce a receipt CRA never asked for.

Once we had that screenshot in hand, along with the matching entry from a second month showing the same processing pattern, the picture reversed. This was not a client who had missed a payment. It was a payment that had been made on time, processed by her bank on schedule, and then delayed somewhere in the transfer to CRA's account long enough to fall outside the window that triggered the default flag. The five-day deadline in the voicemail was real, but the underlying premise, that Selam owed a missed month, was not.

What we did

1. Pulled three months of banking history before calling anyone. We had Selam export three months of transaction records, comparing when each debit actually cleared her account against the month CRA flagged as missing. That comparison showed the same short posting lag on two other months CRA had not caught, confirming the problem was systemic rather than a one-time glitch. It also surfaced one earlier month, from a slower stretch of shifts, where the amount that left her account fell short of the instalment — a real shortfall, flagged separately so it would not weaken the timing argument.
2. Called the collections officer directly instead of filing written correspondence first. A default notice with a five-day deadline does not leave time for a letter to sit in a queue. Speaking to Dilshan directly let us establish, before the deadline passed, that the file was open to review and that no requirement to pay would issue while the payment question was being sorted out. That single call likely saved weeks; a written response alone could easily have missed the five-day window entirely, leaving the freeze to proceed before anyone reviewed the underlying facts.
3. Walked through the timing discrepancy with the collections officer using Selam's own records. We laid the bank confirmation date beside the CRA posting date for the same debit and showed that the gap was consistently a few business days, not an absence. This reframed the conversation from 'the client missed a payment' to 'a processing lag exists and here is what it looks like,' which is a very different starting point for a collections officer deciding whether to escalate or to pause a file.
4. Requested a formal reconciliation of the account rather than a one-off correction. A single fixed entry would have resolved this month's dispute but left the same timing gap ready to trigger another false default later. We asked collections to review the full arrangement and adjust how late-posting debits were treated going forward, rather than accept a manual fix limited to the single disputed month that had prompted the call.
5. Negotiated revised terms rather than insisting on the original schedule. Even once the missing payment was accounted for, Selam's arrangement had been tight enough that any future timing hiccup risked tripping the same default clause. We asked for a small buffer built into the schedule and a longer grace period before a missed debit counted as default, so an ordinary bank-side delay would no longer be treated the same as an actual missed payment.
6. Confirmed the outcome in writing before treating the file as closed. Verbal agreement from a collections officer is not the same as a documented account status. We asked for written confirmation that the arrangement was reinstated and that no collections action, including any requirement to pay, would proceed on the strength of the resolved dispute. Selam kept that letter, along with the earlier bank screenshots, in case any future collections contact needed the same history retraced.

The outcome

Selam's arrangement was reinstated, but not simply restored to its original terms. CRA's review confirmed that the disputed month's payment had in fact been received, just later than their system's default window allowed, and that portion of the debt was credited back rather than treated as an outstanding month. Collections agreed to build a short grace period into the schedule so a similar processing delay would not automatically trigger default again. The credit reduced what Selam still owed under the arrangement by the amount of the disputed month, bringing the balance back to where it would have stood had the timing issue never been flagged as a default in the first place.

It was not a full win. CRA did not agree that its default-flagging process needed to change generally, only that Selam's specific account would carry a buffer going forward, and one earlier month in the arrangement's history, where a genuine short payment had occurred during a slow stretch of shifts, remained on the books and was rolled into the extended schedule rather than forgiven. Selam ended up paying that amount, just over a full year later than originally planned, with no penalty added for the delay but no reduction either. CRA's position was that the arrangement had been agreed to voluntarily and that a genuine shortfall, even a small one from a slow month, still had to be repaid on some schedule.

The requirement to pay that had been drafted and ready to issue against her joint account was withdrawn before it reached her bank, which mattered as much as the accounting correction. Tigist's paycheque, which shared that account, was never touched. Selam finished the arrangement on the revised schedule roughly a year after this dispute was resolved, with no further defaults and no further collections calls. She still keeps a running screenshot log of every pre-authorized debit that clears the joint account, a habit that started as a defensive measure during this dispute and has simply stayed part of how she manages the arrangement since.

What you can learn from this