What this document contains:
- Rebate calculation
- Rebate claims/rebate payments
- Rebuild rebate agreements
- Close rebate agreements
- Rebate transactions
- Credit claim/payment
- Print rebate transactions
- Other rebates functionality
Rebate calculation
Customer rebate calculation and Supplier rebate calculation are two separate jobs that can be started manually, or scheduled as jobs running with an adequate regularity. For customer rebate calculation it is possible to define the system to run this as the last step in the invoice routine. This set-up is done in the RBT control file.
Customer rebate calculation will, for each invoice line that is flagged as being ready for rebate calculation, match the values from the invoice line against active and open customer rebate agreements. If the invoice line is considered as valid for target accumulation, target forecast calculation will take place for the rebate agreement. Then a rebate transaction is created flagged as a target accumulator. In the event that the current invoice line is also considered as valid for rebate calculation, an agreement forecast calculation takes place for the rebate agreement. The accrual rate is retrieved based on forecasted target turnover and defined accrual type, and a rebate amount is calculated considering the defined rebate calculation type. If a rebate transaction was already created for target accumulation, the same transaction will be updated as a rebate qualifier and the calculated rebate amount will be saved on the transaction. If no rebate transaction exists, the transaction will be created as a rebate qualifier and not as a target accumulator. Whenever a rebate transaction holding a rebate amount is created/updated, corresponding accounting transactions and statistical log file records are created. The statistical log file records are used to transfer rebate amounts to the statistics.
The supplier rebate calculation is similar to the customer rebate calculation. The major difference is that it is based upon goods reception transactions that are flagged as ready for rebate calculation. Whereas the invoice line will be flagged as ready for rebate calculation as soon as it is created, provided that the sales order line was flagged for rebate calculation, the goods reception transaction will be flagged as ready for rebate calculation based on what has been defined as the supplier’s rebate calculation basis code. Three different calculation basis codes exist:
Code | Description |
---|---|
1 | Use reception date and reception values (i.e. prices from purchase order) This goods reception transaction will be flagged for rebate calculation as soon as it has been created. |
2 | Use reception date and values from supplier invoice matching This goods reception transaction will be flagged as ready for rebate calculation as soon as it has been completely matched. |
3 | Use supplier invoice date and values from supplier invoice matching This goods reception transaction is also updated once it has been completely matched. The difference between code 2 and 3 is the date that is used during rebate calculation, e.g. to compare against entered date ranges on the rebate agreement header. For code 2 it is the reception date that is used and for code 3 it is the date on the supplier invoice. |
Rebate claims/rebate payments
Whenever it feels adequate to claim rebates from a rebate payer, or to pay rebates to a rebate receiver, a rebate claim/rebate payment can be created. This can take place after the agreement end date, but it is also possible to do during the lifetime of an agreement.
When a rebate claim/payment is created, a number of rebate transactions will be selected and the sum of the rebate amounts from these transactions will be the total rebate amount to claim/pay.
File | Process description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Work with rebate claims
Work with rebate payments |
Create the rebate/claim header From the initial screen, click the Add option. The header holds the following information:
(Optionally) Select rebate transactions to be included
It is possible to manually change the total rebate amount on the claim/payment header. Then the claimed amount will be updated proportionally for all included rebate transactions. Claim/Pay the rebate claim/payment header Claim method = A/R Claim method = A/P A menu item exists where it is possible to create a number of rebate claims/payments automatically. |
Rebuild rebate agreements
File | Process description |
---|---|
Customer rebate agreements (Rebuild option)
Supplier rebate agreements (Rebuild option) Rebuild customer rebate agreements Rebuild supplier rebate agreements |
It is possible to run into situations where you discover that an active rebate agreement needs to be changed. As soon as an active rebate agreement is changed, it will be flagged as changed as well. It is also possible to run into situations where rebate agreements are created in arrears, with an agreement start date that already is passed. For these situations, the rebuild rebate agreements functionality can be used.
When rebuild of a rebate agreement takes place, all rebate transactions belonging to the agreement will be removed. Then a new rebate calculation will take place for all invoice lines/purchase receptions that are flagged as already rebate calculated, within the dates on the agreement that is rebuilt. This rebate calculation will be done exactly as the normal rebate calculation, and new rebate transactions will be created for the rebate agreement. If rebate transactions already claimed/paid (or even just selected for claim/payment) exist on the agreement that is being rebuilt, then these transactions will remain on the agreement. So if the new rebate calculation detects that an already claimed/paid transaction should not have been included on the agreement, this will be possible to see since the claimed/paid transaction will keep its claimed amount but the calculated rebate amount will be equal to zero. It is possible to set up the rebate agreements so the rebate amount from one agreement can affect rebate calculation for other agreements. This will happen if any agreement type is defined for “End rebate” or “Single rebate”, or if any rebate agreements are flagged for rebate reduction. If this is discovered during rebuild of an agreement, the system will automatically perform a rebuild of those agreements that may have been affected. Via the Rebuild customer rebate agreements/Rebuild supplier rebate agreements menu item, it is possible to start the rebuild of all rebate agreements that are flagged as changed as well as for all open and active rebate agreements. |
Close rebate agreements
File | Process description |
---|---|
Customer rebate agreements (Close option)
Supplier rebate agreements (Close option) |
During the lifetime of a rebate agreement, it is always the accrual rate that is used for the rebate amounts on the transactions that are created for the rebate agreement. So it is first when the agreement end date has passed that we can determine the real outcome for the rebate agreement. Therefore the rebate agreement shall be closed once the agreement end date is passed and all required rebate calculations have been run. The close routine will perform the required updates on the belonging rebate transactions, in order to make the sum of all rebate amounts equal to the total rebate amount that has been established for the rebate agreement.
Example: |
Rebate transactions
File | Process description |
---|---|
Customer rebate agreements
Supplier rebate agreements Work with rebate payments Work with rebate claims Customer rebate transactions Supplier rebate transactions |
Rebate transactions can be accessed from the adjacent mentioned files. It is also possible to access/view a rebate transaction overview, i.e. which rebate transactions that have been created for a specific sales order line, invoice line or purchase order line.
When working with rebate transactions it is possible to change the rebate amount or to delete a specific rebate transaction. Do however note that if this is done, and then the rebate agreement from where it originates is rebuilt, the transaction will appear again with a new calculated rebate amount. If a rebate transaction belonging to a closed rebate agreement is changed or deleted, then the change/deletion will be final. |
Credit claim/payment
File | Process description |
---|---|
Work with rebate claims
Work with rebate payments |
If it is discovered that an incorrect rebate amount has been claimed or paid, then functionality exists to correct the mistake. By using the option for Adjust claim/Adjust payment for the claimed/paid rebate claim/payment that is to be corrected, a list of all included transactions will be displayed. Here it is possible to adjust the incorrect transactions. After confirming the adjustment, the credit claims/payments will be created. Depending on claim method for rebate claims, credit A/P transactions or a credit claim order will be created. For a rebate payment it will always create a claim payment order. |
Print rebate transactions
File | Process description |
---|---|
Print customer rebate transactions
Print supplier rebate transactions |
A flexible printout routine exists for the rebate transactions. It is possible to determine the order of the printed transactions using up to six different sequence fields. For each sequence field it is also possible to determine whether or not sub-total is to be printed, and whether or not a page break is to take place.
Two different types of printouts can be produced. First type of printout is a transaction list, which quite simply lists the transactions (printing adequate information). The second type of printout is called a Claim basis list. The purpose of this list type is to make it possible to send to the rebate payer/receiver, clarifying the detailed content of an actual rebate claim/payment. A large number of selection criteria are also available, making it possible to select the transactions that are to be included for each specific printout occasion. |
Other rebates functionality
Other functionality that is included in the IBS Customer/Supplier Rebates application is:
- Rebate agreement reorganisation
This routine will physically delete rebate agreement information from the rebate agreement files. It is possible to determine whether or not to delete open, closed or deleted rebate agreements. In case open rebate transactions (status = F) exist for the deleted agreement, these will also be removed. - Rebate claim/payment reorganisation
This routine will physically delete rebate claims/payments and their belonging rebate transactions. Since the rebate transaction file is building statistical information, this shall most likely not be reorganised very often. Compare e.g. how often the sales invoice lines are reorganised. - Transfer rebate statistics
Whenever a rebate amount is added, changed or deleted, a record will be written to the rebate transaction statistical log file. These records together with the information in the rebate transaction file will be used to update the statistic information. The transferring of this information will be started from this routine.
Two new system statistic keys have been added for RBT:
- 256 Rebate agreement group
- 257 Rebate agreement
Four new system balance types have also been added:
- 276 Supplier rebate amount
- 277 Supplier rebate amount, affect margin
- 278 Customer rebate amount
- 279 Customer rebate amount, affect margin