SAASInventory

Audit Trail

Every inventory transaction in Inventory Pro-every receive, issue, move, and adjustment-is permanently recorded in the audit trail. This complete transaction history answers the critical questions: “Where did this stock go?” and “Who made that change?”

Access MethodPath
Via DocumentsInventoryDocumentsAudit Trail
Via ReportsReports → Type: InventoryAudit Trail
Item HistoryInventory OverviewHistory icon (magnifying glass)

What Gets Tracked

The audit trail records all stock movements and changes:

Transaction TypeExamples
ReceivingPO receipts, direct receives, appointment receives, transit receives
IssuingSO issues, direct issues, work order issues
MovingLocation moves within warehouse
TransitsInter-warehouse transfers (ship and receive)
LeasingLease out, lease returns
Cycle CountsAdjustments from cycle count posting
Work OrdersComponent issues, assembly receipts
AdjustmentsManual stock corrections

Recorded Information

Each audit trail entry includes:

FieldDescription
Date/TimeWhen the transaction occurred (timestamp)
UserWho performed the transaction
Transaction TypeReceive, Issue, Move, Transit, etc.
WarehouseWarehouse affected
LocationBin/location involved
Item IDPart number
DescriptionItem description
UnitsQuantity affected
Serial/LotSerial or lot number (if applicable)
ReferencePO#, SO#, WO#, Transit Slip#, etc.
Reason CodeAdjustment code (for direct receives/issues)
RemarksAny notes entered on the transaction

Key Characteristics

  • Permanent: Cannot be edited or deleted
  • Automatic: Every transaction is logged without user action
  • Complete: All transaction details preserved
  • Timestamped: Exact date and time recorded
  • User-tracked: Shows who performed each action

Filtering the Audit Trail

Filter the audit trail to find specific transactions:

FilterUse For
Date RangeTransactions within time period
Item IDAll transactions for specific item
UserTransactions by specific person
WarehouseTransactions at specific location
Transaction TypeOnly receives, only issues, etc.
ReferenceSpecific PO, SO, or WO number
SerialTrack specific serialized unit

Transaction Types

TypeCodeDescription
Receive1Stock added (PO, direct, transit)
Issue-1Stock removed (SO, direct, WO)
Move2Location change (same warehouse)
Transit Ship2Sent to another warehouse
Transit Receive1Received from another warehouse
Lease Out3Leased to customer
Lease Return-3Returned from lease
Cycle Count Adj+/-7Adjustment from cycle count
Split99Lot/serial split operation

Reference Number Prefixes

The Reference field links transactions to source documents:

PrefixDocument Type
PO-#####Purchase Orders
SO-#####Shipping Orders
WO-#####Work Orders
TR-#####Transit Slip
AP-#####Appointment
CC-#####Cycle Count
RX-#####Direct Receive Reference
IX-#####Direct Issue Reference

Common Use Cases

Investigating Cycle Count Discrepancies

When cycle counts show variances:

  1. Filter by Item ID
  2. Review recent transactions
  3. Look for unreported receives or issues
  4. Check for user errors or missing documentation

Tracking Serialized Items

For serialized inventory:

  1. Filter by Serial number
  2. See complete history: receive → moves → issue
  3. Identify current location
  4. Verify chain of custody for warranty or compliance

User Activity Review

To review user actions:

  1. Filter by User name
  2. Set date range
  3. Review transaction types and volumes
  4. Identify training needs or patterns

Order Verification

To verify order fulfillment:

  1. Filter by Reference (PO# or SO#)
  2. Confirm all lines were processed
  3. Check timestamps for timing
  4. Verify correct quantities and locations

Location History

To see what happened at a location:

  1. Filter by Warehouse and Location
  2. Review all in/out transactions
  3. Identify patterns or issues
  4. Support slotting decisions

Exporting and Printing

  • Click Export to download as CSV for external analysis (opens in Excel)
  • Click Print for printer-friendly format including all visible columns
  • Exports respect current filters

Reason Codes

For direct receives and issues, reason codes explain why:

Positive Adjustment Codes (Receives):

  • PO Receipt
  • Found during Count
  • Customer Return
  • Transfer In
  • Correction

Negative Adjustment Codes (Issues):

  • SO Issue
  • Lost/Missing
  • Damaged
  • Scrapped
  • Sample
  • Correction

See the Receiving Stock documentation for more on Positive Adjustment Codes and the Issuing Stock documentation for Negative Adjustment Codes.

Best Practices

  • Regular Review: Check audit trail periodically for anomalies
  • Use References: Include meaningful references on transactions
  • Add Remarks: Document unusual transactions in remarks field
  • Export Regularly: Archive audit trail data for long-term retention
  • Train Users: Ensure staff understand their actions are logged

On this page