Achieving ASC 606 Compliance for Your SaaS Company

ASC 606 Compliance for SaaS Companies.

Most SaaS founders find out their revenue recognition is wrong during a Series A audit. We fix it before the auditor arrives, and we keep it right every month after.

Cleanup completes in 4 to 8 weeks · Flat-fee pricing · Audit-defensible documentation

Automated revenue forecast and projected balance for SaaS companies, illustrating ASC 606 compliance.
Laptop screen displaying ASC 606 revenue recognition guide and download button, illustrating SaaS compliance solutions.

Your Last Accountant Probably Got ASC 606 Wrong.

ASC 606 is the GAAP standard for revenue recognition. For SaaS companies, it’s also the most common reason books fail audit.

The errors are predictable. Annual contracts billed upfront and recognized as revenue when invoiced, not when earned. Multi-year deals with no deferred revenue schedule. Setup fees and professional services bundled with subscription revenue and recognized incorrectly. Discounts applied to total contract value instead of allocated across performance obligations.

We’ve cleaned up books with $2M, $5M, and $12M ARR where the deferred revenue balance was off by six figures. The fix is straightforward. Catching it before diligence is the part most founders miss.

What ASC 606 Actually, Requires for SaaS.

ASC 606 has five steps. For SaaS, the work concentrates in steps three and five.

Identify the Contract

Every signed customer agreement, master service agreement, and order form. We pull contracts directly from your CLM or billing system.

Identify Performance Obligations

Subscription access, implementation, training, and professional services are usually separate performance obligations. Bundled deals require allocation.

Determine the Transaction Price

Discounts, credits, ramps, and variable consideration all affect transaction price. This is where most errors start.

Allocate the Transaction Price

Each performance obligation gets a share of the total based on standalone selling price. SaaS subscriptions usually recognize ratably. Implementation and training usually recognize at a point in time or over the implementation period.

Recognize Revenue When Performed

Subscription revenue recognizes monthly over the contract term. Setup fees recognize when delivered. Usage-based revenue recognizes when consumed. Each gets its own schedule.

What We Do

What we Actually Do.

We handle the operating accounting between funding rounds. The work that has to be done every month, whether or not you’re raising.

Contract-level review

Every active customer contract gets a deferred revenue schedule. Multi-year deals, ramps, discounts, and credits handled per ASC 606.

ASC 606 revenue recognition: deferred revenue waterfall schedule and transaction history for SaaS companies.

Deferred revenue waterfall

A schedule that shows when each customer’s prepaid balance recognizes as revenue. This is what your auditor and your VC will ask for.

ASC 606 revenue recognition process diagram illustrating deferred revenue waterfall and audit-defensible documentation.

ARR-to-revenue bridge

A reconciliation that shows the difference between annualized run-rate and GAAP revenue. Without this, your investor metrics don’t tie to your financials.

ASC 606 revenue recognition process illustration and deferred revenue waterfall schedule.

Restatement of prior periods

If past revenue was recognized incorrectly, we restate. We document the change with the disclosures auditors require.

Deferred revenue waterfall schedule illustrating ASC 606 compliance and revenue recognition for SaaS contracts.

Process setup for ongoing recognition

Monthly close procedures, billing system integration, and revenue schedules that maintain themselves. So this never breaks again.

Deferred revenue waterfall schedule and ASC 606 compliance documentation for SaaS companies.

What You Get

What You Actually, When the Cleanup is Done

When you sign on, the deliverables are specific and the timing is fixed.

Audit-defensible documentation:

Updated books:

Process documentation:

Handoff package:

Who Needs This.

You probably need ASC 606 cleanup if any of these are true:

Finance professional reviewing ASC 606 data on dual monitors for SaaS compliance.

How We're Different.

We handle the operating accounting between funding rounds. The work that has to be done every month, whether or not you’re raising.

Fortress Accounting tracks the metrics that truly matter for your business:

Award icon representing financial accuracy and compliance for SaaS bookkeeping.

Cleanup specialists, not just bookkeepers

This is the work most accounting firms send to consultants at $400 an hour. We do it in-house, flat fee.

Bitcoin logo illustrating crypto accounting services

Built for SaaS, not retrofit from retail

We don't apply ASC 606 like a checklist. SaaS contracts have specific quirks (ramps, discounts, multi-product bundles, usage overages) and we handle them correctly the first time.

Dedicated senior accountants and consistent support for SaaS bookkeeping.

Audit-defensible documentation

Every revenue recognition policy decision is documented. When the auditor asks why setup fees recognize over 12 months instead of at delivery, the answer is in the file.

Calendar icon representing monthly accounting and financial reporting for SaaS businesses.

Direct audit firm relationships

