Compendium Token
How Software Rebates Work (And When They Beat a Discount)
A rebate returns money after the fact; a discount lowers the price up front. For software billing, one of them is far more honest about mid-term growth. Here is the difference.
A discount reduces the price before you pay. A rebate returns part of it afterward. They can end up at the same number, and yet for software billed by the seat they behave very differently — because the thing that determines the right price is often not known until after the period has run.
The mid-term growth problem
Suppose Suite pricing is graduated, so the first five seats cost more per seat than the next five. A firm signs for five seats in January and grows to twelve by June.
Handled as a discount, that requires re-quoting: someone has to notice the growth, recalculate the band, issue a revised agreement, and reconcile what was already invoiced. In practice that either does not happen, or it happens late and generates an awkward credit note.
Handled as a rebate, nothing needs renegotiating. Seats are billed as they are added, and the difference between what was charged and what the volume actually earned comes back as tokens. The firm ends up at the right price without anyone having to remember.
Where rebates fit
- Seat growth. Volume bands settle up automatically rather than requiring a mid-cycle re-quote.
- Annual commitment. Where a budget is already approved, taking the saving as tokens against next year's seats is often more useful than a smaller invoice this year.
- Service tokens. If we miss something we promised, the make-good arrives automatically with the reason attached — no claim form, no negotiation.
- Migration offset. Moving off an incumbent system costs real hours. Offsetting part of that against the first year means switching is not punished.
The trade-off, stated plainly
A rebate is worse than a discount in one specific way: you pay the full amount first and get value back later, so it costs you working capital in between. For a large annual commitment that is a real consideration and a straight discount may genuinely suit you better. Ask for it.
Rebates are better where the correct number cannot be known in advance, where you would rather not renegotiate an agreement every time you hire, and where you want the adjustment to be automatic rather than dependent on someone raising it.
Rebates arrive as tokens, not cash
Worth being explicit: a rebate lands as Compendium tokens, spendable against any Compendium product. It is not a refund to your card. If what you want is money back rather than a lower future bill, a rebate is not the right instrument and we should talk about pricing instead.
How it shows up in your books
On your invoice, tokens are applied as a payment rather than as a line-item discount. That keeps the software expense you record equal to the actual price of the software, with the tokens shown as how it was settled — which is generally what your accountant wants to see, and makes period-to-period comparisons meaningful.
Common questions
What is the difference between a rebate and a discount?
A discount lowers the price before you pay. A rebate returns part of the price afterward, as tokens. Rebates suit situations where the correct price depends on something not known until the period has run, such as how many seats you ended up using.
Are software rebates paid in cash?
Compendium rebates are paid as tokens against Compendium products, not as cash refunds. If a cash reduction is what you need, that is a pricing conversation rather than a rebate.