Won sales, collected payments, and outstanding invoices measure different business facts. A won opportunity is a sales outcome, a payment is a transaction, and an invoice balance is an amount still due. Their dates, currencies, statuses, and relationships can differ, so a useful dashboard defines each total separately.
One customer can produce several different facts
Consider a service deal marked won, an invoice issued for the work, and two partial payments received later. Those are separate records with separate dates. Adding all their amounts together would not produce a useful measure of revenue.
Start by naming the decision. Sales management might need won opportunity value. Collections work needs successful payments and overdue balances. An accountant may need a recognition method that a CRM dashboard does not establish.
Join after respecting the grain
A contact may have several deals, several invoices, and several payments. Joining them all directly by Contact ID can repeat each amount across multiple rows. A spreadsheet can look plausible while its totals multiply.
Aggregate each fact at its own primary record grain before building a customer summary. Use explicit invoice, order, or opportunity references where available. A shared contact alone does not establish which deal a payment belongs to.
Choose the date that belongs to the measure
Opportunity-created date, qualifying won-status date, payment date, invoice-issued date, and invoice-due date answer different questions. A monthly filter is incomplete unless the report defines which date it applies to.
An outstanding invoice balance is usually a current snapshot. Do not label today’s balance as the balance that existed at the end of every previous month without historical snapshots. Missing history should be shown as unavailable.
Keep statuses and currencies explicit
Successful live payments should be distinguished from test, failed, or refunded records. A report of gross collections is not automatically net revenue. State whether refunds are separate and which currency the displayed amount uses.
Invoice Aging groups current eligible unpaid balances by due date. Product Sales uses sale-time order lines. The Subscription Overview sample normalizes supported recurring intervals but does not infer churn history from a current cancelled flag.
Example: why three correct totals differ
| Business fact | Example | Meaning |
|---|---|---|
| Won opportunity | $1,200 won October 3 | A recorded sales outcome |
| Successful payment | $300 collected October 5 | Cash collected in that transaction |
| Current invoice balance | $900 still due | Outstanding balance at the snapshot |
In this simplified invented case, payment plus outstanding balance equals the invoice amount. Real records may also include tax, adjustments, credits, multiple currencies, or unmatched relationships. Define those rules before expecting a reconciliation to balance. Do not treat an invoice line joined to several payments as several independent sales.
Pick the report that matches the decision
Use Sales & Goals for recorded won outcomes against targets. Use Payment Collections for successful transaction volume. Use Invoice Aging for balances requiring collection work, and Customer Payments for a customer-level summary built from separately aggregated facts.
All are available as open synthetic previews. Compare their definitions before connecting real data. A good reporting system should explain why two totals differ, rather than forcing them to agree by changing the underlying meaning.
Sources and further reading
Provider references checked October 16, 2026. Menu labels and source access can change. Product examples describe the reviewed early-access design.