---
schema_version: "1"
id: 73347d12ff560a3b83956df68de94edb0c1b7e5a95d45cabd7cecdc181d5ee5b
title: Process Dealer Claims and Transaction Journals
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/auto_process_transactions_incentives.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.auto_process_transactions_incentives.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: fd961d3d2d6ea043a114c4599c3b0631bd36ff40f0ba858a0b2d92ae8f055abc
description: Convert retail delivery reports into Transaction Journal records to consolidate the list of all vehicle, part, and accessory sales in your company. For each asset that a dealer sells, you can track key details about the transaction, such as the asset identifier, quantity, date of delivery, and other participating dealer accounts. These Transaction Journal records can power CRM Analytics to help you analyze dealer performance and retail sales. You can also initiate other business processes to determine the dealer’s eligibility for sale-based incentives. You can use Rebate Management to manage the end-to-end incentive lifecycle.
products:
  - Automotive
release: "264"
---
# Process Dealer Claims and Transaction Journals

Convert retail delivery reports into Transaction Journal records to consolidate the list of all vehicle, part, and accessory sales in your company. For each asset that a dealer sells, you can track key details about the transaction, such as the asset identifier, quantity, date of delivery, and other participating dealer accounts. These Transaction Journal records can power CRM Analytics to help you analyze dealer performance and retail sales. You can also initiate other business processes to determine the dealer’s eligibility for sale-based incentives. You can use Rebate Management to manage the end-to-end incentive lifecycle.

### 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.</td></tr></tbody></table>

To populate transaction records in journals for downstream rebate calculations or other reporting purposes, choose a method:

## Convert Rebate Claim records into Transaction Journal records

Capture retail delivery reporting with Rebate Claim records in your Salesforce org and convert these records into Transaction Journal records with Data Processing Engine. To convert rebate claims into transaction journal records, clone and customize the predefined Insert Orders Into Journals data processing engine (DPE) definition. Change the data source from Order to Rebate Claim in the definition and then select the required fields in applicable nodes. To periodically transfer records from Rebate Claim to Transaction Journal, schedule a flow at regular intervals to run the DPE definition.

## Populate Transaction Journal records by using claims from dealers

Dealers can share proof-of-sale documents as CSV files and you can use the ProcessCSV Flow action to either transfer the records to a custom object or directly to the Transaction Journal.

## Transfer data from external systems

If the proof-of-sales is stored outside your org, such as Enterprise Resource Planning (ERP) solutions or dealer management systems, use integration techniques to transfer data to the Transaction Journal object. You can use Bulk API or Data Loader to transfer the data.

#### See Also

- [_Salesforce Help_: Upload Proof-of-Sale Documents and Resolve Errors](https://help.salesforce.com/s/articleView?id=xcloud.admin_rebates_proof_of_sale_and_resolve_errors.htm&type=5&language=en_US)
- [_Salesforce Help_: Insert Invoice Records Into Transaction Journals (Example)](https://help.salesforce.com/s/articleView?id=xcloud.admin_rebates_insert_invoice_records_into_transaction_journals.htm&type=5&language=en_US)