A revenue leakage checklist for SaaS teams.
Use this checklist to compare what your customers agreed to pay with what they were billed. Start with a defined group of accounts and one billing period. Keep supporting records and assign an owner to every unexplained difference.
1. Define the scope and collect the records
Choose a billing period and a group of accounts, such as last month's closed deals, recent expansions, or upcoming renewals. A small cohort is easier to reconcile and explain than a company wide export with no clear boundaries.
Gather the latest approved agreement or order, the CRM record, subscription settings, invoices, credit notes, and relevant usage data. Confirm which source defines the approved commercial terms.
- Use stable customer and subscription IDs to match records.
- Record extraction times so timing differences can be explained.
- Align currency, tax treatment, billing frequency, and service dates.
- Document free trials, credits, delayed activation, and processing windows.
2. Check closed deals against first invoices
For every deal whose agreed billing start date has passed, look for the correct subscription and invoice. Check the amount, service period, and customer identity. Allow the normal processing window before describing an invoice as missing.
- Is the customer billable under the approved agreement?
- Is there a matching subscription and first invoice?
- Did the invoice stay in draft or fail to be issued?
- Does an agreed trial or delayed start explain the difference?
3. Check upgrades, seats, and usage
Compare plan changes and expansions with the subscription settings used to generate the invoice. For usage billing, reconcile the same event window and the contract's included allowance before calculating an overage.
- Did the new amount take effect on the agreed date?
- Were added seats included for the correct service period?
- Are usage events complete for the period being checked?
- Do proration, allowances, and credits explain the billed total?
4. Review discounts and credits
Inspect discounts that should have expired and credits applied to recent invoices. Compare each with the approval and agreement. An intentional concession belongs in your commercial records; an unexplained extension needs investigation.
- Does each discount have an approved amount and end date?
- Are expired discounts still affecting invoices?
- Were one time credits applied more than once?
- Do the CRM and billing system reflect the same approved terms?
5. Review renewals and price changes
For customers due to renew, check that the agreed renewal date, billing frequency, and price are reflected in the subscription and next invoice. Confirm cancellations and negotiated exceptions before flagging a missing renewal.
- Did the renewal produce the expected billing event?
- Was an agreed price change applied on the correct date?
- Is the active subscription linked to the right account?
- Does the contract or approved amendment explain any difference?
6. Separate billing gaps from collection issues
After checking the invoice, compare payments and outstanding balances. A correct invoice that has not been paid needs a collection workflow. An invoice for the wrong amount needs a billing investigation. Tracking these separately helps assign the right owner.
- Are payments matched to the correct invoice and customer?
- Are partial payments or credits recorded correctly?
- Do failed payments have an owner and next action?
- Are disputed amounts explained with supporting records?
7. Log, investigate, and verify each exception
For each unexplained difference, record the customer, affected period, expected amount, actual amount, evidence, and owner. Mark it as suspected until the responsible team confirms the cause.
After correcting the source record, verify the resulting invoice or subscription and check the next downstream system. Update the status when the evidence supports resolution, and keep the underlying cause so the same issue can be checked again.
- Separate suspected impact, confirmed underbilling, and recovered cash.
- Set a next action and review date for every open exception.
- Document valid differences so they do not create repeat alerts.
- Schedule the next check around the relevant billing cycle.
What an exception record should contain
Illustrative example. These are sample records.
| Field | CRM or agreement | Billing record |
|---|---|---|
| Customer and period | CUST-1042 / October | CUST-1042 / October |
| Recurring amount | $1,200 agreed | $900 invoiced |
| Evidence | Approved upgrade order | Issued October invoice |
Log a suspected $300 difference, assign it to the billing owner, and verify the effective date and credits. Record the confirmed impact only after that review.
Bring the issue and its evidence together.
Explore how ResolveNow is being built to help your team investigate and track issues across systems.
