# SAP SD Rebate Agreement Request Form Template > Source: https://netray.co/tools/sap-sd-rebate-agreement-request-form-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A request form for creating a volume rebate agreement in SAP SD: who qualifies, what is measured, scale, accrual treatment and approval. ## Category sap ## Erp SAP ECC and S/4HANA ## Audience - Sales operations - SAP SD consultant - Pricing analyst ## Tool **Kind:** template **Output:** document **Fields:** #### Company **Key:** company **Type:** text **Default:** Acme Components Ltd #### Customer name and number **Key:** customer **Type:** text **Default:** Northline Machining (100234) #### Rebate agreement type **Key:** agr_type **Type:** select **Options:** - 0001 Material rebate - 0002 Customer rebate - 0003 Customer hierarchy rebate - 0004 Independent of sales volume - Custom (Z type) **Default:** 0002 Customer rebate #### Valid from **Key:** valid_from **Type:** date **Default:** 2027-01-01 #### Valid to **Key:** valid_to **Type:** date **Default:** 2027-12-31 #### Rebate basis **Key:** basis **Type:** select **Options:** - Net value of billed sales - Quantity shipped - Gross value before discounts **Default:** Net value of billed sales #### Scale or rate **Key:** scale **Type:** textarea **Default:** Up to 250,000: 0% 250,001 to 500,000: 2% retroactive Above 500,000: 3% retroactive #### Products in scope **Key:** scope **Type:** textarea **Default:** All finished goods in product hierarchy 01, excluding spare parts and freight #### Settlement method **Key:** settle **Type:** select **Options:** - Credit memo - Credit memo request with review - Payment by cheque or transfer - Offset against open invoices **Default:** Credit memo request with review #### Requested by **Key:** requester **Type:** text **Default:** Regional sales manager **Blocks:** #### Rebate Agreement Request **Body:** Company: {{company}} Requested by: {{requester}} #### Customer and Agreement **Table:** **Columns:** - Item - Value **Rows:** **0:** Customer **1:** {{customer}} **0:** Agreement type **1:** {{agr_type}} **0:** Valid from **1:** {{valid_from}} **0:** Valid to **1:** {{valid_to}} **0:** Rebate basis **1:** {{basis}} **0:** Settlement **1:** {{settle}} #### Scale or Rate **Body:** {{scale}} #### Products in Scope **Body:** {{scope}} #### SD Processing Notes **Body:** 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 **Table:** **Columns:** - Question - Answer **Rows:** **0:** Accrual account confirmed **0:** Estimated annual rebate cost **0:** Included in budget #### Approvals **Signatures:** - Sales manager - Finance controller - SD support **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the form **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Cta:** Netray can compare rebate accruals against actual billing in your ERP, read-only, so finance sees the gap before settlement. **Faq:** #### Which transaction creates a rebate agreement? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap rebate agreement template, sap volume rebate request form, sap vbo1 rebate agreement form, customer rebate agreement template, sap rebate processing sd, sap rebate agreement types --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json