You are here:
Rebate and Accrual Management Advanced Data Model
Learn about the objects in the Rebate and Accrual Management Advanced data model.
Required Editions
| Available in: Enterprise, Unlimited, and Developer Editions that have Rebate and Accrual Management Advanced enabled. |
The advanced architecture introduces a specialized data model to bridge Salesforce Core with Data Cloud:
- Core Entities: Objects like Rebate Program Accrual Period and Accrual Source store the final calculated results for financial reporting.
- Data Lake Objects (DLOs): Ingested metadata (Rule Meta, Input Meta) and transaction data reside in Data Cloud for high-speed processing.
- Execution Type: A new field on the Rebate Program determines if the program uses "Classic" logic or the "Advanced" Data Cloud engine.
Define an Incentive Structure
Use these objects to design the framework:
- Rebate Program: Name, description, payout frequency, and validity of a rebate program. It's a top-level object that shares a primary-detail relationship with the Rebate Program Payout Period, Rebate Program Member, and Rebate Program Type objects.
- Rebate Program Payout Period: Information about dates and periods that payouts are calculated for. The duration of a payout period depends on the payout frequency and validity of a program. For a monthly program valid for a year, this object holds 12 payout period records. For a custom frequency, the number of records is user-defined.
- Rebate Program Member: Information about the accounts that are enrolled in a rebate program as members. The transactions of active member records are eligible for payout calculations. Account is a lookup object in Rebate Program Member.
- Program Rebate Type: Information about the type of incentives offered through a rebate program. A rebate type record includes information about which payout type is offered, how transactions are aggregated, and how payouts are calculated.
Add Granularity to Incentives
Use these objects to define the granular details and rules:
- Program Rebate Type Benefit: Rebate attainment threshold information for a member. Decide maximum and minimum values for a range, and then define the benefit value for each range.
- Program Rebate Type Aggregation: Defines custom aggregation dimensions (anchors) beyond the default Member and Product grouping. Maps Transaction Journal fields to custom anchors (Anchor1, Anchor2, Anchor3) to enable multi-dimensional accrual tracking by Region, Territory, Channel, or other business criteria.
- Program Rebate Type Benefit Mapping: Field mappings between the Transaction Journal and Program Rebate Type Benefit objects. If the benefits vary by criteria, such as Product, Category, or Region, use these mappings to enable multi-dimensional accrual tracking in Data Cloud.
- Program Rebate Type Filter: Rules that determine eligible member transactions for rebate payouts. The object is also used in predefined data processing engine definitions that process the transaction journal records.
- Program Rebate Type Product: Association of product records with a program rebate type record. Based on the products excluded from or included in a rebate type, only transaction records for eligible products are considered for payout processing.
- Program Rebate Type Reference: Association of eligible rebate types with a target record for standard or custom objects. The Program Rebate Type Reference is a junction object that connects an integrable Program Rebate Type record with another object's record. Examples of target objects: Contract, Opportunity, Quote, Order, and Sales Agreement.
- Unit of Measure Conversion: Information on the unit of measure used in transactions, the unit of measure to use for payouts, and the conversion factor. The Unit of Measure Conversion is a junction object between Unit of Measure and Program Rebate Type.
Manage Transactions and Calculations
Use these objects to manage transactions, aggregation logic, and other processes that help you to calculate payouts:
- Transaction Journal: Transaction records of rebate program members that are used for processing payouts at the end of each period. You can add transaction records to the Transaction Journal from external systems, from existing objects, or from claims submitted by partners.
- Received Document: CSV files that contain claims submitted by partners through the Experience Cloud site. These claims are validated and then converted into Transaction Journal records for payout processing.
Track Accruals
Use these objects to track financial liabilities recognized for rebate programs before actual payout occurs:
- Rebate Program Accrual Period: Time periods for which accruals are calculated based on the accrual frequency defined in the program. For a monthly accrual frequency in a yearly program, this object holds 12 accrual period records.
- Rebate Program Member Accrual: Aggregated accrual amount calculated for a member for a specific accrual period across all rebate types.
- Program Rebate Type Accrual: Accrual amount calculated for a member for a specific accrual period, with separate rows for each rebate type. The values of all rows aggregate to a single row in the Rebate Program Member Accrual object.
- Program Rebate Type Accrual Source: Accrual amount calculated based on transaction data processed through the Data Cloud engine. These records are synced back from Data Cloud to Salesforce Core during the Post-processing (Source Generation) DPE run.
- Rebate Program Member Accrual Adjustment: Manual adjustments made to member accrual records by finance teams to account for mid-period changes or corrections.
Did this article solve your issue?
Let us know so we can improve!
