How to close the payroll month without a three-day scramble

It is the 29th. The salary register is half built, and someone from the warehouse has just sent a WhatsApp message saying four people worked the Sunday shift and were not marked. The biometric export disagrees with the supervisor's register on two of them. Someone else asks whether the new joiner who started on the 18th is being paid for a full month. Payroll was supposed to take a day. It is now taking three, and the third day is spent re-checking the first two.

This is rarely a calculation problem. The arithmetic in payroll is the easy part, and a spreadsheet does it correctly every time. What goes wrong is everything upstream — when inputs arrive, who is allowed to send them, and what happens when one shows up late. A payroll process that closes cleanly is mostly a set of dates that people actually keep to.

Why the month closes badly

If you watch a bad payroll week closely, the same four causes turn up in almost every business:

• The cut-off is soft. There is a date, but late inputs are accepted anyway, so nobody treats the date as real. Once one late input is accepted, the calculation restarts.
• Attendance is not closed before payroll opens. The working-day data is still being argued about while salaries are being computed on top of it.
• Inputs arrive in whatever form the sender prefers — a message, a call, a forwarded mail, a corrected sheet with no note saying what changed.
• Nobody owns the final check. Several people look at parts of the register and everyone assumes somebody else verified the rest.

Fix the cut-off before anything else

A cut-off only works when the whole month is laid out in advance and published — not agreed in a meeting, published, so that a manager who misses it can see they missed it. Put the dates on one page, send it once, and keep it the same every month. Shifting dates for one department teaches everybody that the dates move.

1. 1

   Attendance closes

   The last date a regularisation, leave application or overtime sanction can be approved for the month. After this, attendance is frozen and payroll works from it. This date comes first because everything downstream depends on it.

2. 2

   Inputs due

   One or two days after attendance closes. Every variable input for the month — new joiners, exits, salary revisions, incentives, deductions, reimbursements — is due from the named owner, on the input sheet, by this date.

3. 3

   Register built and checked

   Payroll is computed and the checks below are run. No new inputs are accepted during this window. Anything that arrives is logged for next month, not inserted into this one.

4. 4

   Approval and release

   One named person approves the register against the previous month's comparison, and only then are payments and payslips released. Approval is a signature on a specific version, not a verbal yes.

The gap between attendance closing and salary being paid is what you are buying with this. If your pay date is the 1st and attendance closes on the 28th, three days is tight but workable. If attendance closes on the 31st, no process will save you, and the first change to make is to the calendar rather than to the payroll.

The inputs payroll actually needs

Write down the full list once. Most businesses discover it is shorter than they expected, and that half the delay comes from two or three items that are always late. For each one, name the person who owns it — not the department, the person.

• New joiners: name, employee code, date of joining, salary structure, bank details, and the statutory registrations the role needs.
• Exits: last working day, whether notice was served or paid, leave balance to be settled, recoveries, and the date the clearance completed.
• Salary revisions: effective date, old and new structure, and whether any arrears fall due for earlier months.
• Attendance summary: days present, days on paid leave, days on loss of pay, overtime hours sanctioned, and any regularisations approved.
• Variable pay: incentives, allowances that change monthly, and reimbursements with the claim reference.
• Deductions: advances and their recovery schedule, and anything ordered against an employee that has been properly approved.
• One-off corrections: anything being paid this month that belongs to an earlier month, with a note saying which month and why.

A one-page payroll input sheet

One sheet per month, filled in by the owner of each input, submitted once. The value is not the format — it is that a late or missing input is visibly late, because the row is empty and it has a name against it. A simple version looks like this:

Section            Owner            Due      Submitted   Notes
-----------------------------------------------------------------------
New joiners        HR               25th     [ ]         Count:
Exits              HR               25th     [ ]         Count:
Salary revisions   HR / Founder     25th     [ ]         Arrears? Y/N
Attendance summary Ops / Shift head 24th     [ ]         Frozen on:
Overtime sanction  Dept manager     24th     [ ]         Hours:
Incentives         Sales head       25th     [ ]         Scheme ref:
Reimbursements     Finance          25th     [ ]         Claim refs:
Advances/recovery  Finance          25th     [ ]         Schedule ref:
Prior-month items  HR               25th     [ ]         Month + reason:

Attendance frozen by: ____________   Date: ______
Register approved by: ____________   Date: ______
Version approved:     ____________

Keep the submitted sheet with the month's register. When someone asks in March why a February salary looked odd, the answer is on one page instead of in a search through a year of messages. This is the same discipline that makes attendance, shift and leave data trustworthy enough to pay from in the first place.

Run the same six checks every month

Run these in the same order every time, before approval. Most errors are caught by the first two, and the value of a fixed order is that a skipped check is obvious.

1. 1

   Headcount reconciliation

   Opening headcount, plus joiners, minus exits, equals closing headcount, equals the number of rows in the register. If the row count does not match, stop here — everything after it will be wrong.

2. 2

   Month-on-month comparison

   Put this month's net pay beside last month's, per employee. Investigate every change. Most will be explained by a joiner, an exit, a revision or loss of pay; anything that is not explained is an error you have just caught.

3. 3

   New joiners and exits

   Check each one is paid for the correct part-month, that the joining and last-working dates match the HR record, and that a full-and-final has been computed for every exit in the month.

4. 4

   Loss of pay and overtime

   Trace a sample back to the frozen attendance. Every loss-of-pay day and every overtime hour should be traceable to an approval with a name against it.

5. 5

   Deductions and recoveries

   Confirm each advance recovery matches its schedule and that no recovery has been taken twice or missed.

6. 6

   Bank and statutory outputs

   Check the bank file totals equal the register's net pay total, and that the statutory returns and registers for the month have been prepared from the same figures the register used.

What to do about the exceptions

Exceptions are the real test. A process that survives a normal month and collapses when a manager sends an input two days late has not actually changed anything. The rule that makes the calendar hold is simple: a closed month stays closed.

• A late input is paid as arrears in the next cycle, with the month it belongs to noted on the input sheet. It does not reopen the register.
• A genuine error found after release is corrected in the next cycle in the same way, and the correction is recorded rather than quietly absorbed.
• Only one situation justifies reopening a month — where paying late would breach a statutory obligation or a written commitment to an employee. Name who can make that call, and keep it to one person.
• Count the exceptions. If the same department is late three months running, the problem is that department's input, not the payroll calendar.

Where software helps, and where it does not

Software does not fix a soft cut-off. What it does is remove the copying: when attendance is approved in the same system that holds the employee record, the frozen attendance becomes a payroll input directly instead of being exported, mailed and pasted. That removes a whole class of error, and it makes the freeze real because there is a date after which the system stops accepting approvals for the month.

That is what payroll input management is for — it collects the month's inputs, holds the approvals against them and hands payroll a month that is already closed. But the calendar, the owners and the six checks come first. A business that gets those right will close the month cleanly on a spreadsheet; a business that has not will get the same scramble, faster.

Start with one closed month

Do not redesign payroll in the abstract. Take the month you have just closed, lay it against the four dates above, and mark where each input actually arrived. The late ones are your whole problem, and there are usually two or three of them. Fix those owners and those dates, and the next close is shorter.

If you would rather have someone go through a closed month with you and write the calendar, the input sheet and the check list against how your business actually runs, that is what our payroll process management work does.