7 Signs Your SaaS Company's Revenue Recognition Is Wrong
Sam's List Editorial | 2026-06-06
7 Signs Your SaaS Company's Revenue Recognition Is Wrong Investors don't just read your ARR. They test it. When institutional diligence hits your books, the first thing a good accountant looks for is whether your recognized revenue matches what ASC 606 actually requires — not what your billing system defaults to. These SaaS revenue recognition mistakes aren't edge cases. ASC 606 — the revenue standard FASB issued in 2014 as Accounting Standards Update 2014-09, Revenue from Contracts with Customers , effective for private companies starting with 2019 fiscal years — replaced the old industry-specific rules with a five-step model. Revenue recognition consistently ranks among the most common causes of financial restatements, which is exactly why diligence teams start there. Most SaaS founders know revenue recognition exists as a concept. Very few have books that reflect it correctly without intentional effort. The errors below are common enough that a SaaS-focused bookkeeper can usually find at least two or three in any company that hasn't specifically addressed them. Each one distorts your financials in ways that matter — to your ARR metrics, to your deferred revenue balance, and to how investors price your business. 1. You're Recognizing Annual Contract Value Upfront Instead of as Deferred Revenue A customer signs a $24,000 annual contract and pays on day one. Under cash-basis thinking, you booked $24,000 in revenue. Under ASC 606, you've collected $24,000 in cash and recognized $2,000 in revenue. The other $22,000 sits in deferred revenue as a liability until you deliver the service each month. This is the single most common SaaS revenue recognition error. It's also the most visible to any investor who checks your deferred revenue balance against your cash receipts. The difference doesn't just affect one metric — it inflates your revenue line, understates your liabilities, and makes your margins look better than they are for the period in which cash was collected. If you raised a round on upfront-recognized ACV numbers, you have a potential restatement conversation ahead of you. Better to identify it now than in diligence. 2. Implementation Fees Recognized at Signing — an ASC 606 Bundling Error You closed a deal. Contract includes a $5,000 implementation fee and $1,500/month in SaaS fees. You recognized the $5,000 on day one because the implementation happened in week one. That's wrong under ASC 606 — but only if the implementation isn't a truly distinct performance obligation. In most SaaS contracts, implementation is not separable from the ongoing...
