Can you pay her today?
A client rings on a Tuesday: an employee was underpaid last Friday because the overtime was missed, and they need it paid today. Another wants a leaver's final pay out before the next run. A third wants to pay a bonus mid-month. Each request lands on an administrator already in the middle of scheduled runs.
The payment is processed quickly, sometimes without the usual checking, and sent. Later, the corresponding submission is found to be missing, the figures do not agree with the next regular run, and nobody remembered to charge for it.
Why off-cycle work is disruptive
It arrives outside the calendar, so it competes with planned work. It is urgent by definition, which pushes people to skip steps. It often exists to fix an earlier error, which means the pressure is on. And it is rarely logged in the same way as scheduled runs, so its effect on submissions, pensions and billing is easy to miss.
Some requests are genuinely urgent. Others could wait for the next run, but nobody asks, because saying no to a client feels hard in the moment.
What unmanaged off-cycle work costs
Planned runs get squeezed, which introduces risk into other clients' payrolls. Rushed off-cycle payments create their own errors. Missing or late submissions follow. Pensions for the extra payment may not be handled. And the extra work often goes unbilled, even when your terms allow for a charge.
| Step often skipped | What follows |
|---|---|
| Checking against the last run | The fix itself contains an error |
| Submission for the payment | Records at HMRC out of step |
| Pension on the extra pay | Contributions missed |
| Client approval of figures | Dispute about what was agreed |
| Recording for billing | Work done for free |
How we build an off-cycle request route
- Clients request off-cycle payments through a short form: employee, amount or hours, reason, and when they need it. Phone requests are logged by the administrator in the same form.
- The request is compared with the last run and the client's inputs, for example showing that the missed overtime was in the client's submission but not processed, or that it was never sent.
- The administrator sees the request with its effect and can suggest adding it to the next scheduled run if the timing allows, with the dates shown to the client.
- If it goes ahead, the calculated figures go to the client for approval on the same approval page used for normal runs.
- The run is added to the calendar with its own tasks: submission, pension, payment and payslip, so nothing is left off.
- The request is recorded as chargeable according to your terms and flows into billing, unless you mark it as a bureau error.
Whether a bureau error is charged, and how quickly you can turn around urgent payments, is your policy. The route makes the policy visible and consistent.
Urgent without being chaotic
Off-cycle payments get the same checks and follow-up tasks as any run. Clients see when an extra payment could simply join the next run, and many choose that. Genuine emergencies are handled calmly. Submissions and pensions keep up. And chargeable work is billed, while the bureau's own errors are recorded so you can see where they come from.
Is off-cycle work disrupting you?
- Clients ring for same-day payments several times a month.
- Off-cycle payments skip the usual checks.
- Submissions or pensions for extra payments have been missed.
- Extra runs are rarely billed.
- You do not know how many off-cycle runs came from your own errors.