A payroll run is a sequence with two gates. Inputs are collected until the cut-off, after which changes move to the following month; attendance, leave, joiners, leavers, one-off payments and recoveries are reconciled; the system computes; a named approver signs off; salaries are disbursed; then remittances, returns, records and payslips close the cycle.
The cut-off is the date after which a change lands in next month's run instead of this one. Everything in the cycle is arranged around it. Before it, input owners are chasing the information they are responsible for. After it, the data set is fixed and the work becomes computation and checking. Teams that treat the cut-off as a suggestion end up reopening runs, which invalidates checks already performed and creates versions of the truth nobody can tell apart. Publish the date, put it in the shared calendar, and agree in advance what qualifies as an exception, who may authorise one, and how it gets recorded. A firm cut-off is what makes [payroll management](/payroll-management) predictable.
Attendance and days payable, leave without pay, overtime and shift allowances, new joiners with their structures, exits with their last working day, salary revisions with effective dates, one-off payments such as incentives or referral awards, and recoveries such as loan instalments or advances. Each of these has an owner somewhere other than payroll, which is why collection is the stage that slips. Name the owner per input rather than per department, and give every owner the same deadline. Where the source is a system rather than a person, check that the feed actually ran: a [leave management system](/leave-management-software) that failed to sync is silent, and silence looks exactly like nobody took leave.
Anyone not present for the whole period needs proration, and proration is where conventions matter. A joiner partway through the period is paid for the days worked on whichever basis your policy uses, and their statutory position may begin mid-period too. A leaver might be paid in the regular run or held for a separate settlement, depending on when clearances complete. Both cases need the effective date recorded once and used consistently, because a date entered differently in two places produces two different answers that both look right. Where joiner details flow from your [employee onboarding system](/employee-onboarding-software), verify the structure came across in full rather than assuming it did.
Computation is the fast part. The review that follows is the run. Payroll checks the output against the inputs it accepted, looks at who moved and why, and clears whatever the system flagged as unusual. Anything unexplained goes back for correction before the file reaches an approver, because an approver handed a run with open questions will either rubber-stamp it or return the whole thing. This stage is also where you catch errors no rule can detect: a revision applied to the wrong employee, an allowance approved verbally and never recorded, a recovery that was supposed to have stopped last period.
Approval should rest with a named person, separate from whoever prepared the run, and it should mean something specific: that totals have been reviewed, movers explained and deductions agreed. Vague approval is worse than none, because it produces a signature nobody treats as a control. Decide in advance what the approver receives, usually a summary by department or cost centre, the variance list and the deduction totals. Decide too what happens if they refuse. A run that cannot be reopened without an audit entry is the whole point of the control; if any administrator can quietly edit an approved run, the approval means nothing.
The bank file goes out, and from that moment corrections become expensive in effort and awkward with employees. Check the file total against the approved register before upload, confirm the count of payment lines matches the count of employees due to be paid, and hold back anything with a failed or unverified bank detail rather than releasing a payment that will bounce. Have a named person watching for rejections, because a returned payment discovered a week later is a very different conversation from one resolved the same day. Record what was released and when, since that record is what you reconcile against afterwards.
Disbursement is not the end. Deductions taken from employees have to be remitted to the right authorities, returns filed where they are due, registers and supporting records saved for the period, and payslips made available. Deadlines and formats differ by obligation and by state and they change, so confirm the current position with a qualified advisor or the relevant authority rather than relying on last year's calendar. Post the payroll cost to finance in the format their ledger expects, and log any item you deferred to next month so it does not quietly vanish. The cycle closes when the following month's cut-off is announced.
Pitch N Hire is an applicant tracking system built for recruiters and hiring teams. If this answer described something you want to run properly, the ATS is where it lives.
Free for 1 user · No credit card · Talk to a real hiring expert
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo · Talk to sales · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
