Knowing which system access to revoke when a finance executive leaves is easier if you sort it into three keys: money movement, accounting control, and the logins behind both. Cut the money keys first, but only after you know who replaces each one. The main condition is simple: you need a complete list before the notice period ends, not after the last day.

Start the access inventory before the last working day

A complete list of system access to revoke when a finance executive leaves is rarely written down anywhere. The person may have set up the bank portal years ago, been added as an admin on the accounting platform during a cleanup, and kept a personal email address on a vendor account because nobody asked them to change it. When that person leaves, nobody sees the gap until someone needs a wire approved or a report pulled and the login fails. The safer habit is to build the inventory while the person still works there, and to treat it as a normal business task instead of a farewell chore.

The inventory does not need special software to start. A shared spreadsheet with four columns is enough: the system, the person who holds access, what that access allows, and who should own it afterward. Ask the departing person to walk through each tool with you, then check their answers against the admin pages of each platform. People forget things. A plugin that syncs a bank feed, a tax portal login tied to an old phone number, or a corporate card that still bills to the company can all be missed when the list comes only from memory.

Be clear about who needs to see the inventory. The owner should see all of it, because the owner carries the risk if money moves without approval. An outside accountant may need only the part about the books. The departing person should not be the only one who knows where the passwords live, and the password manager itself should be checked for shared vaults. Keep the list confidential, since it describes exactly where the company's money and records are kept.

What changes next depends on the reason for leaving. A planned departure with a notice period gives you time to move ownership before access is cut. An abrupt exit does not, and it may require changing passwords and reviewing recent approvals the same day. In both cases, the inventory is what tells you which step comes first. Without it, the team will cut the most visible access and leave the quiet access in place, which is usually the reverse of what matters.

Finally, decide now that access changes belong on the offboarding checklist, next to returning a laptop. Put a named person in charge of running the review, and set a date for it. Owners often assume the finance side will handle itself, but finance access is spread across banks, software, and personal devices. It needs a checklist of its own.

Key one: payment authority and bank access

The first key is the one that moves money. It covers online banking users, payment approval rights, wire and ACH release authority, check signing, and any corporate card the person can use or reset. Revoke these before anything else, because a single approved payment can be hard to reverse. In practice, the departing person may have been a second approver for years, which means the bank has been relying on them for a step the company never wrote down.

Start by listing every bank and card provider, then ask each one for its user list. Most banks show who has online access, what role each person holds, and whether they can initiate or approve payments. Pay attention to roles that look minor. A viewer who can download statements with account numbers, or a user who can change contact details, can still be useful to someone who wants to redirect alerts. The list may also include someone who left long ago and was never removed.

Changing the approval rules often matters more than removing a login. If your policy requires two approvers for payments above a set threshold, the departing person may have been the second signature, and nobody else may hold that authority. Before you revoke it, decide who will approve in that seat, and make the bank reflect that choice. A short written policy, even one page, helps the next person know the rule and lets the bank setup match it.

Consider the recurring payments the person managed. Vendor bills set up for automatic payment, subscriptions on a company card, and payroll tax deposits can all depend on one person's account. Move the ownership of each recurring payment to someone who will still be there, or confirm that the payment will run without changes. Missing one tax deposit or one rent payment is the kind of problem that shows up after the departure, when nobody remembers why it happened.

Keep a record of what you changed and when. Ask the bank to confirm in writing that the former user no longer has access, and save that confirmation with the company's records. If you later need to explain a payment history during a lender review or an audit, the record shows which controls were in place on each date. It also protects the departing person, who should not be blamed for transactions made after they left.

Key two: accounting admin rights and who owns the books

The second key controls the books. It includes admin rights on the accounting platform, such as QuickBooks or NetSuite, along with the ability to change the chart of accounts, close periods, edit journal entries, manage users, and connect or disconnect bank feeds. A person with these rights can change the financial record without anyone else noticing, so the review should be strict. Even a trusted employee should not keep admin rights by default. Those rights belong to the named owner.

