Skip to content
ResolveNow

How to detect revenue leakage across your business systems.

Start with one customer cohort and one billing period. Compare the agreement with the subscription and invoice, then investigate every difference before assigning a revenue impact.

Choose a cohort you can explain

Begin with recent closed deals, expansions, or renewals. Define a period and the point when each customer became billable. This gives every comparison a clear boundary.

Record what you include and exclude. A customer still in an agreed trial should not be measured against a fully billable account.

Match the same customer across systems

Use customer, account, subscription, and order identifiers where available. Company names and email addresses can change and should not be the only basis for a match.

Keep uncertain matches out of confirmed totals until someone verifies them. A false match can create a convincing but incorrect discrepancy.

Establish what should have been billed

Read the approved contract or order and its amendments. Identify the price, billing frequency, included usage, effective date, discounts, and credits.

Normalize amounts to the same currency and service period. Apply the agreed rules for proration and usage before comparing the invoice.

Compare with what was actually billed

Inspect issued invoices and the subscription settings that generated them. Look for missing invoices, outdated amounts, expired discounts, and omitted usage.

An invoice in draft is different from an issued invoice. An issued but unpaid invoice is a collection issue. Keep each type visible so the right person can investigate.

Confirm the difference and its cause

Ask the responsible team to review the evidence. Approved exceptions, delayed activation, or a processing window may explain the difference.

Confirm the affected periods before totaling underbilling. Keep suspected impact, confirmed gaps, and recovered cash in separate fields.

Verify the correction and repeat the check

Correct the source of the issue through the approved workflow, then check the resulting subscription or invoice. Confirm that downstream records agree after the update.

Keep the matching rules and approved exceptions for the next check. Run it at a frequency that fits your billing cycle and rate of commercial changes.

Trace an upgrade through three records

Illustrative example. These are sample records.

Compare CRM or agreement values with billing records
FieldCRM or agreementBilling record
Customer IDCUST-1042CUST-1042
Approved upgrade$1,200 per month$900 subscription
Service periodOctoberOctober

The records suggest a $300 difference for October. Verify the upgrade's effective date, proration, and credits before confirming it.

Bring the issue and its evidence together.

Explore how ResolveNow is being built to help your team investigate and track issues across systems.

Explore monitoring