← All insights
Finance leadership

What a Fractional Controller Owns, and When Your Company Needs One

A controller owns whether the books are right. Here is what the seat covers, where the CFO seat starts, and the signs your company needs one.

8 min read

Most founders don't go looking for a controller. They go looking for an answer to a board member's question, find that the numbers aren't finished, and realize nobody on the team owns whether they're right.

That gap has a name. A fractional controller is a senior accountant who owns the accuracy of your books on a part-time or retainer basis: the close, the reconciliations, the controls, and the reporting everyone else relies on.

You get controller-level judgment without a full-time salary, and without asking your bookkeeper to become something they were never hired to be.

We've already covered the difference between the three finance roles in Bookkeeper, Controller, or CFO: Which One Does Your Business Actually Need?, so this article goes one level deeper: what the controller seat owns, where the CFO seat starts, and what good looks like once it's filled.

That starts with the job itself.

What a fractional controller actually owns

A bookkeeper records what happened. A controller owns whether that record is right, and whether it will still be right next month when the business is bigger and messier.

In practice, a fractional controller owns four things.

The close. A published calendar with an owner, a due day, and a reviewer for every task, so the books finish on the same business day each month instead of whenever the scramble ends.

Reconciliations. Every balance sheet account tied out and reviewed, not just the bank accounts. Deferred revenue, prepaids, accrued expenses, and intercompany balances are where quiet errors live.

Controls. Who can approve a bill, who can pay it, who can change vendor bank details, and who checks. At a growing company these decisions usually got made by accident, and a controller makes them on purpose.

Reporting accuracy. The P&L, balance sheet, and cash flow statement arrive on schedule, tie to each other, and mean the same thing every month.

What the controller doesn't own is the question of what to do next. That belongs to a different seat, which is where most of the confusion starts.

Fractional controller vs fractional CFO: accuracy versus direction

The cleanest way to split the two roles is by the question each one answers.

The controller answers "is this right?" Revenue recognized in the right period, costs in the right bucket, cash matching the ledger, and a close that finishes on time.

The CFO answers "what does this mean for what we do next?" Forecasting, pricing, capital, lenders, the board, and transactions. A CFO takes the same financial statements and tells you which decision they support.

The two depend on each other in one direction. A CFO building a forecast on an unreliable close is modeling noise. A great controller without a CFO gives you accurate history and no view forward, which is fine until a raise, a covenant, or an acquisition shows up.

That's why the "fractional controller vs fractional CFO" question is usually framed wrong. It's rarely either/or. It's which gap hurts first. A company with messy books and a raise twelve months out needs mostly controller now and more CFO later. A company with clean books and a board asking for a plan needs the reverse.

So the next question is how to tell which gap you have.

When do you need a controller?

Revenue is a weak signal on its own. Complexity matters more: multiple entities, inventory, deferred revenue, a bank covenant, or outside investors will pull a company toward controller-level work well before headcount does.

The signs tend to look like this:

  • The close lands somewhere after the third week of the following month, and the date moves around.
  • The founder or CEO is doing review work at night that nobody else is qualified to do.
  • The same reconciling items show up month after month without a fix.
  • A lender, investor, or board member asked for numbers and the honest answer was "not yet."
  • Nobody can explain gross margin at the level you actually make decisions, by product, channel, or customer.
  • One person holds the whole process in their head, and a two-week vacation would stall it.

If two or three of those sound familiar, the problem isn't effort. Teams with slow, unreliable closes are usually working harder than teams with fast ones. The difference is process and review, which is the controller's job. Our piece on why your monthly close takes too long walks through the five places a close usually stalls.

Once you've decided you need the seat filled, the next decision is how to fill it.

Should the controller be in-house or outsourced?

An in-house controller is in the building every day and absorbs context by osmosis. The cost is real, though. The median annual wage for financial managers, the BLS category that includes controllers, was $166,570 in May 2025, before benefits, payroll taxes, software, and recruiting. And one hire can't be bookkeeper, controller, and CFO at once. If that person leaves, the function stops and you recruit for months.

