Payout Record is an entity that was introduced much later than Rebate Record, and is intended to solve the problem of calculating and storing the rebate accruals or payouts on an even more granular level.
Info |
---|
There is distinction between:
|
For example, if you need to pre-calculate the rebate money not only for the whole group of customers, but also per each customer, you can use the Payout Record to store such detailed information.
Payout Records allow to store even more fine-grained rebate results than the RR. If, for example, the Rebate Record contains a group of customers and you need to store separately a rebate amount per specific customerId, you can store such numbers into the PayoutRecords.
Sample hierarchy of the objects:
Line item #1 – Negotiated for a group of customers with quarterly payout dates. So you will calculate and approve the rebate separately in 4 rebate records.
Rebate Record – for Q1, for the whole customer group
Payout Record – for Q1, for customer A
Payout Record – for Q1, for customer B
Payout Record – for Q1, for customer C
Rebate Record – for Q2, for the whole customer group
…
Line item #2 – Negotiated for 2 customers with annual payouts.
…
The Payout Records can be reviewed in
, but since their usage is optional and depends on your project needs, you might find the list empty.Fields
Unique Constraints: A combination of three fields – rebateRecordUN, type and name – must be unique.