Look at the periods and the audit trail before you change anything. Ask whether the person edited entries in closed periods, changed account mappings, or approved their own journal entries. Many platforms keep a log of user actions, and a quick read of recent activity often shows whether something needs a second look. Do not assume that a clean-looking balance sheet means the history is clean. A reviewer should compare the last several closes with the supporting documents, starting with the largest adjustments.

Decide who will own the books next, and be specific. Name the person who reconciles the bank accounts, the person who approves journal entries, and the person who closes the period. In a small company, one person may do all three, but it still helps to write it down. An outside accountant can take on the close, yet the owner still needs to know who holds admin control and who can override the system.

Watch for integrations and automated rules. A bank feed rule that categorizes certain transactions, an add-on that sends invoices, or a scheduled report that emails figures to an investor can all keep running after the person leaves, sometimes under that person's login. If an integration is tied to the departing user, reconnect it under a company-owned account first. Otherwise, reporting may stop, or a payroll sync may fail without an obvious cause.

Last, look at how data leaves the system. Exports to spreadsheets, shared folders, and emailed reports can keep copies of sensitive information long after access ends. You do not need to delete every file, but you should know where the financial data lives and who can open it. That check protects the company's records, and it is also what a lender or buyer will ask about when they review your controls.

Key three: shared logins, email, and devices that hold the other two

The third key quietly unlocks the first two. It covers the email address used for bank alerts, password resets, and vendor accounts, the password manager, the phone that receives two-factor codes, and any shared login that several people use. If the departing person controls the mailbox that receives a bank's security codes, they can reset access to almost every other system. This key looks like an IT detail, but it deserves the most attention.

Start with email. Find out whether any finance system is registered to a personal address or to a mailbox that the person managed. Move those registrations to a role-based company address, such as accounts@ or finance@, controlled by more than one person. Then check the recovery options on each account. A phone number or backup email tied to the departing person can keep access open after the login itself is gone.

Two-factor devices are easy to forget. If the departing person used a phone app, a hardware security key, or text messages to approve logins, those methods need to move. Ask the team to enroll a second method for each important account before removing the old one. In practice, this step prevents the worst outcome: a locked account that nobody can recover because the only code went with the person who left.

Password managers and shared vaults need the same attention. Check which vault items the person created, which ones they shared, and whether any credentials exist outside the vault, such as a sticky note or a spreadsheet. Rotate the passwords for the most sensitive systems, starting with banking, email, and the accounting platform. A rotation does not need to be dramatic, but it should be recorded, what's a interim CFO in Massachusetts so the company knows the old credentials no longer work.

Finally, disable access in an order that does not lock you out. Confirm that a company-controlled administrator can still sign in before you remove the departing person's admin role, and confirm that email recovery still works. Test one new login with the new owner before you call the task finished. Many checklists skip this step, and it is the one that saves the most time when something breaks.

How interim, fractional, and permanent finance leaders change who holds each key

The access problem looks different depending on how finance leadership is structured. A permanent CFO or controller usually sits inside the company, uses company-issued devices, and holds admin rights through the normal employee process. An interim CFO is brought in for a defined period, often to cover a gap or a transition, and may have been given broad access that was never meant to outlast the assignment. A fractional CFO works part time on an ongoing basis, often through their own firm, which means some access may sit with that firm rather than with the company.

The difference matters because the departing person may not be an employee at all. If an outside advisor set up the bank portal, the forecasting model, or the reporting dashboard, the company may not know where those assets live. Ask for a clear list of what was built and who holds the credentials before the engagement ends. Ownership should be written into the agreement, so the company does not have to negotiate the handover under pressure.

The table below compares what usually changes for each model. These are general patterns, not promises about any firm or person. Your own contracts and systems will set the real answer.

ModelWho usually holds accessMain access risk when the leader leavesWhat changes next

