By Shawn Elliott, CFO at High Rock Accounting
Yep, this is one of the most common questions I get on a first call with a SaaS founder: “Do I really need a controller, or is my bookkeeper enough?” And honestly, I get why there’s confusion. On the surface, both roles touch your books. Both of them work in your accounting system. Both of them send you reports once a month. But the work they actually do is about as different as writing code and architecting the product roadmap.
I’ve been in the accounting world for 22+ years. I’ve been a bookkeeper, an accounting manager, a controller, a VP of Financial Operations, and now CFO. I’ve sat in every one of these seats. So when I tell founders these roles are not interchangeable, I’m not making a pitch — I’m telling you what I’ve watched go sideways more times than I can count when founders assume they are.
Here’s the thing. If you’re pre-revenue or just getting on your track of revenue, you might genuinely only need a bookkeeper right now. But the minute investors start asking real questions, or you’re heading into a raise, or you’re trying to figure out why your burn doesn’t match your P&L, you’ve got a controller-shaped gap in your business. And most founders don’t realize it until something breaks.
Let me walk you through what each role actually does, where the line is, and when a fractional controller makes sense for a SaaS company.
What a bookkeeper actually does
A bookkeeper records transactions. That’s the core of the job. They’re the person making sure the money coming in and the money going out gets categorized correctly in your general ledger — Xero, QuickBooks Online, whatever you’re running.
On a typical week, a bookkeeper is:
- Categorizing transactions coming through the bank feed and your Brex or Ramp card
- Entering bills and running bill pay through something like Ramp Bill Pay
- Processing payroll entries out of Gusto or Rippling
- Matching customer payments to invoices in your AR aging
- Doing a basic bank reconciliation at month-end to make sure nothing got missed or duplicated in the feed
That is real, important work. I want to be clear about that. A good bookkeeper keeps your day-to-day clean, and if you don’t have one, you end up in the wild, wild west of uncategorized transactions, missing receipts, and a balance sheet that makes no sense. I’ve inherited books like that. It’s not fun for anyone.
But here’s where it stops. A bookkeeper is generally not trained to look at your balance sheet and ask, “Is this account actually right?” They’re recording what happened. They’re not interpreting it, and they’re not making sure it’s GAAP-compliant.
What a controller actually does
A controller owns the integrity of your financials. Full stop. Where the bookkeeper is recording transactions, the controller is making sure those transactions roll up into a set of financial statements that tell the truth about your business — according to GAAP, not just according to whatever made sense at the time.
That looks very different in practice. On a monthly close, a controller is:
- Building tie-out schedules for every balance sheet account — cash, AR, prepaids, fixed assets, deferred revenue, accrued liabilities, equity, the whole nut — so every number on the balance sheet is supported by underlying detail
- Investigating P&L variances month over month. If marketing spend jumped 40%, the controller knows why before you even ask.
- Recording accruals and deferrals — prepaid insurance, annual software contracts paid upfront, commissions earned but not yet paid
- Calculating and posting revenue recognition under ASC 606. For SaaS, this is a big one — if you’re billing annual contracts upfront, that money sits in deferred revenue and gets recognized ratably, not when the invoice goes out.
- Reviewing the work the bookkeeper did and catching errors before they hit your investor reporting
- Making sure your chart of accounts is actually set up to tell you what you need to know — separating payroll between product R&D, sales and marketing, and G&A so you’re not screwing up your CAC number
A controller is also the person who gets you audit-ready before you actually need an audit. That’s one of the things I harp on with founders all the time. The worst time to find out your books aren’t audit-ready is when a Series B lead asks for audited financials and you’ve got 60 days to produce them. If a controller is doing the job right, you’re audit-ready every single month. There’s no cleanup phase, no panic, no scramble to reconstruct two years of history. You just open the file and hand it over on a silver platter.
Why founders mix them up
Honestly, the confusion is understandable. Both roles produce financial statements. Both send them to you. Both use the same software. If you’ve never had a real controller, you might look at your monthly P&L from a bookkeeper and think, “Great, I’ve got financials.”
Here’s what you’re not seeing. You’re not seeing the 90-day aged AR that should have been written off to bad debt. You’re not seeing the payroll liabilities from six months ago that never got cleared out to the P&L. You’re not seeing that your deferred revenue balance doesn’t tie to your billing system because someone applied a payment directly to AR instead of the invoice. You’re not seeing the fixed asset that should have been expensed because it’s under your capitalization threshold, or the one that was expensed but should’ve been capitalized and depreciated.
I’ve walked into companies where the P&L looked beautiful on the surface and the balance sheet was a complete mess underneath — because the bookkeeper was doing exactly what a bookkeeper is supposed to do, but nobody was doing the controller work. The founder genuinely didn’t know what they didn’t know. And that’s the risk.
The SaaS-specific problem
SaaS makes this gap even worse because your accounting is actually pretty complicated, whether you realize it or not.
If you’re selling annual contracts, monthly subscriptions, or credit-based usage, you’re operating under ASC 606. That means revenue doesn’t hit your P&L when you invoice. It hits when you deliver. So if a customer signs a $120K annual contract on January 1st and pays upfront, you don’t have $120K of revenue in January. You have $10K of revenue and $110K sitting in deferred revenue on the balance sheet, and then you recognize $10K each month for the rest of the year.
A bookkeeper usually isn’t building that schedule. They’re recording the cash deposit and calling it revenue. And if your investors want to see GAAP financials for your next round — or a bank wants them for a loan, or a PE group wants them for acquisition diligence — you’re going to have to right that ship. That usually means showing ugly revenue in one period while you true up prior periods, disclosing the change, and explaining to your board why last year’s numbers suddenly look different. I’ve done that cleanup project. It’s painful. It’s expensive. It’s completely avoidable if a controller is on it from the start.
On the SaaS side specifically, a controller is also thinking about things like: Is your chart of accounts set up to calculate gross margin correctly so you can actually see your hosting and customer success costs separately from R&D? Are you tracking ARR consistently with how you’re recognizing revenue? Are the stats coming out of Maxio or Tabs tying to what’s in the GL? When I do month-end reviews with SaaS clients, I’m running a report out of their revenue recognition tool and tying it to what’s sitting on the balance sheet. If there’s a $150K variance, I want to know why before the month closes, not after.
The risk of not having one
Look, I’m not trying to scare you into hiring someone you don’t need. But there are three real risks when you’ve got a bookkeeper and no controller.
Risk #1: Your financials are wrong and you’re making decisions on bad data.
CB Insights analyzed 431 VC-backed startups that shut down since 2023, and “ran out of capital” topped the list at 70%. But here’s the part that matters: they call running out of cash “the final cause of death, not the root problem.” The actual root causes were poor product-market fit (43%), bad timing (29%), and unsustainable unit economics (19%). Those are the things that drained the cash in the first place — and they’re things you can only see if your financials are accurate enough to show you what’s really happening. If your books are wrong, you can’t manage burn, runway, or unit economics in any meaningful way. You’re flying blind, and by the time you figure it out, you’ve got maybe 60 days of cash left and no time to raise. *1
Risk #2: Your next fundraise gets ugly.
Investors and PE groups at Series B and beyond expect GAAP financials. If you show up to a data room with cash-basis books, a messy balance sheet, and a revenue recognition policy that doesn’t exist in writing, you’re going to get re-traded on valuation — or the deal stalls while you clean up. I’ve seen founders lose months of momentum because their books weren’t ready. The round still happens, usually, but at worse terms.
Risk #3: Internal controls are nonexistent.
A controller isn’t just recording things — they’re reviewing. That separation between whoever enters a transaction and whoever reviews it is one of the most basic internal controls in accounting, and when a bookkeeper is working alone with no oversight, you don’t have it. The Association of Certified Fraud Examiners’ 2024 Report to the Nations pegged the median loss from occupational fraud at a small organization (under 100 employees) at $141,000. *2 That’s not a theoretical number. I’ve personally seen founders get hit by a bookkeeper who was running their own bill pay through the company. A controller reviewing the work makes that much harder to pull off.
When a fractional controller makes sense
The good news is you almost certainly don’t need a full-time controller yet. Full-time controller salaries in most US metros are running $150K to $200K+ with benefits and equity. For a SaaS company doing $1M to $10M in ARR, that’s a lot of overhead for a role that doesn’t need a full 40 hours.
This is exactly where fractional controllers come in. You get someone with 15+ years of experience who’s closed hundreds of months for other companies — closing your books, tying out your balance sheet, reviewing the bookkeeper’s work, posting your revenue recognition entries, meeting with you once a month to walk through your financials — for a fraction of the cost. Most of our SaaS clients sit somewhere between $2K and $8K per month for full fractional controller coverage, depending on transaction volume and complexity.
Here are the signals that tell me a founder is ready for a controller:
- You’ve raised a seed or Series A and your investors are asking for monthly board packages
- You’re selling annual contracts or usage-based pricing and you’ve never formally addressed ASC 606
- You’re planning a raise in the next 12-18 months
- You’ve got a bookkeeper but nobody is reviewing their work
- You’ve ever looked at your own financials and thought, “I’m not sure I trust this number.”
If you’re nodding at any of those, it’s probably time to have the conversation. Not because you need a 40-hour-a-week hire — but because you need someone in the controller seat making sure your books are telling the truth.
How we usually set this up for SaaS founders
At High Rock, our most common engagement for a SaaS company in that $1M to $10M ARR range looks something like this. Our team handles the day-to-day bookkeeping in Xero (or QuickBooks Online if you’re already there). Cassandra, my right hand, comes in and reviews it. I come in as the controller — closing the month, reviewing the balance sheet tie-outs, posting the revenue recognition entries, and then sitting down with you to walk through the P&L, the balance sheet, trending, burn, and runway.
We get you on GAAP from day one so you’re not cleaning up later. We partner with you along the way on things like chart of accounts structure, tech stack decisions — Maxio or Tabs for rev rec, Ramp or Brex for spend, Gusto or Rippling for payroll — and whatever questions come up in between. Just a Slack message away. And when you’re ready to scale into a fractional CFO relationship for projections, fundraising support, and strategic work, we already know your business inside and out.
The takeaway
Bookkeepers and controllers are both valuable. They’re just not the same job. A bookkeeper records. A controller owns the integrity of what gets recorded and makes sure it tells the true story. If you’re running a SaaS company that’s anywhere near a raise, an audit, or a serious board conversation, you need both — and if you’re trying to do it all with one role, something important is slipping through the cracks.
If you want a sanity check on what you’ve got set up today, grab a spot on my calendar or jump into our Hawaiian Shirt Friday Ask an Accountant Hour — that one’s free, no pitch, bring your books or bring your questions.
Let’s connect
Hawaiian Shirt Friday — Ask an Accountant Hour — Fridays at 10 AM PT on Zoom: https://us02web.zoom.us/j/88992505122?pwd=LdbL4NYxN2NNk5RanaHRVtrHgT43O9.1
Book a 30-minute call: https://meetings-na2.hubspot.com/shawn-elliott/30-minute-meeting
Sources
*1 CB Insights, “The top 9 reasons startups fail,” March 5, 2026, based on analysis of 431 VC-backed companies that shut down since 2023. “Ran out of capital” topped the list at 70%, with poor product-market fit (43%), bad timing (29%), and unsustainable unit economics (19%) cited as the underlying root causes. https://www.cbinsights.com/research/report/startup-failure-reasons-top/
*2 Association of Certified Fraud Examiners, “Occupational Fraud 2024: A Report to the Nations,” reporting a median loss of $141,000 per case among organizations with fewer than 100 employees. https://legacy.acfe.com/report-to-the-nations/2024/
Enjoyed this article? Consider Sharing
Author
