We are replacing our yearly financial audit firm with one that specializes in SaaS revenue recognition.

Moving to an audit firm that truly speaks "SaaS" and understands the nuances of ASC 606 / IFRS 15 (deferred revenue, contract acquisition costs under Subtopic 340-40, multi-element arrangements, and usage-based pricing) is a massive operational upgrade. Traditional auditors often get bogged down manual-testing standard subscription cohorts or misinterpreting technical provisioning milestones.

Switching over smoothly requires a deliberate transition plan:

• Predecessor Auditor Communication: Formally notify your current firm and request a seamless professional clearance/successor-predecessor communication. Ensure they transfer your permanent file, historical workpapers, and tax schedules cleanly.
• Tech Stack Alignment: Give your new specialized audit team early access to your billing and revenue sub-ledger environment (whether you use Maxio, Sage Intacct, NetSuite ARM, or Stripe Billing) so they can test your automated recognition rules before year-end.
• Opening Balances & Historical Review: Expect the new firm to perform a deeper initial dive into historical contract modifications, unamortized commission assets, and deferred revenue balances to ensure Day-1 alignment with their methodology.

If you'd like, let me know:

• What stage your SaaS company is at (seed/ARR scale, scaling toward Series C/D, or pre-IPO)?
• Whether you are transitioning to a national/mid-tier firm (like BPM, Armanino, or Marcum) or a boutique tech-focused firm?

I can share a tailored onboarding checklist or specific ASC 606 documentation your new auditors will likely request first.

If you’re replacing the annual audit firm, I’d evaluate candidates specifically on whether they have demonstrated SaaS/ASC 606 audit experience—not merely whether they market themselves as “technology-focused.” SaaS revenue can involve performance obligations, SSP allocation, contract modifications, usage-based fees, and deferred revenue, all of which can create significant audit judgment.

What I’d put in the selection criteria

• SaaS audit track record: Ask for the number and size of SaaS clients they currently audit and examples of similar revenue models.
• ASC 606 depth: They should be comfortable with multi-year subscriptions, implementation/onboarding fees, usage-based pricing, discounts, renewals, upgrades/downgrades, and bundled services.
• Revenue-recognition methodology: Ask how they evaluate performance obligations and standalone selling prices rather than simply testing your existing conclusion.
• Audit readiness: A good firm should be able to trace contracts → billing → deferred revenue → revenue recognition → GL and explain what documentation they expect.
• Systems expertise: Make sure they understand your billing/rev-rec stack (e.g., Stripe, Chargebee, Zuora, NetSuite, Sage Intacct, etc.).
• Technical accounting support: Determine whether ASC 606 questions are handled by the engagement team or require a separate technical-accounting engagement.
• First-year transition: Ask exactly what they will request from the incumbent auditor and how they will handle opening balances and prior-year audit work.
• Partner involvement: For a specialized audit, I’d want the actual engagement partner—not just a sales specialist—to have substantial SaaS experience.

Firms worth putting on the initial RFP list

Depending on your size and audit requirements, I'd investigate a mix of large firms and SaaS-focused specialists. Current market materials show firms such as KPMG, RSM, BDO and Baker Tilly offering substantial software/SaaS expertise, while smaller specialists can offer much more concentrated ASC 606 experience.

One useful benchmark is KPMG: its current software/SaaS revenue handbook specifically addresses ASC 606 issues including performance obligations, transaction-price allocation, contract modifications and contract costs.

I'd also look at specialist firms such as Corviniti, whose current practice is explicitly centered on software/SaaS revenue recognition and ASC 606, including technical-accounting and audit documentation.

If you tell me your approximate ARR, number of customers/contracts, billing model (monthly/annual/usage-based), accounting system, and whether you're private or preparing for an IPO, I can narrow this to 5–7 audit firms that are genuinely appropriate for your situation and compare them on SaaS expertise, likely fit, and expected audit complexity.

Switching to an audit firm that speaks the language of subscription metrics, multi-element arrangements, and deferred revenue is a massive win for a SaaS company. It saves you from spending half the audit explaining how ASC 606 applies to your annual billing with co-term add-ons.

Here is how you can set yourself up for a smooth transition and get the most out of your new specialized auditors:

