Introduction
Your month-end close keeps slipping past day ten. The board is asking questions your CFO can't answer without re-checking three spreadsheets. An auditor flags the same reconciliation gap for the second year running.
These moments usually point to one thing: your business has outgrown informal accounting oversight and needs a financial controller.
Many leadership teams struggle with timing this decision. Hire too early, and you've added cost without enough work to justify it. Wait too long, and audit adjustments pile up while your CFO spends nights fixing reconciliations instead of planning next quarter.
The right call doesn't hinge on revenue or headcount alone. It depends on your company's complexity, your finance team's current capabilities, your reporting obligations, and what's most urgent right now.
This guide covers when to hire a controller, how to define the role, which qualifications actually matter, how to run a hiring process that works, and when interim or fractional support makes more sense than a permanent hire.
Key Takeaways
- Controllers own close accuracy, reporting, and controls; CFOs focus on strategy, capital, and stakeholders
- Recurring close delays, audit adjustments, control gaps, or new complexity signal it's time to hire
- Strong candidates show technical depth, process improvement, leadership, and relevant transaction experience
- Compensation varies by location, industry, and company size, so skip the single national average
- Permanent, interim, fractional, or outsourced support should match your urgency and the problem's duration
What a Financial Controller Does
A financial controller owns the reliability and execution of your accounting operations. That includes the general ledger, month-end close, financial statements, reconciliations, and accounting policy decisions.
Day to day, controllers typically oversee:
- General ledger accuracy and the month-end or quarter-end close
- Financial statement preparation and account reconciliations
- Accounts payable and receivable oversight
- Payroll coordination and accounting policy documentation
- Internal controls, audit coordination, and tax-filing support
- Budgeting inputs and cash-flow visibility for leadership
Not every controller personally performs every item on this list. In a lean accounting team, the controller handles most of it directly. In larger organizations, they manage staff who execute the work while the controller reviews, approves, and reports upward.
Controller vs. CFO vs. FP&A Leader
These roles get confused constantly, partly because titles vary so much between companies.
| Role | Primary Focus | Time Orientation |
|---|---|---|
| Controller | Accounting operations, close, reporting accuracy, internal controls | Historical and current |
| CFO | Strategy, capital planning, investor and lender relationships, major decisions | Forward-looking, enterprise-wide |
| FP&A leader | Budgeting, forecasting, scenario analysis, performance management | Forward-looking |
The controller owns the books, the controls, and the reporting. The CFO owns broader enterprise finance strategy and external stakeholder relationships, according to Robert Half's controller guide.
Where the Lines Blur
In smaller or transitional companies, a controller often absorbs broader finance leadership duties, maybe some forecasting, maybe investor updates, simply because no one else is positioned to do it. That works fine as a stopgap. It becomes a problem when it's permanent, and the controller never gets to focus on the accounting fundamentals they were actually hired to own.
When Your Business Should Hire a Financial Controller
Common Readiness Signals
Your business probably needs a controller if:
- Month-end close is consistently late, past day 10 or 15
- Financial statements require significant corrections after the fact
- Reconciliations sit unresolved for weeks at a time
- Leadership doesn't fully trust the numbers it's making decisions from
These aren't one-off bad weeks. They're patterns that repeat every close cycle.
Growth That Outpaces Informal Oversight
Growth creates complexity faster than most teams expect. Accounting outgrows informal oversight when you add:
- Entities, locations, or new departments
- Products, debt, or investors
- Complex revenue across multiple contract types
Recognizing that revenue correctly demands dedicated attention one generalist rarely has.
Audit, Compliance, and Control Triggers
Auditors don't flag every mistake as a material weakness. PCAOB's AS 2201 standard lists specific indicators.
Those include senior-management fraud, a restatement correcting a prior misstatement, and an auditor-identified material misstatement that your internal controls wouldn't have caught on their own.
Watch for:
- Recurring audit adjustments year over year
- Known control deficiencies or weak segregation of duties
- Incomplete or missing documentation for key processes
- New reporting obligations from a lender, investor, or regulator
Transaction-Related Triggers
Acquisitions, divestitures, carve-outs, and refinancing all generate accounting work that didn't exist before. That often includes purchase accounting, opening balance sheets, and post-transaction integration.
Equity or incentive compensation changes add another layer of technical accounting most generalist teams haven't handled before.
When Your CFO Is Doing the Wrong Job
If your CFO, founder, or finance director spends most of the week managing close activities, chasing reconciliations, or supervising bookkeeping instead of planning strategy, that's a controller-shaped hole in your org chart.
A quick readiness test:
- Do you consistently miss clear reporting deadlines?
- Is ownership of accounting processes unclear?
- Are your systems and data reliable enough to support growth?
If you're nodding yes to two or more, a controller hire deserves serious consideration.
Not every accounting problem needs a controller, though. Bookkeeping backlogs usually need cleanup work, not a senior hire. A one-time technical question might just need a specialist's opinion. And if your real gap is forward-looking strategy, you need CFO-level support instead.
Define the Role and Candidate Requirements
Before you post the job, write the scope down. Include:
- Reporting line (CFO, CEO, or board)
- Team size and entities covered
- Systems in use, including ERP, consolidation tools, and close software
- Close timeline and audit or regulatory responsibilities
- Transaction exposure, if any
- Specific first-year outcomes you expect from the hire
This document becomes your scorecard later. Skip it, and you'll end up interviewing against a vague mental picture that shifts with every candidate.
Separate Required From Preferred
Essential technical capabilities aren't negotiable. Require direct experience with:
- Financial reporting under GAAP or other applicable standards
- Reconciliations and internal controls
- Audit coordination and close management
- Relevant accounting systems
Credentials are a separate conversation. Robert Half's controller guide notes that employers typically prefer a CPA or CMA, a bachelor's degree in accounting or finance, and seven or more years of relevant experience, with public accounting background valued highly.
Preferred isn't the same as required. A private company without SEC obligations can hire a strong controller without a CPA; a public or audit-heavy company might not have that flexibility.
Industry and Stage Fit Matters
A controller who thrived at a stable, single-entity private company may struggle in a private-equity-backed environment with monthly sponsor reporting, or at a company juggling multiple entities with different fiscal calendars. Ask directly about their experience in settings that mirror yours.
Leadership and Communication Requirements
Technical skill alone doesn't make a good controller. They also need to:
- Manage and develop accounting staff
- Coordinate effectively with auditors and outside advisers
- Explain financial information clearly to non-financial executives
- Push back on inaccurate or incomplete inputs without creating friction
Before posting the role, confirm the job description also covers:
- Responsibilities and decision rights
- Required systems knowledge and work arrangement
- Reporting relationship and compensation range
- Interview stages
- Measurable 90-day and first-year objectives
Build and Run the Hiring Process
Where to Find Candidates
Good controllers rarely sit on general job boards for long. Source candidates through:
- Specialist accounting and finance recruiters
- Professional associations and accounting networks
- Referrals from your audit firm or advisory partners
- Direct referrals from people who've worked with the candidate
- Networks of professionals with relevant transaction or industry experience
Screen for Substance, Not Titles
A "Controller" title at one company can mean something entirely different at another. When screening résumés, look for:
- Progression in responsibility
- Direct ownership of the close and reporting process
- Team leadership rather than team membership
- Systems implementations they drove
- Measurable outcomes
Don't assume a title proves capability. Ask candidates to describe what they actually did.
Structure the Interview Sequence
Run every candidate through the same process:
- Initial experience screen to confirm fit and background
- Technical interview covering accounting depth and judgment
- Leadership and communication interview
- A practical work sample
- Reference checks
- Final stakeholder discussion
Ask Questions Tied to Real Scenarios
Generic questions get generic answers. Ask about scenarios such as:
- Managing a difficult close under time pressure
- Investigating a reconciliation discrepancy that won't resolve
- Improving controls after spotting a gap
- Handling an audit finding end to end
- Implementing accounting software
- Explaining a complex issue to a non-financial executive
Then get specific to your situation. If you're facing a pending acquisition, a carve-out, or a recurring audit adjustment, describe it and ask the candidate to walk through their priorities, the information they'd need, the risks they'd watch for, and their first three actions.
Use a Work Sample and Score Consistently
Give candidates a simplified close calendar, variance report, or reporting package with a built-in issue, and ask them to explain what they'd investigate and how they'd communicate the result. This single exercise often reveals more than a résumé ever will.
Build a weighted scorecard covering:
- Technical accounting and close ownership
- Controls and systems knowledge
- Leadership and communication
- Industry fit and ability to operate at your company's pace
Score every candidate against the same criteria. Then check references for ownership, judgment, accuracy, and whether they improved processes or just maintained them.
Evaluate Candidates Beyond the Résumé
Red Flags Worth Noting
Watch for these warning signs during interviews:
- Vague descriptions of accomplishments with no specifics
- Inability to explain the reasoning behind an accounting judgment
- No concrete examples of improving a close process or control environment
- Inconsistent understanding of their own past reporting responsibilities
- Poor communication when explaining financial concepts to non-finance stakeholders
A strong candidate explains what they did and how they assessed risk, measured improvement, involved other teams, and documented the outcome. Ask for verifiable examples, and don't let anyone invent metrics on the spot.
Assess Cultural and Operating Fit
Cultural and operating fit matter as much as technical skill. Use collaboration scenarios, conflict-resolution questions, and management-style discussions to see how a candidate:
- Coaches and develops staff
- Partners with executives under pressure
- Resolves conflict across teams
- Aligns with how your leadership team works
Keep the Process Fair
Keep every interview on the same footing:
- Ask consistent questions across candidates
- Evaluate only job-related criteria
- Document your decisions as you go
- Avoid questions that touch protected characteristics
Consistency reduces legal risk and leads to clearer hiring decisions.
Choose the Right Hiring Model
Permanent vs. Interim vs. Fractional vs. Outsourced
Not every need for a controller requires a full-time hire. Compare options based on urgency, expected duration, workload, complexity, and your internal team's current capacity.
| Model | Best Fit | Typical Duration |
|---|---|---|
| Permanent in-house | Sustained complexity, ongoing leadership needs | Indefinite |
| Interim | Vacancy, leave of absence, transaction, or audit deadline | Weeks to several months |
| Fractional | Stronger reporting or direction without a full-time seat | Ongoing, part-time |
| Outsourced | Supplemental close, controls, or reporting support | Ongoing or project-based |
When Interim Support Makes Sense
Interim controller support fits specific moments:
- A controller or CAO vacancy with no clear internal successor
- A leave of absence that leaves a gap in accounting leadership
- A transaction or audit deadline that exceeds current team capacity
- A newly appointed CFO who needs execution support while rebuilding the team
When Fractional or Outsourced Fits Better
If your business needs stronger close discipline, better controls, improved reporting, or forecasting support but doesn't yet have enough work to justify a full-time senior hire, fractional or outsourced support often fits better.
Firms like Stratum Advisory Partners work alongside existing finance teams during transitions, complex accounting matters, transactions, or reporting improvement initiatives. Engagements are scoped to the actual problem rather than a fixed package.
Plan the Full Cost, Not Just Salary
Compensation benchmarks vary by geography, industry, company size, scope, and experience. LHH's 2025 salary guide puts controller base salaries at roughly $227,900 for smaller companies with 1 to 100 employees, rising to $346,600 at enterprise organizations with 15,000-plus employees, with a national average near $284,900.
Company revenue alone doesn't predict pay. Location, complexity, and public or private status matter more.
When comparing a permanent hire against interim or fractional support, factor in payroll taxes, benefits, recruiting costs, technology, and onboarding time, not just the base salary figure.
Before committing to a model, decide what success looks like:
- Close reliability and reconciliation completion
- Audit readiness and control remediation
- Reporting quality and team stability
- Specific transaction deliverables
The right model gets you there fastest for the complexity you're managing.
Frequently Asked Questions
How much should a financial controller be paid?
It depends on your market, industry, company size, and the scope of responsibilities involved. National averages hide significant variation, so benchmark against your specific city, industry, and company size.
What is the average salary for a controller at a $100 million company in the United States?
Revenue alone doesn't set pay. Benchmarks are typically built around employee count, location, and complexity. A controller managing multiple entities and investor reporting will likely earn more than one at a similarly sized, single-entity business.
Do I need a CPA to be a controller?
No, a CPA isn't universally required. Employers often prefer it, especially for public-company, regulated, or audit-heavy roles, but candidates with deep hands-on experience can succeed without one.
When should a company hire a financial controller?
Common triggers include delayed closes, unreliable reporting, control weaknesses, audit or transaction demands, multi-entity complexity, and a CFO or founder stuck doing operational accounting instead of strategy.
What's the difference between a financial controller and a CFO?
A controller owns accounting operations: the close, reconciliations, controls, and reporting accuracy. A CFO leads broader financial strategy, capital planning, and investor or lender relationships.
