Lesson 3 of 6
From SD rebates to Settlement Management
9 min
Contoso pays its aftermarket distributors a year-end rebate: 2% on all alternator purchases above $500,000. In ECC this ran on SD rebate agreements: an agreement with condition records, accruals posted with each invoice, and a settlement at year end that created a rebate credit memo. In SAP S/4HANA, SD rebate processing is replaced by condition contract settlement, part of Settlement Management.
Why SAP replaced SD rebates
Classic rebates relied on the rebate index table VBOX. Whenever conditions or eligibility changed retroactively, the index had to be rebuilt, which was slow on large volumes and could lock data across the organization. In SAP S/4HANA, the VBOX index is not used. Condition contract settlement reads the relevant business volume directly when it settles, so retroactive changes do not need an index rebuild.
| Topic | SD rebates (ECC) | Condition contracts (S/4HANA) |
|---|---|---|
| Agreement object | Rebate agreement (VBO1 / VBO2) | Condition contract (for example WCOCO, or the Fiori apps for condition contracts) |
| Who is eligible | Rebate recipient and condition records | Eligible partners listed on the contract, with the contract number in the condition table |
| Business volume | Built from the VBOX index | Determined from the relevant documents at settlement time |
| Accruals | Accrual condition in billing | Accrual condition types (for example REA1) and delta accruals at settlement |
| Settlement output | Rebate credit memo | Settlement document that posts the credit or the claim |
| Scope | Customer rebates in sales | Customer and supplier rebates, commissions and other settlements on one framework |
How a condition contract works
A condition contract stores the agreement between Contoso and the distributor: the contract type, the condition granter (who pays), validity, eligible partners, and the rebate and accrual conditions. You create the contract and release it; only released contracts take part in pricing and settlement. Pricing finds the contract's conditions when the contract number is part of the access sequence and condition table, so only the eligible partners get them.
- CreateCondition contract for the distributor, valid January to December, 2% rebate
- ReleaseThe contract becomes active for pricing and settlement
- BillEach invoice carries an accrual condition, posting rebate accruals to finance
- SettlePartial or delta settlements during the year; final settlement at year end
- PostThe settlement document creates the credit and reverses the accruals it replaces
SAP delivers standard configuration for sales rebates, including condition types such as RES1 (rebate), REA1 (rebate accruals) and RED1 (delta accruals in a settlement run). Your project may copy and rename them, so check your own pricing procedures. Settlement runs can be scheduled, and settlement types typically include partial, delta and final settlements; the exact options depend on the contract type configuration.
Open rebate agreements at conversion
This is the part that needs a plan. After conversion you can still process existing SD rebate agreements, so they can run to the end of their validity and be settled. You cannot create new ones or extend existing ones. That leaves three practical choices for agreements that are open on go-live day.
- Does the agreement end shortly after go-live?Yes → let it run out and settle it on the old object · No → next question
- Can it be settled early at go-live by agreement with the customer?Yes → final-settle in ECC before cutover · No → next question
- Is it a long or multi-year agreement?Yes → close it at a cut-off date and create a condition contract for the rest of the period · No → run it out, then switch
Whatever you choose, accruals must reconcile. If accruals were posted in ECC and the agreement is settled in SAP S/4HANA, the settlement must reverse exactly those accruals. Finance should compare accrual balances per agreement before and after conversion.
- Before cutoverInventory open agreementsList each agreement, validity, accrued amount and recipient
- CutoverFreeze and reconcileAccrual balances per agreement agreed with finance
- After go-liveRun out old agreementsSettle on the old object until validity ends
- Next periodCondition contracts liveNew agreements only as condition contracts
What would you do?
A sales manager asks Maria to extend a distributor's 2026 rebate agreement by three months right after go-live, using the same agreement. What should Maria tell her?
- SD rebate processing is replaced by condition contract settlement in Settlement Management.
- The VBOX rebate index is not used; business volume is read at settlement time.
- Contracts must be released before they act in pricing and settlement.
- Old agreements can be finished after conversion but not created or extended; plan each open agreement and reconcile accruals.
Check your understanding · not graded
Lesson check
1. Which table is no longer used for rebates in SAP S/4HANA?
2. What must happen to a condition contract before it affects pricing and settlement?
3. After conversion, what can you still do with an existing SD rebate agreement?
4. What should finance reconcile when a rebate agreement crosses the conversion?