Yardi Voyager Audit Trail: View Transaction Change History

In Yardi Voyager, open the transaction, use the Audit or History option (often under Functions or the More menu), then review the log for who changed it, what fields changed, and when. If you do not see Audit/History, the role permissions or database auditing is not enabled, so an admin must grant access or turn on auditing.

 

Where to find audit trail (most common places)

 

• From the transaction screen: Open the exact invoice/receipt/journal entry/payment, then look for Audit, History, Change Log, or Event Log in the top menu, a side panel, or under Functions/More.
• From the module menu: In Payables, Receivables, or General Ledger, open the list/grid, select the item, then use View Audit/View History.
• From Admin/Reports: Some setups expose audit via an Audit Trail report or Security/Activity reporting area.

 

How to run it correctly (so it answers “what changed?”)

 

• Search and open the exact record (same property, same batch, same document number). Audit is record-specific.
• Filter by date range around the suspected change. If available, also filter by user.
• Look for entries like Edit, Post, Unpost, Void, Reverse, Delete. These are the actions that explain balance changes.
• Open the detail line to see field-level changes (example: amount, GL account, vendor, invoice date, check number).

 

Terms explained (quick and plain)

 

• Audit trail: A log of actions taken on a record (who/when/what action).
• Change history: The before/after values for specific fields.
• Posted: Finalized to the ledger; affects financial reports.
• Unposted: Pulled back from the ledger; reports may change.
• Void/Reverse: Cancels a transaction; may create offset entries.

 

Common “it’s missing” causes (even if everything else is set up)

 

• No permission: The user role lacks audit/history access. Fix: admin updates role security.
• Auditing not enabled for that table: Some databases only audit certain record types. Fix: Yardi admin enables auditing for the needed area.
• Change happened via batch/process: Look for batch posting, imports, or automated routines; audit may show the process name instead of a person.

 

Validate and troubleshoot

 

• Cross-check the audit timestamp with batch ID, post month, and user to confirm it matches the report change.
• If audit shows Delete but no details, pull related logs/reports (batch register, posting report) to reconstruct.
• If there is no audit at all for a record that definitely changed, stop and escalate: it usually means auditing was off or access is blocked.

 

When to contact support/admin

 

• You cannot find Audit/History anywhere for transactions you should access.
• You need field-level before/after values but only see high-level actions.
• You suspect changes from an integration/import and need the source identified.