100% QuebecIn Clic Horaire, an employee's hourly rate is not a free field. It descends from the job class their decree assigns them: class A, B or C under CPEEP, and each class carries the floor rate negotiated for the current year.
That is on purpose. The day the parity committee publishes a new grid, you update the grid once and everyone follows: nobody is left under the floor because a record was forgotten.
Paying someone above their class is of course still possible. It is called a rate exception, and it is what this procedure does.
Before you start
- An administrator account, or a supervisor with the “Manage users” permission.
- The right to see financial data: without it, the rate field does not even appear.
- 1
Open the employee list
In the sidebar, unfold “Team” then choose “Employees”. The list shows the whole workforce of the active organisation, including people still waiting for their invitation.
The Team section gathers employees, supervisors and administrators. - 2
Find the person
The search field accepts a name, an email or an employee number. Across several hundred people, the number is the safest: two employees can share a surname, never a number.
Click anywhere on the line to open the record.
The “Hourly rate” column already shows each person's current rate. - 3
Open the “Payroll & banks” tab
The record is split into five tabs. Everything touching pay (decree, class, rate, leave banks, direct deposit) lives in “Payroll & banks”.
The tabs of an employee record. - 4
Understand where the shown rate comes from
The “Hourly rate” field is greyed out, with the mention “inherited from the class” beside it. That is not a bug: the employee class selected just above imposes its base rate, and that rate updates by itself when the decree's grid changes.
In the example, Marilou Pelletier is in class C, whose base rate is $23.90/h. As long as nothing is done, she is paid $23.90/h: and she will stay so after the next grid increase, at the new value.
The rate follows the class: the field is read-only. Close up: “inherited from the class” beside the label, and the base rate reminder under the field. Change the class rather than the rate
If the person truly changed roles (from light maintenance to heavy work, say) correct their class, not their rate. The rate will follow, and the audit trail will say why it moved.
- 5
Open the rate exception
Tick “Custom rate (exception)”. The box changes nothing on its own: it unlocks the rate field for this person, and for them only.
Unticked, the rate follows the class. Ticked, it becomes editable. The box and its explanation, at a readable size. - 6
Enter the new rate
Type the hourly amount. The app refuses to save a rate below the class base rate: an exception is for paying more, never less than the decree floor.
The field arrows step by $0.25. A rate under the floor is rejected
If the amount entered falls below the class base rate, the form says so in red and blocks saving. To pay less, the class itself has to be lower: which is an entirely different decision.
- 7
Save
The button sits at the foot of the form. One save writes the whole record: if you had other corrections in progress in the other tabs, they go out at the same time.
Saving validates the entire record, all tabs together. - 8
Check it in the list
Back in the list, the line shows the new amount, and the “custom” mention under the rate is the reminder that it no longer follows the class. That marker is what will tell you later why this person did not move during a grid increase.
“Custom”: the rate is now independent of the class. The line up close: $25.50 in black, “custom” in amber just below.
What to remember
What the change touches
The new rate applies to hours not yet approved. An already approved timesheet keeps the calculation frozen at the moment of its approval: correcting a rate today does not rewrite a payroll already validated.
What the audit trail keeps of it
Saving writes an “Employee modified” entry naming the fields touched (here the hourly rate) with its author and timestamp. The trace says who changed what and when; to find the previous amount, the payroll already exported is what governs.
A custom rate no longer follows increases
An exception freezes the person outside the grid: the next decree update will not touch them. If the gap is meant to hold over time, you have to come back to the record at every increase: or untick the exception to bring them back in line.
Go further
Can't find what you're looking for?
Our team can answer your technical questions and support your rollout.
