What Is Month-End Close?
Month-end close is the recurring accounting process that turns a month of raw transactions into finalized, GAAP-compliant financial statements, then locks the period so no further entries post. The close produces the trial balance, the three core statements (balance sheet, income statement, and cash flow), every reconciliation with its supporting schedule, and the internal reporting package leadership uses to run the business. A good month-end close checklist encodes that work into a fixed sequence with assigned owners.
It’s a control process, not a data-entry one. The controller sets the close calendar, owns reconciliation quality, reviews and approves the final statements, and applies the same internal controls every cycle. The AICPA frames the close as a governed, documented, repeatable workflow rather than an ad hoc scramble, per its best practices in closing processes.
What a SaaS close produces each period:
- Reconciled cash and balance-sheet accounts, tied to support.
- All accrual and deferral entries: prepaids, accrued expenses, payroll accruals, and depreciation.
- Revenue recognized under ASC 606, with the deferred revenue waterfall reconciled to the general ledger.
- A variance analysis versus budget and a board-ready reporting package.
One distinction worth keeping straight: a hard close fully reconciles and locks the period, while a soft close uses estimates mid-month to preview results faster. Teams that run a soft close mid-month reach the hard close with fewer surprises. Clean account reconciliation is the precondition for all of it.
The 10-Day Close Sequence
How long a close should take is a benchmark, not an opinion. Across roughly 2,300 organizations in APQC’s open-standards benchmarking, the median cycle time to complete the monthly close is about 6.4 calendar days, top-quartile teams finish in 4.8 days or fewer, and bottom-quartile teams routinely run past 10. That median has barely moved in a decade, which tells you the gap is process discipline, not tooling.
For SaaS, use these tiers as a frame: the strongest teams close in 5 to 7 business days, growth-stage teams average 10 to 15, and laggards sit at 20 or more. The monthly close process below runs as a 10-day sequence, working backward from the board reporting deadline. Each phase is gated, so a task never starts before its upstream dependency posts. Knowing how to do month-end close well is mostly about respecting that order.
Days 1-2: Data Lock and Cash
Confirm every sub-ledger and feed has posted before you touch a reconciliation: payroll, the expense platform, billing and AR, AP, and corporate cards. Then reconcile all bank and credit card accounts, because everything downstream depends on cash being right. A continuous bank and card feed turns this phase into a confirmation rather than a rebuild. Process employee expense reimbursements and enforce the expense-report cutoff, so late submissions don’t reopen the period. Do not begin balance-sheet reconciliations until posting is stable, or you’ll redo them. This is the least glamorous phase and the one that most determines whether the rest of the close holds together. Cash first. Always.
Days 3-4: Sub-Ledgers and Accruals
Review the AR aging and reserve for doubtful accounts. Run the AP cutoff and accrue for goods and services received but not yet invoiced. Book payroll, bonus, and PTO accruals. Amortize prepaid expenses such as insurance, software, and prepaid rent. Record fixed-asset depreciation and amortization. If you run multiple entities, reconcile intercompany balances now, before consolidation. Tie each sub-ledger back to its GL control account before you move on, so nothing carries a silent variance into the next phase. This is where the matching principle does its work, pairing expenses with the period that earned them. Missing an accrual here swings margins and forces a correction next month. Handle accrued expenses with the same rigor you give cash.
Days 5-6: SaaS Revenue and Equity
Roll the ASC 606 deferred revenue waterfall and recognize the period’s earned revenue. Reconcile MRR and ARR from the billing system down to the GL revenue account, and explain any delta. Record stock-based compensation expense under ASC 718. Accrue sales and use tax liability on taxable SaaS revenue. Book usage-based true-ups as variable consideration, recognized as consumed. The deferred revenue waterfall is the load-bearing schedule here, and its ending balance has to tie to the deferred revenue account on the balance sheet. These entries are what separate a SaaS month-end close from a generic one. Get them wrong and every downstream metric inherits the error.
Days 7-8: Review and Analysis
Run the P&L flux and variance review against budget and the prior period, and investigate anything over your materiality threshold. Complete intercompany eliminations and consolidation for multi-entity groups. Then the controller reviews the full trial balance line by line, confirming each balance traces to support. Write the variance explanations while the data is fresh, because reconstructing them a week later is where close time quietly disappears. This is the review that catches the entry booked to the wrong account, the accrual that looks off, and the revenue number that doesn’t match the board deck. Variance discipline is what turns a pile of reconciled accounts into financial statements a leadership team can actually trust.
Days 9-10: Reporting and Documentation
Prepare the financial statements, assemble the management reporting package, and roll up the board metrics that matter for SaaS: MRR, ARR, net revenue retention, gross margin, burn, and runway. Finalize every supporting schedule so it reconciles to the GL. Then lock the period and archive the audit trail. Hand the finished package to FP&A and your CFO advisory team, so the close feeds planning instead of ending in a folder. The goal of these two days is not just to report the month but to leave behind a record an auditor could follow later without a single clarifying email. Close, lock, document. That last part, doing it the same way next month, is what turns a good close into a repeatable one.
SaaS-Specific Application
A SaaS month-end close differs from a generic close in one place: revenue. Cash arrives up front on annual contracts, but GAAP recognizes it ratably as the service is delivered, so the deferred revenue waterfall and the MRR/ARR-to-GL reconciliation become the load-bearing entries of the close.
ASC 606 governs the mechanics through its five-step model, cited by subsection so your workpapers point to the exact guidance:
- Identify the contract: ASC 606-10-25-1 through -8.
- Identify the performance obligations: ASC 606-10-25-14 through -22.
- Determine the transaction price: ASC 606-10-32-2 through -27.
- Allocate the price by standalone selling price: ASC 606-10-32-28 through -41.
- Recognize revenue as each obligation is satisfied: ASC 606-10-25-23 through -30.
The waterfall in practice: a $12,000 annual subscription posts to deferred revenue on invoice, then $1,000 falls into recognized revenue each month across the 12-month term. The schedule shows opening balance, new bookings, amounts recognized, and ending balance, and that ending balance must tie to the deferred revenue account every close. Prorations for mid-month upgrades, downgrades, and cancellations get partial-period treatment. Commissions to obtain a contract are capitalized and amortized under ASC 340-40. Stock-based compensation runs through ASC 718, measured at grant-date fair value and expensed over the vesting period, per EY’s share-based payment guidance.
Cutoff ties it together. Every dollar lands in the correct period: billed-but-unearned sits in deferred revenue, earned-but-unbilled is accrued as a contract asset, and only the earned portion hits the P&L. For the full model, see our guide to ASC 606 revenue recognition.
Common Pitfalls
Most close problems aren’t arithmetic errors. They’re process failures, and they surface at the worst possible time: during diligence or the first audit. Here are the ones that show up most often.
- Revenue cutoff errors. Recognizing a full annual contract on invoice instead of ratably, or booking revenue in the wrong period. This is the most audit-visible SaaS mistake.
- Deferred revenue that doesn’t tie to the GL. The waterfall ending balance and the deferred revenue account disagree because prorations, cancellations, or mid-month changes weren’t captured.
- MRR and ARR that don’t reconcile to GAAP revenue. Reporting one set of numbers to the board and another in the GL erodes credibility the moment an investor asks which one is real.
- Unsupported top-side journal entries. Adjustments booked at the end of close with no contemporaneous support. Auditors read these as a control weakness.
- Missing accruals. A blown AP cutoff lands expenses in the wrong month and swings margins.
- Reconciliations started too early. Beginning balance-sheet recs before payroll, billing, or card feeds have finished posting forces rework.
- Stale ASC 718 schedules. Stock-comp expense that never got updated for new grants, forfeitures, or modifications.
Most generalist firms miss these during a rushed close. Indinero’s CPA team catches them during monthly close review, before they ever reach an auditor.
The Audit-Ready Standard
An audit-ready close is one where a Series A or Series B auditor could open the books cold and trace every number to support without a single follow-up email. That standard gets built during the close, not reconstructed months later when the auditor arrives.
What audit-ready actually looks like:
- Contemporaneous documentation. Every reconciliation and journal entry carries its support and its reason, filed during the close.
- Supporting schedules that reconcile. Deferred revenue waterfall, prepaid amortization, fixed-asset roll-forward, accrual detail, and ASC 718 stock-comp schedules all tie to the GL.
- No end-of-period plug entries. Balances are built up from support, not forced to a target.
- A documented materiality threshold. Review effort stays proportional and variance explanations stay consistent.
- A locked period with a logged audit trail. Once closed, the period doesn’t move.
This is also what separates a 10-day close from a 3-day close, and it matters more than headcount. A startup hits a 3-day close through infrastructure, not heroics. It runs on automated deferred revenue, accrued revenue, and cost accruals instead of manual entries. Bank and card feeds reconcile daily, so cash is done before the month even ends. A dedicated close team works a fixed calendar with clear owners. A clean chart of accounts maps transactions right the first time. And a mid-month soft close previews results early. Automated close tooling cuts cycle time by roughly 30% to 50% on average, which explains much of the distance between top-quartile and median performers. Real audit preparation starts with the close, every month.
How Indinero Approaches Month-End Close
Indinero runs a CPA-led, GAAP-first close where the books are audit-ready by default rather than audit-painful. Every monthly close gets a GAAP-discipline review before it ships, so the deferred revenue waterfall, the accrual entries, and the ASC 606 revenue numbers are defensible to an auditor on day one, not cleaned up later.
Because bookkeeping, accounting, tax, and fractional CFO advisory sit under one monthly engagement, the close, the reporting package, and the tax position stay consistent instead of being stitched together across three vendors at year-end. With indinero, your bookkeeping team and your tax team are the same team, so close and tax prep aren’t separate fire drills.
That discipline shows up in the numbers. Indinero handles the GAAP work upfront, so your month-end close runs in days, not weeks, and audit prep becomes months of clean books instead of weeks of scramble. When NeoReach came aboard, indinero cut its month-end close from 45 days to under 14, brought the books to full GAAP compliance for a capital raise, and carried the company through diligence with its investment-banking partners.
The track record behind that: continuous operations since 2009, 500+ regular customers, 100+ years of combined team experience, a 5-star Clutch rating, and SOC 2 compliant (2026). Indinero’s outsourced accounting services run this close inside QuickBooks Online or NetSuite, typically in 5 to 10 business days, on month-to-month engagements starting at $750/mo. A cleaner close shouldn’t cost you a vendor scramble.
Frequently asked questions
A few questions come up on nearly every close, from how long it should take to how deferred revenue and cutoff get handled. The answers below cover the ones SaaS finance teams ask most.
What is month-end close and what does it produce?
Month-end close is the recurring control process that turns a month of raw transactions into finalized, GAAP-compliant financial statements, then locks the period. It produces the trial balance, the three core statements, balance sheet, income statement, and cash flow, every reconciliation with its supporting schedule, and the board-ready reporting package leadership uses to run the business. It’s a governed, documented workflow, not a data-entry scramble.
How long should a SaaS month-end close take?
A SaaS month-end close should take 5 to 10 business days, and the strongest teams finish in 5 to 7. APQC benchmarking across roughly 2,300 organizations puts the median at 6.4 calendar days, with top-quartile teams closing in 4.8 days or fewer. Indinero runs a CPA-led, GAAP-first close inside QuickBooks Online or NetSuite, typically in that 5 to 10 day window, and shorter cycles come from automation depth, not longer hours.
What is the typical sequence of close tasks day by day?
The typical month-end close runs as a 10-day sequence of five two-day blocks, each gated so a task never starts before its upstream dependency posts. Days 1 to 2 lock the data and reconcile cash. Days 3 to 4 handle sub-ledgers, accruals, and depreciation. Days 5 to 6 cover SaaS revenue and equity, including the deferred revenue waterfall and stock comp. Days 7 to 8 run review and variance analysis, and days 9 to 10 produce the statements, the board package, and the period lock.
What SaaS-specific tasks need to happen during close?
A SaaS close adds four subscription-native tasks a generic checklist skips: the deferred revenue waterfall, MRR-to-GAAP reconciliation, stock comp, and capitalized commissions. The ASC 606 waterfall rolls opening deferred plus new bookings minus revenue recognized, and its ending balance must tie to the deferred revenue account in the GL. MRR and ARR reconcile from the billing system down to GAAP revenue, stock comp posts under ASC 718, and commissions to obtain a contract capitalize and amortize under ASC 340-40. Indinero’s CPA team owns each of these every month.
How do you handle deferred revenue and revenue cutoff in close?
Handle deferred revenue with an ASC 606 waterfall tied to the GL each month, and enforce cutoff so recognition matches the period delivered. A $12,000 annual contract posts to deferred revenue on invoice, then $1,000 falls into recognized revenue each month across the 12-month term. Billed-but-unearned sits in deferred revenue, earned-but-unbilled accrues as a contract asset, and only the earned portion hits the P&L. Indinero’s CPA team reconciles that waterfall and captures mid-term prorations and cancellations before the period locks.
What separates a 10-day close from a 3-day close?
What separates a 10-day close from a 3-day close is infrastructure, not headcount or heroics. A 3-day close is a different operating model, running on automated accruals, daily bank and card feed reconciliation, and a clean chart of accounts. A dedicated team works a fixed calendar with clear owners, and a mid-month soft close previews results early. Indinero builds that ledger discipline into the monthly cadence inside QuickBooks Online or NetSuite.
What close mistakes typically show up at audit?
The close mistakes that surface at audit are revenue cutoff errors, deferred revenue that doesn’t tie to the GL, and unsupported top-side journal entries. Auditors also flag MRR reported to the board that doesn’t reconcile to GAAP revenue, missing accruals from a blown AP cutoff, and stale ASC 718 stock-comp schedules that never got updated for new grants or forfeitures. Indinero’s CPA team catches these during monthly close review, before they ever reach an auditor.
