How to Prove Revenue During Fundraising Due Diligence

Saying your company has £3m in ARR is not the same as proving it. Revenue due diligence is the point where investor confidence is either confirmed or quietly undermined — and the companies that struggle are almost never hiding numbers. They simply have not prepared the evidence chain.

TL;DR

• Revenue proof requires a chain from metric to contract to invoice to bank receipt — not just a dashboard screenshot.
• Prepare the evidence before the raise, not in response to investor requests.
• Separate booked, billed and collected revenue in every document you share.
• Redact customer names where confidentiality agreements require it, but preserve the underlying figures.
• Document who can speak to each revenue line — one owner per question prevents conflicting answers.

Investors who have been through enough fundraising rounds have seen every kind of revenue inflation: trials counted as contracts, verbal renewals treated as signed agreements, one-off professional services fees included in recurring revenue. They ask detailed questions because the pattern is common, not because they distrust you specifically. The best response is a clean evidence chain prepared in advance.

What revenue evidence investors actually check

Not every investor asks for the same documents, but most will want to trace at least one or two significant revenue lines from the metric you have quoted to a verifiable source.

The standard evidence chain looks like this:

1. The reported metric — ARR, MRR, contracted revenue, recognised revenue
2. The signed contract — executed agreement with the customer, including term, renewal terms and price
3. The invoice — the billing record that corresponds to the contracted amount
4. The bank receipt — payment received, matching the invoice

A gap anywhere in that chain will generate a question. The question may be benign, but it creates uncertainty and slows the process.

1. Map your revenue before you share anything

Before uploading any documents, create a revenue schedule. This is a table that lists each customer, the contracted amount, the recognised amount in the reporting period, the invoice reference and the payment status.

You do not need to share this schedule in full. It is a working document that helps you identify gaps in your evidence before investors find them. For each customer row, ask: could I produce the contract, invoice and payment receipt if asked?

If the answer is no for a material customer, resolve it before you start the raise.

2. Define the revenue terms you will use

Revenue recognition is technical and jurisdiction-specific. You do not need to litigate the accounting treatment with investors, but you do need to use terms consistently.

Pick the terms relevant to your business, define them in a short document, and use them consistently across the deck, the financial model and the data room.

3. Organise the contract evidence

For each significant customer, include a folder in the data room containing:

• The signed master agreement
• Any amendments or order forms
• The most recent renewal document
• A redaction note if customer-identifying information has been removed

Redact only what is required by the confidentiality clause. Many founders over-redact out of caution, removing information that investors need to verify the revenue amount. The revenue figure itself is almost never subject to a confidentiality restriction — the customer name sometimes is.

If your contracts are with named enterprises and naming them is competitively sensitive, speak to your legal adviser about what can be shared under NDA. A blind schedule listing contract values without customer names is often acceptable for the initial review stage.

4. Prepare invoice and payment records

Contracts prove what was agreed. Invoices and payment records prove what happened. Both are needed.

For each revenue-generating customer in your evidence set:

• Export the invoices from your billing system (Stripe, Xero, QuickBooks, Chargebee)
• Confirm that the invoice amounts match the contract terms
• Note any credits, refunds or billing adjustments and explain them

For payment confirmation, a bank statement extract showing the relevant receipts is usually sufficient. If payments come through a payment processor, an export from that processor can serve the same purpose.

Do not include full bank statements if they contain unrelated transactions. Extract only the relevant receipts and label them clearly.

5. A controlled release process

The revenue evidence is among the most sensitive material you will share. It contains customer relationship details, pricing and occasionally margin information. Handle the release carefully.

1. Determine what each investor needs at each stage. Early-stage exploratory interest does not require full contract access. Advanced diligence may.
2. Set folder-level permissions. Put contract evidence in a separate restricted folder from the general overview documents.
3. Use named access. Revenue contracts should be accessible by name, not via a shared link. Track who opens them.
4. Prepare a Q&A log. When investors ask revenue questions, record the answer, who gave it and what document it refers to. Consistency matters across a long process.

A platform like SendNow lets you track whether specific documents have been reviewed before a diligence call. This is useful for revenue evidence: you can see whether the investor has looked at the contracts before you walk them through the numbers.

Editorial disclosure: SendNow has a commercial relationship with this publication.

6. A realistic example

A healthcare software company is raising a Series A. Their reported ARR is £2.1m. They have 18 customers.

Their data room includes a revenue schedule (internal use), a blind customer schedule shared with investors under NDA (listing contract values by anonymised customer ID), and a contracts folder with signed agreements for their top seven customers by revenue (these seven represent 74% of ARR).

For two customers, they provide the executed master agreement plus two order forms. For one customer, they note that the contract was renewed verbally and show the email confirmation alongside the original agreement — with a note that a signed renewal is pending.

The lead investor traces three revenue lines from the summary metric to the contract to a bank statement extract. The verbal renewal generates one question, which is answered by sharing the renewal order form that was executed during the diligence process.

7. Common problems

• Including trials in ARR. A pilot agreement with a break clause is not ARR. Label it correctly and explain when it converts.
• Citing revenue from a customer who has since churned. Use a current-as-of date on every revenue figure and make the date visible.
• Contracts signed after the reporting date. Backdate your evidence clearly — the contract dates and the reporting period should never appear to conflict.
• Invoices that do not match contract terms. Billing adjustments happen. Note them and explain the reconciliation.
• Multiple people giving different ARR figures. One person owns the revenue number during the raise. All written answers reference the same approved figure.

8. Pre-release checklist

• Revenue schedule created and reviewed internally before the raise
• Revenue terms defined in a short document and used consistently across all materials
• Contracts folder contains signed agreements for all material customers
• Invoices for the reporting period are pulled from the billing system
• Payment receipts or bank extracts are available for the same period
• Redactions are documented — only what is required, not more
• Folder permissions restrict contract access to named investors
• A Q&A log is in place to ensure consistent revenue answers

Frequently asked questions### How much revenue evidence do I actually need to provide?

Lead with your top customers by revenue value. If your top ten customers represent 80% of ARR, prepare complete evidence for those ten. For the remainder, a summary schedule is usually sufficient unless investors ask to go deeper.

What if a significant customer has a confidentiality clause that prevents me from sharing the contract?+

This is common. Discuss with your legal adviser what can be shared under the investor's NDA. A blind schedule showing the revenue amount, term and renewal date — without the customer name — usually satisfies the initial review.

How do I handle revenue from a customer who has just churned?+

Do not include churned revenue in your current ARR figure. If it was included in a previous investor communication, note the change explicitly. Trying to smooth over churn that investors will discover creates a much bigger problem than disclosing it clearly.

What if my revenue recognition differs from how I describe ARR?+

Explain the difference. Many companies report ARR on a contracted basis but recognise revenue under IFRS 15 or ASC 606 on a different schedule. Investors understand this — they just need to know which basis each figure uses.

My company is pre-revenue. What evidence do I share?+

Share signed LOIs, pilot agreements and purchase orders with committed values. Be explicit about what is contracted versus what is indicative interest. A signed pilot with clear terms is worth more to an investor than an unsigned enterprise LOI.

Final takeaway

Proving revenue during fundraising is about building a chain of evidence that an investor can follow without having to take your word for it. Contracts, invoices and receipts are the chain. Your revenue definitions and a customer schedule are the map. The founders who close diligence fastest are the ones who built this chain before the raise started, not in response to each investor request.

Related articles

• How to Share SaaS Metrics With Investors
• How to Share Customer Contracts With Investors
• Build a Fundraising Investor Q&A Workflow