Key takeaways
- Financial diligence follows a fixed order: cash, then revenue schedule, then deferred revenue, then AR aging, then AP aging, then expense categorization and margin. Each step depends on the one before it holding up.
- Cash goes first because it’s the hardest number to manipulate and the easiest to confirm — bank deposits get reconciled against the revenue line across three years of history.
- A gap at any step doesn’t need to be fraud to slow a deal. It just needs to be unexplained. A $175,000 timing gap once cost a Series A round three weeks and a half-turn of valuation.
- Speed of response is itself a signal. When the analyst asks for something, the answer should come back the same day — not because it looks good, but because it tells the investor your finance function knows its own books.
When a VC’s analyst sits down with your financials, they’re not reading a story. They’re running a test. They know what breaks first in startup books, what’s most likely to hide surprises, and in what order to look. If you understand that order — and build to it — diligence becomes a confirmation process instead of a discovery one.
What financial due diligence actually is
Financial due diligence is the period after a term sheet or letter of intent when the investing or acquiring party gets full access to your books and data room. In a well-run process, this runs 30–60 days. In a poorly-run one — usually because the books aren’t ready — it can stretch to 90 days or stall entirely.
What determines where you land in that range isn’t the quality of your pitch. It’s the quality of your books. G Squared CFO, a firm that advises SaaS companies through M&A and fundraising, documents what investors require in detail: two or more years of audited financial statements, monthly financial packages for the past 24 months, and detailed management reports tied to a SaaS P&L structure. When that material is organized and ready, the process moves. When teams have to assemble it under diligence pressure, it doesn’t.
The investor’s analyst is not your adversary. But their job is to verify that what the founder told them in the pitch is reflected in the financial records. They approach that task with a specific methodology, in a specific order.
The order of operations
Step 1: Bank statements and cash
Every financial diligence process begins here. Three years of bank statements (or all available history, if shorter) get pulled and reconciled against the income statement. The question is simple: does cash received match the revenue the P&L claims was earned?
This step is first because it’s the hardest thing to manipulate and the easiest thing to confirm. If deposits don’t match the revenue line — with reasonable explanation for timing — every subsequent number becomes suspect. Analysts don’t need to find fraud. They just need to find a gap they can’t explain. An unexplained gap between cash receipts and recognized revenue is enough to slow a deal and restructure its terms.
What they’re checking specifically: Are cash inflows consistent with the revenue schedule? Are there periods where revenue spikes but deposits don’t? Are there customer names in the revenue schedule that can’t be matched to any bank deposit? Are refunds and chargebacks handled consistently?
Step 2: Revenue schedule by customer and contract
Once cash is confirmed at the aggregate level, the team moves to the revenue schedule — a line-by-line breakdown of every customer, contract start and end dates, contracted amount, and what was recognized each period. This is where the ARR figure from the pitch deck gets stress-tested.
They’re checking whether customer count ties to the deck, whether recognized revenue per the schedule matches the P&L, and whether contract dates support the timing of revenue recognized. Andreessen Horowitz flags this directly in their 16 Startup Metrics guide: ARR should exclude one-time and non-recurring fees — and mismatches between reported ARR and the contract-level data behind it are among the most common early diligence findings.
Step 3: Deferred revenue
For any company with subscription or annual contract revenue, deferred revenue is the next stop. This is money received in advance for services not yet delivered, and it should appear as a current liability on the balance sheet. When it doesn’t — or when it’s lower than it should be given the contract schedule — it’s a signal that revenue was recognized too early.
This matters in both directions. For investors, a missing or understated deferred revenue balance means historical revenue may have been overstated. For acquirers, it’s also a balance sheet question: they’re buying the obligation to deliver future services, and if that obligation isn’t on the books at the right level, it emerges as a cost after close.
Step 4: Accounts receivable aging
The AR aging report shows who owes the company money and for how long. Analysts use it to find two specific problems. First: customers who are past-due but still counted in ARR — accounts that are technically delinquent but haven’t been formally churned. Second: a high proportion of AR that’s past 90 days, which is a signal of either collection problems or billing errors.
The connection between AR aging and ARR is often missed by founders. If 15% of the ARR schedule maps to customers who haven’t paid in three months, the ARR figure is at risk — and the analyst will adjust for it.
Step 5: Vendor aging and accounts payable
On the expense side, AP aging tells the investor what outstanding obligations exist that aren’t currently on the books. A large AP balance with significant aging often signals either delayed payment (a cash management strategy) or expenses that were incurred but never properly recorded as liabilities. Both affect the true picture of the business’s financial position.
Analysts are also looking here for accrued expenses that should exist but don’t — legal fees for services already received, contractor work that’s been delivered but not yet invoiced, commissions owed to salespeople. Missing accruals mean the expense side of the P&L is understated, which overstates margin.
Step 6: Expense categorization and margin analysis
With the revenue and liability picture established, the team reviews how expenses are categorized and whether gross margin is stable and consistent with the industry. Margin noise — significant swings month-to-month without explanation — is a flag for deeper inquiry. It suggests either inconsistent expense timing, one-time costs mixed into operating expenses, or accounting that reflects cash payments rather than economic reality.
| Step | What they pull | Primary question | Common problem found |
|---|---|---|---|
| 1. Cash | Bank statements, 3 years | Do deposits match the revenue line? | Revenue recognized with no corresponding cash |
| 2. Revenue schedule | By customer, contract, period | Does ARR/MRR match contract data? | Expired/unrenewed contracts still in ARR |
| 3. Deferred revenue | Balance sheet + schedule | Is deferred revenue at right level? | Revenue recognized before delivery; missing liability |
| 4. AR aging | By customer and days outstanding | Who owes money that’s in ARR? | Past-due accounts still counted as active revenue |
| 5. AP aging | By vendor and days outstanding | What obligations aren’t on the books? | Missing accrued liabilities, unrecorded vendor obligations |
| 6. Expenses/margin | P&L detail, categorization | Is margin real and stable? | One-time costs in opex; cash-basis timing distorting margin |
What this looks like in practice
A $2.1M ARR SaaS company enters Series A diligence in good shape by every internal measure. Their pitch was tight, the lead investor is engaged, and the data room goes up on a Thursday.
By the following Tuesday, the analyst flags a discrepancy: when they reconcile the revenue schedule to bank statements over the prior 18 months, there’s a $175,000 gap. Not fraud — just a combination of issues. Three contracts were renewed verbally but without signed documents, so their revenue recognition timing is unclear. Two accounts in the ARR schedule are customers who were invoiced but haven’t paid in four months. One customer was accidentally counted twice across two product lines at the same company.
All explainable. But explaining takes three weeks of back-and-forth between the founder’s team and the analyst’s team. During that three weeks, one partner on the investing side loses conviction and wants to see a full reforecast. The round closes — but at a half-turn lower valuation, and on a timeline that almost missed a market window.
The books weren’t wrong. They were slow to reconcile. The practical difference between “wrong” and “hard to explain” is smaller than most founders expect.
What good looks like
A revenue schedule that ties exactly to the P&L revenue line, supported by signed contracts for every customer. A deferred revenue schedule that reconciles to the balance sheet at every period end. An AR aging report with nothing significant past 60 days. Expense categories that reflect how the business actually works, with no large unexplained month-to-month swings.
And the less obvious piece: the ability to answer questions within hours, not days. When the analyst asks for the customer-level AR aging as of March 31, the answer should come back the same afternoon. Speed of response is itself a signal — it tells the investor that your finance function knows its own books, and that there aren’t surprises waiting to surface.
The companies that close fastest in diligence are not always the largest or most sophisticated. They’re the ones where the books are organized in advance, where the revenue schedule is maintained monthly rather than assembled for a raise, and where the finance team treats reconciliation as a continuous discipline rather than a pre-diligence project.
That’s what this guide is about. Step two in that order — the revenue schedule — is where most SaaS diligence actually slows down or stops, almost always for the same reason: revenue recognized when cash was received instead of when it was earned. The next part of this guide breaks down why, and the fix.
