When your controller resigns mid-close, do three things, in this order:

1. Finish this month's close: list every open task, give each one a named owner, and decide who signs it off.

2. Protect your controls: move approval rights, system access and any bank authorities before the controller's last day.

3. Capture what only the controller knew, so the next close doesn't depend on someone who's gone.

For example: day 3 of the close, 4:40 p.m. The controller asks for ten minutes, closes the door, and hands over a resignation letter. Two weeks' notice.

The bank reconciliations for two entities are half done. The intercompany entries between the operating company and three property entities are something only the controller fully understands. The quarterly lender package is due on day 15.

The CFO's first reaction is about the person. The second, about ten minutes later, is about the close.

What should happen in the first 24 hours?

As soon as your HR process allows, have one focused conversation with the controller about the close. Ask three questions:

• Which close tasks are open, and where does each one stand?

• Which tasks does only you know how to do?

• Which deadlines are coming in the next 30 days, inside and outside the company?

Write the answers down that day. They're the starting point for everything that follows.

Finish, protect, capture

This is the framework: three moves, in order of urgency.

1. Finish this close

Make every open task visible. If your team uses a close checklist, update every line with its status and owner. If it doesn't, build one now. RIOO's guide to building a month-end close checklist recommends naming an escalation contact for every task: the person notified if it slips. Typically that's the finance manager or the controller. If the escalation contact is the person leaving, change it today.

Give every task a named owner other than the controller. If your HR and access policies allow, the controller spends the rest of the notice period reviewing and explaining, while someone else does the work. That way the knowledge transfers while the controller can still answer questions.

Decide who signs off this close. Under your approval structure, that may be the CFO, an authorized senior finance professional, or an interim controller. Decide now, not on the last day of the close.

Check external deadlines. Lender reporting, investor statements and audit requests don't move because someone resigned. Some lenders require financials within a defined period after month-end, and a late close can trigger covenant reviews. Tell anyone affected early if a date is at risk. RIOO's guide to the quarterly lender reporting package covers what lenders typically expect.

2. Protect your controls

A resignation is when controls quietly weaken: approvals pile up with one person, and access stays open after it should close. Before the controller's last day:

• Move approval rights. Reassign journal entry, payment and close approvals in your system's approval workflows, so nothing waits in a departing person's queue.

• Plan the access change. Agree with IT exactly when the controller's system access is removed or reduced, in line with your security policy.

• Update bank authorities, where the controller holds them. Change signatories, authorized callers and online banking roles through each bank's process.

• Keep duties separated. During the gap, make sure no one is both posting and approving the same entries because there's nobody else to do it. If staffing makes that impossible for a while, document a compensating control, such as an additional review, approved by the finance leader.

• Review entries made during the notice period. A routine second look at journal entries posted in the final weeks is good practice, not an accusation.

3. Capture what only the controller knew

A controller may carry knowledge that's never been fully written down. Use the notice period to capture it:

• Recurring manual entries: what they are, why they exist, and where the support lives.

• Judgment areas: how accruals, reserves and allocations are calculated, and why.

• Problem accounts: which accounts need watching every month, and why.

• External relationships: contacts at the auditors, lenders, banks and tax advisers, and what each one expects.

• The obligations calendar:

  lender reporting, audit dates, tax filings and owner reporting deadlines.

Record it where the team works, attached to the close checklist and the reconciliations, not in a document nobody opens again.

Who covers until there's a replacement?

Who owns each step?

What should leadership do before anyone resigns?

A controller leaving mid-close is only a crisis if the close lives in one person's head. RIOO's finance statistics guide also notes research linking manual close processes to higher turnover in finance teams, so the problem tends to compound.

Three things reduce the risk before it happens:

• Every close task has an owner and a backup, written on the checklist.

• Judgment areas are documented, with the reasoning, not just the numbers.

• The backup actually does the task at least once a quarter, so the knowledge is tested.

And one control question: if your controller resigned today, could someone else finish this month's close from the checklist and the reconciliations alone? If the honest answer is no, the risk is already there, whether or not anyone has resigned yet.

Note:This blog is general operational guidance, not legal, HR or accounting advice. Follow your organization's HR, IT security and audit policies. Last reviewed October 2026.

Frequently asked questions

Q1. What should a CFO do when the controller resigns during the close?
Finish the current close first: list every open task, give each one a named owner other than the controller, and decide who signs off. Then move approvals, access and any bank authorities, and capture the controller's knowledge before their last day.

Q2. Should the departing controller keep doing the close?
Ideally, if your HR and access policies allow, they review and explain while someone else does the work. That way the knowledge transfers during the notice period, while the controller can still answer questions.

Q3. Who signs off the close when the controller has left?
Whoever your approval structure designates. That may be the CFO, an authorized senior finance professional, or an interim controller. Decide who before the close ends, not on the last day.

Q4. What controls are at risk when a controller leaves?
Approval rights that sit with one person, system access that stays open too long, outdated bank signatories, and gaps in separation of duties when someone ends up both posting and approving entries.

Q5. What knowledge should a departing controller hand over?
Recurring manual entries, how judgment areas like accruals and reserves are calculated, accounts that need watching, contacts at auditors, lenders and banks, and the calendar of reporting and filing deadlines.

Q6. Should we tell the lenders and auditors?
Tell them if any deadline is at risk, and tell them early. Lender and audit timetables usually don't move for internal changes, so early notice is better than a late package.

Q7. What are the options for covering a controller vacancy?
Promoting a senior accountant, hiring an interim or contract controller, bringing in an outside accounting firm for specific tasks, or having the CFO cover a short gap directly.

Q8. How can a finance team reduce key-person risk in the close?
Give every close task a named owner and a backup, document the judgment areas, and have the backup perform each task regularly so the knowledge is tested before it's needed.