The Business Owner Who Was Weeks From Losing His Licence

The situation

What worried Abdi was not the letter itself. It was what the letter meant for his ability to keep driving. Abdi owned a mid-sized logistics company based in Leamington, and while he had drivers and dispatchers for most routes, he still spent several days a month behind the wheel himself, visiting clients, covering shifts when someone called in sick, and moving between yards. A suspended driver's licence would not be an inconvenience. It would be a direct hit to a business that ran, in part, on his own hours on the road.

The letter came from the provincial office that enforces child and spousal support, informing him that his support account showed arrears, and that continued non-payment could lead to enforcement measures, which for a case at that stage typically start with a driver's licence suspension and can extend to intercepting a tax refund. Abdi read it twice, certain there was a mistake. He and Willem, his former spouse, had a support arrangement in place since their separation several years earlier, calculated around Abdi's income from the logistics company and Willem's income as a partner in an engineering firm. Payments came out of Abdi's account every month, automatically, and as far as he knew, they always had.

Willem had since remarried, to Marieke, who had become a steady presence in the children's lives and shared meaningfully in their day-to-day care alongside Willem. The co-parenting relationship between the two households was, by Abdi's account, calm and functional. Nobody had complained to him about a missed payment. Nobody had mentioned arrears in conversation. The first Abdi heard of any shortfall was the enforcement office's letter, which meant that whatever had gone wrong had been building for some time without anyone catching it.

His business had gone through a reorganization the previous year, splitting operations into two entities for tax and liability reasons, a change his accountant had recommended and his lawyer had helped structure. Abdi suspected, without being able to prove it yet, that the reorganization was somehow connected to the letter. What he needed immediately was to understand how far along the enforcement process actually was, and whether he had any real window to fix it before a suspension notice, rather than a warning, arrived.

Where it went wrong

The arrears were real, in the sense that the enforcement office's ledger showed missed payments. They were not real in the sense that Abdi believed. When the business reorganization split his operations into two entities, his accountant had also changed which company account the automatic support payment drew from, consolidating several recurring transfers into a single operating account for simplicity. The instruction to redirect the support payment, however, had never been passed along to the enforcement office, which still had the old account and the old payment schedule on file from years earlier.

For several months, Abdi's bank had continued sending payments from the old account on the old schedule, out of habit as much as instruction, and those had been received and credited normally. Then a routine account cleanup by the bank, unrelated to the reorganization, closed the old account entirely, and the payments simply stopped going out. Nobody flagged it. Abdi's own bookkeeping showed the support line item as paid, because it had been budgeted and approved internally, but the transfer that was supposed to execute it had nowhere to go anymore.

From the enforcement office's side, the picture looked straightforward: payments that had been arriving reliably for years had simply stopped, with no explanation and no contact from Abdi. That is exactly the pattern the office's process is built to catch, and it moved through its standard steps accordingly, first a written notice, and, absent a response or a corrected payment, an escalation toward licence suspension and a tax refund intercept as the next available enforcement tools.

What made this frustrating rather than simply unlucky was that the actual fix, once identified, was not a legal one. The payment needed to be redirected from a working account, the missed months needed to be paid in a lump sum to bring the account current, and the enforcement office needed to be told, clearly and in writing, that the gap was an administrative failure in payment routing rather than a refusal or an inability to pay. None of that required a court application. What it required was speed, and a way to make sure the correction, once made, would actually stop the enforcement process rather than simply sitting in a queue behind it.

What we did

