What an Interim Controller Does
An interim controller keeps the accounting operation running while the seat is empty, owning the close, the reconciliations and the review layer. The work is operational and recurring rather than strategic and episodic. That means the monthly close, bank and credit card reconciliations, review and release of accounts payable, the receivables aging, cash management, accrual entries, balance sheet schedules, audit and lender schedules, and the reporting package that goes to leadership.
The defining feature isn’t seniority. It’s the review layer.
In most small finance teams the controller is the only person who reviews someone else’s work before it becomes a number in a statement. So the fastest way to write the job description is to list what stops the week the controller walks out. Nobody approves the journal entries. Nobody signs off the bank reconciliation. Nobody reviews the payables batch before it funds. Nobody owns the close calendar, answers the auditor, or writes the variance narrative.
Interim controller services cover that operating layer inside the process you already run. The interim reports to your CEO or your finance leader, works in the systems you already use, and closes on the calendar you already publish. For the baseline role definition, our breakdown of what a controller does versus a comptroller or a CFO draws those lines in detail.
Two boundaries keep this honest. An empty CFO seat is interim CFO leadership, a different decision with a different scope, so indinero’s CFO services is the place to start on that one. And an interim controller doesn’t rebuild the finance function, renegotiate the capital structure, or own board strategy. The seat is the scope.
When a Company Needs an Interim Controller
When to hire an interim controller comes down to three triggers: a vacancy, a planned leave, or a surge the team can’t absorb. All three share one feature. The deadline doesn’t move while the seat sits empty.
A vacancy. The controller resigns and the search will take a while. The Bureau of Labor Statistics projects about 115,300 openings for accountants and auditors each year over the 2025 to 2035 decade, with most of them coming from workers transferring to other occupations or leaving the labor force. A credible controller search is a real search. The close doesn’t pause for it.
Write the cost of an open seat the way your team experiences it. Lost output on the work nobody picked up. Overtime for the people who stayed. A close that slips a few days, then a few more. And review steps quietly skipped, because the only reviewer left.
That last one is the strongest argument here. When the team absorbs the controller’s work, the person who prepares a reconciliation often ends up reviewing it too. Segregation of duties collapses. An interim controller puts an independent reviewer back in the chair, which makes this a controls answer and not only a capacity answer.
A planned leave. Controller leave coverage is the easiest trigger to plan for and the one most often left late, because the date is known months ahead and the decision still gets made in the final week.
Under the Family and Medical Leave Act, eligible employees at covered employers are entitled to up to 12 workweeks of unpaid, job-protected leave in a 12-month period for reasons including the birth of a child, placement through adoption or foster care, an employee’s own serious health condition, or care for a spouse, child or parent with a serious health condition, with military caregiver leave extending to 26 workweeks (U.S. Department of Labor, Wage and Hour Division). That is a statutory entitlement, not a plan for coverage. What it tells you is that the role is protected, so you’re covering a seat rather than replacing a person, and that changes how the scope and the handback get written.
A surge the team can’t absorb. Three versions show up most. An audit, where the request list and the supporting schedules land on top of a normal close and audit preparation becomes a second job for the same people. A lender request, where the work is readying the numbers, meaning clean books and reconciled accounts a capital provider can read. And a system change, where the team keeps closing the old way while standing up the new one, which is what makes a move from QuickBooks to NetSuite hard to staff. In each case the controller you have is competent and simply oversubscribed. That’s a capacity problem, and it gets misdiagnosed as a performance problem.
Two non-triggers, said plainly. If the need is permanent and ongoing, hire. And if there’s no finance function at all and you want the whole thing run for you, that’s a different model.
Interim Controller vs a Rushed Hire, a Temp or Outsourcing
Five routes cover a controller gap, and the right one depends on how permanent the need is and who directs the work. Every route below has a real strength. Full-time hiring is the right answer for a permanent, ongoing need, and nothing here says otherwise.
| Route | What it fits best | What it does well | Where it strains | Who directs the work |
|---|---|---|---|---|
| Full-time hire | A permanent, ongoing controller need with a stable scope | Builds institutional knowledge and owns the function long term | The search runs while the close still has to happen, and a compressed search raises the odds of a mismatch | Your CEO or finance leader, permanently |
| Temp or clerical staffing | Volume work with clear instructions, such as data entry or invoice coding | Adds hands for defined, repeatable tasks and takes transaction volume off the team | Rarely carries the review authority the seat needs, so someone senior still supervises closely | Your team, closely and day to day |
| Project-based specialist | A bounded technical problem with a deliverable, such as a cleanup or a reporting rebuild | Deep expertise aimed at one outcome, with a clear definition of done | Doesn’t cover the recurring close, and the seat is empty again the day the project ends | Your team sets the outcome, the specialist directs the method |
| Ongoing outsourced finance function | A company that wants the accounting function run rather than supported | Removes the hiring and retention problem and brings a defined process with team depth | A full move to an outside operating model is a bigger change than seat coverage needs | The provider runs the function to agreed standards, your team sets priorities above it |
| On-demand controller support | A seat that needs covering, a known leave, or a surge the team can’t absorb | Matches controller-level expertise to the role and works inside your existing systems | It’s support, not a permanent answer, so a permanent need still ends in a hire | Your team keeps priorities and day-to-day management, the provider supplies the expertise |
How to choose comes down to three questions, in this order.
How permanent is the need? If the work is ongoing and will look the same next year, hire. A temporary controller isn’t a cheaper substitute for a permanent one, and treating it as one is how a gap becomes a habit. The honest value of interim cover during a search is narrower. It takes the deadline pressure out of the hiring decision, and deadline pressure is what produces bad hires in a review-authority role.
How well defined is the need? A defined outcome with a deliverable points to project-based help. An undefined but recurring obligation, which is exactly what a close is, points to seat coverage. If you can’t describe the outcome in one sentence, the first work item is scoping, not sourcing.
Who should direct the work? This question separates the last two rows. If your controller, VP Finance or CEO will set priorities and manage the work day to day, you want capacity inside your own operating model. If you’d rather someone else own the function and report results, that’s an ongoing outsourced finance function, and what finance as a service covers is the better read. The middle option is an ongoing outsourced controller layer, where a provider runs the controller function month after month. Both are real answers. Neither one is seat coverage.
How to Scope an Interim Controller Role
Scope an interim controller role in five parts: the outcome, what’s in and out, system access, review points, and the handback condition. Written well it fits on one page, and it doubles as the handback checklist later.
-
The outcome, in one sentence. Not a duty list. An outcome, such as “the close is completed and reviewed on the existing calendar, and the audit request list is answered without pulling the staff accountant off the close.” That forces leadership to decide what matters, and it gives both sides a test for done.
-
What’s in scope, and what’s explicitly out. Name the in-scope work by artifact: the close checklist, the reconciliations, the payables review and release, the receivables aging, accrual entries, balance sheet schedules, the reporting package, and the audit or lender schedules. Then write the exclusions down. Signing authority on bank accounts, hiring decisions, vendor negotiation, tax filings owned elsewhere, systems selection, and anything that belongs to a CFO rather than a controller. The unwritten exclusion is the one that becomes an argument later. In the first close, the interim owns the calendar and the review layer rather than process changes, and parks improvement ideas in a written list.
-
The least system access that does the job. Scope access to the task, not to the title. Read and post rights in the general ledger. Review and approval in the payables workflow without payment release. Read-only bank access rather than payment initiation. Payroll reports rather than the ability to change pay data. The Journal of Accountancy’s 2023 refresher on internal controls frames this as the principle of least privilege, where users get only the access their tasks require and no more. Set the revocation condition in the same moment you grant the access, and keep a written access list from day one, because that list is what gets revoked at handback. Our post on security in outsourced accounting goes deeper on the control side.
-
Review points and who approves. Name the approver for each decision class before the work starts. Journal entries above a threshold you set. The payables release. The bank reconciliation sign-off. Accounting policy judgments. The single point of contact for the auditor. The default, and the right one, is that your CEO or finance leader approves and the interim recommends. An interim controller reports to your leadership, never to the provider.
-
The handback condition. Write it at the start. The engagement ends when the permanent hire is seated or the returning controller is back and the artifacts in the next section exist. Defining the exit up front keeps a temporary arrangement from quietly becoming the permanent structure.
On timing, the honest answer is that timing depends on the role and scope. What it depends on is worth naming: how senior the role is, how wide the scope is, how fast you can grant access, and how well documented your close already is. If the scope turns out to be wider than the seat, a broader conversation about indinero’s accounting services is the better place to start.
A fictional example, for illustration only. The company below is invented, not a client. A four-person finance team: one controller, one staff accountant, one payables clerk and one part-time bookkeeper. The controller resigns. Leadership maps the recurring close tasks and finds the controller prepared about a third of them and reviewed nearly all the rest. Reassigning everything internally would leave the staff accountant preparing and reviewing the same reconciliations, removing independent review on 100% of the balance sheet accounts. The scope written instead gives the interim all of the review items plus the technical preparation the staff accountant hasn’t done before, and leaves the rest with the team. Every reconciliation keeps an independent reviewer.
How to Hand the Controller Seat Back
Hand the controller seat back by leaving behind the artifacts the next person needs, so nothing lives only in the interim’s head. That’s the whole test. Run the first close as documentation work that happens to produce financial statements, and most of the handback is done before anyone needs it.
What the permanent hire or the returning controller should inherit:
- The close checklist as actually run, with owner and sequence per task, including the steps that weren’t in the previous version. If there’s no baseline to adapt, a general month-end close checklist is a reasonable starting point.
- Reconciliation notes per balance sheet account, including where the support lives and what the recurring differences are.
- An open items register with owner, status and next action, including anything deferred during the close.
- Judgments and estimates made during the engagement, with the basis for each, so the successor isn’t reverse-engineering a number.
- A contact list covering banks, lenders, key vendors, the payroll provider, the auditor and system administrators.
- The access list to revoke, with the revocation done and approval authority formally returned to the permanent holder.
- A short list of what was found broken and what was deliberately deferred, with a recommendation on each. Almost nobody produces this one. It’s usually the most useful page in the stack.
Standard procedures and checklists are what make a close both fast and accurate, and cross-training is what removes the holdup when a key person is absent, as the Journal of Accountancy’s 2018 guidance on streamlining the month-end close argues.
Should the interim onboard the permanent hire? Yes, and the shape matters. Run one shared close with a deliberate role reversal. The interim runs it while the new hire observes against the checklist, then the new hire runs the next one with the interim reviewing and available for the items that only surface at cutoff. Harvard Business Review’s 2016 guidance on off-boarding is skeptical of asking a departing person to write a long how-to document, on the grounds that it often doesn’t get written and nobody reads it when it does, and recommends pairing the outgoing person with the successor so the successor can observe, practice and get feedback. A walkthrough beats a binder.
When the original controller comes back from leave instead, add one thing. The delta. What changed, what was found, what was deferred, and what decisions were made while they were out, because they’ll be held accountable for all of it.
How Indinero’s On-Demand Finance Support Works
Indinero’s on-demand finance support provides access to experienced finance professionals for a defined need, without a full move to an outsourced model. For a controller seat, that means controller-level expertise working inside your existing process, with your own leadership still directing the work.
When a controller, accounting or specialist seat is empty or a deadline outgrows the team, indinero can match a professional to the role, so you skip a lengthy hiring cycle.
The model has four steps. Define the role, which means aligning on the need and the right role based on your current priorities. Match a professional who integrates into your existing workflows and systems. Support the work. Then scale up or down as your needs evolve. For a vacancy or a leave, that fourth step is the handback, which is why the exit condition belongs in the scope document on day one.
Indinero’s professionals work within your existing systems and processes, so your team doesn’t change how it operates to get help. Your company keeps control over priorities and day-to-day management, and that control line is the whole point of indinero’s on-demand finance support. It’s the difference between adding capacity and handing over a function.
An indinero controller can take on reconciliations, payables and audit schedules inside your process, while your team keeps its priorities. Indinero provides CFOs, controllers, accounting professionals and finance specialists, and the mix depends on the need and the scope. CFO-level support is available for a defined initiative, though ongoing strategic CFO leadership is its own engagement rather than part of covering a controller seat. On an audit, indinero supports the preparation and your independent auditor performs the audit.
Timing depends on the role and scope. Facts about the firm rather than this service: continuous operations since 2009, stable ownership, 100+ years combined team experience, and SOC 2 compliant (2026).
A covered seat isn’t a favor to the finance team. It’s how the close stays reviewed and the numbers stay credible while you hire. If your controller seat is empty or about to be, start with a conversation about the role and the scope. Talk to an expert, and we’d love to learn how your close actually runs.
Frequently asked questions
A few questions come up every time a controller seat needs covering. Here are the short answers.
Is an interim controller the same as an interim CFO?
No, an interim controller and an interim CFO are different seats with different scopes. The controller owns the close, the reconciliations, the review and release of payables, the receivables aging, cash management, and the reporting package, while the CFO seat is strategic leadership. An empty CFO seat is interim CFO leadership, a separate decision for owners and leadership teams, and indinero treats ongoing strategic CFO leadership as its own engagement rather than part of covering a controller seat.
Can an interim controller cover a parental leave?
Yes, a planned parental leave is one of the clearest cases for interim controller cover, because the scope and the return are both known. Preparation is what makes it work. Document the close before the leave starts, agree what the interim owns and what stays with your team, and write the handback condition into the scope on day one, including what changed and what was deferred while your controller was out.
What should an interim controller own during the first close?
In the first close, an interim controller should own the close end to end on the calendar you already publish, with your leadership approving. That means the close checklist as it actually runs, the reconciliations, the review and release of payables, the receivables aging, and the reporting package. The first close is also where undocumented steps surface, so writing the checklist as run makes it the handback document later.
What affects how quickly an interim controller can start?
How quickly an interim controller can start depends on the role and the scope, not on a standard timeline. Four things move it: how senior the role is, how wide the scope runs, how fast you can grant the least system access the work needs, and how well documented your close already is. Indinero scopes the role first, so the conversation starts with the seat and the handback condition rather than a date.
Who does an interim controller report to?
An interim controller reports to your CEO or your finance leader, not to indinero. Your company keeps control over priorities and day-to-day management, which in practice means one named approver for the work, defined review points for journal entries, the payables release and the bank reconciliation sign-off, and your leadership deciding what gets worked first. The interim recommends, your approver decides.
Should an interim controller help onboard the permanent hire?
Yes, when the timing allows it, an overlap between the interim controller and the permanent hire is worth planning for. Walking a close together beats reading a manual, so an indinero controller runs one while the new hire observes against the checklist, then they swap. If no overlap is possible, the handback package carries it: the close checklist as run, reconciliation notes, open items, and the access list to revoke.
