Operations
Part of Operating payroll software in 2027 with named roles, quality gates and careful FPS handling
A payroll workflow from opening the period to reconciling the outputs
Build an England payroll software workflow from controlled inputs to approval, FPS, pension exchange, reconciliation, employee outputs and correction.
A payroll workflow should make responsibility and evidence visible from the first input to final reconciliation. Software can calculate and transmit information, but the employer still needs controlled data, approval, exception handling and a route to correct mistakes.
1. Open the payroll period
Confirm legal employer, PAYE scheme, pay date, frequency, active population, tax year and authorised operator. Lock or copy the prior approved state so changes can be traced.
HMRC's running payroll guidance explains that employers complete tasks each tax month and report pay and deductions on or before payday. Use the actual payment date and current guidance for the circumstances.
2. Collect and validate changes
Receive starters, leavers, hours, overtime, absence, bonuses, deductions and bank changes through approved routes. Apply cut-off times and named approval. Validate completeness, effective dates, duplicates and unusual values.
Do not allow an integration to bypass ownership. Preserve source, timestamp, approver, transformation and exception state.
3. Calculate and review
Run gross-to-net calculations in the correct tax-year configuration. Compare headcount, gross pay, net pay, employer liabilities and material variances with an appropriate prior period or approved expectation.
Separate the operator from the final approver where the organisation's control design requires it. Record overrides and their reasons.
4. Complete pension work
Assess applicable workers, calculate contributions, process authorised worker events and prepare provider information. The Pensions Regulator's software checklist identifies provider formats, tax-relief method, communications and records as well as calculation.
Confirm acceptance by the pension provider and reconcile results. A generated file is not the final outcome.
5. Approve, report and pay
Obtain documented payroll approval before releasing actions. Send the FPS through authorised software and retain the acknowledgement or error. HMRC's FPS guidance says the report is generally due on or before payday and should be corrected as soon as possible if errors are found.
Keep submission, employee payment and HMRC payment authority distinct. Reconcile payment files or instructions to the approved payroll before release.
6. Issue outputs and reconcile
Provide payslips through the approved secure and accessible route. Post or export the payroll journal, check control accounts and compare the expected HMRC balance when available. Complete pension reconciliation and record unresolved differences.
7. Correct and close
HMRC's payroll error guidance shows that correction method depends on the error and timing. Escalate to competent payroll advice instead of applying one universal reversal.
Close the period only after submissions, payments, pensions, employee outputs, reconciliations and exceptions have named outcomes. Restrict later changes, retain the audit record and schedule the next period. Review recurring errors to improve the source process rather than normalising correction work.
Run an exception queue
Give every exception a type, affected employer or employee, discovery point, deadline, owner, status and evidence. Distinguish an incomplete input from a calculation defect, rejected submission, pension mismatch or payment problem. The response and authority differ.
Prioritise by employee and reporting consequence, not simply arrival order. Support staff should be able to see who is acting without gaining unnecessary access to payroll details.
Protect the workflow during change
Before a new tax-year release, integration or configuration change, preserve the current version and expected results. Test ordinary and edge cases, safe rollback and any customer action. Avoid discretionary change close to the employer's critical cut-off.
After deployment, compare the first outputs with approved expectations and watch submission and pension responses. Record the version that produced each payroll. A dependable workflow makes both the normal sequence and the recovery route clear to a trained substitute when the usual operator is unavailable.