Covering a payroll you have never run
The administrator who runs a care company's payroll is off sick in pay week. You hand it to a colleague. They open the payroll file and find a dozen pay elements with names like 'Enh1', 'WE prem' and 'SSP top'. The client's hours sheet says some staff did a sleep-in. Nobody knows how sleep-ins are paid for this client.
The colleague phones the sick administrator, who answers from bed. Or they guess, and the client rings next week because the night staff were underpaid.
Why client pay rules stay in people's heads
Each client's pay rules come from their contracts, policies and history. They are set up in the payroll software as pay elements, but the software records how to calculate, not when to use each element or why. The context, 'weekend premium only applies to support workers, not managers', or 'this client pays enhanced sick pay after six months of service', is knowledge the regular administrator builds up over years.
Writing it down is never urgent. Payroll runs every period, and the person who knows it best has no need of notes.
What undocumented rules cost
Cover becomes risky, so administrators feel unable to take holiday in pay weeks. Errors happen when someone new runs a payroll. Leavers take years of client knowledge with them, and the replacement relearns it through mistakes. And the bureau cannot easily spread work in crunch weeks, because only certain people can run certain clients.
| Rule type | Example of what gets forgotten |
|---|---|
| Overtime and premiums | Which roles get which multiplier |
| Enhanced absence pay | Service thresholds and top-up rules |
| Bank holiday pay | Who is paid for them and how |
| Bonus and commission | When they are paid and on what basis |
| Allowances | Which are taxable elements in the software |
| Client quirks | Who at the client confirms what |
How we build a client pay rulebook
- We read each client's pay elements, rates and settings from your payroll software, and look at recent runs to see which elements are used, by whom and how often.
- A language model drafts a first rulebook from that setup and from past emails with the client, in plain words: 'Weekend premium (WE prem) is paid to support workers for hours worked on Saturday or Sunday'.
- The regular administrator reviews and corrects it, and where needed the client confirms the rules that come from their policies.
- Each run shows the rulebook alongside the processing screen or checklist, so the person running it sees the relevant rules for this client.
- When a new element appears or a rate changes in the software, the rulebook flags the entry for update.
- Rules are dated and attributed, so anyone can see who confirmed a rule and when.
The rulebook describes how the client pays. It does not decide whether the client's policies are correct; that is for the client and their adviser.
Payrolls anyone trained can run
Cover becomes routine: the colleague opens the rulebook, sees how sleep-ins are paid, and processes the run properly. Holidays in pay week stop being a negotiation. New starters learn clients faster. And when an administrator leaves, their knowledge of each client stays behind in a form others can use.
Is your bureau relying on memory?
- Cover for a sick administrator means phoning them.
- Pay elements have cryptic names only one person understands.
- Errors cluster when someone new runs a payroll.
- Clients' pay policies are not written down at the bureau.
- Only certain administrators can run certain clients.