• Audit Readiness Assessment: Request a pre-audit kick-off meeting to align on your specific technical accounting positions (e.g., standalone selling price determinations, contract modifications).
• Historical Review: Expect a deeper dive into your historical revenue schedules during year one as they establish their baseline workpapers and testing methodologies.
• Integration Check: Ensure your billing, CRM, and ERP systems (like Stripe, Salesforce, and NetSuite) are tightly integrated so revenue subledgers reconcile seamlessly for the audit team.
• Policy Documentation: Refresh your formal revenue recognition accounting policies to explicitly reflect your subscription tiers, usage-based billing components, and professional services bundling.
• Timeline Alignment: Build in extra wiggle room for the initial audit cycle, as a new specialized firm will likely have a more rigorous information request list (PBC list) tailored to software metrics like ARR, CAC, and net revenue retention.

Would you like me to help you draft a pre-audit data request checklist or outline the key ASC 606 revenue areas your new firm will likely scrutinize first?

That makes sense. For a SaaS company, I’d treat ASC 606 expertise as a primary auditor-selection criterion, rather than simply choosing a generalist audit firm that happens to have technology clients. SaaS arrangements can create significant judgments around performance obligations, standalone selling prices, variable consideration, contract modifications, and contract costs.

A reasonable shortlist to investigate would include:

• Corviniti — highly specialized in software/SaaS revenue recognition and ASC 606, with a stated focus on technical accounting and PCAOB audit experience.
• Armanino — strong fit for growth-stage technology companies, particularly if you want audit plus technical-accounting/advisory capabilities.
• RSM — worth considering if you're moving toward a more substantial mid-market audit environment.
• BDO — another good mid-market option with significant technical-accounting resources.
• Baker Tilly — potentially attractive if you want SaaS specialization combined with broader private-company advisory services.
• Deloitte or KPMG — better suited if you're larger, preparing for an IPO, or have unusually complex revenue arrangements. KPMG, for example, maintains a dedicated software/SaaS ASC 606 handbook.

What I'd put in the RFP

Don't just ask prospective firms how many SaaS companies they audit. Ask them to demonstrate how they would handle your actual revenue model:

1. How many SaaS audits under ASC 606 have they performed in the last 2–3 years?
2. Have they audited contracts containing subscription + implementation/professional services?
3. What is their experience with usage-based/consumption pricing?
4. How do they evaluate and document standalone selling prices (SSP)?
5. How do they audit contract modifications, upgrades, downgrades, renewals, and cancellations?
6. How do they test the deferred-revenue rollforward from contracts through the subledger and GL?
7. What revenue-recognition systems have they audited—e.g., NetSuite ARM, Zuora, Stripe integrations, Chargebee, Maxio?
8. Who specifically will be the engagement partner and senior manager, and how much SaaS experience do they personally have?
9. Will they perform a pre-year-end ASC 606 technical review so there aren't surprises during the audit?
10. What will the first-year audit timeline and fee look like, given the additional onboarding work involved in changing auditors?

One thing I'd emphasize: the best firm isn't necessarily the one with the most sophisticated technical accounting group. You want a firm that understands SaaS deeply and has a repeatable audit process. A technically brilliant auditor who turns your annual audit into a six-week forensic exercise may be worse operationally than a firm that knows your revenue model cold.

If you give me your approximate annual revenue, private/public status, number of customers, billing model (monthly/annual/usage), whether you bundle implementation or services, and accounting system, I can narrow this down to a 3–5 firm shortlist and a side-by-side evaluation matrix.

Transitioning to a specialized SaaS revenue recognition audit firm is a major milestone. Because standard audits often miss the nuances of ASC 606 multi-element arrangements, usage-based billing, and deferred revenue schedules, shifting to domain experts will streamline your year-end process significantly.

Here is a structured checklist to ensure a seamless transition:

• Pre-Transition & Notification:
  • Formal notification: Send a formal written notice of termination/non-renewal to your outgoing audit firm, adhering to any notice period specified in your engagement letter.
  • Successor communication: Authorize your new firm to communicate directly with your predecessor regarding any prior audit findings, workpapers, or unresolved accounting positions (as required by professional standards).
  • Timeline alignment: Establish a revised year-end audit timeline with the new team, factoring in their initial onboarding and risk-assessment phases.
• Data & Documentation Handover:
  • Access provisioning: Set up secure access for the new auditors to your financial systems (e.g., QuickBooks, NetSuite, Sage), billing systems (e.g., Stripe, Chargebee, Maxio), and CRM (e.g., Salesforce, HubSpot).
  • Contract repository: Organize a centralized, easily accessible repository of your top customer contracts, particularly those with non-standard terms, side letters, or multi-year commitments.
  • Revenue schedules: Export and clean up your deferred revenue waterfalls, contract liability roll-forwards, and unbilled receivable balances.
