DonkeyHR

Payroll cut-off date: how to set one that works

Set a payroll cut-off that leaves time to check approved attendance and leave, then carry late changes into the next run with a clear record.

DonkeyHR Team · 2026-10-27 · 6 min read

A payroll cut-off date is your internal deadline for receiving approved inputs for a payroll run. Choose it by working backwards from your planned salary date, leaving time to check attendance, leave and other changes. Carry changes approved after the cut-off into the next month's run, with a record of the original period and the adjustment. Make sure managers and employees know the deadline and how late approvals will be handled.

Why does a payroll cut-off matter?

Payroll depends on information from several people. Employees report missed punches. Managers approve leave. The office team records changes that affect pay. Without a shared deadline, these inputs can keep changing while payroll is being checked.

That creates avoidable work. A late leave approval may change an absence entry after someone has already checked the employee's pay. The person preparing payroll must then reopen the calculation and check whether anything else changed.

A cut-off creates a stable set of inputs for review. It also gives employees a clear explanation when an approved change appears in the following run.

The deadline should organise the work. It should not become a reason to lose a correction or leave an employee unsure about their pay.

How should you choose the cut-off date?

Start with your planned salary date and work backwards through the actual tasks involved. Allow room for collecting inputs, resolving queries, checking the calculation and approving the final payroll.

Ask the people doing each task how much time they need. A deadline that looks convenient on a calendar may fail if managers cannot finish attendance reviews before it.

Consider your working pattern too. If staff work shifts, the attendance record may need checking across overnight work. If an approver is away, someone else needs to handle pending requests. Regional holidays can also affect when the office team is available.

Choose a date you can explain simply and follow consistently. Avoid changing it informally whenever someone asks for more time.

Your internal cut-off does not replace applicable payment or compliance requirements. Rules can change during the transition to the labour codes, so check the current notification or official portal when setting your process.

What exactly should close at the cut-off?

Define which inputs must be ready and what “ready” means. Submitted is not always approved. A leave request sitting with a manager is different from leave that has completed the required approval chain.

Your cut-off process should cover:

  • Attendance records checked for missing or disputed entries.
  • Leave requests approved through the required chain.
  • Missed-punch corrections reviewed by the responsible person.
  • Joining, exit and pay changes confirmed by the office team.
  • Pending items recorded with an owner and a reason.
  • Approved inputs handed over for payroll checking.
  • Late changes placed in a record for the next run.

Keep the attendance period separate from the submission deadline. Tell staff which period the run covers and when corrections for that period must be approved.

Also state who gives the final confirmation. Otherwise, payroll may receive competing versions of the same record.

How should attendance and leave approvals connect?

Attendance and leave should tell a consistent story before payroll is calculated. A missing punch should be investigated rather than silently treated as a confirmed absence. An employee who has applied for leave should be able to see whether approval is still pending.

Give employees time to review their records before the deadline. Ask managers to clear requests early enough for HR to complete any further approval.

Where the process requires manager approval followed by HR approval, both stages need to finish before the input is treated as approved. A manager's approval alone should not be confused with completion of the chain.

Keep the payroll decision visible when a request remains unresolved. Record what information was available at the cut-off, who needs to resolve it and how any later correction will reach payroll.

This helps prevent the same absence being adjusted repeatedly because different people acted on different records.

What should happen when approval arrives late?

Use a clear default: carry the approved change into the next month's payroll run. Record the period it belongs to, the approval received, the earlier payroll treatment and the adjustment needed.

Do not simply overwrite the old attendance entry and assume payroll will notice. The attendance record and the payroll correction need to remain connected.

Illustrative worked example: suppose your internal cut-off is the 25th of the month. A leave request completes approval on the 27th. The approval arrives after the cut-off: 27 minus 25 equals 2 calendar days.

Under this illustrative process, the approved leave change goes into next month's run. The adjustment record identifies the original leave period and explains how it differs from the treatment used in the earlier payroll.

The example sets no statutory deadline and calculates no salary deduction. The pay effect depends on the leave policy, the employee's record and applicable requirements. Check the current notification or official portal where legal treatment is relevant.

Before completing the next run, confirm that the adjustment was included and close the pending item.

How do you explain the process to employees?

Use a short written note that answers the practical questions: what period payroll covers, when inputs must be approved, who handles queries and where late changes will appear.

Explain the difference between applying for leave and completing approval. Employees should know whom to contact if a request is waiting with an approver.

Tell an affected employee when a correction will appear and what period it relates to. Avoid a vague promise that it will be “sorted later”.

For the office team, keep a shared adjustment record with clear ownership. Review it before each run so that carried-forward items do not disappear between months.

Common mistakes

Setting the deadline without consulting approvers often creates a queue of pending requests. Choose a workable date and arrange cover when an approver is unavailable.

Treating every unresolved attendance entry as final can create unnecessary corrections. Review disputed entries and document the decision used for payroll.

Accepting late changes through private messages makes them easy to miss. Use the same recorded process for every employee.

Carrying an adjustment forward without naming its original period makes checking difficult. Preserve that connection and confirm completion.

FAQ

Is the cut-off date the salary date?

No. The cut-off closes approved inputs for checking. The salary date is the planned payment date. Leave enough time between them to complete your review.

Does late approval mean approved leave is lost?

Your process should carry the approved change into the next run and record its original period. Explain the treatment to the employee and check applicable requirements.

Can the cut-off change around holidays?

You can plan an internal deadline around office availability. Communicate the change before staff and managers need to act, and check that it fits applicable requirements.

Can software help with the approval process?

DonkeyHR is in beta and supports configurable leave approval chains, including manager then HR approval, alongside leave policies and regional holidays. A written cut-off process still needs clear owners, a late-change record and a final payroll check.

Related reading