Month-End Close Checklist for a SaaS Company (What to Reconcile, Defer, and Review Every Month)

Ask a SaaS founder how the month went, and you will usually get two numbers: MRR and the bank balance. Both feel solid. Neither one tells you what the business actually earned.

A customer who pays $24,000 upfront for an annual plan puts $24,000 in the bank today, but only $2,000 of it is revenue this month. Stripe deposits arrive net of processing fees, refunds, and disputes, often bundled across several days of charges. Hosting bills land after the month they cover. A sales rep's commission on a two-year deal may belong on the balance sheet, not in this month's expenses. And somewhere in the background, sales tax obligations may be quietly building in states you have never visited.

None of this causes a problem in month one. It shows up in diligence when an investor asks why MRR, revenue, and cash all tell different stories and nobody can reconcile them. A month-end close is how you prevent that: a short, repeatable routine that ties billing, cash, and the books together while the month is still fresh enough to fix.

Here is the full checklist, built specifically for SaaS companies.

Why closing the books is different for SaaS

Most small businesses can get away with reconciling the bank and calling it a close. A subscription business cannot, because cash, billing, and revenue run on three different clocks:

• Cash arrives before it is earned. Annual and multi-year prepayments are a liability (deferred revenue) when collected and become revenue only as the service is delivered. That is the core of ASC 606 for subscriptions.
• Payouts are net, batched, and late. Stripe and similar processors deduct fees, refunds, and disputes before paying out, and one deposit can cover many days of charges. The bank never shows gross sales.
• The billing system is not the ledger. Upgrades, downgrades, prorations, credits, and failed payments all live in the billing tool first. If they never reach the books correctly, MRR and revenue drift apart.
• Some costs belong on the balance sheet. Prepaid annual software and sales commissions on contracts longer than a year are usually spread over time rather than expensed when paid.
• Costs need the right home. Hosting, support, and payment fees belong in the cost of revenue; engineering time may need tracking for tax. Misclassify them and gross margin, and every metric built on it is wrong.
• Sales tax follows customers, not offices. Whether SaaS is taxable depends on the state, and economic nexus means you can owe collection in a state with no physical presence.

That is why "we reconcile the bank" is not a SaaS close. Bank reconciliation proves the cash moved. It says nothing about whether revenue, deferred revenue, accruals, and taxes were recorded correctly.

The SaaS month-end close checklist

Work through the six steps in order. Each one feeds the next, so revenue is only finalized after cash is reconciled, and the review happens only once everything else is in. Expect the first close to take longer; once the routine is set, most early-stage companies can close within the first one to two weeks of the following month.

Step 1: Lock the cut-off and pull the data.

Step 2: Reconcile cash and payment processors.

Step 3: Recognize revenue and roll forward deferred revenue.

Step 4: Record expenses, accruals, and prepaids.

Step 5: Check tax and compliance items

Step 6: Review, reconcile to metrics, and lock.

Xero:-

Worked example: the two reconciliations that matter most

Two schedules do most of the heavy lifting in a SaaS close. Here is what each looks like for a fictional B2B SaaS company in a single month.

1. Stripe gross-to-net reconciliation

The company charged customers $50,000 during the month. The bank received $47,600. The gap is not missing money; it is fees and refunds that need their own lines in the books.

If the company had booked the $47,600 deposits as revenue, it would have understated sales by $2,400, hidden $1,600 of payment processing cost (which belongs in cost of revenue), and buried $800 of refunds. Every line here should come from the processor's balance or payout report, not from the bank feed.

2. Deferred revenue roll-forward

The company sells mostly annual plans billed upfront. Its deferred revenue schedule for the month looks like this:

The $22,000 recognized from deferred revenue lands on the income statement as subscription revenue. The $122,000 closing balance sits on the balance sheet as a liability: services the company still owes customers. The schedule should tie, customer by customer, to the billing system, and the closing balance should match the general ledger to the dollar. Under ASC 606, revenue is recognized as the service is delivered, which for most subscriptions means evenly over the term.

With both schedules done, the last check is the MRR-to-revenue bridge. Suppose month-end MRR is $85,600 but recognized subscription revenue is $84,300. The difference should be explainable in a few lines: $2,100 less because new customers started mid-month, $1,200 more from a one-time implementation fee recognized this month, and $400 less from a service credit. If the gap cannot be explained, something in billing never made it to the books.

A sample close calendar

A close only works if it happens on a schedule. This is a realistic target for a lean SaaS finance function, counted in business days after month-end:

Common month-end mistakes SaaS companies make

• Booking cash as revenue. Recording an annual prepayment as revenue in the month it arrives overstates revenue now and understates it for the next eleven months. It is the single most common SaaS bookkeeping error.
• Using Stripe deposits as sales. Payouts are net of fees, refunds and disputes. Record gross charges and post the deductions separately.
• No deferred revenue schedule. Without a roll-forward that ties to billing, the deferred revenue balance is a guess, and so is revenue.
• Expensing every commission. Incremental commissions on contracts longer than a year are generally capitalized and amortized. Expensing them all at once makes high-growth months look worse than they are.
• Skipping accruals. Cloud hosting, contractors and usage-based tools often bill after the month ends. Without accruals, costs land in the wrong month and gross margin swings for no real reason.
• Misclassifying cost of revenue. Hosting and support sitting in overhead inflate gross margin, which then inflates LTV and payback.
• Ignoring sales tax until someone asks. Exposure builds quietly in states where you crossed a threshold. It is far cheaper to track monthly than to reconstruct during diligence.
• Never locking the period. If last month stays open, a late edit can silently change reports you already sent to your board.

The SaaS close at a glance

When it makes sense to hand off the close

Plenty of founders run this checklist themselves for a while, and with one billing tool, monthly plans only and a few dozen customers, that is reasonable. The work changes shape quickly, though. Annual and multi-year contracts add a deferred revenue schedule. A sales team adds commissions to capitalize. Usage pricing adds estimates. Customers in new states add sales tax tracking. An investor update adds a hard deadline.

At that point the question is not whether the checklist is hard; it is whether it gets done fully, every month, by someone who knows what a clean SaaS balance sheet should look like. That is the work our accounting services for SaaS companies are built around: Stripe and bank reconciliations, deferred revenue schedules, accruals and a close package each month. If the books are already months behind, catch-up and cleanup bookkeeping gets them current first, and our outsourced bookkeeping team keeps them there.

→  Accounting services built for SaaS companies

→  Outsourced bookkeeping and month-end close