The execution layer of the finance function: the close, the ledger, the reporting package, and the controls, run by senior hands so the numbers are simply right, on time, every month.
We make the numbers simply right, on time, every month: the close, the reconciliations, and the package everything above depends on.
Controller services: the close, the reporting package, right-sized controls, and audit-ready books
Key takeaways
What it is. The execution layer of the finance function, delivered as an outsourced or co-sourced role: the general ledger, a monthly close on a calendar, reconciliations that prove every balance, a reporting package that means something, and controls sized to a small team.
Where it breaks. A four-to-six-week close signals missing structure, monthly financials that answer no question anyone asked, and paper controls a lean team cannot actually operate.
How we help. We rebuild the close as a dated, owned process (five to ten days within a few cycles), ship a reporting package on a fixed date, and install controls that cover the risks that actually harm small companies.
The controller is the least glamorous role in finance and the one everything else stands on: the CFO’s strategy is only as good as the actuals beneath it, the board pack is only as credible as the close behind it, and the audit is only as cheap as the reconciliations were disciplined. When the controller layer is weak, everyone above it is doing controller work badly.
This page covers controllership as we deliver it, typically as an outsourced or co-sourced function beneath your CFO or alongside our fractional CFO practice. The transaction-processing layer beneath it lives at bookkeeping; the forward-looking layer beside it at FP&A.
The close
The monthly close, from weeks to days
A close that takes four to six weeks is missing a system: no calendar, no owners, reconciliations done once a year under audit pressure, and estimates rediscovered each month, and the stale numbers it produces feed every decision upstream. We rebuild the close as a dated, owned process. Cutoffs and accruals come first, revenue and expense cutoff enforced and recurring accruals and deferrals run from standing methodologies. Reconciliations follow, standardized for every balance sheet account and performed monthly rather than heroically at year-end. The flux review, actuals against prior period and plan, is both error detection and the first draft of the management narrative. Then the statements and reporting package ship on a fixed date, every month. The realistic trajectory is a six-week close compressed to five to ten business days within two to three cycles, then held there by the calendar. Once the calendar, owners, and standing schedules exist, a five-day close costs no more effort than the six-week version did.
The monthly close rebuilt as a dated, owned process. Illustrative day ranges.
Controls
Right-sized controls for a small team
Small finance teams face a structural problem: real segregation of duties requires more people than exist, so either the controls live only on paper or one trusted person can move money alone. Right-sizing means covering the two risks that actually cause loss, cash out the door and revenue misstated, with mechanisms a lean team can sustain. Bank-level payment controls, dual approval on disbursements above a threshold, positive pay, and no shared credentials, make the bank enforce the segregation the org chart cannot. System-enforced approval workflows on purchases and vendor-master changes address the small-company classic, vendor-master fraud. The monthly reconciliation discipline from the close is the detective control that catches what the approvals miss. And an outsourced controller provides structural segregation, an independent senior review of the ledger, the payments, and the reconciliations, separation of duties purchased rather than hired. What we do not install: SOX-filer frameworks, walkthrough documentation nobody will maintain, or policies too long to follow; when a lender, acquirer, or filing finally requires the full program, the SOX practice takes over a foundation instead of a blank page.
Controls sized to the risks that actually harm small companies. Illustrative.
This is for you if
The close takes weeks, and the numbers arrive too late to matter.
Nobody can explain every material balance with support, whatever the org chart says.
An audit, lender, or diligence process is about to interrogate the ledger.
One trusted person can move money alone, and everyone knows it.
What you get
The close, rebuilt A dated calendar, standing reconciliations for every account, and a five-to-ten-day close that holds.
The monthly package Statements with comparisons, the flux narrative, the working capital view, and a stable KPI set, on a date.
Right-sized controls Bank-enforced payment approval, system workflows, and reconciliation discipline, sized to a lean team.
Scrutiny readiness A pre-built PBC list and a data room that assembles in days, for the audit, the lender, or the buyer.
How We Help
What we deliver
On a controller engagement, you get the numbers right, on time, with the proof attached.
The close, rebuiltA dated calendar, standing reconciliations for every account, and a five-to-ten-day close that holds.
The monthly packageStatements with comparisons, the flux narrative, the working capital view, and a stable KPI set, on a date.
Right-sized controlsBank-enforced payment approval, system workflows, and reconciliation discipline, sized to a lean team.
Scrutiny readinessA pre-built PBC list and a data room that assembles in days, for the audit, the lender, or the buyer.
When companies bring us in
The close takes weeks, and the numbers arrive too late to matter.
Nobody can explain every material balance with support, whatever the org chart says.
An audit, lender, or diligence process is about to interrogate the ledger.
One trusted person can move money alone, and everyone knows it.
Our Experience
Where we have done this work
Engagement Notes
Closes rebuilt and held
Controller engagements across growth and sponsor-backed companies: six-week closes compressed to business days and held there by calendar rather than heroics, balance sheets where every account carried a monthly reconciliation, and reporting packages that fed management, boards, and lenders from a single close.
Engagement Notes
Controller functions under audit and diligence
Controller functions that met their audits and diligence processes ready: PBC lists answered from standing schedules, first-year audits after acquisitions run from documented opening balances, and data rooms assembled in days because the filing discipline predated the request, the difference between a review and a reconstruction, paid for in advance.
The Detail
The gaps, and how we close each one
Issue 01
What a controller owns, and what one is notThe Role
Title inflation has blurred the role from both directions: bookkeepers promoted to controller in name, and controllers quietly expected to be CFOs. The role has a real definition, and companies that cannot state it usually have an unfilled role behind someone’s title.
The treatment
The controller owns the integrity of the numbers: the general ledger and its chart of accounts, the monthly close and its calendar, the reconciliations that prove every balance, revenue and expense recognition applied per policy, AP and AR oversight, payroll accounting, and the production of financial statements that are actually right. Above sits the CFO, who owns judgment, capital, pricing, the board, and consumes the controller’s output; below sits bookkeeping, which processes transactions the controller reviews and structures. The test for whether you have a controller gap: can someone in the building explain every material balance on the balance sheet, today, with support? If the answer routes to “the bookkeeper thinks” or “the CFO would have to dig,” the role is empty regardless of the org chart. We fill it with senior people who own the judgment, with Big Four expertise where it matters, because that judgment is where controllership either protects an audit or costs you one.
What we do: We fill the role with senior hands and make every material balance explainable, with support, on any day.
Issue 02
The close: from weeks to days, permanentlyThe Close
A close that takes four to six weeks is not slow bookkeeping, it is the absence of a system: no calendar, no owners, reconciliations done annually under audit pressure, and estimates rediscovered each month. Slow closes also mean stale numbers, which means every decision upstream depends on old data.
The treatment
We rebuild the close as a documented, owned, dated process: a close calendar with every task assigned and sequenced (cutoffs, accruals, reconciliations, review), standardized reconciliations for every balance sheet account performed monthly rather than heroically at year-end, recurring estimates (reserves, accruals, deferrals) run from standing methodologies instead of monthly improvisation, and a flux review, actuals against prior period and plan, that functions as both error detection and the first draft of the management narrative. The realistic trajectory for most mid-market companies: a six-week close compressed to five to ten business days within two to three cycles, then held there by the calendar rather than by effort. The compounding payoff is everywhere downstream: current numbers for management, a board pack that ships on schedule, and an audit that tests a process instead of reconstructing a year, the same close discipline our audit support practice is built on.
What we do: We rebuild the close as a dated, owned calendar and hold it at days, not weeks, permanently.
From our engagements: The close is the one finance process where the fix is permanent: once the calendar, owners, and standing schedules exist, a five-day close costs no more effort than the six-week version did. The six-week close was never six weeks of work; it was six weeks of missing structure.
Issue 03
A monthly reporting package that means somethingThe Package
Most monthly financials answer no question anyone asked: a system-generated P&L, a balance sheet nobody reads, no comparison, no narrative. Management then runs the business on bank balance and instinct, which works until the month it very much does not.
The treatment
The package we build has a fixed structure and an audience: financial statements with comparisons, actuals against budget and prior year, at the level management actually operates (department or product views, below the consolidated roll-up); a flux narrative in plain sentences, what moved, why, and whether it will move again, written by whoever ran the close while the answers are fresh; the working capital view, AR aging, AP aging, and the cash implications both carry, because the P&L can look fine while slow collections create a cash problem; and a small, stable KPI set agreed with management once, not reinvented monthly. Delivered on a date, every month, because a package that arrives on the 8th changes decisions and one that arrives on the 25th is too late to inform them. For companies with boards or lenders, this same package feeds the board pack and covenant reporting with formatting, not new work, one close, every audience.
What we do: We deliver the monthly package on a date: statements with comparisons, the flux narrative, working capital, and the KPI set.
Close taking weeks, or balances nobody can prove? Talk to us before the audit prices it for you.
Controls for a small team: segregation without headcountRight-Sized Controls
Small finance teams face a structural problem: real segregation of duties requires more people than exist, so either the controls exist only on paper or one trusted person can move money alone. Most fraud losses at small companies trace to exactly this, and most control programs sized for them are copied from companies ten times larger.
The treatment
Right-sizing means covering the risks that actually kill small companies, cash out the door and revenue misstated, with mechanisms a lean team can sustain: bank-level payment controls (dual approval on disbursements above a threshold, positive pay, no shared credentials) that make the bank enforce segregation the org chart cannot; system-enforced approval workflows for purchases and vendor changes, because vendor-master fraud is the small-company classic; the monthly reconciliation discipline from the close, which is itself the detective control that catches what approvals miss; and an outsourced controller as structural segregation, an independent set of senior eyes reviewing the ledger, the payments, and the reconciliations, which is separation of duties purchased rather than hired. What we do not install: control frameworks built for SOX filers, walkthrough documentation nobody will maintain, and policies too long for a small team to follow. When a real controls program is eventually required, by a lender, an acquirer, or a filing, the SOX practice takes over, and it inherits a foundation instead of a blank page.
What we do: We install the three mechanisms that cover real small-company risk, and skip the framework theater.
Issue 05
Outsourced, in-house, or co-sourced: the honest comparisonThe Model
The controller hire is expensive, hard to assess (most hiring managers cannot technically evaluate one), and binary: one person, one skill ceiling, one resignation away from a gap. The outsourced model trades the single employee for a bench, and the trade has real terms worth stating plainly.
The treatment
The comparison, honestly: a competent in-house controller costs low-to-mid six figures fully loaded, brings one person’s ceiling and one person’s availability, and is the right answer once daily physical presence and deep operational entanglement matter, typically well past the mid-market threshold. The outsourced model delivers the function for a fraction of that: senior review with staff execution beneath it, coverage that does not take vacations or resign, technical depth on call (the person running your close can walk down the hall to the people who write position memos for a living), and scalability through transactions, acquisitions, and audits without a hiring cycle. The co-sourced middle is often the practical answer: your accountant or junior controller handles the daily and the physical, we own the close, the reconciliations, the reporting, and the technical layer, and the escalation path is defined in the engagement rather than discovered in a crisis. The model choice is stage-dependent and revisitable; the only wrong version is a controller title with no one doing the controller work.
What we do: We run the function outsourced or co-sourced, with escalation paths defined in the engagement letter.
Issue 06
The controller as the audit and diligence interfaceAudit & Diligence
Audits and diligence processes are, mechanically, interrogations of the controller function: every request list item is a reconciliation, a schedule, or a support package the controller either has or must build under deadline. Companies without the role pay for it precisely here, in audit overruns and diligence findings.
The treatment
A controller function run to this page’s standard makes external scrutiny cheap by design: the PBC list is largely pre-built, because monthly reconciliations, standing schedules, and rollforwards are the request list (the machinery our audit support page describes exists here first); diligence data rooms assemble in days, because the contracts are filed, the balances are supported, and the reporting package provides the trend story buyers rebuild anyway; and the tax handoff is clean, year-end packages your tax preparer can work from without a season of questions, and provision support where the company has grown into needing one. This is the economics of the role: the controller produces correct months and converts every future audit, financing, and sale process from a records reconstruction into a review. Companies feel the difference in fees the first year and in deal outcomes eventually, which is why controllership pays for itself in audit fees and transaction outcomes.
What we do: We keep the PBC list pre-built and the data room assemblable in days, converting every audit from excavation to review.
FAQ
Frequently asked questions
What is the difference between a controller and a bookkeeper?
The bookkeeper processes transactions; the controller owns whether the resulting numbers are right: the close, the reconciliations, recognition per policy, and the financial statements. If nobody can explain every material balance with support, you have bookkeeping without controllership, whatever the titles say.
How fast can our close realistically get?
Most mid-market companies reach five to ten business days within two or three cycles of installing the calendar, standing reconciliations, and estimate methodologies. The speed is a byproduct of structure, not effort, which is also why it holds.
Can an outsourced controller work with our existing bookkeeper and CFO?
That co-sourced shape is our most common engagement: your team handles the daily and the physical, we own the close, reconciliations, reporting, and the technical layer, with escalation paths defined in the engagement letter. The role integrates; it does not displace.
We are too small for internal controls. What should we actually have?
Bank-enforced dual approval on payments, system workflows on purchases and vendor changes, and the monthly reconciliation discipline, three mechanisms that cover the risks that actually harm small companies, sustainable by a lean team. Frameworks come later, when a lender or filing demands them.
Will this make our audit cheaper?
Materially, and usually in year one: monthly reconciliations and standing schedules are the audit request list, pre-built. Auditors price reconstruction; a controller function converts the audit to review, and the fee difference is visible in the first fieldwork.
Sources & authorities
Primary sources for this page
Internal control framework.COSO 2013: the internal control framework a right-sized program maps to, and the full version a SOX program later adopts.
ICFR for filers.SOX Section 404: the management assessment and auditor attestation the full controls program addresses once a lender, acquirer, or filing requires it.
This page summarizes SEC rules and staff guidance for general information, and is not accounting or legal advice. Rules change; confirm the current text before you rely on it.
