When an input is late, recover the obligation
By The First Payroll Desk editorial desk · Publication editorial desk
Updated
A missed cutoff is an exception to resolve, not permission to miss an agreed payday. First establish whether the employee has started and what payment terms already apply. A start-date change is an option only for a prospective arrangement that can properly be changed; it is not a way to erase pay already earned.
Identify the failure before asking for an off-cycle run
| Failure | Immediate owner and action | Evidence that closes the exception |
|---|---|---|
| No P45 | Employee completes appropriate starter information; payroll confirms treatment | Accepted starter record, not a guessed tax code |
| Wrong bank details | Employee corrects through secure channel; payroll validates before release | Confirmed destination and replacement payment instruction |
| New-hire inclusion missed | Provider payroll identifies available run and approval authority | Accepted employee-specific recovery, amount and receipt date |
| Expense approval late | Separate reimbursement from salary; identify the approved cycle | Item-level disposition communicated to employee |
| Transfer sent but funds absent | Finance obtains trace; provider treasury checks receipt and allocation | Receipt confirmation or accepted alternative funding plan |
| Payroll already released incorrectly | Payroll investigates recall, correction or additional payment | Corrected calculation, payment reference and duplicate-payment check |
The HMRC starter route can resolve a missing P45; it cannot resolve unverified work permission or an unknown bank destination. Do not use a default National Insurance number to get past a software field. HMRC — New starter information — employer help card
A worked late-onboarding branch
In the November case, suppose onboarding completes on Saturday 21 November rather than the planned 19 November. That is after Deel's published UK cutoff. The ordinary route is now next-cycle pay; no recovery has been approved. The team opens an exception for the desired 30 November receipt rather than marking the original inclusion gate complete.
The record reads: “21 November 09:00 UTC — onboarding now complete; standard inclusion missed. Payroll owner to confirm whether a separate run is permitted, the amount and deductions, its funding deadline and payslip timing. Current promised date remains at risk. Next update to employee: 23 November 12:00 UTC.” All entries are fictional planning events. There is no implied supplier approval.
Deel documents off-cycle requests as subject to review. An enquiry, support ticket or advertised on-demand feature is not acceptance of this exception. Deel EOR invoice and off-cycle guidance
Keep a recovery from hiding a second failure
The replacement record must say what changed and what stayed due: employee reference, affected pay period, approved gross/net calculation, funding amount and currency, funds-received deadline, employee receipt date, payslip date and filing owner. Ask payroll to reconcile any advance against the normal run, so the employee is neither paid twice nor unexpectedly deducted twice. A recovery for funding does not automatically extend the legal or employee commitment.
The workbench accepts a late completion only with a recovery reference and an acceptance timestamp. That is a record of your evidence, not an approval generated by the tool. If the recovery changes a downstream deadline, update that deadline from the accepted plan and preserve the old version in your secure records.
Tell the employee what is known
Use a factual update: “Your expected pay date is 30 November. We are resolving [specific item]. [Payroll owner] is responsible. We will confirm the payment arrangement by [time]. Contact [actual channel] if your bank details or payslip access are wrong.” If the original date can no longer be met, the employer must address the obligation and communicate the actual remedy; do not silently substitute the next cycle.