This program generates rebate payments based on the processing period and interfaces with A/R and A/P modules depending on the payment methods. If the payment method is by cheque it will interface to A/P where as if the payment is made by credit note it will interface to A/R.
The processing period is used to work backwards to find the cycle period to be processed.
Also provided are multiple payments per cycle for non-matured rebates. The accrual and payment frequency have been separated hence payment can be independent from accrual.
There is validation logic to make sure all Control Files are setup correctly before payment by calling RBO005 to validate rebate setup.
The Price and Tax Retrieval program DSO936 is called to decide whether to use gross or net price when updating the unit price in the transaction detail file.
Amounts are split into net and tax amount for external reporting.
Generate & post rebate payments
- In the menu, expand Other Modules > Rebate & Commissions > Rebates Payments menu and double-click Generate & Post RB Payments. RBO160 Rebate Payment Process panel appears.
| Field | Description |
| Rebate cycle period | The period for which the rebate cycle is set up is an optional entry. |
| Process period | In Rebate Payments Process, Payments can be processed by Cycle Period or Processing Period. The Process Period is optional but becomes mandatory if you do not enter a rebate cycle period. This is the processing period for which you want to generate and post payments. |
| Current DS period | Current Distribution period will default. |
| Current AP period | Current AP period will default. |
| AP posting period | The A/P posting period defaults to the current processing month and may be overridden. A/P posting period should equal Distribution Period. |
| AP invoice due date | Invoice due date is mandatory. |
| Hold AP invoice | Indicate whether or not to hold Accounts Payable invoices that have been generated. |
| Summary level | Select the summary level with minimum pay amounts to be posted. |
| Payment frequency | Select the targeted rebate frequency as defined in TMSRB/RB-PAY to be included in the payment process. |
| Rebate group | A Rebate group is similar to a Buying Group. Buying groups created for Rebates will probably be the same or similar to TMSDS/CC-BG, but does not have to be. |
| Rebate group level | Once the Rebate group has been entered in the previous field, this Rebate group level will default and can be overridden. An example of levels is: INDIVIDUAL STORES SALES DIVISION DISTRIBUTION CENTER HEAD QUARTER BUYING GROUP Buying Groups typically have several levels as each member of a group may itself consist of a sub group. Rebates can be applied at each/any level and may replace or be in addition to rebates at other levels. All rebate definitions may be given a level within the Buying Group where that level can then be used to specify whether the rebate is in addition or replaces rebates at other levels. The rebate level is applied at the rebate definition, it is NOT necessary to code customers with a Buying Group level class. |
| Rebate agreement | Rebate agreement number or text to identify the agreement with the customer. |
| Rebate type | The Rebate type and Rebate groups form part of a hierarchy for classifying Rebate contracts. TMSRB/RB-TYPE is used to define the list of valid rebate types. . |
| Rebate number | Rebate definition number/s to be in included in the payment process. |
- Enter the required details and click OK to generate the rebate payment.
