Controller vs CFO: what each owns and who decides

Explore the Controller careers hub and the finance careers guide.

Most controller vs CFO pages give you two lists of duties side by side. Close the books on the left. Strategy on the right.

That's not wrong. It just skips how the two seats work together.

I've never been a CFO. I spent years in the seat between the two, doing a lot of the controller work for my business unit and preparing the CFO for the quarter.

This page is about the handoff. The rest of the controller path lives in the controller careers section.

The controller makes the numbers true. The CFO decides what the company does with them.

What's the difference between a controller and a CFO?

A controller runs accounting: the close, reconciliations, internal controls and the audit, so the numbers are right. A CFO runs all of finance: planning, capital, deals, risk and investors, so the company makes the right calls with those numbers. The controller usually reports to the CFO.

The U.S. Bureau of Labor Statistics files both under financial managers. It says controllers "direct the preparation of financial reports," and that experienced financial managers "may advance to become chief financial officers (CFOs)."

And about CFOs: "These executives are responsible for the accuracy of an organization's financial reporting."

So the controller's job is to make sure the CFO never has to defend a number that isn't true.

Controller vs CFO at a glance

The quickest way to see the two seats is to ask what each one answers for when something goes wrong. The controller answers for a wrong number or a broken control. The CFO answers for a bad decision, a missed target or a surprise for investors. Most other differences follow from that.

Titles blur in smaller companies, and "finance director" can mean either seat. Read what the posting owns.

What does a controller do?

A controller owns the close, the general ledger, reconciliations, internal controls, the audit and the financial statements. The controller decides how a transaction is booked, keeps the rules that stop mistakes, and walks the auditors through the evidence. The work is finished when the number is correct and the controls held.

I never had the title.

But in my manager seat, the close for my business unit was mine. About four legal entities, every month, quarter and year end, with most of the entries posted by me.

The judgment calls teach you the handoff. On one new partnership, we had to work out whether we were the principal in the deal or the agent. That one call changes what shows up as revenue.

I wrote the analysis. The CFO approved it. Then I defended it with the auditors.

The audit conversation in an interview is on the controller interview questions page.

For the next judgment call you make in the books, write the one-page memo before anyone asks for it. That's controller work, whatever your title says.

What does a CFO do?

A CFO owns the company's financial decisions: how capital is raised and spent, which deals happen, how much risk to take, and what the board and investors hear. The CFO rarely builds the numbers, and chooses between good options using numbers other people built.

A CFO's day is trade-offs, and the people under a CFO have one job in them. Make them decidable.

I learned that by getting it wrong first.

During an acquisition, IT came in with extra security testing that wasn't in the integration plan. A real chunk of money on top of the budget.

My first reaction was to push back.

Not because security didn't matter. I just couldn't yet walk into the CFO's office and explain why the economics of the deal should change.

Looking back, the pushback wasn't really about the money.

So I started asking. "I just want to understand the necessity of these tests and what it's going to prove."

Once I understood the risk, I agreed. Then I showed IT where the full amount starts to hurt the deal.

Then I split the ask into pieces a CFO could decide on:

We did the must-haves right away, found savings inside the business to pay for them, and moved the rest to the next year.

The way I sum it up now: "preserving the deal economics whilst minimizing a potential security risk."

That's what a CFO does that a controller doesn't. Choose between two good things, the deal and the security, on evidence someone else put together.

Is a controller higher than a CFO?

No. In most companies the controller reports to the CFO, sometimes through a chief accounting officer or a VP of finance. The CFO reports to the CEO and works with the board. At a U.S. public company, though, both put their names on the annual report, so the controller's signature carries real weight.

The SEC's Form 10-K instructions want signatures from the principal executive officer, "its principal financial officer or officers, its controller or principal accounting officer," and a majority of the board. The CFO and CEO also certify the quarterly and annual reports personally.

So the CFO outranks the controller, but they share the report.

Small companies often have no controller and no full-time CFO. They have a bookkeeper, an outside accountant, and maybe a part-time or fractional CFO.

The way I'd put it, owners see finance people like a retainer they only need when they're in trouble, and "this retainer is pretty expensive just to have you kind of like lingering around."

In a small company, the real question is which seat the owner pays for first.

One small business we acquired had an assistant keeping the books and no controller. The 30-60-90 day plan covers folding it in.

If you're looking at a small company, ask who does the close today and who the owner calls when cash is tight.

Can a controller become a CFO?

Yes. Controller to CFO is a well-worn path. The gap is forward-looking work: planning, capital, deals and the board. Controllers who make the move usually get close to FP&A and to deals first, so they've made forward calls before they hold the title.

A controller already has the instinct a CFO needs on a deal. A deal taught me that.

We set up a new operating model with an outside partner. The numbers worked, and everyone was confident in it.

I believed that once a deal works on paper, the hard part is done.

It wasn't.

The trouble started when money had to move. Large payments needed "sign off from the CFO and the CEO," through the business leader and the president.

People were on vacation.

Different amounts went through different routes.

The kind of payment control it needed is on the controller interview questions page.

What I believe now is simpler. "Don't stick to what you put on paper unless you've tested it in the real world."

That's the controller's question, asked at the start of a deal instead of at month-end.

If you want the CFO seat, take it to the next deal you review. Write down who signs each payment and what happens when one of them is away.

That's forward-looking work, and it's the gap.

Where does FP&A fit between a controller and a CFO?

FP&A is the third seat. It owns the budget, the forecast and the analysis behind decisions, and it usually reports to the CFO alongside the controller. The controller tells the CFO what happened. FP&A tells the CFO what's likely to happen next. The CFO uses both to decide.

My own seat had a foot in both. I ran the close for my unit, and I helped prep the CFO on our quarterly results. The FP&A manager vs controller comparison goes deeper on the forward side.

If you're in FP&A and want the CFO seat, your gap runs the other way. Learn how the close works and why each control exists.

A CFO who can't read the books gets surprised.

Which lane fits you: controller or CFO?

Pick the lane by what you like being right about. If you like being right about what happened, the controller path fits. If you like being right about what to do next, and can live with being wrong in public, you're headed toward CFO.

For a controller interview, start with the controller interview questions. To compare every part of finance, see the finance careers guide.

Neither is the lesser seat.

A CFO with a weak controller is guessing.

A controller with no CFO has nobody to hand numbers to.