Setting up the DC1 Customer/Supplier Rebates application

Related topics

This document outlines the instructions for setting up the DC1 Customer/Supplier Rebates application, allowing you to claim rebates from your suppliers and to pay rebates to your customers.

What this document contains:

Setting up basic data

The following describes the set up procedure in the Basic Tables and Files.

Tables/Files To do
Work with companies Activate the DC1 Customer/Supplier Rebates (RBT) application.
RBT control file Define the number series used for automatic numbering of Rebate payments and Rebate claims. In order to get automatic numbering of rebate agreements, number series for the Customer and Supplier rebate agreements are to be defined as well. If these number series are not defined, all agreements have to be given an agreement ID manually.
Function control file If the functionality to calculate expected rebate amount during sales order entry is required, then the RBT-SOE (Rebate calculation at SO entry) function control has to be activated.
DIS control key table Most of the existing DIS control keys are valid to use on Customer rebate agreements and/or on Supplier rebate agreements. The DIS control keys that are to be used have to be activated.
Agreement type table Customer rebate agreement types and Supplier rebate agreement types have to be created. These types will be defined on the Rebate agreements. On the agreement types you define the following:

Sequence: The sequence will determine in which order the agreement types are handled during rebate calculation. The rebate agreements defined with the agreement types that hold the lowest sequence number will be handled first, and then the rebate calculation will proceed until the agreements defined with the type holding the highest sequence have been handled.

End rebate: When a rebate amount is calculated for an agreement, which is defined with an agreement type that is flagged for end rebate, then no more rebate amounts will be calculated even though the current order line may be valid for subsequent agreements.

Single rebate:When a rebate amount is calculated for an agreement, which is defined with an agreement type that is flagged for single rebate, then no more rebate amounts will be calculated for agreements defined with the same agreement type.

Affect margin: This field is only available for customer rebate agreement types. If the RBT-SOE (Rebate calculation at SO entry) function control is activated, this flag will determine whether or not the customer agreement type will be included in the expected rebate amount calculation during sales order entry.

Agreement keys: The DIS control keys, which will be used to determine which order lines that will be valid for rebate calculation, are defined on the agreement type. Up to five different keys will be possible to use.

Target keys: The DIS control keys, which will be used to determine the order lines that will be valid for target accumulation, are defined on the agreement type. Up to five different keys will be possible to use. Target keys are optional. If no target keys are defined, the agreement keys will also determine which order lines are valid for target accumulation.

Agreement group table Customer rebate agreement groups and Supplier rebate agreement groups have to be created. Agreement groups are used for statistics and accounting purposes.
Period weight template table If periods are to be used for forecasting on Rebate agreements, it is possible to define period weight templates in case the same kind of period set-up will be used for several agreements.
Business partner file Rebate receivers used on customer rebate agreements have to be defined as customers, (i.e. Business partner type 1 or 3).

Supplier rebate agreements can use different claim methods, i.e. how to send the claim to the rebate payer. If claim method for A/P is selected, the rebate payer has to be defined as a supplier (Business partner type 2 or 3). For claim method using A/R, i.e. sending a claim invoice, the rebate payer has to be defined as a customer.

Supplier file A Rebate calculation basis code has to be defined for the suppliers. This code will determine which values and dates will be used for the supplier during rebate calculation. Three different calculation basis codes exist:

1 = Use reception date and reception values (i.e. prices from purchase order).

2 = Use reception date and values from supplier invoice matching.

3 = Use supplier invoice date and values from supplier invoice matching.

Currency table Define the currency(s) in which the rebate should be issued.
Item file Create fictitious item(s) that are to be used on Customer rebate agreements and on Supplier rebate agreements that use claim method A/R. This is the item(s) that will end up on the Claim/Payment order lines.
Document type table The system uses this table to validate the document numbers of the transactions transferred from DC1 Distribution to DC1 Financials, if the Handling code of the document type is 1 or 2.

