You are here:
Rebate Configuration Checks
A configuration check reviews whether a rebate program is set up correctly. The check runs before program execution to catch setup errors early and ensure accurate calculations.
Required Editions
| Available in: Enterprise, Unlimited, and Developer Editions that have Rebate and Accrual Management Advanced enabled. |
To start the process, click Check Rebate Configuration in the top-right dropdown of the Program Rebate Type record.
| Check | What It Does | Example Scenario | Fix Guidance |
|---|---|---|---|
| No matching benefit found | Checks if a Program Rebate Type Benefit exists with effective dates covering the relevant period. | No benefit record exists, or no benefit covers the accrual period. | Benefits are optional for advanced accrual calculations. If you specify a flat accrual rate, the engine utilizes that rate. If no accrual rate is specified, the engine falls back to benefit tier values. Add or update benefits only if you intend to use tiered accrual rates. |
| Benefit period and accrual period mismatch | Checks that each accrual period is fully within the effective dates of the assigned benefit. | A benefit fully covers one accrual period but only partially covers another. | Validation flags the partially-covered accrual period. Only the fully covered portion will be calculated. Adjust benefit dates to cover all accrual periods within the rebate program's date range. |
| Benefit dates outside program period | Checks that benefit dates fall within the overall Rebate Program start and end dates. | A benefit has dates earlier or later than the program's dates. | Update the benefit dates so they fall within the rebate program's overall date range. |
| Missing eligibility criteria fields in DPE | Checks that eligibility criteria fields selected on the Program Rebate Type are included in all nodes of the Data Preparation DPE. | An eligibility field (e.g., Product Category) is defined in Program Rebate Type Filter but missing in the DPE data path from the Transaction Journal datasource node through the Input Ingest writeback node. | Add missing eligibility fields to the Transaction Journal datasource node and ensure they flow through all join nodes up to the Writeback to Accrual and Payout Input Ingest DLO node. For step-by-step instructions on configuring field flow through the Data Preparation DPE, see Configure Advanced Rebate and Accrual Pre-Processing - Data Preparation DPE. |
| Missing benefit mapping fields in DPE | Checks that benefit mapping fields (from Program Rebate Type Benefit Mapping records) are included in the Data Preparation DPE. | A benefit mapping references a Transaction Journal field (e.g., Product__c) that isn't selected in the Transaction Journal datasource node or isn't mapped to the corresponding anchor in the writeback node. | Select the benefit mapping source field in the Transaction Journal datasource node and ensure it's mapped to the appropriate anchor (Anchor1, Anchor2, or Anchor3) in the Writeback to Accrual and Payout Input Ingest DLO node. For step-by-step instructions on configuring benefit mapping field flow through the Data Preparation DPE, see Configure Advanced Rebate and Accrual Pre-Processing - Data Preparation DPE. |
Did this article solve your issue?
Let us know so we can improve!
