How long does the monthly close take for vertical SaaS?

A good monthly close delivers accurate financials you can trust by the 10th business day. Outsourced accounting firms treat that date as the standard. Payments add work through settlement lag, disputes and reconciliation. A controller who reconciles throughout the month can finish well before day ten.

What happens during the monthly close?

During the monthly close, a vertical SaaS company controller works through a checklist that ends in financial statements. Most of it runs before month end.

1. Reconcile billing, the payment processor, bank accounts and credit cards all month.
2. Book expenses and accruals for payroll, commissions and vendors.
3. Collect context from management on specific transactions before the month closes.
4. After month end, reconcile the final payouts, which settle in one to three business days.
5. Recognize revenue under ASC 606 and update the deferred revenue schedule.
6. Update accounts receivable when you bill in arrears.
7. Review the statements for errors and unusual movements.
8. Deliver the financial statements with commentary on the main drivers.

A controller does not wait for month end to start. The checklist is spread across the month, so month end holds only review.

Why is the monthly close harder for payments companies?

The monthly close is harder for payments companies because of transaction volume and variety. They process 100,000 or more transactions a month. Those fall into many categories. Stripe alone defines dozens of balance transaction types.

Charges and refunds post every day. A delayed payment, such as ACH, can fail after it first appears. Fees and reserves move funds in and out of the balance. Disputes debit the account when filed and resolve months later.

Platforms add Stripe Connect. Transfers move funds to connected accounts. For destination charges, Stripe debits refunds and disputes from the platform balance. Recovering that money takes a transfer reversal.

Balance change from activity, October 1–31, 2026

This reconciliation is too slow to start at month end. Weekly is the minimum. Daily is better.

How do you close quickly and accurately after month end?

You close quickly and accurately after month end by reconciling every day. Weekly is the minimum, and daily is the goal. Each day, a controller does five things.

1. Match each billing invoice to its payment.
2. Match each payout to its charges, refunds, disputes and fees.
3. Match each payout to its bank deposit.
4. Review new disputes, failed payments and failed payouts.
5. Ask management about unusual activity while it is fresh.

Daily reconciliation protects the controller's time. At month end, only the last few payouts remain. The controller spends the monthly close reviewing numbers, not building them. Our controller services work this way.

It also finds problems while they are fixable. A new dispute usually gives you 7–21 days to respond. A month-end review can miss that window. A missing payout surfaces in a day, not a month.

Platforms cannot lean on the processor's tools. Stripe's bank reconciliation report does not support Connect accounts or manual or instant payouts. So platform controllers match payouts to deposits themselves. Our guide covers how vertical SaaS can trust its Stripe payouts and books.

What do controllers get wrong about payment accounting?

Controllers unfamiliar with payment operations make a few common mistakes. The first is booking the payout instead of the activity behind it. A payout arrives net of fees and refunds, so deposits alone do not equal revenue. They also confuse single transactions with invoices.

The second is ignoring timing. Funds in transit at month end are not yet in the bank. A dispute debits the account when filed and takes two to three months to resolve. By default, Stripe keeps the dispute fee even when you win.

The third is misreading who bears the cost. On a platform, the platform balance carries refunds and disputes first. The platform recovers them only by reversing the transfer to the connected account.

The fourth is picking gross or net revenue by habit. Under ASC 606, a principal controls the service before transfer and recognizes revenue gross. An agent recognizes its fee net, so each contract needs a judgment. Our guide covers how vertical SaaS should recognize payment revenue.

What does a controller do besides close the books?

A controller does more than close the books. In our experience, the best split of their time is thirds. One third goes to accuracy: every number ties to the processor, bank and billing. Errors surface before investors see them.

One third goes to explaining the numbers. The controller owns the story behind financial performance. That means naming the drivers of revenue and margin changes. It also means communicating the insights to the team.

One third goes to improving the monthly close, because the business keeps evolving. Good accounting runs ahead of the company. That means opening revenue accounts and breaking out cost of goods sold early.

It also means modeling how a revenue-model change will hit the books. The chart of accounts should communicate insights about the business. ASC 606's disaggregation guidance lists categories such as service type, customer type and sales channel. Bridges rebuilds the chart of accounts in every engagement to match the business model.

What do strategic finance and a fractional CFO do with the books?

The strategic finance team uses accurate books to analyze the company's performance, build forecasts, and inform decisions. Strategic finance They test hiring and sales plans against available cash. They estimate unit economics by revenue stream, including profit on each payment.

A fractional CFO relies on accurate books to prepare the quarterly board and investor package. Investors expect cohort unit economics tied to the general ledger. Similarly, a vertical SaaS company exploring an exit must ensure the books are accurate so that the financial diligence doesn't slow down the transaction.

Accurate books without judgment might not help the company leadership with strategic decisions, but they are a vital foundation on which the management team relies.