The Complete ASC 606 Guide for SMBs

ASC 606 replaces industry-specific rules with a single principle: recognize revenue when you transfer control of goods or services to the customer, in the amount you expect to be entitled to. The standard operationalizes that principle in five steps, applied contract by contract.

Every downstream complexity - deferred revenue, SSP studies, modification accounting - is just one of these five steps applied to a messier contract. Keep the model in view and the edge cases stay tractable.

The same five steps produce very different recognition patterns depending on the contract shape. Here is how the deals SMBs sign most often typically resolve. (These are the common outcomes, not a substitute for reading your own contracts - small wording changes move deals between rows.)

The mechanics click fastest with real numbers. Take a deal shape almost every B2B SaaS company signs: an annual subscription with a one-time onboarding fee.

Step 2: onboarding here is generic setup and training the customer could buy from a partner, so it is a distinct performance obligation. That gives two obligations. Step 4 says to allocate the $36,000 by relative SSP - not by the line items on the order form:

Step 5: onboarding revenue of $6,300 is recognized when the work completes on January 31. Subscription revenue of $29,700 is recognized ratably at $2,475 per month. So January revenue is $6,300 + $2,475 = $8,775; February through December each show $2,475. Of the $36,000 invoiced on day 1, $33,525 sits in deferred revenue at the end of January and unwinds monthly.

SSP intimidates SMB teams because it sounds like it requires a formal study. It does not. It requires a documented, consistently applied method - and for most SMBs the evidence already exists in the closed-won data.

• Observable prices first. If you sell an element separately (support renewals, training packs, seat add-ons), the observable range of those standalone sales is your SSP. A common practice is to set SSP as the median of standalone sales and treat a band (for example ±15–20% around it) as acceptable.
• Adjusted market assessment. No standalone sales? Anchor to what customers in your market pay for comparable offerings, adjusted for your positioning.
• Expected cost plus margin. For services obligations, build up delivery cost (loaded labor hours) and add your normal services margin.
• Residual approach - last resort. Only appropriate when the price of one element is highly variable or uncertain, such as enterprise software with wildly dispersed pricing. Auditors push back on residual as a default.

Growing SMBs modify contracts constantly - mid-term seat expansions, plan upgrades, term extensions, negotiated discounts. ASC 606 sorts every modification into one of three treatments, and the sorting question is always the same two tests: are the added goods or services distinct, and is the added price at their SSP?

1. 1Separate contract - the modification adds distinct goods/services at a price reflecting their SSP. Example: 10 more seats mid-term at your normal per-seat rate. Account for it as a brand-new contract; the original is untouched.
2. 2Termination-and-replacement (prospective) - the remaining goods/services are distinct from what was already delivered, but pricing does not reflect SSP (a discounted expansion, a renegotiated renewal blended into the current term). Combine the unrecognized old transaction price with the new consideration and spread it over the remaining, go-forward obligations. No restating the past.
3. 3Cumulative catch-up - the remaining goods/services are NOT distinct from what was delivered (typical for a single partially complete services obligation measured on percentage-of-completion). Update the transaction price and measure of progress, and book a catch-up adjustment to revenue in the current period.

For subscription businesses, the practical outcome is that most modifications land in the first two buckets: expansions at list are separate contracts, and discounted mid-term changes are prospective blends. Cumulative catch-ups are mostly a professional-services phenomenon.

Private companies get significant disclosure relief under ASC 606, but "relief" is not "nothing." If you produce GAAP financial statements - for a bank covenant, an audit, or investors - expect to disclose at minimum:

• Disaggregated revenue - revenue split by timing (point-in-time vs over-time) at minimum; many SMBs also split by product line or geography.
• Contract balances - opening and closing deferred revenue (contract liabilities) and contract assets (unbilled receivables), plus revenue recognized this period that was deferred at the start of it.
• Performance obligations - a plain-language description of what you promise, when you typically satisfy it, and significant payment terms.
• Significant judgments - how you determine SSP, how you estimate variable consideration, and why you recognize over time vs at a point in time.

The deferred revenue rollforward is the disclosure that fails first in practice. If your systems cannot produce "deferred revenue opening balance + billings − revenue recognized = closing balance" by month, fix that pipeline before the audit, not during it.

Spreadsheet revenue schedules work at low volume, then fail predictably. The breaking points: more than roughly 50–100 active contracts, any mid-term modifications (a prospective blend in Excel means rebuilding the row and hoping the old version is preserved), co-termed or multi-element deals, usage data that arrives after close, and the moment more than one person edits the workbook. The failure mode is silent - a dragged formula that stops one row short doesn’t error, it just misstates revenue until an auditor ties the schedule to the GL.

This is the point where teams move recognition into a system that stores contracts and obligations as data, generates the monthly waterfall, posts the journal entries, and keeps an audit trail of every modification. That is exactly the revenue layer Fintra provides inside the same platform that runs the rest of the close.