First-Audit Revenue Readiness Assessment
First-Audit Revenue Readiness Assessment
A diagnostic self-assessment for private B2B SaaS controllers, finance directors, and accounting managers preparing for their initial financial statement audit.
:::tip Planning Tool Disclaimer
This assessment is an educational diagnostic and internal planning tool. It is not an audit opinion, assurance service, or certification of ASC 606 compliance. Results should be evaluated in the context of your company's specific contract terms, materiality thresholds, accounting policies, and professional judgment.
:::
Who Should Use This Tool
This diagnostic is structured specifically for private B2B SaaS and subscription companies that:
- Are approaching their first independent financial statement audit.
- Have transitioned or are formalizing compliance under ASC 606 (Revenue from Contracts with Customers).
- Need to benchmark the completeness of their revenue schedules, contract modifications, technical accounting memos, and management review controls.
How to Score
For each question below, assign points based on your current operating state:
| Response | Points | Criteria |
|---|---|---|
| Yes | 2 | Fully implemented, documented, and consistently executed with retained evidence. |
| Partly / Inconsistent | 1 | Performed in practice but lacks formal documentation, consistent cadence, or retained audit trail. |
| No / Not Documented | 0 | Not currently performed, undocumented, or relies entirely on informal memory. |
Total Possible Points: 50 points across 25 evaluation criteria.
Assessment Sections
1. Contract and Change Management (10 Points)
| # | Diagnostic Question | Yes (2) | Partial (1) | No (0) |
|---|---|---|---|---|
| 1.1 | Is there a single, complete population log of all executed customer contracts, order forms, statements of work (SOWs), and amendments for the audit period? | [ ] | [ ] | [ ] |
| 1.2 | Does finance have a formal hand-off process with Sales / Deal Desk to capture nonstandard terms, side agreements, cancellation rights, or oral commitments? | [ ] | [ ] | [ ] |
| 1.3 | Are contract modifications (e.g., upsells, early renewals, price concessions, down-tiers) formally logged and evaluated as separate contracts vs. prospective vs. cumulative catch-up modifications under ASC 606-10-25-12? | [ ] | [ ] | [ ] |
| 1.4 | Are related contracts entered into at or near the same time with the same customer evaluated for contract combination under ASC 606-10-25-9? | [ ] | [ ] | [ ] |
| 1.5 | Is collectibility assessed and documented at contract inception for nonstandard or higher-risk counterparties under ASC 606-10-25-1(e)? | [ ] | [ ] | [ ] |
2. ASC 606 Judgments and Documentation (10 Points)
| # | Diagnostic Question | Yes (2) | Partial (1) | No (0) |
|---|---|---|---|---|
| 2.1 | Has the company documented a formal technical revenue accounting policy memo defining distinct performance obligations for subscription licenses, onboarding, support, and professional services? | [ ] | [ ] | [ ] |
| 2.2 | Is there documented methodology and evidence supporting Standalone Selling Prices (SSP) for bundled deliverables, including historical discounting analysis or residual approaches where applicable? | [ ] | [ ] | [ ] |
| 2.3 | Are variable considerations (e.g., usage caps, SLA penalties, usage-based overages, volume rebates, right-of-return provisions) identified and evaluated for the constraint under ASC 606-10-32-11? | [ ] | [ ] | [ ] |
| 2.4 | Are material rights (e.g., discounted future renewal options, free extension periods) evaluated to determine if they constitute separate performance obligations? | [ ] | [ ] | [ ] |
| 2.5 | Are contract fulfillment costs and incremental costs of obtaining contracts (e.g., sales commissions amortized under ASC 340-40) documented with clear amortization schedules and impairment assessments? | [ ] | [ ] | [ ] |
3. Billing, Usage, and Source-Data Completeness (10 Points)
| # | Diagnostic Question | Yes (2) | Partial (1) | No (0) |
|---|---|---|---|---|
| 3.1 | Are billing exports, CRM contract records, and subledger revenue inputs reconciled monthly for population completeness before revenue recognition runs? | [ ] | [ ] | [ ] |
| 3.2 | For usage-based or consumption revenue models, is raw telemetry data frozen, validated for cut-off, and reconciled to billing files without manual spreadsheet manipulation? | [ ] | [ ] | [ ] |
| 3.3 | Are credit memos, refunds, and invoice cancellations tracked in a dedicated log with clear classification between billing corrections and revenue price concessions? | [ ] | [ ] | [ ] |
| 3.4 | Is there a documented month-end cut-off control ensuring invoices and contracts executed near period-end are assigned to the correct accounting period? | [ ] | [ ] | [ ] |
| 3.5 | Are cash collections and unapplied receipts reconciled to open accounts receivable at each month-end? | [ ] | [ ] | [ ] |
4. Revenue Schedules and Reconciliations (10 Points)
| # | Diagnostic Question | Yes (2) | Partial (1) | No (0) |
|---|---|---|---|---|
| 4.1 | Is recognized revenue generated from an automated subledger or systematic schedule that applies daily or monthly ratable recognition rules consistently? | [ ] | [ ] | [ ] |
| 4.2 | Is a monthly revenue-to-general-ledger tie-out performed, documenting that subledger revenue equals the trial balance without unexplained manual journal entries? | [ ] | [ ] | [ ] |
| 4.3 | Is a formal deferred revenue (contract liability) rollforward maintained monthly: Beginning Balance + Billings - Revenue Recognized ± Adjustments = Ending Balance? | [ ] | [ ] | [ ] |
| 4.4 | Are contract assets (unbilled receivables) distinguished from trade receivables and reconciled monthly with documented recovery milestones? | [ ] | [ ] | [ ] |
| 4.5 | Are manual revenue adjustments, true-ups, and journal entries supported by detailed workpapers and independent management approval? | [ ] | [ ] | [ ] |
5. Management Review and Audit Evidence Retention (10 Points)
| # | Diagnostic Question | Yes (2) | Partial (1) | No (0) |
|---|---|---|---|---|
| 5.1 | Does the Controller or Chief Accounting Officer perform a documented, dated review of the monthly revenue close binder and exception logs before books close? | [ ] | [ ] | [ ] |
| 5.2 | Are all close reconciliations and workpapers locked and archived in a structured, immutable repository that external auditors can independently inspect? | [ ] | [ ] | [ ] |
| 5.3 | Is there a formal threshold-based escalation trigger protocol for nonstandard deals, scope changes, or contract disputes? | [ ] | [ ] | [ ] |
| 5.4 | Can the finance team produce sample audit packages (executed agreement, invoice, usage support, revenue schedule, bank statement, review sign-off) within 24 hours of an auditor request? | [ ] | [ ] | [ ] |
| 5.5 | Are ASC 606 financial statement footnote disclosure workpapers (e.g., remaining performance obligations / RPO, disaggregation of revenue, contract balance rollforwards) maintained on a recurring basis? | [ ] | [ ] | [ ] |
Scoring & Readiness Ranges
Calculate your total score (sum of all 25 criteria, max 50 points):
0 – 20 PointsFoundation Needed
High risk of audit adjustments, scope expansion, and PBC delays.
21 – 35 PointsControls in Progress
Operational mechanics exist; formalize documentation and review sign-offs.
36 – 45 PointsAudit-Ready Baseline
Strong foundation. Validate edge-case technical memos and evidence organization.
46 – 50 PointsExceptional Operating State
Audit-ready posture. Focus on disclosure workpapers and auditor walkthroughs.
Understanding Your Score Range
🔴 Score 0–20: Foundation Needed
- Primary Risks: Revenue numbers may tie in spreadsheets, but lack of population completeness controls, modification tracking, or formal technical memos will likely trigger audit findings or adjustments.
- Immediate Priority: Establish a frozen contract log, draft a core revenue accounting policy memo, and implement a monthly deferred revenue rollforward.
🟡 Score 21–35: Core Controls in Progress
- Primary Risks: Controls are informally executed by key individuals but lack contemporaneous documentation. Auditors cannot rely on controls that lack physical or digital review evidence.
- Immediate Priority: Implement the Month-End Revenue Close Checklist, enforce reviewer sign-offs on all schedules, and formalize contract modification logs.
🟢 Score 36–45: Audit-Readiness Foundation in Place
- Primary Risks: Mainstream subscription revenue is controlled; vulnerability lies in nonstandard edge cases (custom SOWs, concessions, early renewals, commission capitalization).
- Immediate Priority: Review nonstandard contracts with technical accounting memos and organize evidence into a standardized 6-folder audit binder.
🔵 Score 46–50: Strong Operating Baseline
- Primary Risks: Overconfidence on disclosures or late auditor sample requests causing administrative friction.
- Immediate Priority: Prepare draft ASC 606 footnote disclosures (RPO, disaggregated revenue) and conduct a mock auditor walkthrough on 10 random contracts.
What to Do Next
- Implement the Revenue Close Controls: Use our step-by-step Month-End Revenue Close Checklist to institutionalize preventive and detective controls during each close.
- Standardize Evidence Retention: Set up the 6-folder audit-ready evidence binder outlined in the close playbook.
- Review Technical Guides: Review the ASC 606 5-Step Framework and SaaS Revenue Topics for specific accounting considerations.
- Consult Qualified Advisors: Review significant technical accounting conclusions with your external advisors or audit committee prior to audit fieldwork.