Not obvious until someone looks
Most employees at your clients are paid well above minimum rates. The few who are not are often where problems hide. A young employee turns a year older and moves into a higher rate band, but the payroll rate was not updated. A salaried manager works long hours in a busy month. A care worker's travel time between visits is not in the hours sheet. A deduction for uniforms reduces pay for the period.
None of these stand out in a normal variance report. They show up when an employee complains, or during an inspection.
Why below-rate pay slips through
Minimum rate rules involve more than an hourly rate. Age bands, apprentice rates, the treatment of certain deductions, the pay reference period and which hours count all matter. The payroll software pays what it is told; it does not always know the hours actually worked or the employee's age band change unless someone sets it up.
What counts, and how, is set by the rules, and each client's arrangements, with their adviser, determine how those apply. A bureau cannot decide those questions for a client. It can check the figures it processes against the rates and rules it has been asked to apply, and ask questions when something looks wrong.
What undetected below-rate pay costs
Employees are underpaid, which matters to them first. Clients can face arrears and other consequences if underpayment is found later. The bureau's reputation suffers if clients feel it should have spotted something. And annual rate changes each April create a rush of updates where mistakes are likely.
| Situation | Why it can be missed |
|---|---|
| Birthday moves an employee to a new rate band | Rate not updated on the date |
| Annual rate change | Some employees missed in the update |
| Deductions for uniform or accommodation | Effect on pay not checked |
| Salaried staff with long hours | Hours not recorded in payroll |
| Unreported working time, such as travel or sleep-ins | Not in the client's hours sheet |
How we build a pre-run pay rate check
- You configure the rates and bands to check against, updated each year, and any client-specific settings, such as which deductions to include in the check, as agreed with the client.
- Before each run is signed off, the check reads pay, deductions and recorded hours per employee from your payroll software, and dates of birth to work out the applicable band.
- It calculates effective hourly pay for the pay reference period using your configured approach and flags anyone below the configured rate.
- It flags upcoming band changes from birthdays before the run in which they take effect.
- Salaried employees without recorded hours are listed so you can ask the client for hours where their arrangements require it.
- Flags go to the administrator, who can clear them with a note or send a question to the client. Nothing is changed automatically.
The check is a prompt for review, based on rates and settings you provide. It is not a compliance review, and it cannot promise that pay meets every rule. Clients and their advisers remain responsible for how their pay is structured.
A check that asks the right questions
Below-rate cases are spotted before pay day rather than after a complaint. Birthdays and April rate changes are caught on the right date. Clients get specific, early questions about deductions or unrecorded hours. And the bureau has a record that it checked, which clients appreciate when the subject comes up.
Could this happen in your bureau?
- You have clients with employees paid close to minimum rates.
- Age band changes are updated when someone remembers.
- Deductions such as uniforms or accommodation apply to some employees.
- Salaried staff hours are not recorded in the payroll.
- April rate changes are updated by hand across clients.