When partners purchase your products, the transactions are recorded as claims and
invoices. These transactions are used as inputs for rebate payout calculations. Retrieve
transaction data of your org from Salesforce objects such as Orders, from partners
submitting claims via the Experience Cloud site, and from external systems.
Required Editions
| Available in: Enterprise, Unlimited, and
Developer Editions that have Rebate Management
enabled.
|
To store all transaction records for member accounts, use the Transaction Journal object.
If you need additional information such as account territory, invoice status, and
product category for rebate processing, add custom fields to Transaction Journal.
To populate transaction records in journals for downstream rebate calculations, use any
one of these methods.
- Convert Orders in your Salesforce org into Transaction Journal records. To convert
orders into transaction journal records, clone and customize the predefined Insert
Orders Into Journals data processing engine (DPE) definition. To use an object other
than Order, change the data source from Order to the relevant object in the
definition and then select the required fields in all applicable nodes. To regularly
transfer records either from orders or from the custom object to Transaction
Journal, schedule a flow at regular intervals to run the Insert Orders Into Journals
definition.
- Populate supplier invoices and claims submitted by partners in Transaction Journal
records as proof of transaction documents. Partners upload the documents as CSV
files by using the Experience Cloud site. You can use the ProcessCSV API action to
either transfer the records to a custom object or directly to Transaction
Journal.
- Transfer data from external systems, such as Enterprise Resource Planning (ERP)
solutions, to the Transaction Journal object by using either integration techniques
or standard Salesforce methods such as Bulk API or Data Loader.