1. Pulled Abdi's full payment history from his bank and cross-referenced it against the enforcement office's ledger, which confirmed within a day that payments had stopped the same month the old account closed. We did this first because the enforcement office would not accept Abdi's word alone that a mistake had occurred, and a bank-side timeline that lined up exactly with the account closure gave us a clean, documented explanation rather than a guess about what had happened, which shaped every step that followed.
2. Requested a full statement of account from the enforcement office, setting out every payment received and every month recorded as missed, so our numbers and theirs could be compared line by line instead of relying on Abdi's own recollection of what he believed had gone through. This mattered because a mismatch between what Abdi's bookkeeping showed and what the office had actually received was exactly the kind of gap that had caused the problem in the first place, and we needed both ledgers in hand before proposing any fix.
3. Worked with Abdi's accountant to redirect the support payment to an active operating account immediately, so that going forward the automatic transfer would actually execute every month rather than depending on an account that no longer existed. Fixing the root cause first, before addressing the backlog of missed months, meant that no matter how long the enforcement office took to process anything else, new arrears could not keep accumulating underneath the correction while it was being sorted out.
4. Calculated the exact arrears owed for the months the payment had failed to go through, confirming the figure against both Abdi's records and the enforcement office's statement so there would be no dispute later about how much was owed or already paid. Getting this number right before proposing a payment mattered because a lump sum that came up even slightly short would have restarted the same enforcement clock we were trying to stop, undoing the whole point of moving quickly.
5. Arranged for the arrears to be paid in a single lump sum immediately, rather than spread over future months, since Abdi's business income made the full amount affordable. A quick, complete payment was the strongest evidence we could offer that this was an administrative failure rather than a pattern of avoidance, and it gave the enforcement office nothing left to escalate against once it was received and recorded.
6. Contacted the enforcement office directly, in writing, before any suspension notice was issued, explaining the account closure, attaching the bank records, and confirming the lump sum payment had been made. Framing the correction as already complete, rather than as a request for leniency, was deliberate: it gave the office a finished fact to record rather than a promise to evaluate, which left far less room for the file to simply sit while a decision was made.
7. Requested written confirmation that the account was current and that no enforcement action, including licence suspension or a tax refund intercept, was pending or in process. A verbal assurance would not have protected Abdi if the internal file had not actually been updated on the office's end, since enforcement steps can technically still be triggered by an outdated record even after a correction has been received, and only a written confirmation gave us something to point to if that happened.
8. Followed up when the initial response was slower than the timeline allowed, calling the office directly to confirm the correction had actually been logged internally rather than sitting unread in a queue. This step existed because a suspension notice could technically still issue while a written response remained pending, and waiting passively for paperwork to move through an unfamiliar internal process was not a risk worth taking with Abdi's licence on the line.
9. Reviewed the payment mechanism with Abdi's accountant one more time after the correction, adding a manual check each quarter to confirm the support transfer had actually executed. This closed the exact gap that had caused the original problem, since a future account change or bank cleanup could otherwise silently break the payment again without anyone noticing for months, and a quarterly check meant any new failure would be caught in weeks rather than building into another enforcement letter.

The outcome

The enforcement office confirmed in writing that the account was current and that no suspension or intercept action was pending. Because the correction reached them before any formal enforcement step had actually been issued, this was prevention in the clearest sense: Abdi's licence was never suspended, no notice of an intercept ever reached his tax refund, and there was no gap in his ability to keep driving for his own business. Willem and Marieke's household was unaffected by the disruption on Abdi's side, since the arrangement they relied on for support continued without a missed month once the routing was fixed, and the two households, which had never had a conflicted relationship, had nothing new to work through.

The cost of the episode was the lump sum payment covering the months the transfer had failed, an amount that, given Abdi's business income, was manageable but not trivial, and the time spent confirming the record with the enforcement office rather than assuming a fix on the bank side was enough on its own. Nothing about the outcome depended on litigation or a contested hearing. The support arrangement itself was never in dispute between Abdi and Willem; the entire problem was a payment that stopped reaching its destination without anyone being told, on either side of the arrangement.

What made the difference was treating the bank fix and the legal fix as two separate, necessary steps rather than assuming one would take care of the other. Redirecting the payment solved the ongoing problem. It did nothing, on its own, to stop an enforcement process that was already moving on the strength of the old, unresolved ledger. Getting that ledger corrected in writing, before a suspension notice arrived rather than after, is what kept a bookkeeping error from becoming a business problem, and it is the reason Abdi's business reorganization, which had triggered the original account confusion, ultimately caused him no lasting cost at all.

What you can learn from this