+150 XP

Running financial due diligence on a SaaS acquisition target

A private equity associate opens a target's books and finds $40 million in "annual recurring revenue." Three weeks later, after checking cohort retention and contract terms, the real number is closer to $28 million. The gap wasn't fraud. It came from optimistic accounting, churned logos still being counted, and a founder who confused bookings with revenue. This happens constantly in SaaS deals, and it's exactly why financial due diligence (FDD) exists.

Financial due diligence is the investigative process buyers, investors, and lenders run before closing a deal. It verifies a target's financial claims and uncovers hidden liabilities. SaaS (Software as a Service, software delivered by subscription rather than sold as a one-time license) companies have specific FDD traps that don't exist in traditional manufacturing or retail deals.

Why SaaS due diligence is different

SaaS businesses sell a promise of future service, not a physical good delivered today. That creates three structural issues buyers must probe:

  • Revenue recognition timing: money collected today may not be "earned" yet.
  • Contract complexity: pricing, discounts, and renewal terms live in hundreds of individual agreements, not one price list.
  • Metric manipulation risk: ARR (Annual Recurring Revenue) and MRR (Monthly Recurring Revenue) are not standardized GAAP (Generally Accepted Accounting Principles, the US accounting rulebook) terms. Companies define them however flatters them most.

In the US, revenue recognition follows ASC 606 (Accounting Standards Codification Topic 606), issued by the FASB (Financial Accounting Standards Board). Most other markets, including the EU, use IFRS 15 (International Financial Reporting Standard 15), issued by the IASB (International Accounting Standards Board). Both require revenue to be recognized as performance obligations are satisfied, not when cash arrives. This single rule explains most of the confusion buyers encounter.

Revenue quality: the first checklist

Before touching valuation, a buyer needs to know whether reported revenue is real, recurring, and likely to persist.

Checks to run:

  1. ARR bridge analysis: reconcile starting ARR to ending ARR through new business, expansion, contraction, and churn. If the target can't produce this bridge cleanly, treat that as a red flag.
  2. Cohort retention: pull net revenue retention (NRR) by customer cohort over 12 to 24 months. Median NRR for private B2B SaaS companies has run around 100-105% in recent surveys, with top performers above 110-120% (estimate, source: SaaS Capital retention research). Anything meaningfully below 100% signals a leaky bucket.
  3. Logo churn vs. revenue churn: a company can lose many small customers (logo churn) while keeping revenue flat if larger accounts expand. Buyers need to see both metrics separately.
  4. Customer concentration: if the top 5 customers represent more than 20-25% of ARR, renewal risk at close becomes a material valuation issue.
  5. Bookings vs. billings vs. revenue: bookings are signed contracts, billings are invoiced amounts, and revenue is what's recognized under ASC 606/IFRS 15. Sellers sometimes present bookings growth to disguise stalling revenue.

Worked example: a target reports $10 million ARR with 15% gross churn and 25% expansion within existing accounts.

  • Net Revenue Retention = (100% - 15% + 25%) = 110%
  • The existing customer base alone would grow to $11 million next year with zero new sales.

This single calculation often matters more to valuation than the topline growth number the seller leads with.

Deferred revenue: the balance sheet trap

Deferred revenue (also called unearned revenue, or a contract liability) is cash collected for a service not yet delivered. Say a customer pays $120,000 upfront for a 12-month subscription. The SaaS company recognizes $10,000 in revenue per month. After the first month it carries $110,000 as a liability.

Why this matters in M&A:

  • Deferred revenue is a liability, not an asset. The buyer inherits the obligation to deliver the remaining months of service for cash the seller already collected and may have spent.
  • The accounting at close depends on the framework. Under US GAAP, FASB's ASU 2021-08 (effective for public companies in 2023 and all others in 2024) requires acquirers to carry acquired contract liabilities at the amount the target recorded under ASC 606, as if the buyer had signed the contracts itself. The old "deferred revenue haircut," which shrank year-one revenue, is largely gone for US GAAP buyers. Under IFRS 3, acquired deferred revenue is still measured at fair value, often close to fulfillment cost plus a margin. For a European buyer, that can cut reported post-close revenue in year one, and the model should show it.
  • Large deferred revenue balances relative to cash on hand can mean the company has been "living off" prepayments rather than sustainable unit economics.

Check to run: compare deferred revenue growth to new bookings growth. If deferred revenue is growing faster than new sales, the company may be pulling forward annual prepayments to mask a slowdown. This is common in down markets, when reps push customers toward multi-year prepay discounts.

Contract terms: where the landmines hide

Individual customer contracts are the real source of SaaS revenue risk. Buyers should sample at least 20-30% of ARR by contract value.

