Rebate transaction data, aggregation and payout approval
Key Takeaway
Transactions go into the Transaction Journal, DPE definitions roll them up into Rebate Member Product Aggregate records, and scheduled flows turn those into member payouts that are finalized on the payout calculation date and then approved.
Rebate Management rewards partners who hit agreed sales targets by turning their sales transactions into rebate payouts. Transactions are collected in a journal. Data Processing Engine definitions then filter them and roll them up into aggregate records, and scheduled flows calculate member payouts from those aggregates. When a payout period ends, the payout is finalized, can be adjusted and approved, and is then settled in a financial system. Configuring rebates means choosing where transaction data comes from, how it is aggregated, and how payouts are calculated and approved.
The payout pipeline
Rebate payouts move through a pipeline. Transaction Journal records are the input to the calculation. The output lands in member payout records.
- Transaction data goes into a journal.
- DPE definitions filter and aggregate the data.
- Scheduled flows calculate member payouts from the aggregated data.
- Managers review the payouts, adjust them if needed, and approve them.
- Approved payouts are settled in a financial system.
Payouts are calculated per payout period. Program managers set the program's payout frequency to monthly, quarterly, or yearly. The Rebate Program Payout Period object holds one record per period, so a monthly program valid for a year has 12 payout period records.