Payroll has several deadlines because it involves several different actions. Employees need the correct payment. HMRC needs information and money. The pension provider needs contribution data and payment. Your accounts need an accurate record of the whole employment cost.
In this article
- Agree a payroll information cut-off
- Check pay changes and calculations
- Approve payments and required submissions
- Reconcile results before the next run
A dependable routine assigns an owner and evidence of completion to each action. Putting “payroll” into the calendar once a month is too vague: a bank payment can succeed while a submission fails, and a submitted pension file can remain unpaid.
Begin with the payday and the tax month
Write down your contractual payday, the earnings period it covers and the bank processing time needed. Then create earlier internal deadlines for data collection, calculations, review and approval. Internal cut-offs are business controls, not substitutes for statutory deadlines.
HMRC tax months run from the sixth of one calendar month to the fifth of the next. This matters when allocating payments and submissions. Keep the tax-month reference alongside the calendar month so a payment made near the beginning of a month is not assigned casually to the wrong period.
The normal rule is to send a Full Payment Submission, or FPS, on or before payday. Paying HMRC quarterly does not turn employee reporting into a quarterly task. Follow HMRC guidance for exceptions and special circumstances rather than assuming a late report is acceptable because deductions were paid.
Use a calendar with distinct checkpoints
| Checkpoint | What should happen | Evidence to retain |
|---|---|---|
| Input cut-off | Approve hours, changes, starters and leavers | Signed-off input register |
| Draft review | Check pay and deductions against instructions | Reviewed draft and resolved queries |
| Final approval | Authorise the final run and payments | Approval identifying the version |
| Payday reporting | Send the appropriate FPS | Submission acknowledgement |
| Employee payment | Pay approved net amounts and issue payslips | Bank confirmation and payslip release |
| Tax-month review | Decide whether an EPS is needed | EPS decision and acknowledgement if sent |
| Liability settlement | Pay HMRC and pension amounts due | Payment confirmations and reconciliation |
Leave enough time between draft review and payday to solve a missing P45, an unexplained deduction or an incorrect bank account. Where there is only one owner, name a backup who can approve in their absence and give them the necessary access before they need it.
Know when an EPS belongs in the routine
An Employer Payment Summary, or EPS, is not simply another copy of the FPS. HMRC uses it for specific matters, including relevant statutory-payment recovery and reporting a tax month in which no employees were paid. Its EPS guidance sets out when it is needed and the deadline of the nineteenth of the following tax month for relevant reductions. A no-payment EPS is also due by the nineteenth after the unpaid tax month.
Do not send an unnecessary FPS with guessed figures because you want the account to look active. Equally, do not leave a no-payment month unreported without checking the EPS requirement. Record the reason for any reduction and the supporting payroll figures.
Keep payment deadlines separate from reporting
HMRC’s PAYE payment guidance gives the normal monthly deadline as the twenty-second of the next tax month. For postal cheque payments, it must reach HMRC by the nineteenth. Quarterly arrangements have their own schedule. Allow for the clearing time of your selected payment method and use the correct reference.
Pension payments follow the scheme’s agreed process and applicable legal requirements, so do not treat the PAYE date as a universal payroll payment date. Record the pension provider’s upload and payment deadlines separately. Confirm both the file acceptance and the movement of funds.
An illustrative timetable for a small team
Imagine a consultancy with an agreed month-end payday. It sets an internal changes deadline several working days earlier, calculates a draft, and reserves a review day before approval. These are hypothetical internal dates, not statutory requirements.
During review, its owner spots that a bonus was discussed but never authorised. The item is resolved before finalisation. Payroll then sends the FPS, releases payslips and prepares the net-pay file. After payday, the accounts administrator reconciles the pension submission and checks the HMRC liability before arranging payment.
The routine works because “done” means evidence exists for each action. If the FPS is rejected, paying employees does not mark the reporting checkpoint complete. Someone must investigate and confirm a successful submission.
Handle changes to the routine deliberately
Bank holidays, early Christmas payments and changed paydays can affect reporting. Check HMRC’s changing-payday guidance before altering the date recorded in software. Do not assume the bank transfer date always answers every reporting question.
Maintain a separate year-end checklist. Annual payroll reporting includes the final submission and P60 requirements. A monthly calendar should prompt that work rather than trying to hide it inside an ordinary pay run.
Review the timetable when headcount grows, approval becomes slower or variable pay increases. Ask which tasks repeatedly depend on last-minute messages and replace those messages with an approved input process.
If payroll administration is taking too much owner time, discuss the timetable, staff numbers and software through EPOS Accountancy’s payroll page. Confirm available support and precisely who reports, approves and pays. The pricing page explains the route to a scope-based quote.