SAP SD Rebate Agreement Request Form Template
Rebate agreements fail in SAP most often because the request was vague. This form gives sales operations a structured way to ask SD support for a volume rebate agreement, with everything VBO1 needs on one page.
Fill in
SAP SD Rebate Agreement Request Form Template
Rebate Agreement Request
Company: Acme Components Ltd Requested by: Regional sales manager
Customer and Agreement
| Item | Value |
|---|---|
| Customer | Northline Machining (100234) |
| Agreement type | 0002 Customer rebate |
| Valid from | 2027-01-01 |
| Valid to | 2027-12-31 |
| Rebate basis | Net value of billed sales |
| Settlement | Credit memo request with review |
Scale or Rate
Up to 250,000: 0% 250,001 to 500,000: 2% retroactive Above 500,000: 3% retroactive
Products in Scope
All finished goods in product hierarchy 01, excluding spare parts and freight
SD Processing Notes
Agreement is created in VBO1 and checked in VBO3. Rebate condition records are written with the agreement. Billing documents created before the agreement start date can be picked up by the retroactive rebate update in VBOF. Accruals post at billing through the rebate accrual condition, and final settlement uses VBO7 or the settlement run.
Finance Review
| Question | Answer |
|---|---|
| Accrual account confirmed | |
| Estimated annual rebate cost | |
| Included in budget |
Approvals
Internal request form, not a customer contract. Have the commercial terms with the customer reviewed by your legal team. Verify transaction codes and agreement types against your own configuration.
Reconcile rebate accruals with billing
Optional: ask how a read-only reconciliation could work on your own SAP data.
Optional. The tool and every export work without this. No spam.
How to use the form
The sales manager fills in the customer, validity dates, basis and scale. SD support checks the agreement type and the condition records against the configuration, finance confirms accrual accounts, and everyone signs. Export the PDF, store it with the customer file, and keep the agreement number from VBO3 on the printed copy for audit.
How SAP rebate processing works
A rebate agreement is a contract with the customer that is linked to one or more condition records of a rebate condition type such as BO01, BO02 or BO03. Billing documents in the validity period update the rebate index. Accruals are posted when billing documents are released, using the accrual key and the revenue account key set in the pricing procedure. At settlement, a credit memo or payment is created for the earned amount.
- Agreement type controls what the agreement can reference
- Retroactive scales apply the achieved rate to all turnover
- Accruals are estimates until settlement
- Index update is required for retroactive agreements
Reading the scale
State clearly whether the scale is retroactive or marginal. In the example, passing 500,000 earns 3% on all sales if retroactive, but only on the excess if marginal. The two differ by thousands. Also state whether freight, taxes and returns are excluded, since SAP computes the rebate on the value you configure in the condition type and the basis you select.
Common mistakes
Frequent errors are starting an agreement after billing has begun without running the retroactive update, mixing gross and net bases, leaving the accrual account unconfirmed, and forgetting that rebate processing must be active for the sales organisation, the billing type and the sold-to master. Always test with one billing document before announcing the agreement.
Frequently Asked Questions
Which transaction creates a rebate agreement?
VBO1 creates an agreement, VBO2 changes it and VBO3 displays it. Settlement of earned rebates is performed with transactions such as VBO7 or the settlement run, depending on your configuration.
Why is my rebate not accruing?
Typical causes are rebate processing not active in the sales organisation or customer master, the pricing procedure missing the rebate condition, the agreement dates not covering the billing date, or the rebate index not updated.
What is the difference between retroactive and marginal scales?
Retroactive means the final achieved rate applies to the total turnover from the start. Marginal means each tier rate applies only to turnover within that tier. The commercial agreement must state which one applies.
Can one agreement cover several customers?
Yes. A customer hierarchy rebate agreement can apply to all members of a hierarchy, and a rebate recipient can differ from the sold-to. This needs the hierarchy and partner setup to be consistent.
Netray can compare rebate accruals against actual billing in your ERP, read-only, so finance sees the gap before settlement.
Related Tools
SAP SD Rebate Accrual Calculator
Estimate how much rebate to accrue to date and for the full year with a retroactive threshold, then compare with what has already been settled.
SAPSAP SD Condition Record Load Worksheet
Prepare price and discount condition records row by row, check the per-unit value and export to Excel for LSMW, migration cockpit or manual VK11 entry.
SAPSAP SD Transaction Codes Reference
A searchable list of common SAP sales and distribution transaction codes, grouped by process area, for daily use and onboarding.
SAPSAP SD Partner Determination Design Template
Document your partner functions, partner determination procedures and sources per document level, then export a design page for review.
More SAP tools
See all- SAP SD Sales Order Item ABAP SELECT Generator
- SAP Cost Element Categories Reference
- SAP Period End Closing Checklist
- SAP Standard Cost Variance Calculator
- SAP Activity Type Rate Calculator
- SAP Document Types Reference
- SAP Posting Keys Reference
- SAP Cost Center Hierarchy Upload Worksheet
- SAP CO-PA Value Field Mapping Worksheet