You are here:
How Do the Fields Work Together in a Rebate Type?
Review the fields in a Program Rebate Type record and understand how they work together to create an incentive structure. You can create a rebate type from the Related tab of a Rebate Program record.
Required Editions
| Available in: Enterprise, Unlimited, and Developer Editions that have Rebate Management enabled. |
Make sure your admin has given you read and edit access to the Program Rebate Type object and a page layout with the relevant fields.
| Field | Description | Key Considerations |
|---|---|---|
| Calculation Type | Decide how to process transaction journal records. You can either calculate payouts on aggregated transaction records for a period, or for each transaction record. | Select Aggregate Based to aggregate the eligible transactions by a member or by member and product. Select Per Transaction to process payout for each eligible transaction. Select Custom if the admin creates a formula to process payouts. Select Growth Based to aggregate the eligible transactions based on the current period and the same period from the previous year. |
| Calculation Definition | Select an active data processing engine definition to process the eligible transactions as per the calculation type. | The admin clones a predefined Data Processing Engine definition, or creates one from scratch. For more information, see Data Processing Engine Templates with Rebate Management. To view the Calculation Definition field, you must have the View Setup and Configuration system permission. |
| Aggregation Object | The object that stores the aggregated values after the data processing engine runs. | Use the default Rebate Member Product Aggregate object, or a custom object defined by the admin. |
| Measure Type | The type of payout benefit you want to offer. |
|
| Measure Field | The field in the specified aggregation object based on which the payout benefit is generated. | If the measure type is Amount per Unit and the benefit qualifier field is:
If the measure type is Percentage of Revenue and the benefit qualifier field is:
If the measure type is Fixed Amount and the benefit qualifier field is:
|
| Benefit Qualifier Field | The field in the selected aggregation object based on which the qualifying benefit value is fixed. | To use the Stepped calculation method, select the same values for Measure Field and Benefit Qualifier Field. |
| Calculation Method | The calculation method for tiered benefits with measure type of Amount per Unit and Percentage of Revenue. |
|
| Product Filter Type | The filter criteria to apply for the products associated with the rebate type. |
|
| Unit of Measure | The default unit of measure associated with the program rebate type. | Optionally, convert the transactions in the Transaction Journal to this unit of measure before processing. |
| Calculation Basis | The basis for rebate payout or accrual amount calculation. |
|
| Accrual Rate | The rate you want to accrue at for the rebate program member. | This rate is in the same unit as the specified measure type, such as percent or amount. |
| Integratable | A checkbox that determines whether the rebate type record is of type template. | When selected, the record is available for integration with any standard or custom object such as a quote, contract, opportunity, or order. Eligible and applied rebates can be viewed for these objects. |
Rebate payout source calculations use BigDecimal for precision-safe rounding, ensuring that stored values, UI display, and API responses remain aligned. Decimal precision is applied consistently across all rebate payout source calculations.
For example, if the total transaction amount is 5,070.75 and a 10% benefit is applied, the rebate is calculated as 507.08, not 507.07. The value remains consistent across stored records, UI display, and API responses.
This feature is available by default for orgs created in Winter ’26. For orgs created before Winter ’26, contact your Salesforce representative to turn on the org value Rebate Management: Big Decimal Precision Enabled (set to 1). Users using the previous calculation method can continue with their existing behavior without making any changes.
Here's an example that explains the difference between Retrospective and Stepped calculation methods.
As per a rebate type, when the transaction quantity is 50 units or less, a member gets a $10 rebate per unit. And, when the transaction quantity is 51 units or more, the member gets a $20 rebate per unit. For the month of January, the member records a total transaction quantity of 75 units.
- If the calculation method is Retrospective, the member is eligible for the second benefit. The total payout is $1500.
- If the calculation method is Stepped, the member is eligible for the second benefit. But the total payout is $500 for the first 50 units and $300 for the next 15 units.

