Your Month-End Close Takes Fourteen Days

It is Wednesday the 3rd, 9:22 AM. Your controller opens the month-end close checklist for the Monday finance stand-up. 47 open items. 22 sit in reconciliation. Nine sit in accrual. Six sit waiting on a department head to confirm a variance. One $940K revenue account is unreconciled because the billing export from Stripe does not tie to the deferred revenue schedule by $38,412.

She opens the Stripe file. The billing team pushed a new discount code on the 21st that landed in a different SKU than the finance mapping expected. The revenue rec model was built when the company had four SKUs. There are now eleven. The senior accountant flagged the variance on the last day of the month, sent a Slack message to the head of billing, and never got a reply. The audit committee meets on the 15th.

She opens the department variance queue. Six line items sit waiting on a nod from marketing, engineering, or sales ops. Marketing spent $84K over budget on a paid campaign that was reallocated mid-month and never re-tagged. Engineering shows a $12K AWS spike nobody can explain. Sales ops flagged a $22K commission true-up that the RevOps lead needs to sign off on before it books. Every variance is a two-message conversation. Together they will burn six business days.

Month-end close is a function. Most Series B and C teams have not staffed it because the controller ran a nine-day close at Series A and assumed velocity would come with the next hire. The function lives in the gap between the controller who owns the checklist, the senior accountant who reconciles the sub-ledgers, the billing lead who pushed a discount code that broke a mapping, the FP&A analyst who needs the numbers by the 10th to update the board pack, the CFO who watches days-to-close drift from nine to fourteen over four quarters, and the CEO who signs off on numbers three weeks after the month ended. On the org chart it sits inside Finance. In practice it sits inside a checklist nobody rebuilds.

The 47 items nobody is driving

Pull the close checklist from the last three months. The NetSuite or QuickBooks task list, the Google Sheet the controller keeps as her working copy, the Slack channel where variances get flagged, the audit prep folder, the FP&A working file, and the CFO inbox. Most teams find 40 to 90 tasks on the checklist at Series B with 30 to 50 percent still open on day seven. Ten to fifteen percent sit past day ten. Three to five percent slip into the following month.

Walk the past-seven bucket. The first item is prepaid expense amortization where the schedule was built in Q4 and three new SaaS renewals have not been added. The fourth is a headcount accrual that needs the People ops file, which lands on the 6th because the payroll close runs three days behind. The seventh is the $940K revenue tie-out that fails on a SKU mapping nobody owns. Each item has a single, specific blocker. None of them are accounting-knowledge problems. All of them are nobody-driving-the-clock problems.

The team that should own this knows it is broken. The controller cannot reconcile eleven sub-ledgers, chase six department heads, and rebuild the revenue rec model in the same week. The senior accountant flags variances and waits. The FP&A analyst starts the board pack on day nine with three placeholders that never get filled. The CFO sends a Sunday email to the CEO with a caveat that the number could move two points. The function sits unstaffed while the audit committee meets on the 15th with a close that landed on the 14th.

Hiring a senior accountant is the slow answer

The textbook fix is a senior accountant or close manager. Loaded comp in the US runs $110K to $160K a year. Months one through two go to reading the current close checklist, mapping the sub-ledgers, and shadowing the controller through one full close. Months three through six are when days-to-close moves from fourteen days to eleven days as the manager catches the mid-cycle stalls. The controller gets one day of the week back.

The fractional version is faster to start and stops at the same wall. Five to nine thousand a month buys eight to twelve hours a week of senior finance ops time. The first month closes six stuck reconciliations and rebuilds one sub-ledger mapping. The 30 to 40 items a month that need a Tuesday nudge and a Thursday sign-off stay untouched because the hours run out and the consultant moves to the next client.

Both versions assume the work is a person running a checklist. The work itself is pulling every sub-ledger export within a day of month-end, reconciling every account against the prior period, mapping every new SKU and discount code as it lands, drafting the variance email that names the missing input, escalating the right variance to the right department head with the specific dollar impact, updating the FP&A working file before the CFO opens it, and never letting a checklist item sit past day three without a shipped response. On 47 open items that is 45 to 70 hours a week of senior finance work, and no single hire clears that pile while also rewriting the close playbook.

What a fractional AI finance ops function does