When your auditor has questions about our policy decisions, they call us directly. We work with RSM, Citrin Cooperman, Wolf & Company, and BPM regularly.

Our Team Members

Who You'll, Work With.

ASC 606 cleanup is led by a senior accountant with revenue recognition specialization. Most engagements are staffed with a senior lead, a staff accountant for transaction-level work, and a CPA reviewer who signs off on the final policy and restatement.

We’ll introduce you to your specific team during the audit call.

Three Steps

The Three-Step Cleanup.

Audit Call

We review your current revenue policy, contract structure, and books. We tell you what’s broken in the first 30 minutes.

Flat-free Quote

Based on contract count and complexity. No hourly surprises.

Cleanup and ongoing close

4 to 8 weeks for most SaaS companies. Monthly close after that.

Common Questions

Common Questions, Before You Commit

How do I know if my revenue is actually wrong?

The fastest test: try to produce a deferred revenue waterfall. If you can’t, your revenue is probably wrong. Second test: does your ARR reconcile to your revenue through a documented bridge? If no, same problem. We’ll do this check on the audit call, no charge.

Some firms tell early-stage founders ASC 606 is optional until audit. It’s not — it’s the GAAP standard, full stop. What’s true is that pre-seed founders sometimes get away with simpler accounting because no one has audited yet. The day you raise institutional capital, ASC 606 becomes non-negotiable. Catching it earlier is always cheaper.

Generally no. ASC 606 governs financial reporting, not tax. Most SaaS companies use cash-basis or modified cash-basis for tax purposes regardless of how their books are kept for GAAP. We coordinate with your tax preparer (or handle taxes ourselves) to make sure restatement doesn’t create unintended tax consequences.

We document every policy decision with the reasoning, the relevant ASC 606 paragraph, and the alternative considered. When auditors challenge a position, we have the answer ready. In practice, the firms we work with regularly approve our policy positions because they’ve seen the documentation before.

Minimal. We handle the work. Your team’s involvement is roughly five to ten hours over the four-to-eight week period: an initial kickoff call, access provisioning to your billing system and books, and one or two follow-up calls if we need clarification on contract terms. We don’t pull your finance team off their actual work.

Most Common Questions

Frequently Asked Questions

What is ASC 606 and why does it matter for SaaS?

ASC 606 is the GAAP standard for revenue recognition. For SaaS companies, it requires recognizing subscription revenue ratably over the contract term, not when invoiced. It matters because auditors and institutional investors require ASC 606 compliance before signing off on financials.

Subscription revenue recognizes ratably over the contract term, typically monthly. Setup fees and professional services are usually separate performance obligations and recognize when delivered or over the implementation period. Usage-based revenue recognizes when consumed. Discounts allocate across performance obligations based on standalone selling price.

A deferred revenue waterfall is a schedule that shows when each customer’s prepaid balance will recognize as revenue over time. It’s the standard auditor and VC request for SaaS companies. If you bill annually and recognize monthly, you need one. Without it, your revenue numbers can’t be verified.

Common signs include ARR that doesn’t reconcile to revenue, no deferred revenue balance on the balance sheet despite annual billing, all revenue recognized when invoiced rather than when earned, and discounts or credits hitting MRR but not the GL. Any one of these is a red flag.

Most billing systems (Stripe, Chargebee, Recurly) calculate billing accurately but don’t enforce ASC 606 revenue recognition correctly across performance obligations. They’re a data source, not a revenue recognition system. Your books need to apply ASC 606 on top of the billing data.

Most SaaS cleanups take 4 to 8 weeks. Companies with multi-year contracts, multiple billing systems, or international entities take longer. We quote a fixed timeline after the audit call.

Yes, if you plan to raise institutional capital or get audited later. Switching from cash-basis or simplified accrual to ASC 606 mid-stream is painful and often requires restating prior periods. Get it right early.

Cleanup is quoted as a flat fee based on contract count and complexity. For most SaaS companies between $1M and $20M ARR, cleanup is a defined project rather than an hourly engagement. After cleanup, ongoing bookkeeping with ASC 606 maintained correctly starts at $3,500/month for Series A through Series B companies. Full pricing on our pricing page.

Still have questions? Contact us.

Fix it Before Your Audtior Finds It.

The cost of waiting is concrete. Founders who wait until diligence to fix ASC 606 issues typically lose 4 to 8 weeks of deal momentum, $40K to $120K in emergency cleanup fees, and meaningful leverage in the term sheet conversation.

The fix is boring, which is why it works.

Cleanup in 4 to 8 weeks · Flat-fee pricing · Audit-defensible documentation · Direct relationships with RSM, Citrin Cooperman, Wolf & Company, and BPM