What a controller does that a bookkeeper does not

The short answer

A bookkeeper produces the records. A controller is accountable for whether those records can be relied on, and for keeping the forward view current between closes. It is a supervisory and technical role, not a faster bookkeeper.

The market prices that difference plainly. The median annual wage for financial managers, the Bureau of Labor Statistics category that includes controllers, was 166,570 dollars in May 2025. Nobody pays that for faster data entry. They pay it for someone who is answerable when the numbers are wrong.

Three things that change at the line

Accuracy moves from output to accountability. A bookkeeper categorises transactions and reconciles accounts. A controller decides whether the resulting statements are right, and says so. That is a judgement about the books, not another pass through them.

Someone owns the controls. Who approves a payment, how cash moves, which exceptions get caught before they post. A bookkeeper works inside those rules. A controller sets them and is responsible when they fail.

The forward view becomes part of the job. Bookkeeping closes a period and is done. The controller also owns what happens between closes: the budget and the variance against it, and what is going to hit the bank in the coming weeks. That work has no deadline attached, which is exactly why it is the part that slips.

Why firms conflate the two

Because at a small client, one person often does both, and the bookkeeping has a deadline while the controller work does not. The close ships. The forward view is rebuilt on the afternoon somebody asks for it.

That is not a failure of skill. It is what happens when a continuous responsibility sits next to a scheduled one and only the scheduled one is tracked. The distinction matters most at the moment a client asks whether they can afford something, because that question is answered from the controller half of the job.

There is a practical test. If the only person who could say whether last month’s numbers are right is the person who entered them, the controller role is not being performed, however good the bookkeeping is. And if answering a client’s forward-looking question means rebuilding their position from scratch, it is not being performed continuously, however well it is performed at the close.

The full scope, and the part that is hardest to deliver from outside the business, is covered in controller services. How many clients one person can carry is a separate question with its own answer in how many clients a fractional controller can handle.

Frequently asked questions

Can one person be both?

In a small business, often yes, and that is usually how it starts. The risk is not the job title but the review: when the person who records the transactions is also the only person judging whether the records are right, nobody is checking the work. Splitting the review is the point, not splitting the headcount.

Does a business need a controller before a CFO?

Usually. The CFO makes the strategic call; the controller makes sure the numbers it rests on are reliable and current. Strong CFO judgement applied to a six-week-old close is still a decision made on stale information.

Is a senior bookkeeper the same as a controller?

Not by seniority alone. The difference is accountability for accuracy, for the controls, and for the forward view between closes. A very good bookkeeper who is not asked to own those things is doing a different job, well.

About the author

Nilanjan Raychaudhuri is the founder of AgentLink (Tublian LLC, Columbus, Ohio), which builds controller-layer software sold through CPA and fractional CFO firms. He has spent the past year interviewing practitioners at fractional CPA and CFO practices about how advisory work is actually delivered. Team page

Wage data from the Bureau of Labor Statistics Occupational Outlook Handbook. Practitioner observations come from design-partner conversations and are used with permission where attributed. Corrections to nilanjan@agentlink.finance.