Direct Deposit and Debits: A Bank Migration Checklist
List the employers that deposit and the creditors that debit, then migrate them one by one with written confirmation.
Published 2026-07-21
A successful bank migration lives in a two-column table. On the left, everything that deposits: employer, government agencies, insurers, each with the form or portal where the account gets changed. On the right, everything that withdraws: mortgage, utilities, telecom, subscriptions, with each debit's usual date. The list is built from statements, never from memory, because annual payments and dormant subscriptions escape recall. Each line then migrates with its request date and confirmation number logged, because a share of providers get it wrong on the first try and written proof gets corrections made free. Weekly surveillance of the old account, for six weeks, catches rejections and stray deposits while they are still benign. This article details the table's construction, the prudent migration order and the checks that turn a source of anxiety into a checklist — one line, one confirmation, one tick at a time.
Build the deposits column
The table's first column lists everything that deposits: the employer and its payroll service; the government agencies — tax refunds, credits, allowances, benefits — each with its own account-change portal; the insurers that reimburse; the clients, for the self-employed. Each line specifies the modification channel: HR form, government portal, phone call, void cheque required. Government deposits deserve particular attention: several programs manage their banking details separately, and a single change does not cover them all. The complete column avoids the painful scenario of a tax refund dispatched to a closed account, whose recovery takes several weeks of paperwork and follow-up calls.
Build the debits column
The second column lists everything that withdraws: mortgage or rent, insurance, utilities, telecom, daycare, subscriptions, dues — each with its usual debit date, information that will guide the change's timing. The reliable source is a full year of statements, not memory: annual and semi-annual debits — registration, associations, renewals — escape recall and cause the late rejections. Also note each debit's channel, account or debit card, card-linked subscriptions following a different migration path. This column generally runs longer than anticipated: discovering it in full is already a gain, several lines deserving cancellation rather than migration.
Execute with dates and confirmations
Each line migrates by the same procedure: the change requested just after a successful debit or deposit, never just before one, the request date and confirmation number logged in the table. That documentary discipline is not bureaucracy: a share of providers misapply the first change, and dated proof gets the fees of their error corrected rather than yours. Proceed in manageable waves, five or six lines a week, starting with the critical ones — mortgage, insurance, salary — and finishing with the secondary subscriptions. The completed table, every line ticked with its confirmation, becomes the migration's completion certificate: while one line stays open, the old account's closure waits. A blank statement is the proof.
Watch for rejections during the transition
The transition is watched actively: the old account gets opened weekly for six weeks, hunting two anomalies. Stray deposits first — a payment landing in the old account signals an unapplied change, to be chased with the confirmation number. Rejected debits next, on the new account's side this time: a provider striking the emptied old account generates fees on both sides, to be waived with proof in hand and then fixed at the source. The buffer balance left in the old account absorbs the stragglers meanwhile. Every anomaly caught in week one is fixed with a call; the same one, discovered in month three through a collection letter, costs fees and explanations.
Quebec scenario: compare before confirming
A couple in Châteauguay switches credit unions and turns the bank migration into a checklist taped to the fridge. Left column: everything that deposits — one partner's employer, the revenue agency for quarterly instalments, the other's parental benefits — each with the form or portal where the account gets changed. Right column: everything that debits — mortgage, insurance, daycare, telecom — with each usual withdrawal date. For every line they record the date the change was requested and the confirmation number received, because two providers out of ten get it wrong on the first try. Changes are made right after a successful debit, never right before one, to leave slack. For six weeks, one of them opens the old account every Monday to spot rejected debits or stray deposits. Two stragglers show up and are fixed without fees thanks to the buffer balance left behind. The checklist ends up in their digital records folder, ready to be reused the next time either of them changes institutions. Total cost of the exercise: one marker and two careful Mondays a month.
Checklist
- Build the incoming-deposits column
- Build the outgoing-debits column
- Find each line's form or portal
- Change each line after a successful debit
- Note the request date and confirmation number
- Check the old account every Monday
- Fix rejections while they are benign
- Keep a buffer balance for stragglers
- Archive the list for the next switch
Frequently asked questions
Where should the deposit and debit migration start?
With two columns: who deposits — employer, governments, insurers — and who withdraws — mortgage, utilities, subscriptions. Add for each line the form or portal where the change happens. The complete list, drawn from statements, becomes your checkable migration plan.
Why record the confirmation numbers?
Because a share of providers get it wrong on the first try. The request date and confirmation number let you have a debit still hitting the old account corrected without fees. Without a trace, proof of the change rests on your memory against theirs.
How do I watch for rejections during the transition?
Open the old account weekly for six weeks and flag any unexpected movement: a stray deposit, a rejected debit, a fee. Every anomaly fixes quickly when it is days old rather than months, and the buffer balance left behind covers the stragglers.