Why was our account frozen for a debt that was not ours

The situation

'Why is our account frozen for money we don't owe?' Yusuf asked it almost word for word in his first message to us, forwarded along with a screenshot from his bank showing a hold placed on the company's operating account under a Canada Revenue Agency requirement to pay. He had called the bank first, and the bank could only tell him the hold came from CRA and that they were obligated to comply with it. He had no idea what debt it referred to, because the company, as far as he and his co-owner knew, had no outstanding tax balance at all.

Yusuf worked as a sales director but had spent the last several years building a small consulting company on the side with his spouse, Khalil, a construction project manager who handled the operational end of the business while Yusuf managed sales relationships. The company had grown steadily, and its finances had always been kept current, filings on time, remittances made without incident. The frozen account made no sense against that history, and with Yusuf and Khalil in the middle of separating, a sudden financial shock to the business they still jointly owned landed at an especially bad moment.

Before contacting us, Yusuf had already tried to fix it himself, working from advice he found searching online. Several forum posts and a generic legal information page suggested that a frozen account tied to a CRA action meant an assessment had likely been issued and that the correct response was to file a formal objection to dispute the amount owing. He drafted and submitted an objection within days, citing the company's clean filing history and requesting the assessment be reversed.

The objection went nowhere, because it was aimed at the wrong problem entirely. There was no assessment against Yusuf and Khalil's company to object to. The debt behind the requirement to pay belonged to a different company altogether, one that happened to share a name close enough to theirs that a records match had pulled the wrong file. An objection process built to dispute an assessment cannot fix an error where the assessment was never directed at the company in the first place, and weeks passed with the account still frozen while the objection sat unresolved in the wrong queue.

The legal problem

A requirement to pay is one of the more forceful collection tools available to the Canada Revenue Agency. It allows CRA to require a third party, most commonly a bank, holding money owed to a tax debtor to redirect that money to CRA instead, without a court order and often with very little advance notice to the account holder. It is designed for situations where a taxpayer has an established debt and has not responded to earlier collection efforts, and banks generally comply immediately because the legal obligation to do so falls on them, not on the account holder. That is precisely why a mistaken requirement to pay is so disruptive: the bank has no discretion to question it, and the account holder is often the last person to learn what triggered the freeze.

The problem in this file was not that the tool had been misused against a legitimate debtor. It was that it had been directed at the wrong debtor entirely. CRA's collections system had matched an outstanding tax debt to a company with a name close enough to Yusuf and Khalil's that an internal records search returned the wrong entity, and the requirement to pay was issued against their bank account instead of the account belonging to the company that actually owed the money, run by a business owner named Samir with no connection to Yusuf or Khalil at all.

This kind of mistaken-identity error is uncommon but not unheard of, particularly among businesses whose registered names differ by only a word order, a punctuation mark, or a single added term. Correcting it required something different from a standard tax dispute. There was no assessment to challenge and no calculation to argue over, because the underlying debt was real, it simply belonged to someone else. What was needed was proof, clear enough for a collections officer to act on quickly, that Yusuf and Khalil's company was not the entity named in CRA's records as owing the debt. Simply asserting the two companies were different was not going to move a collections file quickly; the proof had to be specific enough that no further verification step was needed on CRA's end.

Time mattered more than it would in an ordinary dispute. Every day the account stayed frozen, the company could not pay suppliers, could not make payroll on schedule, and risked real operational damage that no amount of eventual correction would undo retroactively. The online advice that had sent Yusuf toward an objection had cost several weeks the file could not afford, and the misdirected objection now sitting in CRA's system needed to be withdrawn cleanly so it would not confuse the actual fix once it was underway.

What we did

1. Withdrew the misfiled objection immediately. Leaving an active objection in the system, aimed at an assessment that did not belong to the company, risked creating a second layer of confusion once collections began reviewing the identity question. Withdrawing it cleanly meant the file collections were now working from had only one issue in front of it, not two overlapping and unrelated ones.
2. Requested the CRA business number and full legal name attached to the requirement to pay. This was the single most important step, because it let us compare CRA's target directly against Yusuf and Khalil's actual registration. The business number returned belonged to a different corporation entirely, confirming within a day that this was a matching error rather than a dispute over an amount owed. That single number did more to move the file than pages of argument could have, because it gave collections something objective to check against their own system rather than taking Yusuf's word for it.
3. Assembled the company's incorporation documents, CRA business number, and filing history as identity proof. Rather than argue in the abstract that a mistake had occurred, we built a package showing exactly which registered entity Yusuf and Khalil's company was, with a business number that did not match the one named in the requirement to pay, so the discrepancy was demonstrable rather than asserted.
4. Escalated to a collections supervisor rather than working through the general enquiries line. A frozen account with active business consequences needed a decision-maker with authority to act quickly, not a queue built for routine questions and standard processing times. We requested direct escalation, explaining the operational harm accruing daily, to get the file in front of someone who could issue a correction. A live financial hardship needs a person with authority to bypass the queue, and asking for one directly is usually the fastest way to reach them.
5. Obtained written confirmation that the requirement to pay would be rescinded. Once collections accepted the business number mismatch, we insisted on a formal rescission notice sent to the bank, rather than a verbal assurance that the matter was handled, so the bank had clear written authority to release the hold rather than waiting for its own internal confirmation process.
6. Followed up directly with the bank once the rescission issued. Banks do not always release a hold the moment CRA sends a correction; sometimes a second confirmation call is needed to move it through the bank's own compliance process. We called the bank's business unit directly to confirm receipt of the rescission and pushed for same-day release of the funds.
7. Requested a permanent flag on the company's file noting the prior mistaken-identity error. A records match error that happened once could happen again if CRA's system retained the same matching logic. We asked for a note placed on file specifically identifying the near-identical company name as a known source of confusion, to reduce the chance of a repeat freeze. We asked specifically that the note reference both companies' business numbers side by side, so any future automated match would be flagged for manual review before another requirement to pay could issue in error.

The outcome

The requirement to pay was rescinded roughly ten days after we took over the file, and the bank released the hold within two business days of receiving CRA's written confirmation. The full amount that had been frozen, which had reached the low six figures by the time collections escalated the matter internally, was returned to the company's operating account without any portion retained or applied against any debt, since none was ever properly owed. CRA did not treat the correction as requiring any further review once the business number mismatch was confirmed in writing, which meant the release, once authorized, proceeded without additional delay or documentation from Yusuf and Khalil.

The operational disruption during the freeze was real. Yusuf and Khalil had to delay one round of supplier payments and draw briefly on a personal line of credit to cover payroll while the account sat frozen, a cost that was not reimbursed by CRA, since the error, however clearly established, did not carry a compensation mechanism for the inconvenience it caused. The company's bank was willing to waive the interest on the short-term credit line once Yusuf explained the circumstances, which softened the cost somewhat even though CRA itself offered nothing. The company absorbed a modest amount of interest on the short-term borrowing as the only lasting financial cost of the episode.

The file note requesting a permanent flag against the mistaken-identity error was confirmed in writing, and no repeat freeze occurred in the following year. Yusuf and Khalil completed the separation of their personal affairs on a separate timeline from the business, which they agreed to keep operating jointly, and both credited the early identification of the business number mismatch with turning what looked like a serious tax dispute into a correction that, once the right people were looking at the right facts, took only days to resolve. Yusuf later said the hardest part had not been the freeze itself but the two weeks spent chasing the wrong fix online before anyone pointed him toward the actual cause.

What you can learn from this