Hand the general ledger, the sub-ledger exports, the Stripe and billing data, the AP and AR aging files, the SaaS subscription list, the payroll register, the close checklist, and the FP&A working file to a fractional AI agent that runs on a daily cadence. The agent does the work a senior accountant, a close manager, and an FP&A analyst would do together. The cadence is daily during close week, per-transaction on new billing events, weekly on the sub-ledger reconciliations, and quarterly on the checklist rebuild.

Every sub-ledger reconciled inside a day of month-end. Stripe, the AP aging, the AR aging, payroll, the fixed asset register, and the deferred revenue schedule get pulled and tied out against the GL by end of day one. The $38,412 SKU mapping variance surfaces on the 2nd with the specific discount code, the affected invoices, and a proposed journal entry, not on the 14th as a mystery. The senior accountant reviews and books, or edits and books.

Every variance routed to the right department head with the dollar impact named. The $84K marketing overspend routes to the CMO with the campaign, the reallocation timestamp, and a two-line explanation. The $12K AWS spike routes to the head of engineering with the service breakdown. Same shape as the lead routing function on the sales side, run on the finance side.

Accrual schedules rebuilt as the contracts change. New SaaS renewals, new hires, new commission plans, and new customer contracts get added to the amortization and accrual schedules the day the contract signs, not the day the controller notices during close. The prepaid schedule updates on the 22nd when the new tool renews, not on the 8th of the following month when it fails a tie-out.

Checklist items tracked against a three-day clock. The agent watches every open item against a target close date. Any item sitting past day three triggers a Monday brief for the controller with the specific blocker, the affected accounts, and a draft resolution. The 47-item list resolves into six workstreams on a Monday morning.

FP&A working file fed nightly, not on day nine. The CFO opens a dashboard showing days-to-close at 6.8 and falling, the six items past target, and the projected variance to the board pack. The FP&A analyst starts the board pack on day four with actuals, not on day nine with placeholders. The audit committee gets the close pack five business days before the meeting.

The unit economics of a fourteen-day close

A Series B company at $18M ARR running a fourteen-day close is burning three specific things. The controller, the senior accountant, the FP&A analyst, and the CFO spend a combined 90 to 140 hours a month on close work against a fully loaded hour of $180 to $280. That is $16K to $39K a month of senior finance time on work a playbook covers. Ten to fifteen percent of that time comes back inside a sprint.

The board pack lands on day fifteen instead of day eight. The CEO makes hiring, spend, and pricing calls on numbers that are three weeks stale. On a company shipping $470K in monthly new ARR against a $1.2M monthly burn, a week of decision lag on a spend correction is $60K to $120K of variance that lands in the next month instead of the current one. Multiply by four quarters and the close cadence becomes a real number on the P&L.

The audit and diligence tax is the third line. A fourteen-day close with unreconciled variances turns into three weeks of auditor questions in Q1, a two-week diligence rescope in a Series C process, and a caveat on the ARR walk when the CFO cannot tie discount realization to the deferred revenue schedule. The close-manager hire runs $140K to $200K loaded with a two to three month ramp before days-to-close moves.

A 14-day sprint to stand up the agent runs in the low to mid five figures. Ongoing cost lands closer to one contractor than a finance hire. The 47-item triage lands on the controller's desk in week one. The first stuck reconciliation clears in week two. The FP&A dashboard runs nightly before the sprint closes.

What changes after the sprint

Picture the same Wednesday the 3rd, 9:22 AM moment, fourteen days after the sprint ships. The controller opens the close checklist. Past three reads six items against the twenty-two from a fortnight ago. Past seven reads one. Past ten reads zero. The Monday brief shows nine variances routed this week with the specific department head and dollar impact named on each. The days-to-close reading on the dashboard reads 7.2 and falling.

By the 8th the $940K revenue account is reconciled after the SKU mapping rebuilt against the eleven live SKUs. The $84K marketing variance closed on the 4th after the CMO signed off inside a day. The $22K commission true-up booked on the 5th after RevOps confirmed the plan. The CFO closes the board pack on the 9th with actuals, not placeholders. The audit committee reads a close pack that landed six business days before the meeting.

If your close currently lives on a Google Sheet the controller opens once a week and a revenue rec model built when the company had four SKUs, the version where every sub-ledger ties out on day one and no checklist item sits past day three is fourteen days away. Month-end close is a function. You can hire against it, you can retain a fractional controller for it, or you can scope a sprint and have it running this month. The work is the same. The math is not.