Run a Rebate Program for AMER and LATAM Partners (Example)

Program Specifications

The automotive company designs a partner incentive structure with the following requirements:

• Duration: Full calendar year (January 1, 2026 to December 31, 2026).
• Liability Frequency: Calculated monthly to ensure precise corporate forecasting and P&L liability accuracy.
• Data Processing Engine: Execution Type set to Advanced to securely offload high-volume ERP transaction calculations to the Data Cloud platform.

Create the Program and Add Partners

The company creates a rebate program for partners in two regions and aims to increase the sales of two top-selling products.

Create Accrual Periods

• Navigate to the Rebate Program Accrual Periods related list on the newly created record.
• Click New to manually add 12 consecutive monthly records spanning from January 1, 2026 to December 31, 2026.

Enroll Members

• Navigate to the Members related list.
• Click Add Member List and select the predefined Accounts List View containing all verified LATAM dealer accounts.
• Click Add Member to individually lookup and attach the two unique AMER partner accounts.

Note Ensure each account has a unique identifier in the field designated as the Source Matching Field (MemberID) that matches the transaction data.

Create the Volume-Based Rebate Type

Navigate to the Program Rebate Types related list and click New to define the calculation rules. Create the volume-based rebate type with these specifications:

Note Leave the Calculation Definition field blank. Advanced calculation runs using independent Data Cloud transforms.

Create Benefit Mapping

Benefits for the rebate type differ across two products: Grand SUV and Classic Sedan. In the Advanced engine, Product is the criteria used as an Anchor to vary benefits. Ensure that Product is an available field on both the Transaction Journal (Source) and the Program Rebate Type Benefit (Target) objects.

Create a new record under Program Rebate Type Benefit Mappings:

Add Benefits

Create the benefit tiers for the two products. Because you have mapped the Product field, the engine applies product-specific accrual rates based on transaction volumes.

• For Grand SUV, the benefits are scaled based on the total transaction quantity.
• For Classic Sedan, a flat accrual is offered on achieving a quantity threshold.

Accrual Calculation

The admin executes the Data Processing Engine definitions to calculate accruals. The jobs must run in this exact operational order:

• Advanced Rebate and Accrual Pre-Processing - Rule Configuration DPE: Generates the foundational metadata and qualification logic needed for the engine to calculate accruals.
• Advanced Rebate and Accrual Pre-Processing - Data Preparation DPE: Ingests transactions, rebate programs, and benefit rules into the specific Data Lake Objects used by the engine.
• Accrual and Payout Engine - Delta Calculation DPE: Identifies transactions that fall within specific benefit dates to determine which new or modified records are eligible for calculation.
• Accrual and Payout Engine - Rule Processing DPE: Executes the actual financial calculations to generate accruals for the qualified transactions.
• Advanced Rebate and Accrual Post-Processing - Source Generation DPE: Aggregates calculated results to create the required accrual member and rebate type records and sources.
• Advanced Rebate and Accrual Post-Processing - Status Update DPE: Finalizes the process by updating the accrual period status and the last calculation date.

Accrual Calculation Output

After the admin runs the six DPE definitions in sequence, the engine generates Program Rebate Type Accrual Source records for each member per product per accrual period. The following table shows the calculated accrual output for January 2026.

These records roll up into the Rebate Program Member Accrual object, giving the finance team a consolidated view of total accrued liability per member for the period.