Financial Due Diligence for SaaS: How Buyers Verify the Numbers

Financial due diligence is the part of a SaaS deal where the price gets confirmed — or the deal quietly falls apart. Everything up to the Letter of Intent runs on the seller's story. Financial diligence is where a buyer stops taking that story on trust and starts checking it.

And there's a distinction most founders miss: reviewing financials and verifying them are not the same thing. A buyer can read your P&L, nod along, and still not know whether the revenue is real. This post walks through what buyers actually examine in financial diligence, the reconciliations that decide the outcome, and how the numbers get verified rather than just reviewed.

For the full, cross-category process, see the broader SaaS due diligence checklist. This one goes deep on the financial half.

What financial due diligence is

Financial due diligence is the buyer's independent confirmation of a target's financial position — typically after an LOI, usually over a few weeks. For a SaaS business, it centers on one question above all others: is the recurring revenue real, recurring, and durable?

Everything else — margins, costs, working capital — matters, but the revenue quality is what sets the valuation and what buyers scrutinize hardest.

The documents buyers request

Financial diligence starts with a data request. Expect to provide:

Profit & loss statements — usually monthly, two to three years back.
MRR/ARR breakdown — new, expansion, contraction, and churned MRR by month.
Billing system and payment processor exports — Stripe, and any other billing source.
Bank statements — to confirm the cash actually landed.
Deferred revenue schedule — how prepayments are recognised over time.
Cohort and retention data — how each customer group behaves over its life.
Customer list with revenue by account — to assess concentration.
CAC, LTV, and churn metrics — the efficiency and durability of the revenue.

Collecting these is the easy part. What the buyer does with them is where deals are made or broken.

What buyers are really checking

Behind all those documents, a buyer is answering five questions about your revenue.

Is it real? Did the money genuinely come in, from genuine customers? This is the verification question, and the one most likely to be underexamined.
Is it recurring? Or does the "ARR" quietly include one-time fees, services, and usage spikes that won't repeat?
Is it recognised correctly? Under standards like ASC 606, revenue is earned as the service is delivered — so an annual prepayment is mostly deferred revenue, not current-period income. Booking it upfront overstates performance.
Is it durable? Cohort retention and net revenue retention reveal whether revenue holds or leaks. NRR above 100% is what buyers pay premiums for.
Is it concentrated? Revenue leaning heavily on one or two accounts carries single-point-of-failure risk and gets discounted.

The reconciliations that decide the outcome

Financial diligence is, at its core, a series of reconciliations — checking that the same revenue tells a consistent story across independent sources.

Billing vs. bank. Do the charges in the payment processor match the cash that actually hit the bank, net of fees and payout timing?
Billing vs. general ledger. Does the recognised revenue in the books reconcile with the raw billing data?
The MRR bridge. Does the movement in MRR — new, expansion, contraction, churn — actually add up month to month?
Revenue vs. behaviour. This is the reconciliation most traditional diligence skips: does the revenue match the real traffic, engagement, and customer activity that should accompany it?

That last one is the difference between reviewing numbers and verifying them. Billing data can reconcile perfectly with the bank and the ledger and still be fabricated — because all three can be fed from the same inflated source. What billing can't easily fake is the behaviour real customers produce. When revenue implies thousands of active accounts and the traffic and engagement can't account for them, the numbers don't hold, no matter how clean the P&L looks. These are the signatures that expose fabricated revenue.

Why "reviewing" isn't "verifying"

Most financial diligence is document review: the seller supplies exports and statements, and the buyer reads them. The weakness is that documents can be edited, and a static export can't be re-checked at the source. A dashboard screenshot or CSV is a claim, not proof.

Verification means confirming the numbers against live, source-connected data the seller can't alter between capture and review — billing pulled directly from the processor, reconciled against analytics pulled directly from the source. That's what separates revenue a buyer will credit in full from revenue they'll discount for risk. Source-connected revenue verification is how that reconciliation gets done in practice.

For founders: get ahead of it

If you're heading toward a raise or sale, run this diligence on yourself first. Reconcile your billing against your bank and your analytics, separate recurring from one-time revenue, document your deferred revenue, and make sure your numbers hold up under the same cross-checks a buyer will apply. The founders who compress diligence and defend their valuation are the ones who walk in already verified.

FAQs

What is financial due diligence for a SaaS company? The buyer's independent confirmation of the target's financials — especially whether the recurring revenue is real, genuinely recurring, and durable. It usually runs for a few weeks after an LOI.

How long does financial due diligence take? Commonly two to six weeks, depending on deal size and how clean and reconciled the seller's data is. Pre-reconciled financials are the biggest factor in keeping it short.

What documents are needed for SaaS financial due diligence? Typically P&L statements, an MRR/ARR breakdown, billing and payment-processor exports, bank statements, a deferred revenue schedule, cohort and retention data, a customer revenue list, and CAC/LTV/churn metrics.

How do buyers verify SaaS revenue is real? By reconciling it across independent sources — billing against bank and ledger, and revenue against the real traffic and behaviour behind it. Revenue that can't be reconciled with customer activity is the clearest sign something is wrong.