The core principle is that you recognize revenue when you deliver the service, not when the customer pays. For a monthly SaaS subscription billed monthly, the timing lines up naturally because billing and delivery happen in the same period. Things get more involved when customers pay upfront for annual or multi-year contracts.

If a customer pays $12,000 upfront for an annual subscription, you don’t book $12,000 in revenue the day the payment hits your account. You recognize $1,000 per month over the twelve months of service. The remaining balance sits on your balance sheet as deferred revenue, which is a liability because you still owe the customer future access to your software. Each month as you deliver, deferred revenue goes down and recognized revenue goes up.

Implementation and onboarding fees add another layer. If the setup is a distinct service the customer could reasonably purchase on its own, you can recognize that revenue when onboarding is complete. If setup is just a necessary step to use the software and has no standalone value, you spread that fee over the contract term along with the subscription revenue. The answer depends on how the service is structured, and getting it wrong can misstate your growth rate.

Usage-based components need to be tracked separately. If a customer pays a platform fee plus overages based on API calls or seats, the base fee gets recognized ratably while the usage portion is recognized as the customer consumes it. Blending these together in a single line obscures what’s really driving your revenue.

The formal standard behind all of this is ASC 606, which follows a five-step framework for identifying performance obligations, determining the transaction price, allocating it, and recognizing revenue as obligations are fulfilled. For a straightforward monthly subscription it feels intuitive. For bundled products with professional services, multiple tiers, and variable pricing, it requires careful analysis.

For early-stage SaaS companies still on cash basis accounting, this might not change your tax return today. But investors expect accrual-basis financials with revenue recognized correctly. Messy revenue numbers make due diligence painful and can slow down a funding round. A deferred revenue schedule that doesn’t reconcile to your contracts raises red flags fast. Getting this right from the beginning saves you from a painful and expensive restatement later.

The practical starting point is building a revenue schedule that maps every active contract to its monthly recognized amount and deferred balance. Update it each month as new contracts come in, renewals happen, and churn occurs. This becomes the backbone of accurate financial reporting and feeds directly into the SaaS metrics that matter, like ARR, net revenue retention, and gross margin.

If your current books just record deposits as revenue when they arrive, the financials aren’t telling the real story of your business. Working with bookkeeping services that understand subscription economics means your monthly financials actually reflect performance, not just cash movement. That distinction matters when you’re making hiring decisions, planning spend, or sitting across the table from an investor.