ASC 606 Audit Checklist for SaaS Companies

For a subscription business, ASC 606 audit preparation is not just a technical accounting exercise. It is a test of whether contracts, billing data, revenue schedules, controls, and disclosure support all tell the same story. This ASC 606 audit checklist gives CFOs, controllers, and finance leaders a practical way to prepare evidence before fieldwork begins.

Need audit-ready ASC 606 support? Contact GuzmanGray to discuss revenue recognition, SaaS audit readiness, and PCAOB-quality assurance support.

ASC 606 requires companies to apply a five-step model: identify the contract, identify performance obligations. Determine the transaction price, allocate that price, and recognize revenue when obligations are satisfied. For SaaS and subscription companies, those steps can become complicated because renewals, upgrades, discounts, usage fees, bundled services, and contract modifications all affect the accounting trail.

The goal is not to create a binder of disconnected schedules. The goal is to help an auditor move from signed agreement to revenue recognition conclusion without rebuilding management’s analysis from scratch. Use the checklist below as a preparation framework, then tailor it to your contracts, systems, control environment, and audit timeline.

ASC 606 audit checklist for subscription businesses

An ASC 606 audit checklist should connect the accounting conclusion to the evidence behind it. At minimum, it should cover customer contracts, performance obligations, transaction price, allocation, revenue timing, deferred revenue, systems, controls, disclosures, and management judgments.

For subscription businesses, the checklist should be especially specific about recurring revenue mechanics. A standard product sale may have a single delivery event. While a SaaS arrangement may include hosted access, onboarding, implementation, support, renewals, expansions, credits, usage charges, and termination rights. Each item can affect timing, allocation, or disclosure.

This article is intentionally more tactical than a broad ASC 606 audit guide for SaaS companies. The focus is preparation: what to gather, what to reconcile, what to document, and what to review before auditors ask for support.

What the checklist should prove

A strong checklist proves four things. First, management understands the company’s revenue streams and the contract terms that drive them. Second, the accounting policy is applied consistently across similar arrangements. Third, revenue schedules reconcile to operational systems and the general ledger. Fourth, judgments and estimates are documented well enough for audit review.

That matters even when ASC 606 does not materially change reported revenue. The standard can still require more robust footnote disclosures and clearer support for management estimates. A company that waits until fieldwork to organize this evidence may lose time to avoidable follow-up requests.

GuzmanGray works with high-growth, middle-market, public-company, IPO-ready, and SaaS businesses that need technical credibility without losing responsiveness. That right-sized approach is valuable when accounting teams need senior attention, practical coordination, and audit-ready documentation.

1. Review contracts and performance obligations

Start the ASC 606 audit checklist with the evidence that defines each customer arrangement. Gather signed master service agreements, order forms, amendments, renewal notices, approved pricing terms, and any side letters or nonstandard approvals. The first review should show which documents form one contract and when that contract became enforceable.

Do not rely only on the billing system. Auditors assess how management identifies revenue sources, executes customer contracts, and enters them into financial reporting systems. The ASC 606 five-step process starts with the contract and then identifies its performance obligations.

Contract evidence and scope

Build a contract repository that links every active subscription to its full source record. Each record should include the base agreement, order forms, approvals, renewal terms, and later changes. It should also show the customer, contract term, payment terms, and the date each document took effect.

• Confirm that both parties approved the arrangement and their rights are clear.
• Check whether payment terms and collection expectations are documented.
• Find side letters, email approvals, or sales terms stored outside the main repository.
• Assess whether related order forms or amendments should be reviewed together.

Distinct subscription promises

List every promised good or service before deciding which items are separate performance obligations. Common subscription promises include hosted access, implementation, data migration, training, support, and future updates. Bundled pricing does not prove that all promises are one obligation.

For each promise, document what the customer receives and whether it is distinct from the other items. Explain the role of implementation services and ongoing support. Also flag usage-based fees, optional purchases, and material rights for analysis in later steps. This discipline supports ASC 606 audit readiness and helps reviewers follow the contract history without rebuilding it.

2. Test transaction price, allocation, and recognition

This part of an ASC 606 audit checklist should trace amounts from signed terms through the revenue schedule and general ledger. The final three steps test how much revenue is assigned, when it is earned, and whether later contract events change the result.

Transaction price and variable consideration

Start with a sample that covers standard subscriptions, usage charges, upgrades, discounts, credits, and contract changes. For each item, tie the fixed fee to the contract and recalculate any variable amount using the approved billing data.

Test whether management considered refunds, service credits, rebates, usage, and other terms that can change the transaction price. Then inspect the estimate method, source data, approval, and evidence supporting any limit placed on variable consideration.

• Compare estimates with later invoices, credits, and cash receipts.
• Check that renewal, upgrade, and downgrade terms flow into the right reporting period.
• Trace manual adjustments to an approval and a clear business reason.
• Review unusual discounts or credits for side agreements and changed obligations.

Allocation and recognition timing

Next, recalculate how the transaction price is allocated to each performance obligation. Tie each stand-alone selling price to observable sales, an approved price list, or a documented estimate when direct evidence is not available.

Finally, trace each allocated amount to the revenue schedule and test whether recognition matches delivery of the related obligation. Check the service start date, customer acceptance, usage records, milestones, and any pause or termination terms that affect timing.

Reconcile billed amounts, recognized revenue, contract assets, and deferred revenue to the general ledger. Practical audit checks for revenue recognition can help teams compare the accounting result with common SaaS contract patterns.

What evidence should a SaaS company prepare?

The best evidence package is organized by assertion, not by who produced the file. Auditors should be able to connect contract terms, billing events, revenue calculations, and financial statement balances without searching through unrelated folders.

