A founder I know closed a $120,000 annual contract in January. Collected the full amount upfront. Sent a screenshot of the wire transfer to his investors that same afternoon.
His accountant called him the next morning.
"You haven't recognized any of that revenue yet."
The founder was confused. The money was sitting in his bank account. How had he not made it?
This is the moment most founders discover revenue recognition — the accounting principle that determines when revenue actually counts. And it is one of the most misunderstood concepts in startup finance.
The core idea
Revenue recognition answers a simple question: when did you earn the money?
Not when did you receive it. Not when you invoiced it. When did you earn it.
Under accrual accounting — which is what your auditors, investors, and the IRS care about — you recognize revenue when you have delivered the product or service you were paid for. Not before.
That $120,000 annual contract collected in January? Under GAAP, it gets recognized at $10,000 per month over 12 months. January through December. The $110,000 sitting unearned on your balance sheet is a liability called deferred revenue. You owe that service to your customer. Until you deliver it, you have not made that money.
Why this matters for your startup
Three reasons this trips founders up constantly.
First, your P&L is not telling you what you think it is. If you are recognizing revenue correctly, your income statement reflects work delivered, not cash collected. A great January on the P&L might mean you delivered a lot of service — or it might mean you had strong collections from work done in prior months. These are very different stories.
Second, investors know the difference. Any serious investor looking at your financials will ask about your deferred revenue balance. A large deferred revenue balance is actually a good sign — it means customers have paid you for future work. But if you are not tracking it, you cannot tell that story.
Third, it affects your metrics. ARR, MRR, churn, net revenue retention — all of these depend on when you recognize revenue. If your recognition policy is inconsistent or wrong, every metric downstream is wrong too.
The practical version
For most early stage SaaS companies the rule is straightforward. Recognize revenue ratably over the contract period. A 12 month contract recognized monthly. A one time implementation fee recognized when the implementation is complete. Professional services recognized as delivered.
Where it gets complicated is custom contracts, milestone based billing, and bundled products with multiple deliverables. That is when you need an accountant involved in the decision, not just the bookkeeping.
The one thing to do this week
Pull your balance sheet and find the deferred revenue line. If you do not have one and you collect any upfront payments, you have a recognition problem worth fixing before your next fundraise.
If you do have it, make sure the balance makes sense relative to your contracts. Too low means you may be recognizing revenue too fast. Too high means you may have a collections issue hiding in plain sight.
Your P&L tells a story. Make sure it is the right one.
— Clark Lombardy The Unaudited
Tools and templates from The Unaudited → theunaudited.gumroad.com