The quick answer
Open View Audit Trail, choose the action and transaction type you need, then submit the filters. Check the returned row’s date, user, action, and transaction context before exporting the result. Open the transaction’s System Notes separately when you need a changed field and its old and new values.
The screenshots use sample values and fictional names. Your available filters and history depend on your role, account settings, and the records you can access.
Before you start
You need access to the audit-trail view and enough record access to investigate the transaction. Decide which transaction type, action, user, and date range you are investigating. This page reviews transaction-level activity; it is not a general script or integration log viewer.
01. Filter the audit trail
Open Transactions > Management > View Audit Trail. Navigation and access can vary by role. Set Action to the change you are investigating and choose the relevant Transaction Type. The recorded example uses CHANGE and Purchase Order. Use available filters relevant to the investigation, such as Users, dates, Amount, Account, or Name. Then select Submit to apply the filters.
02. Confirm the matching change
Read the result row from left to right. Check the columns verified on this page: Date/Time, Username, Action, Type, Internal ID, Document Number, Transaction Number, Post Date, Account, and Amount. These are transaction-level columns. For field-level history, open the transaction’s System Notes or an appropriate System Notes search; that follow-up is outside the recorded steps. The example results contain several actions and transaction types, so they do not prove that the requested filters carried over. If the row is not the right change, return to the criteria and narrow the filters rather than treating a similar-looking result as evidence.
Check the result
- The displayed actions and transaction types must match your intended criteria; check them before relying on the report.
- The relevant row identifies the intended transaction and user.
- The action, date, and transaction context match the investigation; field-level detail requires a separate System Notes review.
03. Export the result when needed
The dated account inspection confirmed Export - CSV and Export - Excel on this results page. Use an available export action only after the filtered rows answer the question you are investigating. Keep the filter choices with the exported file or case note so another reviewer can reproduce the result. An export reflects the visible result set at the time you create it; it does not prevent later changes to the transaction history.
Common questions
What does the View Audit Trail show?
It shows recorded changes that match the filters you apply. A row identifies transaction-level context such as date and time, user, action, transaction references, account, and amount. Field names and previous and updated values require System Notes detail or a suitable System Notes search. The exact columns and available history can vary by account and permissions.
Why is the change I need not in the results?
Check the transaction type, action, date range, and record access first. A narrow filter can exclude the row, and your role may not have access to every transaction or audit-history entry.
Can I export an audit-trail result?
The inspected results page has CSV and Excel export actions; availability can depend on the interface and permissions. First confirm that the result rows and filters match your investigation. Keep the filter context with the export because the same page can return different rows when the filters or account data change.