Industry guides
SaaS revenue recognition for small software companies
November 18, 2026 · 10 min read

Quick answer
SaaS revenue counts when you deliver the service, not when the customer pays. A $24,000 annual plan paid upfront is $2,000 of revenue a month for 12 months, with the rest held as deferred revenue on the balance sheet. Monthly plans are revenue in the month they cover, setup fees are usually spread over the subscription, and usage fees count in the month the usage happens.
A customer signs a $24,000 annual plan on March 1 and pays the whole thing by card. Stripe sends the money a couple of days later. Your accounting software sees a $24,000 deposit and, unless someone tells it otherwise, books March as a record month. April then looks like a collapse, even though nothing about the business changed.
It's one of the most common problems in small SaaS books, and it's fixable with one schedule and a few rules you apply the same way every month. This post walks through how each kind of pricing turns into revenue, a worked example with a deferred revenue schedule, why your billing tool's MRR will never quite match the P&L, and how to handle Stripe payouts so the fees don't disappear.
1/12
How much of a prepaid annual plan counts as revenue each month
$0
Revenue on the day an annual payment arrives. It all starts as deferred revenue
2 numbers
MRR (an operating metric) and GAAP revenue. Both are useful; they're rarely equal
Why can't you just book revenue when the cash comes in?
You can, if you keep your books on the cash basis and nobody outside the company reads them. The moment you sell annual plans, though, cash-basis numbers start lying to you. A good sales month looks like a great quarter, and a month with no renewals looks like a crisis.
Under US GAAP, revenue follows ASC 606. For a subscription, the promise is to keep the software available for the whole term, so the revenue is earned a little at a time as each month passes. The money the customer paid for months you haven't delivered yet is deferred revenue: a liability, because you owe them the service (or a refund, depending on your terms). If you want the full five-step framework behind this, we cover it in ASC 606 in five steps.
Investors will expect accrual numbers. Fixing this early beats restating two years of revenue mid-raise.
How does each pricing model turn into revenue?
Most small SaaS companies mix two or three of these. The table is the short version.
| What you sell | When the cash usually arrives | When it counts as revenue |
|---|---|---|
| Monthly plan | At the start of each month | In the month it covers |
| Annual plan, paid upfront | All at once, at signing or renewal | One-twelfth a month over the 12 months |
| Annual plan, billed monthly | Each month | In the month it covers (same as a monthly plan) |
| Setup or onboarding fee | At signing | Usually spread over the subscription, not on day one |
| Usage or overage fees | Billed after the month ends | In the month the usage happened |
| Multi-year plan, paid upfront | All at once | Spread over the full term, month by month |
Setup fees trip people up the most. If the setup work doesn't give the customer something useful on its own (you're configuring their account so they can use the product), it usually isn't a separate service. The fee is treated as an advance payment for the subscription and spread over it. If renewals skip the fee, the spreading period can run longer than the first contract, which is a judgment call for your accountant or auditor. Real implementation projects that the customer could have hired someone else to do are a different case and may be recognized as that work is done.
Usage fees are the opposite problem: the revenue is earned before you bill it. If a customer used $1,500 of overage in March and you invoice it on April 1, that $1,500 belongs in March.
A worked example: one annual plan, twelve months of revenue
Say you run a project management tool. On March 1 a customer signs a 12-month plan for $24,000 plus a $3,000 setup fee, and pays all $27,000 by card that day. The setup is just getting their workspace and users configured, so it isn't a separate service.
The month-by-month result looks like this: $27,000 of cash in March, and $2,250 of revenue every month from March to February ($2,000 of subscription plus $250 of setup fee).
One annual contract: cash collected vs revenue recognized
$24,000 annual plan + $3,000 setup fee, paid March 1
- Cash collected
- Revenue recognized
Hypothetical example. 12 months × $2,250 = $27,000, the same as the cash collected.
Show the numbers
| Cash collected | Revenue recognized | |
|---|---|---|
| Mar | $27,000 | $2,250 |
| Apr | $0 | $2,250 |
| May | $0 | $2,250 |
| Jun | $0 | $2,250 |
| Jul | $0 | $2,250 |
| Aug | $0 | $2,250 |
| Sep | $0 | $2,250 |
| Oct | $0 | $2,250 |
| Nov | $0 | $2,250 |
| Dec | $0 | $2,250 |
| Jan | $0 | $2,250 |
| Feb | $0 | $2,250 |
The deferred revenue schedule is the piece of paper (or spreadsheet tab) that makes this happen every month. For this contract it starts at $27,000 and drops by $2,250 each month-end:
| Month-end | Recognized this month | Deferred revenue left |
|---|---|---|
| March | $2,250 | $24,750 |
| June | $2,250 | $18,000 |
| September | $2,250 | $11,250 |
| December | $2,250 | $4,500 |
| February | $2,250 | $0 |
In practice the schedule has one row per contract and one column per month, and the month-end entry is a single journal: debit deferred revenue, credit subscription revenue for the total. The balance left on the schedule must equal the deferred revenue balance on your balance sheet. If it doesn't, something was booked straight to revenue that shouldn't have been.
What does a full month look like?
One contract is easy. Here's the same company's whole March, so you can see how the pieces combine:
- Monthly plans: $18,000 billed and collected in March
- The new annual contract above: $27,000 collected
- Annual plans sold in earlier months: $9,000 of deferred revenue moves into March revenue, with no new cash
- Usage overage for March, invoiced April 1: $1,500
Cash from customers in March is $45,000. Revenue for March is $30,750.
March: from cash collected to revenue
Same hypothetical SaaS company
- Adds revenue
- Not March revenue
- Total
Hypothetical example: 45,000 − 22,000 − 2,750 + 9,000 + 1,500 = 30,750.
Show the numbers
| Cash from customers | $45,000 |
| New annual plan deferred | −$22,000 |
| Setup fee deferred | −$2,750 |
| Earlier annual plans released | +$9,000 |
| March usage billed in April | +$1,500 |
| March revenue | $30,750 |
If you'd booked revenue as cash arrived, March would show $45,000 and April might show $18,000 or so. The real business earned close to the same amount in both months.
Why doesn't MRR match the revenue in your books?
Because they answer different questions. MRR (monthly recurring revenue) is an operating metric from your billing tool: the recurring subscription value you have running right now, with annual plans divided by 12. GAAP revenue is what you actually earned in the period under accounting rules.
In our example, end-of-March MRR is $29,000: $18,000 of monthly plans plus $11,000 a month from annual plans ($2,000 from the new one, $9,000 from older ones). March revenue is $30,750. The $1,750 gap is the $250 of setup fee and the $1,500 of usage, neither of which most companies count as recurring.
Other things that push the two apart:
- Mid-month starts and cancellations. MRR jumps on the day a plan starts; revenue counts only the days it ran.
- Discounts and credits. The billing tool may show list price; revenue should reflect what the customer actually owes.
- Refunds. These reduce revenue (or deferred revenue), not just the bank balance.
None of this means MRR is wrong. It means you should report both, label them clearly and keep a short reconciliation between them each month. Investors understand the difference. They get nervous when nobody can explain it.
How should Stripe payouts be recorded?
Stripe (and Chargebee or Paddle sitting on top of a processor) doesn't send you your sales. It sends your balance after fees and refunds, on a schedule. Book only the deposit and three things go wrong at once: revenue is understated, fees vanish, and deferred revenue never gets set up.
Back to March: say Stripe fees on the $45,000 come to $1,380, so deposits total $43,620. The right way to book it:
From the billing data
- Record gross charges: monthly plans to revenue, annual plans and setup fees to deferred revenue
- Record refunds and credit notes against the right customer and plan
- Record usage billed after month-end as revenue in the month it was used
From the Stripe balance
- Record processing fees as an expense ($1,380 in the example)
- Treat Stripe like a bank account: a clearing account that receives gross charges and pays out to your bank
- Reconcile that clearing account to Stripe's balance report so it ends at the right amount, not a mystery number
At month-end
- Post the deferred revenue release from the schedule
- Tie deferred revenue on the balance sheet to the schedule
- Explain the gap between billing-tool MRR and booked revenue
Sync tools help with volume, but they don't know your revenue policy.
Common mistakes in SaaS revenue
Booking annual plans straight to revenue. The classic. The fix is a deferred revenue account and a schedule, set up before the next renewal season.
Recognizing setup fees on day one. It's tempting because the work happens upfront. Unless the setup is a service the customer could use on its own, it gets spread.
Letting the integration decide. Sync tools post whatever mapping you gave them, and many map every charge to one revenue account. Check the mapping when you add a new plan or price.
Ignoring usage until it's billed. This pushes revenue into the wrong month every month, which matters most when you're showing growth.
Netting fees against revenue. Your gross margin is a number investors care about. Payment fees belong in your costs, not hidden inside a smaller revenue line.
When should you get help?
Doing this yourself is fine when you have monthly plans only, one price list and a few dozen customers. Monthly plans are revenue in the month they cover, and a careful founder can keep that straight.
It's time for outside help when annual or multi-year plans are a real share of sales, when you add usage pricing or setup fees, or when a raise or an audit is on the calendar. That's when a deferred revenue schedule, a monthly Stripe reconciliation and an MRR-to-revenue bridge stop being nice to have. It's the core of what we do for software companies at Fintrix Consulting: see how we work with SaaS businesses, including the burn and runway numbers investors ask for (our startup runway calculator is a free place to start).
Frequently asked questions
Is deferred revenue a bad thing on the balance sheet?
No. It's a liability because you still owe the customer the service, but for a SaaS company a growing deferred revenue balance usually means customers are paying you ahead. Lenders and investors read it that way too.
Do I need ASC 606 if I'm a small private company?
If you prepare GAAP financial statements, yes: ASC 606 applies to private companies too. If your books are cash basis for internal use only, it isn't required, but annual plans will make those books misleading.
How do I handle an upgrade in the middle of an annual plan?
Recognize the original plan up to the upgrade date, then spread the remaining deferred balance plus the extra charge over the rest of the term. The exact method depends on your contract terms, so agree on a policy with your accountant and apply it the same way every time.
Does a refund policy change when I recognize revenue?
Usually it changes how you record refunds rather than when you recognize subscription revenue. If you offer refunds on unused months, the deferred balance is the amount at risk. Talk to your accountant if refunds are frequent or large.
Should I track ARR or MRR?
Both are the same idea at different scales (ARR is usually MRR × 12). Pick one for internal reporting, define it in writing (what's in, what's out) and keep it separate from GAAP revenue.
The bottom line
SaaS revenue follows the service, not the cash. Put prepaid plans and setup fees into deferred revenue, release them monthly from a schedule that ties to the balance sheet, record usage in the month it happens, and book Stripe gross with fees as an expense. Keep MRR as your operating metric and show a short bridge to booked revenue. Do that every month and your numbers will hold up when an investor starts asking questions.
Sources
This article is general information, not advice for your situation. Rules change and details matter, so talk to us or your CPA before acting on it.
More articles
- Construction bookkeeping mistakes: job costing, retainage and WIP
November 18, 2026
- Bookkeeping for medical and dental practices: what's different
November 18, 2026
- Nonprofit grant accounting: restrictions and functional expenses
November 18, 2026
Have a question about this article?
Ask us. A real person will reply by email within one business day. Your question isn’t published.
Ready for books you can trust?
Book a free 30-minute consultation. We'll review where your finances stand today and show you exactly how we'd help.