If you use different number series for invoices and credit notes (as defined in DIS control file), you also have to define two different document number series in this table. One document number series with the same number range as the invoices in the Number series table, and another with the same number range as the credit note in the Number series table. The document number series for invoices can, e.g., be connected to document type DMI and document number series for credit notes can, e.g., be connected to document type DMC. See About number series handling for invoice related documents for more information.

Transfer group table Preloaded with transfer groups RB01 (Rebate A/P) and RB02 (Rebate transactions). The Voucher types for these Transfer groups (e.g. RB) must be the same in the Interface type table (see below).
Interface type table You must define a SRC Interface type (for the Supplier rebate claims A/P interface) and assign the same Voucher type (e.g. RB) as that which is preloaded in the Voucher type field within the Transfer group table RB01.
Voucher type table Voucher type(s) to use for Transfer groups and for Interface type has to be created.
Voucher type number series table Voucher number series must be created for the new voucher type(s) that is created for interface type SRC.
Document number series table Add new number series for Rebates:

  • A/P RCI = A/P supplier rebate invoice.
  • A/P RCC = A/P supplier rebate credit note.
  • A/P RCZ = A/P supplier rebate zero invoice.
  • G/L SRC = Supplier rebate transaction.

It is recommended to set parameters as follows:

Series type = 1 (Yearly)
Handling code = 1 (Automatic)
Duplicate control = YES (Duplicate numbers not allowed)

Signature table Add handlers that will be used on the Rebate claim and on the Rebate payment headers.
Structure type table Field Rebate code defines how rebates are calculated for sales order structures. This field is mandatory and must have one of the following system values:

1 = Rebates are calculated only for the parent.

2 = Rebates are calculated both for the parent and the components.

3 = Rebates are calculated only for the components.

Sales order type table For the normal SO type you have set up in your system, set the Calculation field (under Rebate handling) to YES. This indicates that rebates will be calculated from Customer rebate agreements for this sales order type.

To perform the Rebate payment handling, define at least one SO type with the following:

  • Field Invoice/credit note = Credit note.
  • Field Rebate handling, Payment order = YES (indicates that this sales order type shall be used when paying rebate amount to rebate receivers).
  • Field Document printout = YES for Invoice.

The following is only applicable if you want to register a Credit payment where you credit already paid customer rebate transactions:

Define at least one SO order (claim) type with the following:

  • Field Invoice/credit note = Invoice.
  • Field Rebate handling, Payment order = YES (indicates that this sales order type shall be used when crediting paid rebate amount from rebate receivers).
  • Field Document printout = YES for Invoice.

The following is only applicable if you want to register a rebate claim where claim method for rebate transactions = A/R claim:

Define at least one SO order (claim) type with the following:

  • Field Invoice/credit note = Invoice.
  • Field Rebate handling, Claim order = YES (indicates that this sales order type shall be used when claiming rebate amount from rebate payers).
  • Field Document printout = YES for Invoice.

The following is only applicable if you want to register a Credit claim where claim method for rebate transactions = A/R claim method:

Define at least one SO order (claim) type with the following:

  • Field Invoice/credit note = Credit note.
  • Field Rebate handling, Claim order = YES (indicates that this sales order type shall be used when claiming rebate amount from rebate payers)
  • Field Document printout = YES for Invoice.
Purchase order type table For the PO types you have set up in your system, the Rebate calculation field can be set to YES. This indicates that rebates will be calculated from Supplier rebate agreements for these purchase order types.

Create rebate agreement headers

The customer and supplier rebate agreements are set up to control what and how to calculate the rebate amounts that are to be paid to the customers or claimed from the suppliers. Create as many Customer and Supplier Rebate Agreement Headers as required.

File To do
Customer Rebate Agreements

Supplier Rebate Agreements

