Keep won deals, signed contracts and payments separate

Name the commercial event precisely

Closed-won value is the value recorded when a deal reaches your defined Won stage. It can represent an accepted quote or another agreed commercial milestone. Collected payment is an actual recorded transaction. Revenue recognition is an accounting question that should follow the business’s accounting policies.

The dashboard label should make the distinction clear. A column called Revenue can hide pipeline estimates, contract value and cash in the same number. Use the specific event and value definition that the source record supports.

Trace an illustrative project

These invented amounts explain the distinctions; they are not a customer result. Do not add Won value, signed value and payments together as total revenue. They describe stages and transactions associated with the same project.

Make the value label explain what has happened

Imagine a $5,000 project marked won in October with a $1,000 deposit received and the remaining $4,000 expected later. The opportunity value is $5,000, and the recorded cash received so far is $1,000. Adding those figures together would count overlapping value rather than a larger result.

The signed agreement, invoice and payment each provide different evidence. A sales report can show won value, while a collection report shows confirmed payments and adjustments. The definitions should remain explicit when a project is cancelled, a deposit is refunded or a payment arrives after the sale period.

For marketing review, decide whether the question concerns new won customers, booked project value or collected payments from a particular cohort. Keep these views connected through the opportunity identifier. This lets the team follow the same business through time without turning a forecast into cash or treating one customer’s staged payments as several acquisitions.

Put these definitions next to revenue reporting

• The business event that marks an opportunity won.
• Whether value means quoted, contracted, invoiced or received amount.
• How partial payments, refunds and cancellations are represented.
• The date basis and the customer/opportunity cohort behind the total.

Keep dates and adjustments visible

A deal can be won in one month and paid in another. A cash view uses payment dates; a sales-cohort view follows the inquiries or deals selected for analysis. Neither should silently switch its basis during a comparison.

Refunds, cancellations, partial payments and corrected values need explicit handling. Preserve the relevant event history and show whether a value is gross, net or still pending. The operational report should not invent an accounting treatment from incomplete CRM data.

Connect the right evidence to each metric

1. Agree what makes a deal Won and who records that event.
2. Keep signatures and payment transactions as separate verified records where connected.
3. Define how partial payments, refunds and cancellations affect each view.
4. State the reporting date basis and observation date.
5. Reconcile selected examples across CRM and the relevant payment records.

If no payment source is connected, show that limit instead of relabeling Won as Paid. A manually entered amount can be useful, but it should retain its evidence source and review responsibility.

Use the distinction in marketing decisions

A campaign can produce substantial quoted value with little confirmed business. Another can bring smaller contracts that move faster. Evaluate the stage appropriate to the decision and let the sales cycle mature before drawing a conclusion.

Growth Control’s illustrative customer journey separates Won, Signed and Paid for this reason. The implementation should preserve those meanings in the actual workflow and reports, with payment evidence where the engagement includes that connection.

Questions and answers