Payroll process flowchart (cut-off to payment and filing)
Payroll process flowchart from cut-off to payment: starters and leavers, approved hours, variance checks, gross-to-net, an independent pre-payment review, funding, the bank file, statutory filing, payslips and the journal.
What the payroll process flowchart (cut-off to payment and filing) process is
Payroll is judged on a single output every person in the organisation checks personally, which makes it the least forgiving process there is. It is also the one most often described as a calculation, when almost nothing that goes wrong is a calculation. The engine applies the tax tables correctly. What breaks is upstream. A leaver's last day reaches payroll a week after the run, so someone who no longer works there has been paid and the money now has to be asked for back. A promotion agreed verbally in month one is backdated in month four, and a single payslip carries an arrears figure nobody warned the employee about. A manager approves overtime after the cut-off because the deadline has never once been enforced. And when the run is late, the first thing dropped is the variance check against the prior period, which is the one control that would have caught all three. Underneath sits the structural problem: in a small team the same person collects the inputs, runs the calculation, approves the total and releases the file to the bank, and nobody outside payroll has seen the figures before the money leaves.
This chart is the payroll run itself (one period, from cut-off to a paid, filed and posted result) and it is deliberately not the processes that feed it. Getting a new employee onto the system, with the contract, right-to-work check, bank details, tax code and pension enrolment, belongs to the employee onboarding process at /templates/employee-onboarding-process, and the last-day, final-pay and access-removal sequence belongs to the employee offboarding process at /templates/employee-offboarding-process. Both appear here as one step, "Collect starters, leavers and changes", because payroll consumes their output rather than running them. Absence is the same: entitlement, cover and manager approval are worked through in the leave request process at /templates/leave-request-process, and this chart only asks whether the approved absence arrived before cut-off. Employee expense claims are checked, coded and approved in the expense approval process at /templates/expense-approval-process, and reach payroll only if you reimburse through the payslip rather than a payment run; supplier payments are a different function entirely, mapped in the accounts payable process at /templates/accounts-payable-process. At the far end, the journal this chart posts is an input to the period close, drawn in the record to report process at /templates/record-to-report-process.
Three things most payroll procedures leave implicit are drawn here as steps with names. "Independent pre-payment review" sits in its own lane, held by somebody other than the person who prepared the run, and "Control review passed?" sends errors back to "Correct the input at source" rather than into an override typed straight into the payroll system. That is the segregation-of-duties control an auditor asks about, and here it is a step rather than a principle. "Payroll approved and funded?" is drawn as one decision because the run stops if either half fails: somebody with delegated authority approves the cost, and treasury confirms the cash will clear in time. A run that cannot pass it has somewhere to go, because "Run halted and rescheduled" is a real ending rather than a hole in the diagram. The third is placement. "Submit statutory filing and pensions" sits beside the payment rather than in the tidy-up afterwards, since the return is due on or before payday, and the Off-cycle branch of "Correct in an off-cycle run?" loops back to it instead of ending, because a supplementary payment carries its own return, payslip and journal.
What this flowchart covers
In this template
- Six swimlanes (Employee, Line manager, HR, Payroll administrator, Payroll manager and Finance and treasury) across six phases: Cut-off, Input collection, Validation, Calculation and control, Approval and payment, and Post-payroll.
- Input collection drawn as a chain of three hand-offs in three lanes rather than one queue: HR's "Collect starters, leavers and changes", the employee's "Submit timesheets, overtime and expenses" and the line manager's "Approve hours, overtime and absence", all tested at "All inputs received by cut-off?".
- A completeness check before a correctness check: anything missing routes to "Chase or defer the missing input" and back to the same cut-off test, while "Load inputs and run validation checks" feeds "Variances explained?", whose Unexplained branch loops through "Correct the input at source" and revalidates.
- The segregation-of-duties control drawn as real steps rather than assumed: the preparer's "Prepare the pre-payment control pack", then "Independent pre-payment review" in the Payroll manager lane, then "Control review passed?", whose Errors found branch returns the run to source correction instead of to an override.
- Approval and funding kept apart from calculation at "Payroll approved and funded?", whose Approved branch runs "Release the payment file to the bank" and then "Submit statutory filing and pensions" before "Publish payslips to employees", because the statutory return is due on or before payday rather than in the tidy-up afterwards.
- Three endings and a post-payday loop: a held run stops at "Run halted and rescheduled"; otherwise "Post the payroll journal to the ledger" and "Archive the payroll run evidence" close the period before "Pay error reported after payday?" is asked, and its Reported branch runs "Assess the error and agree a remedy" into "Correct in an off-cycle run?", where Off-cycle sends "Run an off-cycle supplementary payment" back through the filing, Next period leaves at "Correction carried to the next run", and a period with nothing reported closes at "Payroll paid, filed and posted".
When to use this template
- You are writing a payroll SOP, or a service description for an outsourced provider, and need one picture of who owns each input, who reviews the run and who releases the money.
- An error reached the bank last period, and you have to show the board where the pre-payment control sits, who holds it, and why it did not catch this.
- The same person prepares, approves and releases the run, and you need a segregation of duties that works with the headcount you actually have rather than the one the control framework assumes.
- Cut-off is treated as advisory, late inputs arrive by email after the run has started, and you want the deadline and the deferral rule drawn rather than renegotiated every month.
- You are implementing or migrating a payroll system, or bringing an outsourced payroll back in house, and the hand-offs, thresholds and filing deadlines have to be specified before anything is configured.
How it works
Rename the lanes to your own organisation
Replace Employee, Line manager, HR, Payroll administrator, Payroll manager and Finance and treasury with the roles you have. The two payroll lanes are the point of the chart, so do not merge them without deciding who else will hold the review. If payroll is outsourced, keep the provider as one lane and add a retained lane for the person who signs off their output, because the accountability does not leave with the processing. Where HR and payroll are one desk, merge those lanes rather than drawing a hand-off nobody makes.
Put the cut-off calendar into the chart
"Payroll cut-off announced for the period" is inert until it carries dates. Publish the whole year at once: input cut-off, approval cut-off, funding date, payday and filing date for every period, with the ones shifted by bank holidays marked. Then state what actually happens to a late input — held to the next run, or handled off-cycle at a cost somebody has to authorise. A cut-off with no stated consequence is one the noisiest manager renegotiates every month, and it is always the same manager.
Set the variance thresholds in figures
"Load inputs and run validation checks" needs numbers before it means anything. Most teams flag a movement in gross pay against the prior period on a percentage and a cash floor together, so a small salary does not trip on every overtime hour and a large one does not hide a real error. Set them so the exception report comes back at a length somebody will genuinely read: two hundred lines are read about as carefully as none. Then name who clears each exception, and keep the cleared report, because that is the evidence the check was run rather than skipped.
Give the independent review a named holder
The control fails quietly when the reviewer is nominal. Name the role rather than the person, and make sure the holder sits outside the preparation: a finance manager, the HR director, the provider's own reviewer, or an external accountant on a small team. Give them the pack in a form they can argue with, and give them a slot in the calendar before the funding deadline, because a review squeezed into the hour before the bank cut-off is a signature rather than a review. Then decide where the sign-off is recorded, since that record is what an auditor asks for.
Attach your filing and pension deadlines
"Submit statutory filing and pensions" is jurisdiction-specific and it is where penalties live. In the UK that means a Full Payment Submission on or before payday, an Employer Payment Summary where one is due, and pension contributions paid inside their own statutory window. Write your own deadlines onto the step, and name both who files and who confirms the submission was accepted rather than merely sent. Decide what happens when one is rejected: a return that bounced overnight, with the notice unread, is the commonest way a deadline is missed by an organisation that believed it had met it.
Agree the correction policy, then walk it through and publish a version
Settle "Correct in an off-cycle run?" before you need it: the hardship test that forces an immediate payment, who authorises the cost, and the rule for recovering an overpayment, which is a legal question rather than an administrative one. Then walk the finished chart through with a payroll administrator, whoever holds the review, HR and treasury, correct it to what they actually do rather than what the manual says, and publish that revision while keeping the earlier ones, so anyone opening it later can tell which version they are reading.
Frequently asked questions
What are the steps in a payroll process?
A pay period runs like this: announce the cut-off; collect starters, leavers and permanent changes from HR; collect timesheets, overtime, absence and any expenses reimbursed through the payslip, with the line manager approving hours; check every input has arrived by cut-off and chase or defer what has not; load the inputs and run validation and variance checks against the prior period; investigate and correct anything unexplained at source; calculate gross to net; prepare a pre-payment control pack and have it reviewed by someone who did not prepare the run; approve the cost and confirm the funding; release the payment file to the bank; make the statutory filing, which in the UK is due on or before payday, and pay pension contributions inside their own window; publish payslips; post the payroll journal to the ledger; and archive the evidence. Errors found after payday go to a decision about an off-cycle run rather than being carried by default.
What is segregation of duties in payroll, and how does it work in a small team?
In most organisations the payroll figures are seen by two or three people before the money moves, so the review before payment is the only outside check they get. Segregation of duties means the person who prepares the run is not the person who approves the cost and not the person who releases the file at the bank. The risk it addresses is not only fraud — a fictitious employee, an altered bank account — but the ordinary keying error that reaches everyone on the payroll at once and is discovered by them rather than by finance. In this chart it is a step, "Independent pre-payment review", rather than a policy sentence, and what it produces is a dated sign-off. Small teams cannot always split three ways, so split the two that matter most: whoever prepares the run must not release the payment. The reviewer need not sit in payroll at all — a finance manager, the HR director or an external accountant can hold it, provided they are given the pack and the time to use it.
How is this different from the HR processes that feed payroll?
This page is the run, not the events that change it. The employee onboarding process at /templates/employee-onboarding-process covers getting a new hire contracted, checked, provisioned and enrolled; the employee offboarding process at /templates/employee-offboarding-process covers notice, handover, access removal and final pay; and the leave request process at /templates/leave-request-process covers entitlement, cover and manager approval for time off. All three end where this chart begins, arriving as "Collect starters, leavers and changes" or as approved absence tested at "All inputs received by cut-off?". Expense claims are the same: they are validated and approved in the expense approval process at /templates/expense-approval-process and only appear here if you reimburse through the payslip. Use those templates to fix why the input is late or wrong. Use this one to fix what the payroll run does with the inputs it receives, and what happens when they do not arrive.
What should happen when an employee has been overpaid?
Treat it as a legal question before an administrative one, and establish the facts first: the amount, the periods it covers and how it happened. In the UK the Employment Rights Act 1996 excepts the recovery of an overpayment of wages from the rules on unlawful deductions, so an employer is not barred from taking it from pay — but that is a long way from taking it unannounced. Tell the employee in writing, agree a repayment schedule they can actually meet, and spread a large recovery over several periods rather than clearing it out of one net payment. Where the person has already left there is nothing to deduct from and it becomes a debt to be asked for. Take advice where the sum is significant, the employee disputes it or the error ran for a long time, because someone who reasonably believed the money was theirs and has spent it may have a defence. Then fix the cause: most overpayments are a leaver notified after cut-off, which is a hand-off problem rather than a payroll one.
Should a payroll error be corrected off-cycle or in the next run?
Decide it against a written test rather than by whoever asks loudest. An off-cycle, or supplementary, run costs money — a payment file, a bank charge, a second statutory submission and someone's afternoon — so it is not the default. It is the right answer when the employee has been left materially short, when a statutory payment such as sick or maternity pay has been missed, or when the error affects enough people that waiting is untenable. Carrying the correction to the next period is reasonable for small amounts and for an overpayment already agreed as recoverable. Log the cause either way, so the same variance does not reappear next month. In this chart the choice is drawn as "Correct in an off-cycle run?" in the Payroll manager lane, and the Off-cycle branch loops back through "Submit statutory filing and pensions" rather than ending, because a supplementary run carries its own return, its own payslip and its own journal.
Where this process fits
In most operations this process follows Employee onboarding process flowchart and hands off to Record to report process flowchart (cut-off to sign-off).
Comes before
- Employee onboarding process flowchart — A cross-functional employee onboarding process template covering pre-boarding checks, IT provisioning, day one, first week and the day-90 probation review.
- Employee offboarding process flowchart — A cross-functional offboarding flowchart with HR, manager, IT, payroll and facilities lanes: notice, handover, exit interview, access revocation, final pay.
- Leave request process flowchart — Leave request process flowchart: submission with dates and leave type, balance and cover checks, manager approval, HR escalation, payroll and return to work.
- Employee promotion process flowchart (nomination to effective date) — Employee promotion process flowchart: nomination or application, eligibility, the evidence pack, calibration across the peer group, funding, senior approval, pay within the band, the letter, effective date and handover.
Comes after
- Record to report process flowchart (cut-off to sign-off) — Record to report process flowchart for the period-end close: sub-ledger cut-off, accruals, intercompany matching, balance-sheet reconciliations, journal approval, consolidation, flux review, disclosure and sign-off.