Review audit events
Find, filter, and preserve an organisation audit event with its operational context.
What this is7 sections
Use Organisation Audit to locate recorded activity, inspect the row detail, and preserve only the evidence authorised for the review.
What this is
The audit landing page is category-based. Choose Employee, Time & Attendance, Transactions, Compliance, Payroll, or Documents, then select the relevant log table. Logs expose operational columns such as time, employee/period/run, action/status, actor, references, and sometimes before/after values.
Before you begin
- Confirm the selected organisation and the period, payroll run, employee, document, or transaction involved.
- Define the minimum evidence needed and the authorised reviewer.
- Keep local timestamps and identifiers with the organisation’s review record.
Product navigation
Open Organisation Audit. For workspace-scoped statutory pack history, open Workspace audit when available.
Steps
- Choose a category
On Organisation audit, select the category matching the event’s operational area.
- Filter the log
Select a log table from the category view. Use the available Search, Employee, Action, Status, Actor, From, To, period, or identifier filters; their exact set differs by log.
- Review the table
Review the table’s time, actor, action/status, affected record, and correlation/reference columns. If no rows appear, adjust the selected filters or choose another log in the category.
- Inspect a row
Select the row’s View log row action and inspect the detail, including before/after values or failure information where supplied.
- Correlate the event
Correlate the event with the affected employee, payroll period/run, statutory pack, document/export, or proof bundle in its owning screen. Record the event ID/timestamp and the review conclusion without altering the audit row.
What to check
The event belongs to the intended organisation and category, filters were interpreted correctly, the actor and timestamp are recorded, and any related payroll/output evidence is reviewed separately.
For a statutory pack investigation, compare Organisation Audit → Compliance → Payroll run pack usage with Workspace audit → Compliance → Update history and Installed / available packs. If a log is empty, verify its scope, selected organisation, table, and date filters before concluding that no event exists.
Important boundaries
An audit event proves that the local system recorded activity; it does not prove the underlying data was correct or an official submission was accepted. Audit details can expose personal and payroll information; share the smallest approved excerpt.
Common problems
A flat-log expectation is incorrect for Organisation Audit
Return to the category cards and choose its log table.
An audit category or screen is unavailable
Check persona and workspace scope; ask the owner for access rather than using shared credentials.
An audit row cannot establish the result
Review the owning payroll/document/compliance screen and preserve both references.