Interim CFOOften a temporary login granted for a defined assignmentBroad access that outlives the planned end dateRevoke by the end date and confirm the change in writing Fractional CFOA mix of company accounts and the adviser's own firmAccess that builds up over months and goes unreviewedReview user lists and shared tools every quarter Permanent CFOCompany accounts issued through the normal employee setupGaps at the edges, such as personal devices and old vendor loginsAdd bank approvals and accounting admin to the offboarding checklist

In practice, an interim assignment is the one most likely to leave broad access behind. The engagement is meant to end on a fixed date, but the access often does not end with it, especially if the person helped with a transition or a financing. Put the end date in the access plan from day one, and schedule the review before that date arrives, not after.

A fractional arrangement needs a different kind of attention. Because the work continues for months, access tends to accumulate: a new bank user here, a reporting tool there, a shared drive added during a close. The risk is less about one dramatic exit and more about access nobody has reviewed in a long time. A short quarterly look at the user lists keeps that buildup visible.

With a permanent CFO, the company usually has the strongest controls, because access follows the employee process. The gaps tend to sit at the edges, such as personal phones, old vendor logins, or admin rights granted for a special project. The departure checklist still needs all three keys. HR's offboarding step rarely covers bank approvals or accounting admin rights unless someone adds them.

The order to revoke access without stopping payroll or closing the month

Order matters because some access keeps the business running. If you cut the payroll login before payroll runs, or disable accounting admin before the month closes, the team may lose the ability to finish work already in progress. A practical sequence cuts the highest risk first, keeps operations working second, and cleans up the rest after the next cycle.

A workable order looks like this:

Money movement: remove payment initiation and approval rights, and add a backup approver where policy requires one. Recovery paths: move email, security codes, and phone numbers to company-controlled addresses and devices. Accounting admin: assign the named owner first, then remove the departing user's admin role. Shared logins and devices: rotate passwords, update shared vaults, and wipe or collect company devices.

Start with the money keys, because they carry the most immediate exposure. Remove the departing person's ability to initiate or approve payments, and do it before the last working day if possible. If a payment is scheduled during the transition, confirm who will release it and make sure the bank shows that person as the approver. A missed approval is easier to explain than an unauthorized one.

Next, handle the recovery paths. Move account recovery to a company-controlled address, enroll new two-factor methods, and confirm that the departing person can no longer receive security codes. Do this before you change passwords, or you may lock yourself out of a system you still need. Keep the old mailbox open for a short period with forwarding turned on, so vendor messages are not lost in the gap.

Then change the accounting admin rights. Assign admin to the named owner, remove the departing person's admin role, and check that bank feeds and integrations still run. If the platform requires a period to be closed first, coordinate with whoever runs the close, and avoid making the change in the middle of month-end work. The best time is usually after the close is finished and reviewed.

Finish with the shared logins and devices. Rotate passwords for the systems you have just moved, collect or wipe company devices that held finance data, and remove the person from shared vaults. Then check the list again and mark each item with a date and a name. The final pass is usually quick, but it is the one that shows the work is finished.

Handing over ownership before anyone's login is disabled

Access is only half of the handover. The other half is knowing what the person did, why they did it, and what should happen next. A departing finance leader usually carries knowledge that never reached a document: which vendor always sends invoices late, which bank requires a phone call for large wires, which adjustment repeats every quarter. If that knowledge leaves with the person, the company will rediscover it the hard way.

Ask for a short written handover on the core processes. Cover the close calendar, recurring payments, bank and card relationships, the reports sent to investors or lenders, and any open issues. Keep the document plain. A few pages with clear owners and due dates are more useful than a long binder nobody reads. The most valuable items are often the exceptions rather than the routine steps, so ask directly: what breaks, and what do you do when it does?

Pair the successor with the departing person for a short overlap if you can. Let the new owner perform one task while the old owner watches, such as approving a payment run or reconciling a bank account. Then switch roles for the next task. This shows whether the handover is real, and it gives the successor the context they need to make decisions without guessing.