Key terms to review:

  • Auto-renewal vs. opt-in renewal: auto-renew clauses inflate the appearance of "sticky" revenue.
  • Termination for convenience: if a customer can walk away with 30 days' notice, effective contract life is far shorter than the paper term.
  • Most-favored-nation (MFN) clauses: promising one customer the lowest price can conflict with future price increases across the book.
  • Data processing agreements (DPAs) are required under GDPR (General Data Protection Regulation, EU law governing personal data) if the target processes EU personal data on behalf of customers. Missing DPAs across a customer base is a compliance gap. GDPR Article 83 allows fines of up to 4% of global annual turnover.
  • SLA (Service Level Agreement) penalty clauses: uptime guarantees with financial penalties are a hidden liability if the product has reliability issues.

Compliance gaps that kill deals (or cut price)

Buyers, especially private equity and strategic acquirers, run compliance checks alongside financial ones because gaps translate directly into post-close costs or liabilities.

  • SOC 2 (System and Organization Controls 2) is a US audit standard from the AICPA (American Institute of Certified Public Accountants) that verifies security controls. Enterprise-focused buyers often walk if the target lacks a current SOC 2 Type II report, since it signals unmanaged security risk.
  • Sales tax nexus: since the 2018 Supreme Court case *South Dakota v. Wayfair*, US states can require sales tax collection based on economic presence, not physical presence. Many SaaS companies under-collect across states, and back-tax exposure is a common diligence finding.
  • VAT (Value Added Tax) in the EU: digital services sold to EU consumers require VAT collection, usually reported through the EU's OSS (One Stop Shop) scheme. Missed VAT filings are a frequent, quantifiable liability that buyers deduct from purchase price.
  • Cross-border data transfers: after the 2020 Schrems II ruling, sending EU personal data to the US needs a legal mechanism. Since July 2023 that can be certification under the EU-US Data Privacy Framework, otherwise Standard Contractual Clauses (SCCs) with a transfer impact assessment. A target with neither in place has a legal exposure the buyer will flag to counsel.

For a practical framework on the SaaS metrics buyers examine, the SaaS Capital benchmarking reports are a solid free reference.

Knowledge check

1. In the opening example, a target's reported ARR was significantly higher than the figure calculated after due diligence. What best explains this kind of gap in SaaS deals?

2. Why does revenue recognition timing create a structural challenge specific to SaaS due diligence, compared to a traditional retail or manufacturing deal?

3. Why are ARR and MRR particularly risky metrics to rely on at face value during SaaS financial due diligence?

MULTIPLE CHOICE

4. Select ALL correct answers about why SaaS companies present distinct due diligence challenges compared to traditional manufacturing or retail businesses.

Select all the correct answers.

MULTIPLE CHOICE

5. Select ALL correct answers about ASC 606 and IFRS 15 as they relate to SaaS revenue recognition.

Select all the correct answers.

Building the due diligence checklist

A working FDD checklist for a SaaS target should be organized into four buckets, each with a named owner (finance, legal, or security):

  1. Revenue quality: ARR bridge, NRR/GRR, cohort retention, customer concentration, bookings-to-revenue reconciliation.
  2. Balance sheet: deferred revenue schedule, acquisition accounting treatment of deferred revenue (ASU 2021-08 under US GAAP, fair value under IFRS 3), accounts receivable aging, capitalized software costs (ASC 350-40 in the US).
  3. Contracts: sample review of the top 20-30% of ARR, auto-renewal terms, MFN clauses, termination rights, DPAs.
  4. Compliance: SOC 2 status, sales tax nexus study, VAT registration status, GDPR transfer documentation (DPF certification or SCCs), any pending litigation or regulatory inquiries.

Each item should produce a dollar-quantified adjustment. That means either a purchase price reduction or a post-close reserve such as an escrow holdback, not just a narrative comment.

🎬 [VIDEO: "How Private Equity Firms Analyze SaaS Companies" - youtube.com - a walkthrough of the ARR, churn, and retention metrics buyers model before making an offer]

Key Takeaways

  • ARR and MRR are not GAAP-defined. Rebuild the ARR bridge yourself rather than trusting the seller's dashboard.
  • Deferred revenue is a liability the buyer inherits. US GAAP buyers now carry it over at the target's ASC 606 amount (ASU 2021-08), while IFRS buyers still remeasure it at fair value, which can shrink year-one revenue.
  • Contract-level review (auto-renewal, termination clauses, MFN, DPAs) catches risks that aggregate financial statements hide.
  • Compliance gaps are quantifiable and typically become price adjustments or escrow terms. Check US sales tax nexus, EU VAT/OSS registration, GDPR transfer mechanisms, and SOC 2 status.
  • Treat every diligence finding as a number: a valuation deduction, an escrow holdback, or a post-close remediation cost.