CFO vs Controller: What Each One Actually Owns

CFO vs Controller: What Each One Actually Owns

Short answer: A controller owns whether the numbers are right. A CFO owns what you do about them. The controller closes the books, reconciles the accounts and produces financial statements you can trust. The CFO uses those statements to forecast, price, allocate capital and answer the questions a board or a lender asks. Most companies under $50 million in revenue need the controller function first, and hire the CFO title second.

The clean division

The controller looks backward and owns accuracy. Month end close. Bank and credit card reconciliation. Accounts payable and receivable. Chart of accounts. Revenue recognition. Payroll accounting. Financial statement preparation. Audit support. The controller's job is that when a number appears on a report, it is correct and it ties to something.

The CFO looks forward and owns judgment. Forecasting and modeling. Pricing. Capital structure and fundraising. Banking and lender relationships. Unit economics. Capital allocation. Board reporting. The CFO's job is deciding what the numbers mean and what should happen next.

The two roles fail differently, which is the useful part. A weak controller function produces numbers nobody trusts. A weak CFO function produces trustworthy numbers nobody acts on.

What a controller actually does in a month

The abstract description hides how much of this is a recurring operational cycle rather than a set of projects.

Days one to three. Close the prior month's subledgers. Cut off accounts payable and receivable. Confirm payroll posted correctly. Chase anything outstanding from the operations side.

Days three to six. Reconcile every bank account, every credit card, every payment processor. This is where most companies quietly fail, because reconciliation is often being forced rather than genuinely performed. A reconciliation that balances because someone booked a plug is not a reconciliation.

Days five to eight. Recurring journal entries. Accruals, prepaid amortization, depreciation, deferred revenue movement, allocations across departments or channels.

Days eight to ten. Review. Compare to prior month and to budget, investigate variances, fix what is wrong, and produce the statements.

A well-run close lands in five to ten business days. If yours takes longer than fifteen, the constraint is almost never effort. It is usually that the structure requires manual reconstruction every month.

What a CFO actually does in a month

Far less predictable, and that is the point. A CFO's month is driven by what the business is deciding.

Reforecasting as actuals land. Pressure-testing pricing against real margin data. Managing the lender or investor relationship, which is mostly about being ahead of bad news rather than presenting good news. Modeling the decision in front of the company: a hire, a facility, a channel, an acquisition. Building the board materials and, more importantly, the argument inside them.

The common thread is that all of it depends on the controller's output being correct. A CFO working from unreliable statements is producing confident-sounding fiction.

The mistake almost everyone makes

Companies hire the CFO title when they have a controller problem.

The symptom that triggers the hire is usually "I do not have visibility into my numbers." That sounds strategic, so a CFO gets hired. Then the CFO spends the first six months fixing the close process, cleaning the chart of accounts and rebuilding the reporting, because you cannot forecast on top of books that do not reconcile.

You have now paid CFO compensation for controller work. Worse, you have hired someone whose actual skill set is idle for half a year, which is one of the most common reasons those hires do not last through the first year.

The order is not negotiable. Accuracy comes before judgment. You cannot model your way out of bad data.

What each costs, honestly

A controller in a mid-sized US market typically runs $120,000 to $180,000 base. Fully loaded with payroll taxes, benefits, equipment and software, plan on $150,000 to $220,000.

A CFO ranges far wider, $200,000 to $400,000 or more, and frequently carries equity. In venture-backed companies the equity component is often the larger part of the package.

Both figures assume you can find and keep the person, which brings in two costs nobody budgets:

Search. Two to four months for a controller, often longer for a CFO, and longer still if you need sector-specific experience.

Ramp. One to three months before genuine productivity. A controller inheriting messy books is closer to three, because the first close is archaeology.

From posting to real output is commonly five to seven months. That gap is frequently the actual problem a company is trying to solve, and it is worth pricing rather than ignoring.

The cost of hiring the wrong one

A mis-hire at this level is expensive in ways beyond salary.

You lose the search time twice, once going in and once coming out. You lose the institutional knowledge the person built. And in finance specifically, you often inherit a half-finished restructure, because the person started rebuilding the chart of accounts or the close process and left it mid-flight. The next person then has to decide whether to finish someone else's design or start again.

The practical protection is to be precise about which function you are buying before you write the job description, rather than posting for a CFO because it sounds more senior and hoping the market sorts it out.

When you genuinely need each one

You need a controller function when:

• Month end close takes longer than ten business days
• You are not confident the balance sheet is right
• Bank reconciliation is either not happening or is being forced to balance
• You have multiple sales channels or entities and cannot see them separately
• An audit, a lender or a diligence process is coming
• You are making decisions off a report someone rebuilds by hand each month
• Your accountant asks the same cleanup questions every year

You need a CFO function when:

• The books are already reliable and the question has moved to what to do with them
• You are raising capital, refinancing, or negotiating a credit facility
• Pricing or unit economics are the live strategic question
• A board or investor group needs regular reporting and challenge
• You are modeling acquisitions, or preparing to be acquired
• Cash forecasting has become a weekly decision rather than a monthly report

If you read both lists and the first one described you, the answer is a controller function, whatever title ends up on the job posting.

The full finance stack, so the roles stop blurring

Four distinct layers, frequently conflated:

Bookkeeper. Records transactions. Categorizes, enters bills, processes payments. Output is a general ledger.

Staff or senior accountant. Performs reconciliations and prepares journal entries. Output is a closed set of books.

Controller. Owns treatment decisions, the structure, the close, and the accuracy of the statements. Output is financial statements you can rely on.

CFO. Owns the interpretation and the decisions. Output is direction.

Many companies have layer one, believe they have layer three, and wonder why the statements do not hold up. Bookkeeping tells you what was recorded. It does not tell you whether it was recorded correctly, and it will not catch a misclassification that has been repeating for two years.

Where fractional fits

The fractional model exists because these are functions, not headcount. Most companies below $50 million need the controller function continuously but do not need a full time senior person to deliver it, and need CFO judgment periodically rather than daily.

Fractional works well when:

• The work is genuinely part time, ten to twenty hours a month for CFO-level input, more for controller work
• You need seniority you could not afford full time
• You need coverage during a search rather than instead of one
• You have a defined problem with an end state, such as a cleanup, a system migration, or audit preparation

Fractional works badly when:

• The volume genuinely fills a full week
• The role needs to be physically present, or deeply embedded in daily operations
• You need someone building and managing an internal finance team
• The work is mostly transactional, which is a bookkeeping need dressed up

The honest test is hours. If the work is thirty hours a week, hire someone. If it is eight, do not hire a full time person to fill a part time need.

The question to ask before you hire either

Ask which of these two sentences is true.

"I do not trust my numbers." "I trust my numbers and I do not know what to do with them."

The first is a controller problem. The second is a CFO problem. Almost every company under $50 million that thinks it has the second problem actually has the first.

If you cannot answer confidently, there is a faster test. Ask for last month's balance sheet and pick one number, any number. Ask what it is made of. If nobody can tell you within a few minutes, you have a controller problem.

Common questions

Can one person be both? At small scale, yes, and often is. The risk is that urgent controller work crowds out strategic work every single month, because closing the books has a deadline and forecasting does not. If you combine the roles, protect the forward-looking time deliberately or it will not happen.

What about a bookkeeper? Bookkeeping is transaction recording. The controller function is the layer above: reconciliation, judgment on treatment, and producing statements. Many companies have bookkeeping and believe they have a controller function.

Do I need a CPA? For controller work, useful but not required unless you are audit-bound or dealing with complex revenue recognition. For CFO work, rarely the deciding factor. Operating experience in your sector usually matters more.

Should my accounting firm do this? Your tax firm builds a structure optimized for filing and compliance. That is a legitimate but different job from management reporting, and one structure rarely serves both well. Many companies discover their chart of accounts was designed for a tax return rather than for running the business.

What if I cannot afford either? Then the question is which specific piece is actually hurting. Often it is one broken thing, the close, the reconciliation, the channel reporting, rather than the whole function. Fixing one thing properly beats hiring for all of it badly.

How do I know if my current close is actually working? Three checks. Does it finish within ten business days. Does every balance sheet account have supporting detail behind it. Can someone other than the preparer explain any number on it. Two out of three is not a pass.

Does the answer change if I am venture-backed? The sequence stays the same, but the timeline compresses. Investor reporting creates CFO-shaped pressure earlier than the business would otherwise generate it, which is exactly why so many funded companies hire a CFO onto books that are not ready.

When should I move from fractional to full time? When the work reliably fills a full week, when you need someone building a team, or when the pace of decisions means part time availability is creating delays. Cost alone is rarely the deciding factor, because fractional stops being cheaper well before it stops being appropriate.

---

FynScale covers the controller and CFO functions for companies between $1 million and $50 million in revenue, including coverage during a search. If you are not sure which one you need, that is usually a short conversation.