---
schema_version: "1"
id: fc4af4f6c1e792b1004edd0b457a938c3a9948fe9edcd3669d878f907bf3d99f
title: Refine Accruals with Benefit Mappings
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/admin_rebates_adv_refine_benefit_mappings.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.admin_rebates_adv_refine_benefit_mappings.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5c9a635e664f4259e253fa9b703da5c4614f870c28cdaf8ed77574e060de57b7
description: Use benefit mappings to create benefits for a rebate program that vary by additional criteria such as product category, partner territory, member enrollment status, and industry segment. For example, a volume-based rebate type can have benefits in which the accrual amount varies by product category for the same benefit tier.
products:
  - Partner Cloud
  - Cross Cloud
  - Manufacturing
release: "264"
---
# Refine Accruals with Benefit Mappings

Use benefit mappings to create benefits for a rebate program that vary by additional criteria such as product category, partner territory, member enrollment status, and industry segment. For example, a volume-based rebate type can have benefits in which the accrual amount varies by product category for the same benefit tier.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions that have Rebate and Accrual Management Advanced enabled.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d6144e61">User Permissions Needed</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d6144e61 ">To create custom objects and fields:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d6144e61 ">System Administrator</td>

        </tr>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d6144e61 ">To set up Rebate and Accrual Management Advanced:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d6144e61 ">Advanced Rebate and Accruals Admin permission set</td>

        </tr>
      </tbody>
    </table>

To create a benefit mapping, Salesforce recommends that the admin first creates similar custom fields on the Program Rebate Type Benefit and Transaction Journal objects.

In the Advanced engine, the system uses anchors within Data Cloud to group transactions for accrual calculations. You configure grouping by adding Program Rebate Type Aggregation Field records to the rebate type, each record specifies one aggregate field.

By default, the engine aggregates by Member only, using a single Aggregation Field record with the aggregate field set to Member. To aggregate by Member and Product, complete both of these steps:

- Add a second Aggregation Field record with the aggregate field set to Product.
- Customize the Pre-Processing DPE so that the Product anchor is set.

For steps to customize the Pre-Processing DPE to set the Product anchor or a custom anchor, see [Extend Accrual Aggregation with Custom Anchors](https://help.salesforce.com/s/articleView?id=xcloud.rebates_adv_custom_anchors.htm&type=5&language=en_US).

The engine supports up to five aggregation anchors in total — Account and Product as built-in dimensions, and three custom anchors (Anchor1, Anchor2, Anchor3).

To track accruals by additional dimensions such as Region, Territory, or Channel, use the custom anchors (Anchor 1, Anchor 2, Anchor 3) to create custom aggregation criteria. The admin must ensure these custom fields are mapped to the corresponding Data Lake Objects (DLOs) during setup.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-channel_revenue_mgmt-264-0-0-production-enus/0afcbbd8-b325-4d62-baa1-63243d1c10aa/images/icon_note.png)

Note Unlike Classic Rebate Management (which mapped via Rebate Member Product Aggregate), the Advanced engine uses the Payout Source Field on Benefit Mappings. This enables direct mapping between payout source attributes (such as Product or Product ID) and benefit fields for both Data Cloud calculations and embedded features.

## Example

A company wants to differentiate the benefits of a volume-based rebate type by Product Category. The admin must ensure the Product Category information is available on the Transaction Journal and the Program Rebate Type Benefit record.

   
| Object | Field | Data Type | Objective |
| --- | --- | --- | --- |
| Program Rebate Type Benefit | Product Category | Lookup | Enables the program manager to define distinct benefit values and accrual rates for specific product segments within the same benefit tier. |
| Transaction Journal | Product Category | Lookup | Provides the source data for the engine to match against the benefit criteria. |
| Payout Source | Product | Lookup | Provides the field on the payout source mapped directly to the benefit criteria in Advanced Rebates. |

The program manager then maps these fields in the Program Rebate Type Benefit Mapping object. The engine uses this mapping to "Anchor" the calculation to the specific product category during the high-volume processing in Data Cloud.

To capture product category information, the program manager can define benefit tiers as shown below.

- Source Field: The field on the Transaction Journal that serves as the source criteria.
- Benefit Field: The field on the Program Rebate Type Benefit that defines the qualifying criteria.
- Payout Source Field: The field on the Payout Source object (e.g., Product) used in Advanced Rebate Management to map payout data directly to benefit criteria.

    
| Benefit Tier | Minimum Value | Maximum Value | Benefit Value | Product Category |
| --- | --- | --- | --- | --- |
| Tier 1 | 101 | 500 | $3 per unit | Hammers |
| Tier 2 | 501 | Leave it blank | $8 per unit | Hammers |
| Tier 3 | 101 | 500 | $5 per unit | Compactors |
| Tier 4 | 501 | Leave it blank | $10 per unit | Compactors |

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-channel_revenue_mgmt-264-0-0-production-enus/0afcbbd8-b325-4d62-baa1-63243d1c10aa/images/icon_note.png)

Note When the engine matches transaction data to benefit mapping criteria, only exact matching is supported. For example, if a benefit is mapped to Product Category "Compactors", only transactions where the Product Category field exactly equals "Compactors" are matched to that benefit. If no exact match is found, benefit isn't applied to the transaction.