Preparing for an ASC 606 Audit

$4B in ARR, A revenue accounting team of three, A clean Big 4 audit opinion. Most finance leaders would tell you to pick two. Cursor took all three. Their self-serve revenue runs entirely through Stripe. Monthly, annual, usage-based... millions of transactions a month. At that volume, summary-level exports stop working. For ASC 606. For audit support. For close. They seriously evaluated building internally. But every engineering hour spent on Stripe API complexity was an hour not spent on product. They considered AI... and this is a team that uses AI everywhere. Their conclusion: rev rec needs deterministic, auditable logic. A wrong answer here hits the financial statements. Will Smerdon, CA, who leads revenue accounting and order-to-cash at Cursor: "HubiFi provides the deterministic layer on top of the Stripe data that enables us to investigate and resolve issues, reconcile and close the books quickly." In practice: a two-day self-serve close. Three-way reconciliation across Stripe, HubiFi, and NetSuite... automated. A CY24 restatement done in under two months. Over $1M in free trial abuse caught and recovered along the way. And when the Big 4 auditors showed up, the revenue reporting was ready on day one. Not rebuilt for them. Already there. That's the difference between preparing for an audit and being prepared. Full case study in the comments.

Some Accountants mess this up badly Flux (Fluctuation) analysis is a reliable tool to identify Accounting issues Here is a quick scenario Setup: We start with a financial review revealing an unusual revenue increase due to a $6 million invoice issued in June 2024. This invoice pertains to a customer agreement covering three years (January 2024 to December 2026) for a total of $36 million. Clueless Accountant's Approach: ❌The Clueless Accountant simply issues the invoice and records the entire revenue for June without proper consideration. This approach has its pitfalls: ❌Failing to Perform Flux Analysis:  This accountant neglects to analyze revenue fluctuations effectively. ❌Missing Accruals:  Revenue for the months leading up to the invoice is not accrued. Good Accountant's Approach: In contrast,  the Good Accountant takes a meticulous approach. Here’s what they do: ✅Conducts Flux Analysis:  Identifies the revenue spike and reviews the revenue recognition process. ✅Applies ASC 606:  Utilizes the five-step model for revenue recognition: 1. Identify the contract with the customer. 2. Identify performance obligations in the contract. 3. Determine the transaction price. 4. Allocate the transaction price to the performance obligations. 5. Recognize revenue when the performance obligation is satisfied. ✅Confirmation: 👤The Good Accountant verifies with the service delivery team that the service was delivered evenly over the first five months, concluding that $1 million should be accrued for each month. ✅Journal Entries 👤The Good Accountant also makes appropriate journal entries for revenue recognition, ensuring that the financial statements accurately reflect the revenue generated during each month leading up to the invoice.

💡 SaaS Finance Leaders: ASC 606 Is Not Optional—Here’s What You Need to Know If you're in SaaS finance—CFO, controller, FP&A, or accounting—you can’t ignore ASC 606. In a recent No Fluff webinar, I sat down with revenue recognition expert Jill Hauck to demystify ASC 606 through the lens of real-world SaaS scenarios: subscriptions, usage, services, and hardware. This training was a goldmine to help you refine your rev rec policies. 🔍 Key Takeaways: - Subscription Revenue: Daily rev rec is audit-friendly, but smoothed recognition can work—just be ready to defend it. - Usage-Based Models: Predictability determines whether you accrue or defer. Overages? Track separately or your retention math suffers. - Professional Services: Time & materials vs. milestone-based vs. spreading over term—it depends on how intertwined services are with SaaS. - Hardware: Sale, lease, or bundled? Each impacts timing and GAAP treatment. - SSP & Discounting: Your rev rec allocation is only as good as your SSP logic. Inconsistent discounting? That’s a red flag. - Gross vs. Net: Are you the principal or just the agent? Misclassify this, and your margins take a hit. - Contract Start Dates: "Go live" vs. "contract execution"—choose a policy and enforce it consistently. 📊 Revenue recognition is not a "set it and forget it" task. It's a blend of finance, legal, and ops—and it shapes everything from Board decks to due diligence (lots of failed DD due to this). Pricing models change. Business models change. Finance leaders must continually assess their revenue streams. 👉 Learn more at the link in the comments. Want the slides? Just comment "slides" below. #SaaS

