No articles found for “”.
Approving payroll
Approving a payroll run is the step that turns a draft computation into a locked, ready-to-pay run. It's the formal sign-off before money moves.
How to approve
- Open the computed run.
- Confirm the figures on the Computation tab match what you expect.
- Click Approve run.
- Confirm the approval. If you have not recently confirmed your identity, SpireSlip may prompt you for your password or biometric verification (Touch ID / Face ID) before the approval goes through. This security gate appears only when your session requires re-verification.
Runs with one-off payments need a second person
If a run has one-off payments (a bonus, arrears, final pay and so on), anyone who added, changed or removed one of them cannot approve that run; a different owner or admin must. The account owner can approve anyway by writing a reason, which is recorded in the audit log. If only one person on the account can approve payroll, this check does not apply. See One-off payments.
Requiring a different person to approve every run
The account owner can require that nobody approves a run they prepared. When this is on, the person who created a run, or who last computed it, cannot approve it; another owner or admin must. It applies to every run, not only runs with one-off payments. It is off unless the owner turns it on.
- Open Entities, choose the company, and open the Payroll tab.
- Open Disbursement and scroll to Payroll approval.
- Tick Require a different person to approve payroll.
- Click Save approval setting.
If you prepared a run and someone else can approve it, you see "You prepared this run, so a different person must approve it. Ask another owner or admin to approve." If no one else on the account can approve, the owner can approve their own run by writing a reason of at least 10 characters, which is recorded in the audit log. An admin cannot do this. Only the owner can change this setting, and every change shows in the company's History tab. Runs cannot be approved through the API while this setting is on; approve them in SpireSlip. A payroll preparer can never approve, whatever this setting says (see Team members and roles).
What approval does
- Locks the payroll lines. The figures cannot be edited or recomputed after approval, they're frozen at the approved values.
- Records a cryptographic hash of every line. This hash is verified again at disbursement to confirm nothing has changed in between.
- Stamps the approval with the date, the time (Lagos time, WAT) and the name of the person who approved it. Both appear on the run page.
Why the hash matters
The hash is a tamper-detection mechanism. If anything in the payroll lines changes between approval and disbursement, even a single kobo, the hash will no longer match and disbursement will refuse to proceed. This guarantees that what gets paid out is exactly what was approved.
If you need to change something after approval
An approved run cannot be edited. If you discover a mistake, void the run (see Voiding a payroll run) and create a fresh draft for the same period. The audit trail will record both events.
Once approved, the next step is to disburse, see Disbursing salaries.