Payroll pays whoever is on the list. If someone leaves and nobody tells payroll, the salary keeps going out until someone notices. This post covers five controls that help you stop salary going to someone who has left, and it is honest about the one step none of them can replace.

Five layers of payroll controls resting on one base: record the leaver.

Key takeaways

  • SpireSlip stops paying a leaver only once someone marks them as terminated. It does not detect that a person has left.
  • Terminate before you approve the run: an approved run is not changed by a termination.
  • Separate preparing from approving, and approve and send as two steps.
  • Pay only verified bank accounts, and check bank changes before you approve.

How to stop salary going to someone who has left

Every control below narrows the gap between the day someone leaves and the day payroll knows. None closes it without an HR action, because a payroll system cannot see a resignation, a dismissal or a person who simply stopped coming in.

So the principle is: make leaving a recorded step, then let the system enforce it. The five controls follow from that.

Control 1: make leaving a recorded step

Terminate the employee in SpireSlip, with a last working day, before the run is approved. Terminating removes the person from future payroll runs and keeps the full history: payslips, payroll lines and the audit trail.

The details matter:

  • An unapproved run that covers the last working day pays the person only to that date, then they drop off. The last working day can be no more than 60 days ahead.
  • An approved run is not changed by a termination. Terminate first, or void the run and start again.
  • If the person is already on a draft or computed run, compute it again after terminating.
  • The termination is logged with the date, the reason and who did it.

After a final pay or offboarding run, SpireSlip shows a prompt on the run page: Mark as terminated. Nothing is terminated automatically, and there is a Do this later link, so someone has to act on it.

Control 2: separate preparing from approving

A payroll preparer can create and compute runs but cannot approve, void or send them, and cannot change pay or bank details. Only the owner and admins can approve and pay.

There is also a setting, off by default, called Require a different person to approve payroll. When it is on, whoever created or last computed the run cannot approve it while another owner or admin can. If nobody else can approve, the owner may approve their own run with a written reason, which is recorded. An admin cannot override. Turn it on if you have more than one person who can approve.

Separately, a run with a one time payment cannot be approved by the person who added or changed that payment. That check is on for every run, unless only one person can approve.

Control 3: approve, then send, as two steps

Approving a run is the sign off that locks it. The figures cannot be edited or recomputed after approval, and the approval is stamped with the date, the time and the approver's name. SpireSlip keeps a hash of every line and checks it again before sending, and before any retry. If the lines changed after approval, the payment stops.

Money moves only at a separate step, Disburse now, where SpireSlip asks the person to confirm it is them. To change an approved run, void it and start again; both events are recorded.

Control 4: pay only verified bank accounts

If any employee's primary account is unverified, sending through SpireSlip does not start, and the unverified employees are named. The one way past it is deliberate: an owner or admin can leave that person out of the send with a written reason and send everyone else, and the run is not marked paid while anyone is held. Verifying checks the account name with the bank and shows the returned name for you to confirm.

If the bank's name does not match the employee, an admin has to confirm the mismatch deliberately, entering a password or code each time. Newly added or imported accounts start unverified.

Be honest about one gap. An employee can change their own bank details in the portal. If the account name matches the name on file, the change is saved at once, with no HR approval, and it is used on the next run. Owners and admins get a note in the app, not an email. So make a bank change check part of your routine before approval, and look at who changed what.

Control 5: compare runs before approving

Before you approve, open the payroll variance report. It compares two runs and lists New employees, Exits and Salary changes, with headcount totals. Ask three questions: is everyone who left listed under Exits, is every new name expected, and does every salary change have a reason?

Then use the audit log, shown on the company's History tab, to see who did what: terminations, approvals, overrides and bank changes. It is how you answer, later, who did what and when.

Does SpireSlip tell me when someone has stopped coming to work?

No. SpireSlip does not detect absence or departure. HR has to record it.

Does SpireSlip check whether two employees share a bank account?

No. There is no check for the same account used by two employees, so look at the bank details when you review the run.

How SpireSlip handles this: we remove terminated people from future runs, lock every run when it is approved and send salaries only to verified accounts, so the steps you record are enforced on every run.

Book a demo

Official source: Your state Internal Revenue Service

This article is general information, not legal or tax advice.