100% QuebecBetween an employee's punch and their pay, there is a human decision. This is it: someone looks at what was punched, compares it with what was planned, and rules.
Until a timesheet is approved, it enters no payroll export. It is the gate of the whole cycle, and that is why it is handled every week rather than the night before payday.
Before you start
- The “Approve timesheets” permission.
- Hours already submitted: by mobile punch, or keyed in by hand.
- 1
Open the week to review
The page opens on the current week, often empty on a Monday morning: the hours to review are last week's. The arrows on either side of “Today” step back one week at a time.
The summary line gives the number of timesheets, the total hours to be paid, and (in amber) how many are still waiting for a decision. That last figure is the one that has to reach zero before payroll.
The “All statuses” filter isolates the pending timesheets when the week is busy. - 2
Read a line
Each line sets two things against each other: the hours actually punched, and just below, in green, the schedule that was planned. The gap between the two is all there is to review.
The “Paid” column gives the result of the calculation (hours retained and amount) and a badge explains what the decree added, when it added something.
The table scrolls sideways: the per-line actions are on the right. Punched 11:14 – 11:15, planned 8:00 – 16:30, status “Pending”. Why the amount does not always follow the minutes punched
The building-services decrees guarantee a minimum of paid hours to anyone who showed up (four in Montréal, three in Québec City) capped at the length of the planned shift. The “Reporting pay applied” badge says how many minutes that floor added. It is not a punch error: it is the text applying.
- 3
Select what you reviewed
Tick the timesheets you have just read. The bulk approval button only appears once a box is ticked, and it announces how many timesheets it is about to process.
The box in the column header selects the whole displayed week: handy when nothing is off, dangerous when nobody has read it.
Each line also carries its own actions (approve, refuse, correct) to the right of the table. The button counts the selection: no approving blind. - 4
Approve
Approval locks in the pay calculation of each retained timesheet: the rate, the decree and the version in force that day are recorded with it. A later change to the decree will not rewrite that payroll.
The pending counter drops by as much, and the approved lines leave the queue.
The week's total paid hours does not move: approval recalculates nothing, it validates.
What to remember
An approval does not undo with one click
There is no “unapprove” button. Correcting an already approved timesheet goes through a revision, which requires a written reason when the timesheet came from punches: the note tells an owned correction apart from a silent rewrite, and it stays in the audit trail.
Refuse rather than approve
A timesheet that does not hold up gets refused, with a reason. The employee sees it refused in their app and can resubmit it corrected. That beats a correction made behind their back: the trace explains why the hours changed.
What approval unlocks
Only approved timesheets enter the pre-payroll export. One forgotten in the queue does not break the export: it is simply absent from it, and an amber banner says how many were left aside.
Go further
Generating a pre-payroll export
Assemble the columns your payroll software expects, check what goes into the file, and understand what a preview does not freeze.
LireBuilding an employee's schedule
Placing a shift on a site: who, where, when, with which breaks, and reading the total paid hours before saving, not after.
LireCan't find what you're looking for?
Our team can answer your technical questions and support your rollout.