Keep the package current during the year. If finance waits until audit planning to gather evidence, teams may discover missing approvals, incomplete contract modifications, or revenue schedules that no longer match the source system.

3. Confirm systems, processes, and controls are audit-ready

ASC 606 audit readiness depends on more than the accounting memo. It also depends on whether revenue data flows reliably from sales activity to billing, revenue recognition, and the general ledger. Subscription companies should map that flow before fieldwork starts.

Map the revenue data flow

Document how a contract moves from CRM to order management, billing, revenue subledger, and the general ledger. Identify where manual spreadsheets enter the process and which reports feed the revenue schedule. Spreadsheets can be useful, but they also create risk when formulas, inputs, and changes are not controlled.

For each system, note the owner, key fields, report names, and reconciliation points. Then test whether contract terms in the source documents agree to billing and revenue outputs. This is especially important for companies with multiple billing platforms, recent acquisitions, or fast-changing product packaging.

Review controls before the audit

Controls should address completeness, accuracy, authorization, and review. Examples include contract approval controls, billing review controls, revenue schedule review, manual journal entry approval, and reconciliation of deferred revenue. Keep evidence of who performed the control, what they reviewed, when they reviewed it, and what exceptions were resolved.

Public companies and IPO candidates should also consider PCAOB expectations when building the evidence trail. GuzmanGray’s PCAOB registration and public-company audit experience can help management teams prepare revenue processes for more rigorous review without applying a one-size-fits-all approach.

Mid-audit readiness check: If your team is preparing for financing, an IPO path, or a first financial statement audit, talk with GuzmanGray before fieldwork begins.

4. Document disclosures, judgments, and estimates

ASC 606 often requires management to make and document judgments. Those judgments may relate to performance obligations, stand-alone selling price, variable consideration, contract modifications, timing of recognition, principal versus agent conclusions, or disclosure disaggregation.

Auditors do not only inspect the final answer. They review the process used to reach the answer. A strong memo explains the facts, cites the relevant policy, describes alternatives considered, and shows why management’s conclusion is reasonable.

Judgment memos to prepare

• Performance obligation conclusions for common subscription bundles.
• Stand-alone selling price method and update cadence.
• Variable consideration estimate method and constraint analysis.
• Contract modification treatment for upgrades, downgrades, and renewals.
• Disclosure judgments for revenue categories and contract balances.

These memos should be practical, not academic. Each one should connect directly to the company’s real contracts, data, and control environment. If the business changes pricing or packaging during the year, update the memo before the audit team identifies the change.

Disclosure support

Even when reported revenue does not change significantly, ASC 606 can require more robust disclosures. Prepare support for disaggregated revenue, remaining performance obligations, contract assets, contract liabilities, and significant judgments. Reconcile disclosure schedules to the same source data used for the financial statements.

Audit committees, lenders, investors, and underwriters all value clear revenue support. For high-growth companies, good documentation can also shorten diligence cycles and reduce last-minute technical accounting surprises.

How should you prepare for an ASC 606 audit?

Preparation works best when it starts before auditors send the first request list. The steps below help finance leaders move from scattered support to a focused audit package.

1. Assign ownership. Name one finance owner for contracts, one for systems data, and one for technical accounting conclusions.
2. Inventory revenue streams. List subscription plans, implementation services, support, usage fees, renewals, expansions, and other revenue sources.
3. Build the contract population. Tie active customers to signed agreements, amendments, billing records, and revenue schedules.
4. Reconcile core schedules. Reconcile billed revenue, recognized revenue, deferred revenue, contract assets, and contract liabilities to the general ledger.
5. Prepare technical memos. Document performance obligations, pricing, allocation, recognition timing, modifications, and significant estimates.
6. Test controls and exceptions. Review whether approvals, reconciliations, and manual adjustments were performed and retained.
7. Meet with auditors early. Discuss unusual contracts, new products, pricing changes, and disclosure questions before fieldwork compresses the timeline.

That sequence gives the audit team a complete starting point. It also gives management time to correct documentation gaps before they become audit delays. For SaaS businesses with rapid growth or public-company ambitions, early preparation is usually less disruptive than a rushed clean-up during fieldwork.

Frequently asked questions

What are the 5 steps of ASC 606?

The five steps are identifying the contract with the customer, identifying performance obligations. Determining the transaction price, allocating the transaction price, and recognizing revenue when each obligation is satisfied.

What is included in an ASC 606 audit checklist?

An ASC 606 audit checklist usually includes contracts, performance obligation analysis, pricing support, allocation schedules, revenue recognition schedules, deferred revenue reconciliations, controls, disclosure support, and management judgment memos.

How does ASC 606 apply to SaaS businesses?

ASC 606 applies to SaaS businesses by requiring management to analyze subscription contracts, bundled services. Usage fees, upgrades, renewals, and support obligations before deciding when and how much revenue to recognize.

Why is an ASC 606 checklist important for subscription businesses?

A checklist helps subscription businesses organize evidence before audit fieldwork. It reduces follow-up requests, supports consistent revenue recognition, and helps management explain judgments tied to recurring revenue arrangements.

Ready to strengthen your ASC 606 audit readiness?

GuzmanGray helps subscription, SaaS, middle-market, public-company, and IPO-ready businesses prepare for complex audit and revenue recognition requirements. Our team combines PCAOB-quality technical standards with responsive, right-sized service for finance leaders who need practical support.

Contact GuzmanGray to discuss ASC 606 audit readiness, revenue recognition support, audit and assurance services, or advisory help for your next reporting cycle.