Published July 7, 2026 ยท Updated July 7, 2026
Everything a small business on QuickBooks Online needs to know about applying ASC 606 โ the 5-step model, common contract scenarios and pitfalls, and how CloseFlow's apps automate deferred revenue, recurring JEs, and reconciliations.
ASC 606 โ Revenue from Contracts with Customers โ is the U.S. GAAP standard that governs when and how much revenue every business must recognize. It replaced dozens of industry-specific rules with a single 5-step model that applies whether you sell software subscriptions, professional services, physical products, or bundled solutions.
Small businesses running on QuickBooks Online are just as accountable under ASC 606 as public companies. But QBO on its own doesn't defer revenue, doesn't schedule ratable recognition, and doesn't produce the disclosures the standard requires. That's where the gap โ and the risk โ lives.
ASC 606 is the FASB's revenue recognition standard, effective for private companies for annual periods beginning after December 15, 2018. Its core principle: recognize revenue to depict the transfer of promised goods or services to a customer in an amount that reflects the consideration the entity expects to be entitled to in exchange.
Translation: don't book revenue when cash comes in โ book it when you actually earn it by delivering what the customer paid for.
Small businesses often assume ASC 606 is a public-company problem. It isn't. Any company that reports under U.S. GAAP โ for a bank covenant, an SBA loan, an investor board, an M&A due-diligence request, or a reviewed/audited financial statement โ is bound by it. Getting revenue recognition wrong is the fastest way to fail an audit, break a covenant, or blow up a diligence process during a sale.
The practical stakes for a small business: overstated revenue in one period, understated revenue in the next, a deferred-revenue balance that no one can reconcile, and disclosures the CPA has to write from scratch every year.
QBO is excellent at invoicing, receiving payments, and producing a trial balance. It is not a revenue recognition system. Specifically, QBO does not:
Every QBO team applying ASC 606 does that work outside of QBO โ historically in Excel, and increasingly in purpose-built apps like CloseFlow.
These are the ASC 606 fact patterns that trip up small businesses on QBO most often. Each includes what typically goes wrong and what the standard actually requires.
What often happens: A customer prepays $12,000 for a 12-month SaaS subscription. QBO records the full deposit as revenue when the invoice is paid.
ASC 606 treatment: Under ASC 606, the performance obligation (access to the software) is satisfied ratably over 12 months. Record $12,000 as deferred revenue on receipt and recognize $1,000 per month.
What often happens: You charge a one-time $5,000 setup fee plus $2,000/month. Booking the setup fee immediately overstates revenue in Month 1.
ASC 606 treatment: If the setup has no standalone value to the customer (they can't use it without the subscription), the $5,000 is bundled with the subscription and recognized over the contract term.
What often happens: A 3-year contract escalates 5% annually. Recognizing each year at the invoiced amount misstates revenue.
ASC 606 treatment: Estimate total consideration over the contract term and recognize revenue on a straight-line basis (or by pattern of transfer), with the difference flowing through a contract asset or deferred revenue.
What often happens: A client pays a $10,000 retainer for legal or consulting work. QBO shows it as revenue when deposited.
ASC 606 treatment: The retainer is a customer deposit โ recognize revenue only as hours are worked or milestones are hit. Unused retainer sits as a contract liability.
What often happens: You ship products but customers have a 30-day return window. Recognizing 100% of sales at shipment overstates net revenue.
ASC 606 treatment: Estimate expected returns using historical data, reduce revenue and record a refund liability and return-asset for goods expected to come back.
What often happens: A $60,000 fixed-fee project bills 50% up front and 50% at completion. Recognizing on the invoice date front-loads or back-loads revenue.
ASC 606 treatment: If the customer controls the work as it's performed, recognize over time by input (hours, cost-to-cost) or output (milestones completed). Otherwise recognize at a point in time when control transfers.
What often happens: You sell a device with 12 months of firmware updates and support for a single price.
ASC 606 treatment: Identify each distinct performance obligation, allocate the transaction price based on standalone selling prices, and recognize each obligation as it is satisfied.
What often happens: Volume rebates, usage-based pricing, or performance bonuses distort billed vs. earned revenue.
ASC 606 treatment: Estimate variable consideration using either expected value or most-likely amount and constrain the estimate so a significant reversal is not probable.
ASC 606 requires qualitative and quantitative disclosures even for private companies (though the private-company disclosure set is lighter than public). Expect to disclose:
CloseFlow doesn't replace QBO โ it fills the ASC 606 gap around it. Purpose-built apps that a small business can turn on in an afternoon:
Related apps and guides:
Yes. ASC 606 applies to any entity that reports under U.S. GAAP and enters into contracts with customers โ regardless of size or accounting system. Small businesses with reviewed or audited financials, bank covenants, investor reporting, or M&A prospects need to comply.
No. QBO recognizes revenue when an invoice is created or a sales receipt is entered. It does not natively defer revenue, schedule ratable recognition, track performance obligations, or produce a deferred revenue rollforward. Those calculations happen outside QBO โ usually in spreadsheets or in a dedicated app.
Treating annual prepaid subscriptions and retainers as revenue on receipt. This overstates revenue in the collection month and understates it in every future month of the contract. The fix is a deferred revenue schedule with a recurring monthly recognition journal entry.
CloseFlow's Recurring Journal Entries app posts monthly revenue recognition JEs from a schedule you define once. The Balance Sheet Reconciliation app ties deferred revenue on the GL to the underlying contract schedule every month. The Approval Workflows app routes new-contract revenue treatment for controller review. Together they give you an ASC 606 process without leaving QBO as your system of record.
Most small businesses don't need a dedicated rev-rec platform. What they need is (1) a contract-level schedule of performance obligations and expected recognition, (2) a monthly recurring JE to move deferred revenue into recognized revenue, and (3) a monthly reconciliation of the deferred revenue GL account to the underlying schedule. CloseFlow provides all three.
Automate deferred revenue journal entries, reconcile deferred revenue every month, and route new-contract revenue treatment for review โ all on top of your existing QBO.