---
schema_version: "1"
id: 842e0a6b7f7e75a678c9209b8c00888db14b6ea4a02844981c52bec13ba47c93
title: Inventory Transaction Audit Trail
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/it_srvcs_asset_mgmt_txn_audit.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.it_srvcs_asset_mgmt_txn_audit.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d2d05f8034dd79fbb277bde4bdd59b645590de2f3498953acd895ed720a7a83b
description: Maintain data integrity and visibility across asset-based inventory by using an automated double-entry transaction engine. By separating physical stock movements from state-bucket changes, IT Hardware Asset Management tracks inventory transitions while preserving auditability for finance reconciliations and compliance investigations.
products:
  - Service Cloud
  - Agentforce IT Service
release: "264"
---
# Inventory Transaction Audit Trail

Maintain data integrity and visibility across asset-based inventory by using an automated double-entry transaction engine. By separating physical stock movements from state-bucket changes, IT Hardware Asset Management tracks inventory transitions while preserving auditability for finance reconciliations and compliance investigations.

### 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: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions with Agentforce IT Service.</td></tr></tbody></table>

## Dual-Ledger Data Model: PIT vs. PIAT

To support granular asset tracking across lifecycles, the inventory engine automatically logs quantitative changes by using two platform objects:

- **Product Item Transaction (PIT):** Standard object that tracks physical inventory movement in and out of a location by recording changes directly to **Quantity On Hand**.
- **Product Item Additional Transaction (PIAT):** Standardized object that tracks internal status shifts within state buckets, including **Quantity Allocated**, **Quantity Soft Reserved**, **Quantity Damaged**, and **Quantity On Hold**.

## Asset Location & Product Item Hierarchy

- **Location:** Base site record configured with **Usage Type** set to **Asset-based**.
- **Product Item:** Represents inventory stored at a specified location.

## Transaction Engine Architecture

Quantitative stock changes on a Product Item split into two specialized transaction objects based on movement type:

  
| Object Record | Inventory Metric Tracked | Transaction Scope |
| --- | --- | --- |
| Product Item Transaction (PIT) | Quantity On Hand | Records physical stock increases or decreases moving in and out of the location. |
| Product Item Additional Transaction (PIAT) | State Quantity Buckets | Logs internal state shifts, including Quantity Allocated, Quantity Soft Reserved, Quantity Damaged, and Quantity On Hold. |

## Polymorphic Lookup Association

Both PIT and PIAT ledger entries use the polymorphic lookup field **RelatedRecord** to link inventory transactions back to the originating operational record:

- Asset Activity
- Fulfillment Order Line Item
- Return Order Line Item
- Product Transfer
- Inventory Item Reservation

**Inventory transaction relationships**

![Diagram showing how PIT and PIAT ledger entries relate to originating operational records through the RelatedRecord polymorphic lookup.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-it_service-264-0-0-production-enus/0a574a10-4c7a-4681-aacf-0767f8beaad4/it_service/images/it_srvcs_asset_mgmt_inv_rlshp.png)

## Movement Transactions

Physical updates alter total inventory counts at a location or transfer hardware between locations. These actions generate a **Product Item Transaction (PIT)** entry to update **Quantity On Hand**.

- _Examples:_ Receiving a vendor shipment, dispatching a product transfer to a stockroom, or marking an asset as disposed.

## State Change Transactions

Internal status changes shift inventory between operational states without moving physical stock out of a location. These actions generate a **Product Item Additional Transaction (PIAT)** entry to update designated state quantity buckets.

- _Examples:_ Soft-reserving inventory for a request, allocating stock to an order, or marking stock as defective.

## Formula Fields and Audit Behavior

Calculated inventory fields, such as **Quantity Available**, don’t directly generate transaction records when values change. Because **Quantity Available** is a formula field derived from **Quantity On Hand** minus state allocations, PIT and PIAT ledger entries fully capture underlying changes. Double-entry transaction records preserve complete audit trails.