Margin intelligence
Every deal has a path. Every gap has a cost.
Follow revenue from commercial decision to realised margin — and see exactly where value escapes. Leakage is not a bad deal; it is money that left without anyone making a decision.
Start with a number
Annual revenue moving through your incentive programmes. A round number is fine — this is a shape, not an audit.
Watch where it goes
Nine joins, in the order the money meets them. Select any one to read what happens there.
Leaked
$18.1M – $53.5M
3.6% – 10.7% of the number you entered
Realised
$447M – $482M
What survives the nine joins
Seen vs unseen
$30M · $5.8M
At the midpoint, across the 7 priced leaks: 5 a report could show you, 2 it never will. The visible ones carry more money — they are simply the ones you can still go and find.
The ribbon's narrowing is exaggerated — single-digit percent is invisible at true scale. Each stage's share of the narrowing is its real share of the loss; the overall depth is not.
What this assumes — and where you should disagree with it
The percentages come from the benchmark ranges published on each leak. They are quoted against different bases, so before anything can be added they have to be expressed as a share of the one figure you entered. Those conversions are assumptions about the shape of a channel business, not research — they are round numbers on purpose, because precision here would imply a rigour they do not have.
| Base | Assumed | Why |
|---|---|---|
| Net revenue | 100% | The figure you entered is net revenue through programmes, so this is the base itself. |
| Contracted revenue | 70% | Not all revenue sits under a rebate or incentive agreement. Terms can only drift where terms exist. |
| Rebate-eligible revenue | 45% | The subset of contracted revenue on qualifying products, customers and periods — what a join can actually fail on. |
| Purchase spend | 75% | Cost of goods as a share of revenue. Vendor entitlements are earned on what you buy, not on what you sell. |
| MDF & co-op spend | 2% | Marketing development and co-op funds as a share of channel revenue. A large percentage of a small base — which is exactly why it must not be applied to revenue directly. |
| Channel revenue | 100% | Revenue moving through partners, distributors or resellers — the same population the figure describes. |
| Gross revenue | 100% | Gross sits above net by the value of credits and returns — a few points, not an order of magnitude, so it is treated as the same base. |
Two of the nine carry no dollar figure. Accrual drift is a variance against a liability and reporting latency is measured in time; multiplying either by a revenue figure would produce a confident number that means nothing. They are shown, and excluded from the total, rather than guessed at — which means the real exposure is above the range, not below it.
Ranges are indicative benchmarks drawn from published channel-incentive and pricing research together with our own implementation experience. They vary widely by programme complexity, channel depth and data quality — treat them as the opening question in a diagnostic, not a guarantee.
The same problem, stated twice
Once for the person who owns the P&L, once for the person who owns the systems. Neither column is a summary of the other.
The financial problem
The variance you keep explaining as mix is mostly leakage.
- Entitlement earned and never claimed, because no system was watching the threshold.
- Claims paid without validation, because checking each line cost more than the line.
- Concession stacks nobody ever saw summed, approved one defensible step at a time.
- Accruals estimated rather than calculated, producing true-ups that distort periods months later.
The technical problem
Nothing fails, so nothing alerts.
- Unmatched transactions land in a suspense file with no owner — they do not error, they just stop existing.
- Agreement terms live in documents rather than as executable rules, so no event can fire when a threshold is crossed.
- The three prices for a transaction live in three systems and are never compared.
- Reporting aggregates live over transaction tables, so the answer takes hours and nobody explores.
How RevUpra closes them
Control at every join
Leak diagnostic
A structured assessment against the nine leak points using a quarter of your own data — not a benchmark deck.
Exception queues, not suspense files
Everything that fails to match becomes named, owned work rather than a silent drop.
Executable agreement terms
Rates, thresholds and windows as queryable fields the engine evaluates, so entitlement raises itself.
Line-level claim validation
Every submitted line checked against its authorisation; only exceptions reach a person.
Stack visibility at approval
The combined effective rate of every concession, shown before the last approval rather than after settlement.
Materialised financial reads
Channel and margin positions available in days, not weeks, so decisions land inside the period.
Benchmarks
What good looks like
Use this as a self-assessment. If you cannot produce one of these numbers for your own programme, that is itself the finding.
| Metric | Typical today | Target |
|---|---|---|
| Transactions matched to an agreement | 82 – 92% | >99.5% |
| Claim lines validated before payment | 20 – 50% | >99% |
| Vendor entitlement claimed in-window | 88 – 95% | >99% |
| Accrual variance at settlement | 10 – 30% | <2% |
| Days to gross-to-net close | 25 – 45 | <5 business days |
Two to four percent of the revenue flowing through incentive programmes is a common recovery once leakage is closed. The honest number for your business comes from a diagnostic against your own data.
The platform underneath
One platform. One commercial truth.
The leaks are not nine separate problems to buy nine tools for. They are one problem — the commercial decision and the financial record living in different systems — which is why closing them takes a single layer that spans the whole journey.
Commercial control
The decision, and the terms it becomes.
- Deal Modeler
- Contract lifecycle + e-sign
- Pricing engine
- Price protection
- Special agreements
Incentive control
Everything earned around the transaction.
- Vendor rebates
- Customer rebates
- Trade promotions (MDF / co-op)
- Ship & debit
- Channel incentives
Financial control
What reaches the ledger, and what settles.
- Accrual engine
- Claims & validation
- Settlement
- Usage-based billing
- e-Invoicing
Shared across all of it
- Governed AI agents
- Data layer
- Integration hub
- Audit trail
- UR-DEF reporting
- Tasks & approvals
- Custom apps
- Signet e-signature
Terminology
Terms on this page, defined
Plain-language definitions with the reason each one tends to leak.
- Revenue leakage ↗
- Money that was earned but never collected, or paid out when it was not owed, through failures of process and data rather than of commercial judgement.
- Pocket price ↗
- What you actually keep from a transaction after every on-invoice and off-invoice reduction.
- Cross-reference ↗
- Resolving a partner’s identifiers — product, customer, entity — to your own master records so transactions can be matched.
- Accrual ↗
- The liability or receivable recognised as a rebate is being earned, before it is actually settled.
See what RevUpra can recover for you.
Thirty minutes, tailored to your programmes. We walk an agreement through modelling, contracting, accrual, claim and settlement using examples close to your own — and model an indicative ROI against your volumes.