Sales Rebate Processing (1B6)

Agreements regarding customer-side chargebacks can be made between traders and customers. In the context of these agreements, all sales revenue from a customer is collected and a subsequent incentive is granted (for example, after exceeding a sales revenue threshold). This is paid out to the customer by credit memo or can be offset against additional sales revenue. The sales revenue data used for settlement purposes can be determined flexibly from point-of-sale data, sales orders, or from other documents.

This scope item covers the subsequent settlement of rebate conditions agreed upon with customers. You use condition contracts to enter the rebate conditions, together with the process control parameters, business volume selection criteria, and settlement dates for partial and final settlement. You can create condition contracts for one customer or multiple customers.

Customer invoices are used to determine the business volume. In the case of multiple customers, the individual revenue of each customer assigned is used to calculate the settlement values. To pay out rebates to customers, you create settlement documents.

Settlement documents are usually immediately released to accounting. You can also create a two-step condition contract to collect and post settlement documents of different condition contracts in one journal entry to accounting. 

Furthermore, you can choose how the system determines the taxation for the settlement items.

This business process describes the creation of a condition contract for one or more customers.

The condition contract is created for one or multiple customers for which rebates will be calculated based on their transaction business volumes.

The business volume is checked after sales transactions are processed.

The contract is settled and accruals are reversed.

The status of the settlement document is checked as well as the document flow and posting information.

This is the process diagram for scope item 1B6, Sales Rebate Processing.

The main steps of the process are as follows:

The Customer Requests Rebates step confirms the intention of the customer to order goods and expect a rebate on sales.

The Create Condition Contract for one customer step initiates the agreement with one contracting party.

The Create Condition Contract for multiple customers step initiates the agreement with multiple contracting parties.

The Check Business Volumes step confirms the volumes of sales from the contracting parties.

The Final Settlement with Reversal of Accruals step ensures that the reversal of the accruals together with the customer revenues for the final settlement are posted

The Check Settlement Document Status step serves as confirmation of the creation of the accounting documents for a rebate condition contract settlement.

The main benefits of the business process are listed in the figure Business Benefits.

The following table lists the principal roles and SAP Fiori apps used during the process steps.

With the SAP Fiori Manage Customer Condition Contracts app, you can get an overview of your rebate agreements in the form of condition contracts related to your customers. You can quickly search and identify specific contracts, and analyze or navigate to them. In addition, you can navigate to create new customer condition contracts from within this app.

The Manage Customer Condition Contracts analytical app is launched using a KPI tile.

An OData service authorization for the app must be assigned to system users.

The OData service authorization must be assigned to a PFCG role.

The example business catalogue SAP_SD_BC_CC_MNGC can be used to create the PFCG role.