• Technical Accounting Alignment:
  • ASC 606 documentation: Review and update your internal revenue recognition accounting policies, specifically addressing how you handle distinct performance obligations, standalone selling price (SSP) determinations, and variable consideration.
  • Historical position papers: Compile technical memos for any complex historical transactions so the new team understands your past judgements and conclusions.

To help tailor this transition plan, could you share:

• What is your target year-end audit start date?
• Are you migrating from a traditional local CPA firm to a national/tech-focused firm?
• Do you currently use a billing/rev-rec automation tool (like Maxio, Zuora, or Levers) or manage it via spreadsheets?

That’s a sensible move if revenue is a material or complex part of your SaaS business. Under ASC 606, SaaS audits can involve nuanced judgments around performance obligations, transaction price, allocation, contract modifications, and variable consideration.

When evaluating replacement firms, I’d focus on:

• SaaS-specific experience: Ask how many SaaS companies they audit and what percentage of their revenue comes from subscription/software businesses.
• ASC 606 depth: Look for demonstrated experience with multi-element arrangements, implementation/professional services, usage-based fees, discounts, renewals, cancellations, upgrades/downgrades, and contract modifications.
• Revenue systems: Make sure they understand your billing/CRM/ERP stack and can audit automated revenue-recognition processes rather than relying primarily on manual samples.
• Technical accounting resources: Determine whether you get direct access to a revenue-recognition specialist when unusual contracts arise.
• Audit approach: Ask for examples of how they've identified revenue-recognition risks at other SaaS companies.
• Independence: If you want the firm to advise on ASC 606 issues as well as audit them, clarify what consulting/accounting assistance they can provide without impairing independence. AICPA specifically flags this issue for revenue-recognition engagements.
• References: Ideally, speak with two or three current SaaS clients of comparable size and complexity.
• Transition plan: Have the prospective firm explain exactly how they'll take over from your incumbent auditor, including opening balances, prior-year workpapers, and revenue-related audit documentation.

A particularly useful interview question is: “Walk us through the five most difficult SaaS revenue-recognition issues you've encountered recently, and how you audited them.” A specialist should be able to get very specific rather than giving you a generic ASC 606 presentation.

If you’re preparing to select the new firm, I can also help you build a SaaS-focused audit-firm RFP/evaluation scorecard with weighted criteria and interview questions.

Switching to an audit firm that deeply understands SaaS metrics and complex subscription revenue models (like ASC 606 compliance, multi-element arrangements, and deferred revenue) is a major milestone for a software company. It will save you countless hours of explaining why your bookings don't equal your recognized revenue.

Here is a quick checklist and roadmap to ensure a smooth transition:

• Pre-Successor Communication: Ensure your current auditor has formally resigned or been notified, and request that they cooperate with the incoming firm for a standard professional clearance letter.
• Data Room Preparation: Organize your historical contract repository, standard order forms, master subscription agreements (MSAs), and any non-standard side letters or custom concessions.
• ASC 606 Documentation: Update your technical accounting memos for significant contracts, particularly around distinct performance obligations, variable consideration, and contract modifications.
• System & Subledger Alignment: Ensure your billing engine (e.g., Chargebee, Maxio, Stripe) and ERP (e.g., NetSuite, QuickBooks) reconcile cleanly with your revenue subledger, as this will be the first thing the new team tests.
• Timeline Alignment: Map out the interim vs. final audit fieldwork dates to account for the incoming firm's onboarding learning curve during the first year.

Would you like help with:

• A transition checklist to request from the incoming auditor?
• Key SaaS revenue recognition areas they will likely scrutinize first?
• Drafting a communication template for your board or current auditor?

That makes sense. For a SaaS company, I’d prioritize an audit firm with deep ASC 606/software experience, rather than simply choosing a general CPA firm that happens to audit SaaS clients. SaaS revenue can involve performance obligations, standalone selling prices, contract modifications, usage-based fees, implementation services, and deferred revenue—all areas where specialized judgment matters.

Firms I’d put on the shortlist

Deloitte specifically highlights SaaS issues such as standalone selling prices, hybrid cloud arrangements, variable consideration, termination provisions, contract acquisition costs, and performance-obligation disclosures. KPMG's current software/SaaS handbook likewise focuses extensively on ASC 606, contract modifications, performance obligations, and contract costs.

Corviniti is an interesting specialist option: its founder describes 20+ years of technical-accounting/PCAOB audit experience and specifically focuses on software revenue recognition.

What I'd require in the RFP

Don't just ask, "How many SaaS clients do you audit?" I'd ask each firm for:

1. Number of SaaS audits performed under ASC 606 in the last 2–3 years.
2. Examples involving subscription + implementation/professional services.
3. Experience with usage-based or consumption pricing.
4. Their approach to standalone selling price (SSP) determinations.
5. Experience auditing contract modifications, upgrades, downgrades and renewals.
6. How they test the deferred-revenue rollforward.
7. Experience with revenue-recognition software such as NetSuite ARM, Zuora, Stripe, Salesforce integrations, etc.
8. The actual audit partner and senior manager who would be assigned—not merely the firm's industry credentials.
9. Whether they can perform a pre-year-end ASC 606 technical review before the audit.
10. Fees and expected first-year audit hours, since changing auditors can create substantial onboarding work.

One particularly important point: don't choose solely on who has the most technical accounting expertise. You want a firm that can turn that expertise into a relatively predictable annual audit. A firm that identifies every theoretical ASC 606 issue but creates a six-week audit process isn't necessarily better than one that understands your model and has a disciplined methodology.

If you tell me your approximate annual revenue, private vs. public, number of customers/contracts, billing model (annual/monthly/usage), and current accounting system, I can narrow this to 3–5 firms that are most appropriate and compare their SaaS/ASC 606 capabilities.

Switching to an audit firm that speaks fluent SaaS and understands the nuances of ASC 606 revenue recognition is a massive power move. It will save you countless hours of explaining why your deferred revenue waterfalls look the way they do.

Here is a quick-hit checklist to make the transition smooth, organized, and painless:

• Data Room Setup - Spin up a dedicated, highly secure virtual data room (VDR) specifically for the incoming auditors. Pre-populate it with your master SaaS contracts, standard order forms, Master Services Agreements (MSAs), and any non-standard side letters.
• Accounting Policies & Memos - Gather and update your technical accounting position papers—especially around ASC 606 compliance, multi-element arrangements, contract modifications, capitalization of commission costs (ASC 340-420), and R&D capitalization (ASC 350-40).
• Revenue Subledger & Waterfalls - Ensure your billing or revenue recognition engine (whether it's Maxio, Chargebee, Zuora, or a custom NetSuite setup) can easily export historical deferred revenue schedules, billings reports, and cash collection tie-outs.
• Predecessor Auditor Communication - Facilitate the official handoff between your old firm and your new firm. Your new auditors will need to review the predecessor's working papers (especially regarding opening balances and prior year judgments), which requires a standard professional clearance letter.
• Timeline and Milestones - Map out a revised audit timeline backward from your board or investor deadline. Keep in mind that a specialized SaaS firm might deep-dive into things your previous generalist firm skipped, like customer acquisition cost (CAC) amortization or usage-based pricing models.

To help tailor this transition plan, let me know:

• What billing/rev rec system are you currently using?
• Are you backed by venture capital or private equity , or eyeing an IPO/exit soon?

I can give you a more specific list of items your new SaaS auditors will likely scrutinize first.

That makes sense. For a SaaS company, I’d evaluate the replacement audit firm less on its general audit reputation and more on how deeply the engagement team understands ASC 606 and your actual revenue model. SaaS revenue can involve significant judgment around performance obligations, transaction-price allocation, contract modifications, variable consideration, and timing of recognition.

When comparing firms, I’d specifically ask for:

• Relevant SaaS audit experience: How many SaaS companies similar to yours do they audit?
• ASC 606 expertise: Who on the engagement team actually handles the technical revenue questions?
• Complex contract experience: Usage-based pricing, implementation/professional services, renewals, discounts, multi-year contracts, credits, etc.
• Revenue-recognition process: Can they help you establish a defensible policy and monthly close process, rather than merely identify problems during the annual audit?
• Systems expertise: Experience with your billing, ERP, CRM, and rev-rec systems.
• Technical accounting support: Whether ASC 606 consultation is included in the audit relationship or billed separately.
• Investor readiness: If you're fundraising, acquiring another company, or contemplating an eventual transaction, ask about diligence and audit requirements that could arise.
• Partner involvement: Get the actual audit partner and revenue-recognition specialist involved during the selection process.

There are several types of firms worth considering. Large firms such as KPMG and PwC have extensive software/SaaS revenue-recognition practices, while firms such as BPM and Corviniti explicitly market specialized ASC 606/SaaS expertise.

One important distinction: if you're replacing the financial statement auditor, make sure you're evaluating an actual independent audit firm—not simply a technical-accounting or outsourced-accounting provider that specializes in SaaS rev rec.

If you give me your ARR/revenue size, location, accounting system (e.g. NetSuite, Intacct, QuickBooks), revenue model, and whether you're private or preparing for a financing/IPO, I can research and shortlist 5–10 audit firms that are particularly strong fits, including likely cost/size tradeoffs.