04 / Customer Economics & Cash
You Announced 6%. Why Did Only 2% Arrive?
Follow the increase from announced terms to matched transactions, then decide which exceptions to keep.
The example below is illustrative.
Measure the promise and the result
At the end of the renewal cycle, the pricing team reported that it had raised list prices 6%. Finance reported that measured realized prices rose 2.1% in its comparable set of transactions. Sales could name deals that would have gone elsewhere at the full increase. Service could produce contracts whose price terms had yet to roll. The first clue was that all three accounts could be right.
A price decision goes through contracts, renewal dates, quotes, approval rules, rebates and credits. Some of the difference between announcement and invoice is a choice already made. Some is timing. Some is an exception a company would prefer to stop. Calling the difference “leakage” before tracing it risks taking credit for an increase that could never have been collected and punishing discretion that protected profitable business.
Build the matched-cohort waterfall
Take an $84 million prior-period base of comparable transactions. Use fixed quantities or weights to isolate the change in net realized unit price, with comparable specifications, customer terms and currency. Keep excluded transactions in a separate reconciliation showing what share of the base you could measure. Units with bundle changes or materially different service commitments need separate treatment. Use a single waterfall order so an account excluded on contract eligibility cannot also create a “seller override” loss for the same dollars.
| Stage on the same base | Change versus prior stage | Running price gain |
|---|---|---|
| Announced increase | +6.0 points | 6.0% |
| Price protected or renewal outside period | −1.4 points | 4.6% |
| Approved retention and volume concessions | −1.0 points | 3.6% |
| Documented competitive responses | −0.7 points | 2.9% |
| Discretionary overrides and later credits | −0.8 points | 2.1% |
On this fixed base the headline 6% represents $5.04 million at constant activity. The 2.1% realized change represents $1.764 million on the same basis. The $3.276 million difference is a modeled bridge. It is not a collection opportunity. For example, the 1.4 points protected by contract or timing belong in an eligibility forecast. The 0.8 points of overrides and credits earn investigation, but the $672,000 arithmetic does not establish how much any policy change would recover.
Trace one contract line before interpreting the whole row. A buyer purchased 1,000 comparable units at $100 last period. The new terms call for $106. The approved order and invoice both show $106, but a later discretionary credit memo reduces the payable amount by $800. Match the memo to the original invoice and verify its reason with the approver. Net realization is $105.20 per unit, so the credit reduces the gain from 6.0% to 5.2% on that line. That is 0.8 points on its $100,000 prior-period base. In the $84 million bridge, enter $800 as one contribution to the overrides-and-credits bucket. It becomes part of the $672,000 only when combined with the other verified adjustments.
Test the denominator before taking the report to the executive team. Suppose the matched cohort is $84 million out of $100 million last year, and the remaining $16 million included buyers that since stopped ordering. The waterfall can still describe price on retained comparable transactions. It says nothing by itself about whether the pricing change drove the lost business. Keep a separate bridge for lost buyers, new buyers and volume or mix changes. Present the bridges together since a strong retained-customer price result can coexist with a weak total contribution result.
Audit what produced the exception
Draw a sample from the biggest adjustments and another from the typical adjustment. For each, compare list or contract terms, quote, signed order, invoice, and rebates or credits posted later. Ask who had discretion at each step and what evidence was visible. A salesperson paid on bookings can improve their result while shifting the concession to gross contribution. A project lead can protect a relationship with a service credit whose effect finance sees next month. Both mechanisms should leave records. Where the ledger and approval trail disagree, show the disagreement in the review.
Compare renewal and exception patterns by seller, buyer class, product, and week relative to the period close. A quarter-end cluster could show that sellers gain from moving revenue forward. It could also show that the underlying contracts renew together or that a promotional window ends then. Compare the same seller and similar eligible accounts inside and outside the cluster. Examine commission and credit timing before changing policy. Quote-to-invoice consistency with late credit concentration points to a different intervention from below-floor quoting.
The four-date reconstruction supplies the chronology: when the exception became known, when it was raised, when it was authorized, and when the credit actually posted.
Compare money kept and business won
A pilot on a comparable cohort can make the choice tangible. Suppose the tighter exception rule raises net price from $100 to $103 and incremental cost stays $70 a unit. Shipments of 9,500 at the new terms would contribute $313,500, versus $300,000 on 10,000 at the old terms. The break-even quantity is about 9,091 units at $33 contribution. If shipments fall to 8,900, contribution falls to $293,700. The appropriate question is what drove the lost quantity, whether the company can replace it, and whether churn appears outside the pilot’s observation period.
Measure eligible bid and renewal win rate along with realized contribution dollars. If a pilot loses accounts that use disproportionate service capacity, compare both options using contribution after that capacity is redeployed or the operating expense actually falls. If it loses repeat customers whose later orders would have contributed strongly, make that future loss visible as a scenario. The discount contribution bridge is useful at the approval level. This article assigns the difference across a cohort.
Decide what to change
Run the waterfall at a consistent lag after each period so credits have time to post. Label late or incomplete records. Put a named owner and a proposed decision against each of the largest eligible buckets: fix a configuration mismatch, change approval authority, preserve a profitable exception, or run a measured trial of a new price policy. For a trial, agree in advance on its minimum contribution and maximum lost-volume thresholds.
Take this to your team. Which price decisions would you deliberately make again after seeing the buyer, invoice, contribution and credit together?