Skip to main content
SpireSlip

Running payroll, end to end

A SpireSlip payroll cycle moves through four discrete steps. Each step has its own help article with the mechanics. This page is the overview so you can see how they fit together before you click into any one of them.

The four steps

  1. Create a payroll run. Pick the schedule type (monthly, weekly, bi-weekly, custom) and the period. SpireSlip creates a draft with one line per active employee whose schedule matches. See Creating a payroll run. Someone who joins later can be added while the run is not approved; see Adding an employee to a run.
  2. Compute and review. SpireSlip applies the tax engine to every line: gross, allowances, statutory deductions (PAYE, pension, NSITF, NHF, ITF if applicable), and per-employee components. Review the totals before approval. See Computing and reviewing. If your company has switched on attendance changes pay, absence, unpaid leave, lateness and approved overtime are included here; see How attendance changes pay. Commission is added on the run; see Paying commission.
  3. Approve. Approval locks the run: payroll lines become immutable, the approval hash is stamped, the audit trail is sealed. Once approved, the run cannot be edited. An owner or admin can still void it with Void run before anyone on it is paid or a payment is in progress. See Approving payroll.
  4. Disburse salaries. SpireSlip sends transfers through Paystack. Each employee's bank account is paid in Naira. Failed transfers are flagged for retry. See Disbursing salaries. If you pay from your own bank instead, download a file to upload there and then record the run as paid outside SpireSlip; see Paying salaries from your own bank.

When to use each schedule type

  • Monthly, the default. Use for permanent salaried staff. The run spans a full calendar month.
  • Weekly, use for staff paid every week (for example every Friday). Each salaried person is paid the amount per week set on their profile. Staff paid by the day or by the hour are paid from their confirmed attendance; see Paying daily, hourly and commission-only staff.
  • Bi-weekly, use for fortnightly cadences common in field-service teams. Spans 14 days.
  • Custom, use for non-standard periods such as a back-dated catch-up run that spans an arbitrary date range. A bonus, 13th month, arrears or any other extra payment for employees who are already on a payroll run for the same period cannot be added as a separate run. Do not enter a bonus as a taxable custom allowance: SpireSlip taxes custom allowances as if they were paid every month, so the tax on a one-off amount would be too high. Add it as a one-off payment on the run instead.

Each employee carries a schedule_type on their record. Only employees whose schedule matches the run appear on it. If an employee is missing from a run you expected to see them on, check their profile and confirm their assigned schedule.

Draft vs approved

A draft run is mutable. You can recompute, edit individual lines, change schedule types on employees, and even delete the draft entirely. Drafts are the place to experiment. A computed run can still be changed too: any change sends it back to draft, and you compute it again before you approve it.

An approved run is locked permanently. The payroll lines, tax computations, and totals are frozen, the SHA-256 approval hash is stamped, and the audit trail is sealed. From approval onwards you can disburse, schedule the disbursement, retry a failed line, record the run as paid outside SpireSlip, or void it (owner or admin, with a reason, before anyone on it is paid or a payment is in progress). See Voiding a payroll run.

Email verification gate

Before you can approve or disburse, the account owner's email address must be verified. Creating and computing runs work normally before verification, so you can still test the workflow. If you see the amber verification banner on the dashboard, click Resend email to get a fresh verification link. Approval and disbursement actions stay disabled until the link is clicked.

If a transfer fails

SpireSlip does not roll back the whole run when a single transfer fails. The run stays in disbursed state, the successful lines are paid, and the failed lines are marked Failed. Click Retry on each failed line to resend the transfer (SpireSlip first asks you to confirm it is you if you have not in the last 10 minutes). The most common causes are an incorrect account number, a wrong bank code, or insufficient float on the disbursement source. See Transfer failures and retry for where the reason for a failure is shown.

A typical monthly cadence

  • Last week of the month, create the run. Schedule type monthly, period the calendar month closing.
  • Mid-week before payday, compute and review. Cross-check totals against your accruals.
  • Salary day morning, approve. The run locks.
  • Salary day, immediately after approval, disburse. Transfers usually land in employee accounts within minutes.

For multi-entity accounts on the Complete, Enterprise, or Accountant plan, see Bulk payroll runs to fire monthly across every entity in one operation.

For contractors paid via WHT, the workflow is the same but the engine applies withholding tax instead of PAYE. See Running payroll for contractors.