The first month runs on memory you no longer have
The first thing that breaks is payroll, because it is the first deadline: someone has to know the pay rates, the schedules, the banking details and how the remittances get filed, usually within days of her departure. Payables wobble next, since nobody knows which vendors are on terms, which are on auto-debit and which invoice in the pile is already paid. Then a CRA deadline arrives, an HST filing or a source deduction remittance, and it does not care that you are short-staffed; late remittances draw automatic penalties and interest.
Underneath the deadlines sits the quieter damage. Receivables stop being chased, so cash slows exactly when you may need to pay a recruiter. The books fall behind, and every unattended week makes the eventual catch-up longer. If she was the only person who understood how the file was kept, her chart of accounts, her workarounds, her filing system, the records themselves become a puzzle for whoever comes next. Every unattended week also carries a cost in decisions postponed, because you cannot manage what nobody is measuring.
The damage is visible from outside the building too. Vendors notice payments arriving late and tighten terms. Customers notice invoices arriving wrong or not at all, and a lender who asks for statements mid-gap gets silence, which reads as a signal even when it is only a staffing problem. Finance is quiet infrastructure; its failures are public, and the reputational repair takes longer than the operational one.
None of this requires a bad exit. Two weeks of notice, generously worked, is nowhere near enough time to transfer years of accumulated knowledge that was never written down.
The real problem is key-person risk, not the resignation
The exposure existed long before she gave notice; the resignation only prices it. A finance function where one head holds the process, the passwords and the history is a single point of failure, and single points of failure eventually fail, through resignation, illness, a family emergency or a long vacation. Loyalty is a reason to be grateful; it is not a control.
The risk compounds with tenure, which is the cruel part. The longer and better someone runs the function alone, the fewer questions anyone asks, the more the process bends to their personal habits, and the deeper the dependence grows. Ten good years can build a dependency that two weeks of notice cannot unwind, and the owner who trusted most ends up exposed most.
There is also a version of this risk that is uncomfortable to say out loud: a finance person who is the only one who enters transactions, moves money and reconciles the bank operates with no segregation of duties. Most people are honest, and the honest ones are the first to benefit from a structure where their work is visibly reviewed, because review protects them from suspicion as much as it protects you from error. If everything runs through one person unreviewed, you have both a continuity problem and a control problem, and they have the same solution: fix the structure and both risks fall together.
Write the process down while she still works for you
The single highest-value move available today is documentation, done as a project with a deadline rather than a someday intention. The goal is that a competent stranger could run a month of your finance function from the documents alone; that sentence is the standard, and anything less specific produces binders that look reassuring and answer nothing. In practice it means five artifacts:
- A payroll runbook. Pay dates, rates, how hours are collected, how the run is executed, how remittances are filed and when.
- A month-end checklist. Every step of the close in order, from bank reconciliations to the reports produced at the end.
- A vendor and customer map. Who is on terms, who auto-debits, who gets paid how, which customers need chasing and how invoicing actually happens.
- A compliance calendar. Every recurring filing, HST, source deductions, T4s, WSIB and EHT where they apply, with the deadline and the owner named.
- A where-things-live index. Software, files, statements, government accounts, and how each is accessed.
Have her write them, pay for the time, and have someone else test-drive one month against the documents while she is still there to correct them. The test-drive is the step everyone skips and the one that makes the documents real.
Then keep the documents alive. A runbook written once and never updated decays into fiction within a year, so put a recurring date in the calendar, quarterly is plenty, where she updates what changed and someone else re-reads it. Staleness is the failure mode of every continuity plan; the refresh is cheap, and the habit is the actual asset.
Access belongs to the corporation, not the employee
Every credential your finance function depends on should be owned or recoverable by the corporation, checked this month rather than during an exit. The pattern that hurts is accretion: accounts opened in her name over the years because it was convenient, until the company cannot reach its own information without her. An hour spent listing every account and who controls it is the cheapest audit you will ever run.
| What lives with one person | What breaks when she leaves | The fix that survives her |
|---|---|---|
| Payroll knowledge and schedule | Missed or wrong pay runs, late source deduction remittances | Payroll runbook plus a second person who has actually run it |
| Banking and software logins | Locked out of your own records and payments | Corporate-owned admin accounts, individual user seats, a maintained credential list |
| CRA account access | No visibility on balances, mail or deadlines | Owner registered on My Business Account, with representative authorizations reviewed and revocable |
| Vendor terms and payment habits | Duplicate payments, missed payments, strained suppliers | Documented payables map with terms and methods |
| How the books are actually kept | Records the successor cannot interpret; a long, costly catch-up | A consistent close checklist and periodic outside review of the file |
Two rules cover most of it. The owner holds admin rights and the employee holds a user seat, never the reverse; and no shared credentials, because shared logins mean no accountability and painful password resets at exit. When someone does leave, access changes should happen the same day, not as an afterthought. The same review should confirm who CRA lists as authorized representatives on the corporation's accounts, because departed employees and long-gone providers have a way of lingering there for years.
Replacing her will take longer than her notice period
Plan for the gap, because the timeline is unforgiving: weeks or months to find a credible replacement, then months more before the new person runs your file at full speed, all while the daily work continues to arrive. Without documentation, the new hire is not onboarding; they are doing archaeology, reconstructing how things were done from bank statements and guesswork, at your expense.
This is also the moment owners discover that one job posting cannot describe what she actually did, because over the years she absorbed pieces of several distinct roles. It is worth reading which roles a complete finance function actually contains before writing the posting, and what the replacement will really cost once you add everything up before assuming a like-for-like hire is the obvious answer. Sometimes it is; often the exit is the right moment to restructure the function instead.
Bridge the gap deliberately rather than hoping the timeline cooperates. Interim options exist: paid handover time if the exit is friendly, a temporary bookkeeper running the runbook, or an outside firm stepping in to stabilize payroll and filings while you decide what the function should look like next. The worst plan is asking the office manager to absorb it, which converts one understaffed function into two.
The restructure question deserves an honest hour before any posting goes up. If the departing person was really doing one role, replace the role. If she had accreted three roles over the years, bookkeeper, payroll administrator and de facto controller, then a like-for-like posting recreates the same single point of failure with a new name on it, and the next resignation replays this whole page.
The facts that set your exposure, and the team answer
Score your own risk against five questions, honestly:
- How many people could run the next payroll without calling her? If the answer is zero, that is the first fix.
- Does month-end follow a written checklist that someone else has actually executed at least once?
- Who owns the admin logins for banking, accounting software and CRA access, the corporation or the employee?
- How far behind would the books be after four unattended weeks, and what deadlines fall inside that window?
- Does anyone outside the building see the books regularly, so that a departure never means the knowledge existed in only one place?
Two or more weak answers means the exposure is live, and the order of operations matters: access first, payroll runbook second, compliance calendar third, because those are the failures with dates attached. Everything else can follow at a saner pace.
That last question is why continuity is structurally easier with a team than with any single employee, inside or outside. In an Ongoing Financial Partnership, the books, payroll, filings and reporting run under End-to-End Accounting as documented processes owned by a firm rather than memories owned by a person, so vacations, illnesses and resignations stop being existential. Some clients pair that with a trusted internal person for the on-site work, which is a resilient design: the person can leave, and the function keeps running. If you are staring at a resignation letter right now, a free 15-minute discovery call is a sensible first move; stabilizing a finance function mid-exit is work we know well.
