What a controller owns that a bookkeeper does not
A bookkeeper records transactions. A controller owns the accuracy of the whole set of books. That means the chart of accounts, the accrual policies, the close process, the reconciliations, and the sign-off on every number that leaves the building.
The distinction shows up when something is unusual. A customer prepays for a year. A vendor sends a bill for last quarter. A contract has milestones and a refund clause. A bookkeeper may enter these as they arrive. A controller decides how they should be recognized, documents the reasoning, and makes sure the next person follows the same rule.
For a small company, the best setup is usually a bookkeeper doing daily entry and a part-time controller reviewing, closing, and fixing. You get senior judgment for a handful of hours and keep the daily cost low. If you also need forecasting and board work, add a fractional CFO on top.
Problems that point to a controller, not another bookkeeper
Some symptoms look like bookkeeping problems but need a higher level of skill to fix. Here are the ones that most often lead teams to search for fractional accounting help.
- The close drags past the 15th of the month and numbers keep changing after you share them.
- Bank and credit card accounts have unreconciled items from several months back.
- Revenue is booked when invoices go out, even though contracts run over many months.
- Sales tax, payroll tax, or 1099 reporting has errors or late filings.
- An auditor, lender, or buyer is asking for support you cannot produce quickly.
- You moved accounting software and the old data never fully matched the new.
Fixing these takes judgment, not just hours. A controller sets the policy, cleans the backlog, and trains the team so the problem does not return in the next quarter.
The first three months of a controller engagement
Weeks 1 to 4 clean up the backlog
The controller starts with a review of every balance sheet account. They tie each one to a bank statement, a subledger, or a schedule. Anything they cannot support is listed, and the list is worked down in order of size. Expect a cleanup memo that states what was wrong and what changed.
Weeks 5 to 8 build the close routine
Next comes a written close checklist with owners and dates. The controller sets cutoff rules, accrual methods, and a review step before anything is final. Your first on-time close usually lands here, often by the fifth or sixth business day.
Weeks 9 to 12 prepare for scrutiny
With a steady close, the controller turns to what outsiders will ask for. They build supporting schedules for revenue, deferred revenue, fixed assets, and payroll liabilities. They also prepare a binder for your tax preparer, lender, or auditor so requests are answered in hours, not weeks.
Controller, CFO, or an accounting firm for your stage
These roles overlap, so it helps to see them next to each other. The table compares the options on cost, speed, and how you buy.
| Option | Rate or fee | Start time | Main strength | Commitment | Paperwork |
|---|---|---|---|---|---|
| Fractional controller on Side.work | About $110 to $180 an hour plus a 12, 8, or 5 percent platform fee | Often within a couple of weeks | Close, controls, and accuracy | Weekly hours cap and a notice period | One contract, weekly timesheets, one invoice |
| Fractional CFO | About $175 to $300 an hour plus platform fee | Often within a couple of weeks | Forecasting and strategy | Weekly hours cap and a notice period | Same contract flow |
| Full-time controller | Salary and benefits | Months to hire | Daily ownership | Open ended | Employment terms |
| Accounting firm | Monthly package | Weeks to onboard | Compliance and tax | Annual agreement | Firm engagement letter |
A firm is strong at tax and compliance. A controller is strong at the daily integrity of your numbers. Pick based on which gap hurts more today.
What fractional accounting costs in a real month
Suppose you hire a controller for 8 hours a week at $140 an hour. The rate sits inside the $110 to $180 guide for senior US controllers.
The monthly specialist cost is $140 times 8 times 4.33, which equals $4,849.60. On the Growth plan the platform fee is 8 percent, or $387.97. Your monthly total is $5,237.57 on one invoice for approved hours only.
During a cleanup you might set the cap at 12 hours for the first two months, then drop to 6 once the close is stable. Because the cap lives in the contract, the monthly bill moves with the work. Review plan fees to see how the percentage changes between Starter, Growth, and Scale.
It also helps to think about hours by task. A full cleanup of a messy year can take 40 to 80 hours across several weeks. A steady monthly close for a small company often takes 6 to 10 hours. Reviewing a bookkeeper, answering questions, and handling tax requests adds a few more. Ask each candidate to estimate hours by task before you set the cap, and compare their estimates across candidates.
For comparison, many companies spend the same money on rework without noticing, through late filings, penalty fees, and hours that founders spend fixing spreadsheets.
Hiring a controller through Side.work
Create a role, choose fractional controller, and enter weekly hours and budget. The shortlist shows verified profiles ranked for fit, along with availability for each coming week. You can filter by the systems you use, such as your accounting platform, payroll tool, or billing system.
Send intros, hold a short call, and choose one. The contract includes the hours cap, notice period, scope, and a standard NDA and IP assignment. Because a controller sees sensitive data, read the security page and decide which access levels to grant. A read-only bank feed plus ledger access is enough for most work.
After the start date, the controller logs hours and you approve the timesheet once a week. One invoice covers approved hours and the platform fee. The detail is on the how it works page.
Questions that reveal real controller experience
Anyone can say they close books. These questions separate people who have done it under pressure from those who have only read about it.
- How do you decide what to accrue at month end, and where do you write that rule down?
- Describe a close you shortened. What was the bottleneck and how did you remove it?
- How do you handle revenue from annual contracts or usage billing?
- What do you do when an account will not reconcile after two attempts?
- Which accounting and payroll systems have you run, and which do you prefer?
- How do you work with a bookkeeper who is not as strong as you would like?
Strong answers include a concrete example and a number, such as days saved or accounts cleaned. If your needs lean more toward planning than accuracy, consider a part-time CFO before a controller.
Systems, access, and controls a controller will ask about
A good controller spends the first days learning how your money moves. Expect questions about every system that touches a dollar, and have the answers ready so the engagement starts fast.
They will ask which accounting platform holds your ledger, who has permission to edit it, and whether closed periods are locked. They will ask how invoices are created, whether they flow in from a billing tool or are typed by hand, and who approves bills before payment. They will ask how payroll runs and which provider files the taxes.
They will also look at controls. Who can add a vendor? Who can change bank details? Does one person both approve and release payments? In small companies a single founder often does everything, and that is understandable. A controller will not scold you. They will suggest simple checks, such as a second approver for payments over a set amount and a monthly review of new vendors.
On the data side, ask the controller to document what they find. A short memo covering the chart of accounts, the close steps, and the known issues becomes the manual for the next person, whether that is a new bookkeeper or the controller who replaces them. Good documentation also cuts the cost of any future audit, lender review, or sale of the business, since the buyer can see how the books were kept.
Finally, agree on what the controller should not touch. You may want to keep sole control of bank logins, for example, and have the controller work from statements and read-only feeds. That is a reasonable setup and rarely slows the work.