---
schema_version: "1"
id: 577ee83f22e62cfeb3aa099ad6e33c28e817f37de4a83dc34876fd81c16c95d0
title: Create a Transaction Journal
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/chrm_cpit_create_transaction_journal.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.chrm_cpit_create_transaction_journal.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 06afb9da37ef437ae3852f2ca51975199e25ca5a9cbba2d7059b8e39727ac4e6
description: Use transaction journal records to capture information stored in sale documents such as orders, invoices, and shipments. This information is processed to update the Partner Unsold Inventory (PUI) records. A PUI record is created for each sale document, reflecting the original product quantity in the sale document.
products:
  - Partner Cloud
  - Cross Cloud
  - Manufacturing
release: "264"
---
# Create a Transaction Journal

Use transaction journal records to capture information stored in sale documents such as orders, invoices, and shipments. This information is processed to update the Partner Unsold Inventory (PUI) records. A PUI record is created for each sale document, reflecting the original product quantity in the sale document.

### 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>Professional</strong>, and <strong>Unlimited</strong> Editions with the Channel Revenue Management add on</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
          <col>
        </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="d24014e61">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d24014e61 ">To create transaction journals</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d24014e61 ">Channel Partner Inventory Admin User</td>

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

To track this inventory, create Partner Unsold Inventory (PUI) records by running the Data Processing Engines (DPEs) that accurately calculate the remaining quantity of inventory. This data is used to create the partner unsold inventory and partner unsold inventory ledger records.

![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 We recommend that you add the Account, Product, Quantity, Price, and Journal Type information while creating a transaction journal record.

1. From the App Launcher, find and select **Transaction Journals**.
2. Click **New**.
3. Search for an existing account or create an account.
4. In the Journal Type field, select **Sale Document** when selling inventory to a partner.
5. Select the Activity Date.
6. For the Status field, select **Pending**.
7. Select a product and price type.
8. Enter the quantity of products sold in that transaction.
9. Enter an amount in the Sale Unit Price or Resale Unit Price field.
10. Enter the transaction amount for this transaction.
11. Save the record.

![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 creating a Transaction Journal in an org where both Rebate Management and Channel Partner Inventory Management are enabled:

- Specify the Journal Type for Channel Partner Inventory Management. The Journal Type determines how the Transaction Journal is used within Channel Partner Inventory Management processes. If the Journal Type is left blank during creation, the system defaults the Usage Type to Rebates.
- Configure DPE filtering on Status for Rebates Transaction Journals. Rebates DPEs do not automatically exclude records based on the Transaction Journal Status field. If customers intend to use the Status field (for example, Approved, Rejected, or Pending) to control which records generate aggregates or payouts, they must explicitly configure filters in the Rebates DPE definitions. For example, to ensure that only eligible records are processed and to exclude any status other than Approved (such as Pending or Rejected), include filter logic such as: TransactionJournal.Status = 'Approved'.
- Review legacy records for compatibility. If existing Rebates Transaction Journal records default to a Pending status, note that DPEs do not filter by Status by default and will process all PoS transactions. Ensure that the appropriate DPE filter logic is configured so that the correct records are processed and unintended records are not included or excluded.