100% QuebecEvery action taken in the organisation leaves a line: a login, an approved timesheet, a corrected hourly rate, an automatic compilation of punches. The audit trail is that log.
It serves twice. Day to day, to answer “who changed this?” without blaming anyone at random. In an inspection, to show the parity committee the exact chronology of a file.
Before you start
- An administrator account with the “View audit trail” permission.
- 1
Open the console
“Audit trail” sits in the Payroll section of the sidebar. The console opens on the most recent entries, all categories together.
The log is read-only: the interface offers no way to touch up a line, and neither does the API, it only serves reading and exporting.
“System” entries are the automatic ones: punch compilation, reminders, scheduled jobs. - 2
Narrow the search
Three filters combine, and each accepts several values at once: who acted, what kind of action, on which record. The text field searches everywhere: a name, a detail, an identifier.
It is the combination that makes the console useful: “what Nathalie did to timesheets” takes two clicks, with no thousand lines to read.
Filters stack; with nothing selected, everything is kept. - 3
Bound the period
Both bounds accept a date AND a time. For an inspection, the time is what counts: two corrections made the same day are told apart to the minute.
“Reset” clears every filter at once: safer than emptying them one by one and forgetting one.
Left empty, the bounds exclude nothing. Close up: each bound has its own time field, next to its date. - 4
Read an entry
A line carries the timestamp, the author with their identifier, the type of action, the detail in plain language, and a short reference on the right.
The detail is written to be read by a human, not by a machine: “changed Marilou Pelletier's hourly rate” rather than a technical diff.
The identifier in brackets tells two people with the same name apart. The right-hand column is the entry reference: it lets you cite one precise line in a report. What the line does not say
The log names the fields touched, not always their before and after values. To reconstruct a historical amount, the payroll already exported is what governs: see the export history.
- 5
Export
Tick the lines to pull, or tick none: the export then takes everything the filters keep. That is the behaviour to remember: an export launched with nothing selected is not empty, it is complete.
The Excel file is for reworking; the PDF is for handing over as is.
The export follows the active filters, not the page on screen.
What to remember
Who can read the log
Access requires the administrator role AND the “View audit trail” permission. That permission is set per person, and it can be restricted to certain categories of entries only.
Automatic actions are logged like the rest
Punch compilation, note reminders and the billing close appear under the author “System”. A night with no human intervention still leaves a trace: useful to explain a timesheet nobody created by hand.
Go further
Can't find what you're looking for?
Our team can answer your technical questions and support your rollout.
