A periodic job that recalculates a customer's rebate claims in To be calculated status on the total sales of the rebate period, adds an adjustment claim for the difference and sets the claims to Calculated. Unlike the claims created per invoice line, the result reflects the whole period's volume. These are the older customer rebates of Sales and marketing. Microsoft describes Rebate management as the newer module for rebate deals, provisions and royalties; choose one of the two for a project.
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone
1What it is and why
What it is
A periodic job that recalculates a customer's rebate claims in To be calculated status on the total sales of the rebate period, adds an adjustment claim for the difference and sets the claims to Calculated. Unlike the claims created per invoice line, the result reflects the whole period's volume. These are the older customer rebates of Sales and marketing. Microsoft describes Rebate management as the newer module for rebate deals, provisions and royalties; choose one of the two for a project.
What you do here
Use this periodic task to bring claims that are waiting for recalculation up to date, so they can be approved.
Example
For example, BEAT-000123 buys 40 and then 60 units in one week under a 2.00 / 4.00 per-unit agreement. Cumulate rebates for that week moves the customer to 4.00 for all 100 units and adds an adjustment claim of 80.00.
The page in Dynamics 365. page title tab to open what to set or check
About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.
When to run it
When to run it
After invoicing, when claims from periodic rebate agreements are in To be calculated status and must reflect the period's total sales volume.
How often
At the end of each cumulation period of the agreements (week, month, year or customized period).
What the output shows
Claims in Calculated status, with an adjustment claim when the period's volume reaches a higher threshold. For amount-based agreements with item rebate groups, the threshold is checked per item.
Run it per customer for exactly the period the agreement cumulates sales by (for example the week), after all invoices of that period are posted, and before Approve.Claims are first created per invoice line at that line's rate; Cumulate recalculates them on the period's total volume and records the difference as an adjustment claim.
Choosing dates that don't match the agreement's cumulation period, or approving claims still in To be calculated, so the customer is paid at the lower rate.Test: Cumulate adds the adjustment claim
Feature management and licence
Licence or add-in
On the live system, Accounts receivable clerk and Accounts receivable manager use this page.
Checked in Dynamics 365
Solution architect
5Design impact
Shared or per company
Per company: the job works on the rebate claims of the legal entity it runs in; the claims table holds its records per company. Microsoft data model
Can it be undone
Reversible: Recalculated and adjustment claims aren't posted until they are approved and processed. Microsoft Learn
If you change it later
Recalculates claims for the period and adds adjustment claims; nothing is posted. Microsoft Learn
Technical architect
6Technical
Menu item
action:pdsRebateCumulateChecked in Dynamics 365
Form
DialogChecked in Dynamics 365
Roles to set it up and use it
To use itAccounts receivable clerk CustInvoiceAccountsReceivableClerkAccounts receivable manager CustInvoiceAccountsReceivableManagerGive people one of these roles. On this system, 2 roles can run this page.Checked in Dynamics 365
Load order: Cumulate rebates has no data entity in Data management: it is a periodic job and stores no data of its own. The claims it recalculates are covered by the Customer rebates entity (SalesRebateEntity) of the Rebates page.Checked in Dynamics 365