Be careful with third-party advisers. If the company uses an outside accountant, a fractional CFO firm, or a bookkeeping service, confirm who will be their main contact after the departure. Ask them to send a list of what they hold, what they have built, and what they need from the company. A clear contact prevents the common problem of an adviser continuing to work with someone who is no longer there.

Keep the handover tied to access. Do not cut the departing person's login until the successor has confirmed they can do the core tasks. If the successor cannot approve a payment or find a report, you still have an open dependency, and the answer is to fix it before the cut. The handover is complete when the work continues without anyone needing to message the former employee.

How to verify that access is actually gone

After the changes, verify them. Assume that at least one system still accepts the old login until you have tested it. Try to sign in with the departing person's credentials where your policy allows it, or ask the platform to show the current user list again. Do not rely on someone saying they removed things, or on a checkbox that looks changed. The check takes little time, and it is the only way to know the result.

Check the logs for activity after the departure date. Banks, accounting platforms, and cloud drives often show sign-ins, exports, and approvals with timestamps. Look for anything unusual, such as a login from an unfamiliar location, an export of a full ledger, or a payment approved under the departing person's name. If you find something, treat it as a security matter, and speak with your bank and your IT provider before you contact the former employee.

Look also for dependencies that surface later. A monthly report may fail a week after the departure because it ran under the old user, or a vendor may keep sending invoices to a personal address. Keep the offboarding list open for a short period, and review it after the next close and the next payroll cycle. Those two events tend to reveal what the first pass missed.

Document the final state. Save the signed-off checklist, the bank confirmations, the platform user lists, and the date each key changed. This record helps if a lender, investor, or buyer asks how access was managed during the transition. It also helps the next person understand the setup without rebuilding it from memory.

Set a reminder for the next review, even if the company feels settled. Access drifts over time as people join projects, add tools, and change roles. A short quarterly check of the three keys is enough for most small businesses. What changes next is usually not the list itself but the habit of looking at it, and that habit keeps the next departure from turning into an emergency. Checking the result is the last part of any plan for system access to revoke when a finance executive leaves.

Worked example: a hypothetical controller leaving a Boston services firm

Imagine a services company in the Boston area whose controller is leaving after a notice period. The company uses QuickBooks for the books, two bank accounts, a corporate card program, and a shared drive for the monthly close. The controller set up most of these tools and has been the second approver on payments. Nobody has written down the access list. This is a hypothetical case, built to show the steps, not a description of any real business.

The first step is the inventory. In this case, it takes one afternoon of walking through the bank portal, the accounting admin page, the card dashboard, and what's a interim CFO in Massachusetts the email account used for vendor alerts. The owner finds three surprises: a viewer role for an old bookkeeper, a card tied to a personal mobile number, and bank alert emails that reach only the controller's inbox. Each goes on the spreadsheet with a named owner and a due date.

Money keys come first. The owner changes the second approver role to a manager who is staying, and the bank shows the new rule before the controller's last day. The old bookkeeper's viewer access is removed. The recurring vendor bills are checked, and two of them move to the company's accounts-payable mailbox, so nothing depends on one inbox. The card is reissued to a company-controlled phone number.

Next comes the books. The owner becomes the admin on QuickBooks, and the controller's admin role is removed after the current close is finished. The bank feed rules are reviewed to confirm they still categorize transactions correctly. The owner asks the outside accountant to confirm the close calendar and the list of recurring journal entries, so the next close does not depend on one person's memory.

Then the logins and devices. The controller's email is forwarded for a short period, the bank alert address moves to a company role mailbox, a second two-factor method is enrolled for the bank, and the shared items in the password manager are reviewed. The company phone that held the controller's two-factor app is wiped after its data is copied to a company device. Each change is marked with a date and a name, and the checklist is signed by the owner.

After the last day, the owner checks the logs and tests one sign-in with the successor. In this hypothetical case, the first month-end close runs without a break, and the owner adds a quarterly review to the calendar. The setup is not perfect, but the three keys are now in known hands. The next departure will start from a list instead of a search.