An outsourced controller trades physical presence for coverage and seniority at the frequency you need it. The work doesn't stop when one person is out, the tooling usually comes with the engagement, and scope can move up or down as the business changes.

The honest limitation of outsourcing is that it requires you to be deliberate about communication. A company that needs someone physically present in daily operations should probably hire. A company that needs a reliable close, real controls, and someone senior reviewing the numbers before the CEO sees them usually doesn't need that person on payroll yet.

Whichever route you pick, the first three months tell you whether it's working.

The first 90 days with a fractional controller

Good onboarding starts by finishing the current period the way it's already being done, then taking over at a clean break. That's how we run transitions at Cherry Hill, and it's a fair standard to hold anyone to.

A useful way to look at the first 90 days is in three phases.

Days 1 to 30: diagnose and stabilize. A senior reviewer reads the ledger, the chart of accounts, the reconciliations, and the current close process. Cleanup gets scoped separately if the books need it, rather than buried inside the monthly fee. By the end of the month you should have a written view of what's reliable, what isn't, and what gets fixed first.

Days 31 to 60: install the close. A close calendar with owners and reviewers goes live. Balance sheet reconciliations get reviewed as they're completed, not at the end. Standing accrual schedules replace month-to-month guesswork. If the books were in reasonable shape to begin with, the new team should be running your close within one full cycle.

Days 61 to 90: controls and reporting. Approval limits, payment authority, and vendor-change procedures get documented. The monthly reporting pack settles into a consistent format, with variance commentary against budget and prior period. This is also where automation earns its keep. Bank feeds, rules-based coding, and first-pass reconciliations should be doing the rote work so senior time goes to review.

By day 90, the test is simple. Could you hand a lender a clean set of financials for last month, on a predictable date, without pulling anyone off their day job? The goal of diligence-ready books starts right here.

That foundation is also what makes the CFO seat worth paying for.

Controller and CFO work better as one coordinated team

Plenty of companies end up with finance stitched together from separate vendors: a bookkeeping service, a freelance controller, a CPA firm for tax, and a consultant for the model. Each is competent. Nothing reconciles across them.

The cost shows up in the handoffs. The forecast uses a different revenue definition than the close. The tax preparer finds in March a classification issue that could have been fixed in July. The founder becomes the integration layer between firms that have never spoken.

When the controller and the CFO sit on the same team, the forecast is built on a close the same people own. Board reporting is authored rather than assembled. Tax planning happens during the year because the people closing the books already know the position. And you make one call for one financial question, not three.

That's the model behind our accounting and controller services, which pair with fractional CFO support under one fixed monthly fee rather than hourly billing. Scope gets reviewed as the business changes, so you can start with controller-level ownership and add CFO depth when a raise, a lender, or a transaction calls for it.

There are still a few things this arrangement won't do, and they're worth naming before you commit.

What a fractional controller will not do

A fractional controller is not your auditor. If you need an audit or a review, that has to come from an independent firm. A good controller prepares the schedules and manages the process, but can't sign the opinion.

And a controller alone won't set strategy. Accurate books tell you where you are. Deciding where to go next is CFO work, and quietly asking a controller to do it puts you back to expecting one role to do three jobs.

Where should you start?

If you're still sorting out which roles your company needs, start with Bookkeeper, Controller, or CFO: Which One Does Your Business Actually Need? for the full breakdown. If you'd rather see where your own books stand, the eight-question finance assessment gives you a score and the order we'd fix things in.

When you're ready to talk it through, get in touch with Cherry Hill. A senior practitioner will review your setup and tell you plainly whether a fractional controller is the right answer.

Until next time.

Where does your finance function actually stand?

Eight questions on how your books run today. You get a score, a read on where you are fragile, and the order we would fix things in.