The Pay-Run Workflow: From Draft to Disbursed, Explained

A payroll mistake is not like a typo in a memo. It moves money into people's bank accounts, and once it lands, it is hard to pull back. The pay-run workflow exists so that nothing irreversible happens until a human has looked at the numbers and said yes. This guide walks through every stage, from draft to completed, and explains the single idea that keeps payroll teams out of trouble: calculation is safe to repeat, but approval is the point of no return.

What are the stages of a pay-run workflow?

A well-built pay run moves through seven states: draft, validated, processing, review, approved, disbursed, and completed. The first four make no changes to anything permanent — they only gather data and compute numbers. The last three commit real side effects: they touch loan balances, leave balances, and finally the money itself. You can cancel any run before it is disbursed.

1. Draft — you open the pay period and pull in who gets paid. Fixed pay (basic, allowances) comes from each employee's salary structure; nothing is calculated yet.
2. Validated — the system checks the inputs: missing salary structures, employees with no bank details, variable pay (overtime, commission, bonuses) uploaded for the period, attendance data present. Problems surface here, cheaply.
3. Processing — the actual calculation: gross, tax withholding, statutory deductions, attendance-based deductions, net. This is calculation ONLY — no side effects — and you can re-run it as many times as you like.
4. Review — a person reads the payslips, checks totals against last period, and spots the outlier: the employee whose net doubled, the missing bonus, the wrong overtime.
5. Approved — the commit. Now the side effects fire: loan installments are deducted and their balances updated, leave balances are adjusted, and the run is locked from further recalculation.
6. Disbursed — payment is released to employees, whether through a bank file, a transfer, or a payment provider. Past this point, cancellation is no longer a button — it is a bank recall.
7. Completed — payslips are published to employee self-service and the payroll journal is posted to the general ledger. The period is closed.

Why is processing reversible but approval the commit?

Because the two do fundamentally different things. Processing only reads inputs and writes numbers onto the run itself — payslip lines you can throw away and recompute. Approval reaches out and changes records that live *outside* the run: it deducts a loan installment, it burns leave days. Undo those cleanly and you invite double-deductions and drifted balances. So good payroll software refuses to touch the outside world until you approve.

This is the difference between a draft and a transaction. You can edit a draft a hundred times; the last version is the only one that counts. But the moment you approve, the run stops being a draft and becomes a set of committed facts. That is why the sequence is deliberate: recalculate freely while it is cheap, then approve once, on purpose, when a human has seen the result.

What happens at each stage, exactly?

The clearest way to see the design is a side-by-side of each state: whether it changes anything permanent, whether you can safely repeat it, and whether you can still cancel. Notice how the whole table stays green — no side effects, fully reversible — right up until approved.

Why do review and approval controls matter?

Because payroll is where honest errors and quiet fraud both hide. A review step forces a second pair of eyes onto the totals before money moves — catching the doubled net, the ghost employee, the overtime that should have been zero. Separating who *runs* payroll from who *approves* it is a basic control, the same logic banks use to require two signatures on a large cheque.

Controls also mean traceability. Every good pay run keeps a record of who approved it and when, so a later question — "why was this person paid more in March?" — has an answer instead of a shrug. This matters most when payroll data flows straight into your accounts. Read our guide on how to choose payroll software for the full control checklist, or what is payroll software if you are starting from scratch.

The safest pay run is the boring one: nothing surprising in review, one deliberate approval, no reversals. Excitement in payroll is a symptom, not a feature.

How does this connect to the rest of the business?

A pay run does not live alone. Its inputs come from attendance and leave — absences, overtime, lateness — and its output is a journal that belongs in your finance ledger. When those three sit in one system, the run at approval can read real leave balances and write a real journal voucher without anyone re-keying a spreadsheet. When they are three separate tools, that hand-off is where errors breed.

That is the honest case for an all-in-one platform. On a system like ERPnBox, payroll lives inside the HR app next to employee records, attendance, and leave, and connects to a real double-entry Finance ledger — one login, one per-seat price, set up from a chat and usable in any language. The advanced controls this article teaches — a reversible processing stage, formula pay codes, cost allocation — are the standard you should hold *any* payroll tool to; treat this guide as your checklist when you compare options, not a spec sheet for one product.

If you promise employees a take-home figure rather than a gross, the run's calculation gets one layer harder — see net-to-gross payroll for how grossing-up works inside the same workflow. And if your team needs the depth of a specialized payroll bureau in your country, a dedicated tool such as Gusto or a regional payroll provider can be the right call — the workflow principles here apply to all of them.