Revenue Recognition Across the Globe: IFRS 15 | ASC 606 | Ind AS 115 – Practical Insights by Industry We now follow a common 5-step framework, but the real challenge lies in how each sector applies it practically. Here's how as per my understanding 👇 🚗 Automobile What’s happening? Sale of car, warranty, free services = multiple performance obligations. Revenue split: Car = point-in-time | Service/Warranty = over time. Region tip: Under Ind AS 115 and IFRS 15, treatment is largely aligned, but discounting of financing elements may differ slightly in practice due to interest rate assumptions. 🏦 Banking & Financial Services Fee-based income: Loan processing, advisory, AMC, etc. Recognition: Origination fees = over time. Transaction/advisory fees = when service delivered. Ind AS/IFRS follow similar guidance, but ASC 606 has slightly more prescriptive rules for non-interest income. 🛒 FMCG Revenue recognized when goods are delivered to distributor/customer. Watch for: promotional schemes, trade discounts, returns — all treated as variable consideration. No major differences across the three frameworks, but estimation technique and significant financing component test may differ slightly in India. 💻 Software / SaaS SaaS model: Revenue over time. Licensing: Perpetual = point in time Subscription = over time India-specific note: Under Ind AS 115, customization services bundled with licenses often need more judgment to unbundle. 🏗️ Construction / EPC Projects Revenue based on performance obligation over time — typically % completion. Claims, variations, liquidated damages = part of variable consideration. Under all 3 standards, method is aligned, but cost capitalisation and interest income treatment could vary slightly in India. 📱 Telecom Bundled contracts (device + plan): Split revenue across obligations. Device = point in time, Plan = over time. Under ASC 606, contract asset is explicitly recorded; Ind AS and IFRS are similar but local practice may influence timing of asset recognition. 🏥 Healthcare Revenue recognized when services rendered or performance obligation is complete. Insurance and government schemes introduce variable consideration. India: Many hospitals applying Ind AS 115 need to estimate expected payments, factoring delays and non-recoveries common in the public sector. 🛍️ Retail / E-commerce Revenue = when control passes (delivery/pickup). Returns, loyalty points, gift cards = deferred revenue or reduction in transaction price. All 3 frameworks are aligned here. IFRS 15 = ASC 606 = Ind AS 115? Yes — conceptually, they’re nearly identical, but in practice quite different 💬 How does your team approach revenue recognition? Drop your insights or examples below #IFRS15 #ASC606 #IndAS115 #RevenueRecognition #Finance #Accounting #Automobile #FMCG #Banking #Telecom #SaaS #Construction #Healthcare #Retail #FinanceTransformation #FinancialReporting #USGAAP #IFRS #IndiaGAAP

Revenue recognition errors show up in roughly 40 percent of quality of earnings reviews. The resulting valuation adjustments routinely hit 10 to 15 percent of enterprise value. By the time the buyer's diligence team is asking questions, the damage is already baked into your financials. Most SaaS founders between $1M and $30M ARR do not think about ASC 606 until it is too late. The standard itself is straightforward. Five steps. Identify the contract. Identify the performance obligations. Determine the transaction price. Allocate the price across obligations. Recognize revenue as each obligation is met. For a clean single product subscription, this is easy. Recognize ratably over the term. But SaaS contracts are rarely clean. You bundle implementation, training, premium support, and usage based overages into one agreement. Each may be a separate performance obligation with a different revenue recognition timeline. The standard requires you to separate them individually. Common mistakes. Recognizing all contract value as subscription revenue on day one. Treating setup fees as immediate revenue instead of deferring. Not separating professional services from the SaaS contract. The fix is not a spreadsheet tweak the month before you go to market. Get your accountant to audit revenue recognition 12 months before a potential exit. Fix the methodology. Restate if needed. Revenue recognition is not an accounting preference. It is a valuation input.