Last reviewed October 7, 2026 · By the NYBACS advisory team
Short answer
A US business usually needs controller support when the questions it asks of its numbers outgrow transaction recording — typically once it has accrual reporting, multiple entities or currencies, investors or a lender, payroll in several states, an upcoming audit, or a month-end close that keeps slipping. A controller owns the close, accounting policies, internal controls and the accuracy of the financial statements, while the bookkeeper continues the day-to-day entries.
Key takeaways
- Bookkeeping records transactions; controller work reviews them, sets accounting policy and signs off that the statements are right.
- Common triggers are a priced funding round, an audit request, debt with covenants, complex revenue recognition, intercompany flows and multi-state payroll.
- Controller support can be fractional — a few days a month — long before a full-time hire makes sense.
- Basic controls such as payment approvals, segregation of duties and documented reconciliations matter as soon as more than one or two people touch money.
- Waiting until an audit or diligence request usually means paying for cleanup and controller work at the same time.
What changes when a controller steps in
| Area | Basic bookkeeping | With controller support |
|---|---|---|
| Transactions | Recorded and categorized | Reviewed for accuracy and consistency |
| Month-end | Bank feeds matched | Full close checklist, accruals, sign-off and period lock |
| Accounting policy | Implicit, often inconsistent | Written policies for revenue, capitalization, expenses |
| Revenue | Recorded when invoiced or paid | Recognized under a defined policy, with deferred revenue schedules |
| Controls | Founder approves informally | Approval limits, segregation of duties, vendor change checks |
| Reporting | Standard reports from software | Reporting pack with analysis, reconciled to the ledger |
| External parties | Ad hoc responses | Single point of contact for auditors, tax preparers, banks and the parent |
The bookkeeper does not disappear. The controller layer sits above the bookkeeping and makes it reliable enough for outsiders to depend on.
Signs you have outgrown basic bookkeeping
- Investors, a board or a lender now receive monthly or quarterly numbers.
- An auditor — for investors, a lender or a foreign parent — has been or will be engaged.
- Revenue comes from contracts with multiple elements, usage pricing or annual prepayments.
- There are two or more entities, or a foreign parent with intercompany charges.
- Payroll runs in several states, or employees and contractors span countries.
- The month-end close regularly takes longer than a month or keeps being reopened.
- The founder is still the only person reviewing the numbers and approving every payment.
- Different reports of the same figure — revenue, cash, headcount cost — do not agree.
Two or three of these together are usually a clear signal.
Controls a controller typically puts in place
Small companies are disproportionately exposed to payment fraud and simple errors, because one person often handles everything. A controller introduces proportionate controls:
- Payment approvals with limits, and a second approver for larger amounts.
- Vendor master changes verified by call-back to a known number before any bank detail change is accepted — business email compromise schemes commonly target exactly this step.
- Segregation of duties, so the person who creates a vendor is not the same person who releases payment.
- Reconciliation review and sign-off every month.
- Accounting policies in writing: revenue recognition, capitalization threshold, expense reimbursement, intercompany charging.
- Access rights in the accounting and banking systems limited to what each person needs.
These are also what an auditor or investor diligence team will ask about.
Fractional, outsourced or full-time
Most growing startups do not need a full-time controller at first. A fractional controller, working a few days a month alongside the bookkeeping team, can own the close, review entries and maintain policies. As transaction volume, entity count and reporting demands grow, the time required increases; a full-time hire becomes sensible once the role is a daily job rather than a monthly one.
For a US subsidiary of a foreign group, the parent's finance team may already provide some controller functions. The gap is usually US-specific knowledge — US GAAP, sales tax, payroll, information returns — and someone who owns the US close on a US timetable.
Making the transition without starting over
- Assess the current books and fix opening balances where needed.
- Document the policies already in use, then decide which to change.
- Set a close calendar and checklist with named owners.
- Define the reporting pack and its recipients.
- Agree who does what between the bookkeeper, controller and, later, a CFO.
Done in that order, the business keeps its existing bookkeeping and adds review and structure on top.
The first close under the new arrangement usually takes longer than usual, because the controller is setting baselines: confirming that every balance-sheet account has a supporting schedule, that deferred revenue and accruals are calculated the same way each month, and that intercompany balances agree with the other side. After two or three cycles the close should become faster than before, not slower. If it does not, the checklist or the division of work between bookkeeper and controller needs adjusting rather than more hours.
Common mistakes to avoid
- Asking the bookkeeper to make revenue recognition or capitalization decisions without review.
- Hiring a CFO for strategy and fundraising while nobody owns the month-end close.
- Allowing one person to create vendors, approve invoices and release payments.
- Waiting for the auditor to identify missing accounting policies.
- Accepting a vendor's bank detail change by email without verifying it by phone.
- Adding controller support but leaving the close calendar undefined, so nothing actually changes.
NYBACS 360° support
How NYBACS helps
- Provides fractional controller support that owns your close, reviews entries and signs off monthly statements.
- Writes practical accounting policies for revenue, capitalization, expenses and intercompany charges.
- Designs payment approval and segregation-of-duties controls sized for a small team.
- Prepares reconciliations and schedules for your independent auditor and acts as the day-to-day contact — without issuing any audit opinion.
- Plans the transition from your current bookkeeping so nothing is rebuilt unnecessarily.
Frequently Asked Questions
How is a controller different from a CFO?
A controller makes sure the historical numbers are complete, accurate and controlled. A CFO uses those numbers for forward-looking decisions: forecasting, fundraising, pricing and capital allocation. Most companies need the controller layer first.
Does a controller need to be a CPA?
No license is legally required for a controller role. Experience with US GAAP, closes and audits matters most; a CPA license is required for attest services such as audits and reviews, which are performed by an independent firm.
How much controller time does a startup need?
Early on, often a few days a month around the close. It grows with transaction volume, the number of entities and the frequency of external reporting.
Can the controller be based outside the US?
Yes, provided they understand US GAAP, US tax filings and state requirements and can work to the US close calendar. Many cross-border groups combine a US-focused controller with the parent's finance team.
Will controller support reduce audit effort?
Well-prepared reconciliations, schedules and policies usually reduce audit adjustments and back-and-forth. The auditor sets its own scope and fees, so no specific saving can be assumed.