Create headers with:

  • Agreement start and end dates.
  • Agreement type. (Selected agreement type will define which DIS control keys that will be used for the agreement).
  • Agreement group.
  • Rebate payer (for customer rebate agreement / Rebate receiver (for supplier rebate agreement).
  • Rebate currency, i.e. the currency in which the rebate amount will be calculated, paid/claimed, and in which currency all amounts for the agreement are to be displayed/entered. If no currency is entered, the default currency for the payer/receiver will be retrieved.
  • For Supplier Rebate Agreement: Type of claim method (A/R or A/P). This dictates how the rebates will be claimed.
  • Affect margin:– Will determine how the rebate statistics is updated. If the RBT-SOE (Rebate calculation at SO entry) function control is activated in the Function control file, this flag will also determine whether or not the agreement is included when expected rebate amount is calculated during sales order entry.
  • Define a Rebate calculation type. Three different calculation types are available:
    • 1 – Accumulated = the rate from the highest reached target will be applied to all rebate transactions.
    • 2 – Interval = for the turnover that exceeds a target, the specific rate for this target is calculated for the rebate transaction until the next target is reached. It is then that the rate from the next target is applied until another next target is reached, etc.
    • 3 – Average = each rebate transaction receives the rate from the current reached rate. A total average rate is calculated for all transactions and the same rate is assigned to all transactions.
  • Define an Accrual type. Two different accrual types are available:
    • 1 – Forecasted = accrual rate will be taken from the forecasted target turnover. The forecasted target turnover can either be calculated or manually defined.
    • 2 – Safety = different meaning for customer and supplier agreements.
      For a Customer rebate: Retrieves accrual rate from one target limit level above the forecasted.
      For a Supplier rebate: Retrieves accrual rate from one level below the forecasted but at least the lowest level.
  • Rebates VAT. The field determines whether the rebate transactions will be claimed using the same VAT information as on the original order line, or if no VAT will be used for the claimed/paid rebates. If this field is set to YES, then the same VAT will be used as on the original order line from which the transaction originates. If this field is set to NO, no VAT will be applied and the system will retrieve the valid zero-rated VAT handling code.
  • Fictitious item: Depending on the claim method, it may be mandatory to define a fictitious item on the agreement header. If claim method A/R is used, and on all customer rebate agreements, a fictitious item has to be defined. The reason is that for these agreements, claim or payment orders will be created. The fictitious item from the agreement will end up as the item on the order lines. A fictitious item can also be entered for agreements with claim method = A/P, in case the field Rebates VAT is set to NO. Then the fictitious item will be used to retrieve the correct zero-rated VAT handling code.
  • Select a Target UOM, i.e. the unit of measure in which the target levels are to be defined. Target UOM Turnover means that the target levels are to be defined as amounts. The target UOM Quantity/Unit means that the target levels are to be defined as a quantity according to the defined unit. If the entered unit is equal to the DIS control units for weight/volume, then the target UOM is to be defined as weight/volume.
  • Select a Rate UOM, i.e. the unit of measure in which the rates are to be defined. Rate UOM Turnover % means that the target levels are to be defined as percentages. The second rate UOM Amount/Unit means that the target levels are to be defined as an amount per the defined unit. If the entered unit is equal to the DIS control units for weight/volume, then the rate UOM is to be defined as an amount per weight/volume. The final rate UOM, Fixed, means that the rate will be defined as a fixed amount.
  • Set flags for Cash discount reduction to YES or NO. The flags will determine whether or not expected cash discount 1 is to be reduced from the amount on which the rebate is calculated and on the amount that is accumulated to the target turnover.
  • Set flags for Rebate reduction to YES or NO. The flags will determine whether or not the rebate amount from this agreement will reduce the amount on which the rebate is calculated for following agreements and on the amount that is accumulated to the target turnover for following agreements.
  • Set flags for Manual price to YES or NO. The flags will determine whether or not an order line that is manually priced is qualified for rebate calculation and/or is allowed to contribute to the target turnover accumulation.
  • Set flags for Free of charge to YES or NO. The flags will determine whether or not an order line that is set as free of charge is qualified for rebate calculation and/or is allowed to contribute to the target turnover accumulation.
  • Set flags for BtB transit to YES or NO. The flags will determine whether or not a BtB transit order line is qualified for rebate calculation and/or is allowed to contribute to the target turnover accumulation.
  • Set flags for BtB direct to YES or NO. The flags will determine whether or not a BtB direct order line is qualified for rebate calculation and/or is allowed to contribute to the target turnover accumulation.
  • Set flags for SMS rebate to YES or NO (this flag is only available on customer rebate agreements). The flags will determine whether or not an order line that holds an SMS rebate amount is qualified for rebate calculation and/or is allowed to contribute to the target turnover accumulation.

Some of the following information on a rebate agreement header is automatically updated, while others can optionally be defined:

  • Working days agreement: This field displays the number of working days within the defined agreement dates interval.
  • Working days elapsed: This field displays the number of working days that have elapsed since the agreement start date until current date. When agreement end date is passed, the working days elapsed will be the same as working days for the agreement.
  • Last calculation run: This field displays the date and time for the latest Customer/supplier rebate calculation job.
  • Last transaction created: This field displays the date and time for the latest created rebate transaction, which belongs to the rebate agreement.
  • Target from and to dates: It is possible to enter another date interval for controlling the target accumulation, compared to the agreement date interval. As an example it is possible to accumulate the target turnover for the first half of the year and, based on the target that is reached, calculate rebates for what is sold/purchased for the second half of the year. If no target date interval is entered, then the target accumulation will be done for the same date interval as is defined as agreement date interval.
  • Payer/Receiver reference: A payer/receiver reference can be entered. The entered reference can end up on claim/payment orders and invoices, provided that the order only holds rebate transactions from one agreement.
  • Agreement turnover floor: If rebates are not to be paid until a certain agreement turnover has been reached, it is possible to enter an amount that will be used as the floor from which rebates will start to be calculated.
  • Agreement turnover ceiling – If rebates are not to be calculated for an indefinite agreement turnover, it is possible to define the ceiling for when it is reached no more rebate amounts will be calculated for the agreement.
  • Forecast agreement turnover: Instead of letting the system calculate an agreement forecast, the forecasted agreement turnover can be entered manually. So when a forecast rebate amount is calculated for the agreement, this will be based on the manual agreement turnover in case this has been entered.
  • Forecast target turnover: Instead of letting the system calculate a target forecast, the forecasted target turnover can be entered manually. So when the accrual rate is retrieved, the reached target will be based upon the manually entered forecast instead of the calculated.

Once rebate transactions have started to be created for the rebate agreement, some further information will be saved on the rebate agreement header. This information includes:

  • Current agreement turnover: This field displays the total line value from all rebate transactions that are created as rebate qualifiers, i.e. valid for rebate amount. The line value can be an amount (for Rate UOM = Turnover % or Fixed), or a quantity/weight/volume (for Rate UOM = Amount/unit) depending on entered Rate UOM unit.
  • Current target turnover: This field displays the total line value from all rebate transactions that are created as target accumulators, i.e. valid for target accumulation. The line value can be an amount (for Target UOM = Turnover), or a quantity/weight/volume (for Target UOM = Quantity/unit) depending on entered Target UOM unit.
  • Current target limit reached: This field displays the target level that is currently reached based on the current target turnover.
  • Current target reached rate: This field displays the rate that is defined on the target level that is currently reached.
  • Current rebate amount: This field displays the sum of all rebate amounts on the rebate transactions that has been created for the rebate agreement. Note that during the lifetime of the rebate agreement, the current rebate amount is not calculated using the current target reached rate. Instead it is the accrual target reached rate that is used.
  • Forecast agreement turnover: Unless this value has been defined manually, this field will display the calculated forecast agreement turnover. When a rebate transaction is added for the rebate agreement, a new forecast is calculated for the rebate agreement header. Either this forecast is calculated using periods and period weights (see section for rebate agreement periods below), or the forecast is based on the number of elapsed days in relation to the total number of days for the whole agreement date interval.
  • Forecast target turnover: Unless this value has been defined manually, this field will display the calculated forecast target turnover.
  • Forecast target limit reached: This field displays the target level that is reached based on the forecast target turnover.
  • Forecast target reached rate: This field displays the rate that is defined on the target level that is reached according to the forecast target level.
  • Forecast rebate amount: This field displays the calculated rebate amount based on the rate from the reached target level according to forecast target turnover and the forecasted agreement turnover.
  • Accrual target limit reached: This field displays the target level that is reached based on the forecast target turnover and considering the accrual type.
  • Accrual target reached rate: This field displays the rate that is defined on the target level that is reached according to the accrual target level.
  • Accrual rebate amount: This field displays the calculated rebate amount based on the rate from the accrual target level and the forecasted agreement turnover.
  • Last claim/pay date: This field displays the date for the latest claim/payment of rebate transactions originating from this agreement.
  • Actual total claim: This field displays the amount that currently has been claimed or paid.

Create agreement details for customer and supplier rebate agreements

The rebate agreement header will have an agreement type defined. From the agreement type the DIS control keys, which will be used for determining whether or not order lines are valid for the agreement, are retrieved. One up to five agreement keys will always be defined, but it is also possible to define one to five target keys.

The actual key values, which will be compared to the corresponding values on the order lines, have to be defined for each rebate agreement. These values are saved as agreement details and (if used) target details.

It is the rebate agreement details that hold the values of the DIS control keys, i.e. it is the details that is controlling whether or not an invoice line or a purchase reception is considered as valid for the rebate agreement. During rebate calculation the corresponding values on the invoice line/purchase receptions, according to defined DIS control keys, are compared to agreement details. If an agreement detail record is found, a rebate transaction marked as rebate qualifier will be created. It is possible to use a different set of keys controlling which invoice lines/purchase receptions that are valid to accumulate the target turnover. This is determined on the agreement type. If a different set of target keys are defined, it is possible to create rebate transactions that are either flagged as a target accumulator, as a rebate qualifier or flagged as valid for both. If no target keys have been defined, all created rebate transactions will be created as both rebate qualifiers and as target accumulators (unless a separate target date range has been defined, see above). If a lot of details will be valid for the rebate agreement, it is better to use the Key values functionality. Here all key values are added separately and then the system will generate all detail key combinations automatically.

The table below describes how to create agreement details. Target details are created in the same way. The panels will only display a different panel heading.

File To do
Customer Rebate Agreements

Supplier Rebate Agreements

From the initial panel click the Agreement details options.

Values for the selected DIS control keys will be entered for each agreement detail. The values to enter will vary depending on the DIS control keys that have been selected for the agreement type, which is defined on the rebate agreement header. For example:

  • Customer: Enter a valid customer for the agreement detail.
  • Item group: Enter a valid item group for the agreement detail.
  • Warehouse: Enter a valid warehouse code for the agreement detail.

Create agreement key values for customer and supplier rebate agreements

In some situations it will be better to use the function for Agreement key values, instead of creating the agreement details manually. The main reason will be when a lot of agreement detail combinations have to be entered. Then it is much quicker to enter each key value separately, and let the system generate all key combinations.

The table below describes how to create agreement key values. Target key values are created in the same way. The panels will only display a different panel heading.

File To do
Customer Rebate Agreements

Supplier Rebate Agreements

From the initial panel click the Agreement key values option. Select the keys for which you want to create key values. On the next panel use the Add option to create all valid key values for the selected key.

Once key values have been created for all keys, it will be possible to use the function for generating all key combinations in the rebate agreement detail file.

When details have been generated, all future changes to the key value will have an immediate effect on the agreement details. If a key value is added, all combinations for this key value will automatically be created. If a key value is deleted, all existing details holding this key value will automatically be removed.

Create rebate agreement exceptions

It is possible to create rebate agreement exceptions. The entered exceptions will prohibit order lines to qualify for rebate calculation for the rebate agreement it is matched against.

The table below describes how to create agreement exceptions. It is also possible to create target exceptions, which will prohibit the order lines to contribute to the target accumulation. Target exceptions are created in the same way as agreement exceptions. The panels will only display a different panel heading.

File To do
Customer Rebate Agreements

Work with Supplier Rebate Agreements

First create the agreement exception header(s). From the initial panel click the Agreement exceptions option.

  • Enter an exception ID and an exception description.
  • Enter a date interval between which dates the exception will be valid. This is optional. By leaving the date fields blank, the exception will always be considered as valid.
  • Enter up to five DIS control keys, which values will be used to control the exception.

Next step is to create exception details. Select option Details for the exception header that you want to update. On next panel use the Add option to create exception details. Key values for each selected key have to be entered. It is also possible to limit the details to be valid for a certain date interval.

Create rebate agreement characteristics

This option is only available if the function control for Item Classification (CLA-ITEM) has been activated.

It is possible to create a set of item characteristics, which will be used to qualify items on the order lines that are matched against the rebate agreement. Thus, if the order line matches the agreement keys, it will also be validated that the item on the order line matches the entered item characteristics (if any are entered). If it matches, the order line will qualify for rebate calculation.

It is also possible to create target characteristics, which will verify whether or not the item on the order line is valid to contribute to the target accumulation. Target characteristics are created in the same way as agreement characteristics. The panels will only display a different panel heading.

File To do
Customer Rebate Agreements

Supplier Rebate Agreements

From the initial panel click the Agreement characteristics option. On the next panel click the Add option. Create an agreement characteristic detail by entering:

  • Line number
  • Item characteristics code
  • Operator
  • Comparison value

For an item to be allowed for the validated rebate agreement, the item has to hold a value for the entered characteristics code and then also match the entered comparison.

It is possible to enter characteristics with the same line number. Then all the comparisons with the same line number (i.e. an “AND”-relation) have to be OK for the validated item. Characteristics with different line number groups will be validated as an “OR”-relation.

Define rebate agreement targets and rates

At least one target level with corresponding rate has to be entered for each rebate agreement. If rebate amount is allowed from the very first order line, a target with 0 (zero) entered has to be created.

It is the target turnover that will be compared to the entered target levels and subsequently determine the rate to use when rebate amounts are calculated.

File To do
Customer Rebate Agreements

Supplier Rebate Agreements

From the initial panel click the Targets and rates option. Create a target level with a corresponding rate.

The value to enter as the target level is determined by the defined Target UOM on the Rebate agreement header. It can either be an amount or a quantity according to the defined unit. It can also be a weight or a volume, if the entered unit is the DIS control unit for weight or volume.

The value to enter is determined by the defined Rate UOM on the Rebate agreement header. It can either be a percentage, an amount according to each defined unit or a fixed amount for the whole agreement.

Define rebate agreement periods

When rebate amounts are calculated, the rebate calculation will perform some kind of forecasting for the rebate agreement, in order to try to find the correct target level that will be reached once the rebate agreement end date is reached. Three different options for the forecasted target turnover are available:

  • Enter a forecast target turnover manually.
  • Create agreement periods with period weights (described in the table below).
  • If none of the above is done, the number of elapsed agreement days will be used to calculate the forecast target turnover. This means that when, e.g., half of the days have elapsed for the agreement, the forecast target turnover will be twice the current target turnover.
File To do
Customer Rebate Agreements

Supplier Rebate Agreements

From the initial panel click the Period options. Create agreement period by entering:

  • Period start date (period end date will be calculated automatically based on next start date, or on the agreement end date).
  • Period weight (Note: It is possible to retrieve a pre-defined period weight template from the period weight template table).

The period weight will be used to weigh the turnover for the current period compared to the period weight for the other periods. For example:

    • Four periods with the following weights:
      Period 1, Weight 2
      Period 2, Weight 4
      Period 3, Weight 4
      Period 4, Weight 2
      Total period weight = 10

If the current turnover for period 1 is, e.g., equal to 2000, then this turnover will be considered to be 2/10 of the total forecast turnover for the whole agreement (i.e. 10000).

If the current turnover until period 3 is equal to 12000, this will be considered to be 8/10 of the total forecast turnover for the whole rebate agreement (i.e. 15000).

Activate rebate agreements

Before rebate amounts will be calculated for a rebate agreement, the agreement has to be activated. It is only possible to activate a rebate agreement that has at least one detail and at least one target level created.

File To do
Customer Rebate Agreements

Supplier Rebate Agreements

From the initial panel click the Activate option. Activate the rebate agreements and confirm the activation on the confirmation panel.

Related topics