Skip to main content
SpireSlip

Disbursing salaries

Disbursement is the step that sends bank transfers from your Paystack balance into your employees' accounts. It happens after a payroll run has been approved.

How to disburse

  1. Open the approved run.
  2. Click Review disbursement.
  3. SpireSlip lists every transfer that will happen, with its bank and amount: each employee's primary account, and a row under it for each other account their pay is split to. An employee's rows add up to their net pay, before and after sending.
  4. If any employee's primary account is still unverified, SpireSlip names the employees and will not start the disbursement until those accounts are verified. A second or third account that cannot be paid yet (it is not verified, or Paystack has not set it up as a recipient) is left out of the send, and its share goes to the employee's primary account; the page says how many employees have one. On each of those employees' profiles, an owner or admin clicks Verify next to the account in the Bank accounts section; it checks the account name through your company's payment connection.
  5. Click Disburse now.

Before the transfers go out, SpireSlip asks you to confirm it is you with your password, or your authenticator code if you use one. You are not asked again for 10 minutes when you retry or resume a transfer. See Account security.

How long it takes

After you click Disburse now, SpireSlip starts sending at once and takes you to the run page, which shows Sending next to the run status and a progress box: how many transfers are paid, failed, awaiting confirmation and not started yet. The counts update by themselves every few seconds. A small run finishes in a few seconds; larger runs can take a minute or two. You can leave the page: sending carries on, and the run page shows the result when you come back.

While a run is sending, actions that would change it (void, schedule, retry, mark as paid) are refused with "Salaries for this run are being sent right now. Wait until sending finishes, then try again." If sending makes no progress for a few minutes, SpireSlip resumes it automatically, and the progress box offers a Resume sending button. A transfer that has been sent is never sent again.

Clicking twice, opening the run in a second tab or pressing back and submitting again is safe: a run that is already sending is refused with "Salaries for this run are being sent right now. Wait until sending finishes, then try again.", and a transfer that has been sent is never sent again unless Paystack confirms it failed.

Payslips (and remittance advice for contractors) are emailed after each payment goes through, usually within a minute of the transfer.

What happens behind the scenes

SpireSlip submits each transfer to Paystack and records what Paystack reports back per transfer:

  • Success, the money has been moved to the employee's account.
  • Processing, the transfer was sent but Paystack has not confirmed it yet. Paystack usually accepts a transfer first and confirms it a few seconds to a few minutes later, so most transfers show here first and the run page says how many are awaiting confirmation from Paystack. The employee's payslip and notification, and the run's Disbursed status, wait for that confirmation. SpireSlip checks with Paystack on its own and updates it: every minute at first, then every 15 minutes if a transfer is still unconfirmed after an hour, and hourly after a day. You can click Check status on the run page at any time. A transfer in this state is never sent again while it is waiting, so it cannot be paid twice.
  • Failed, Paystack confirmed the transfer did not go through, so no money left your balance. You can retry it. See Transfer failures and retry.

If a paid transfer is later reported failed or reversed

Rarely, a payment provider reports that a transfer it had already confirmed as paid has failed or was reversed by the bank. SpireSlip does not change the payslip and does not send the money again. Every active owner gets an email, and owners and admins see one urgent notification naming the employee, the amount and the payroll run. Check the transfer in your payment provider account. If the person has not been paid, pay them another way and tell SpireSlip support.

Paying salaries outside SpireSlip

If you paid some or all of an approved run yourself, for example by a transfer from your own bank, you can record that in SpireSlip so the run, the payslips and your records are complete. SpireSlip does not send any money when you do this. An owner or admin can do it; if your company pays salaries through SpireSlip, only the owner can. Bank accounts do not need to be verified for this, and a company without a payment connection can use it for every run.

  1. Open the approved run and click the Transfers tab.
  2. Click Record as paid outside SpireSlip.
  3. Leave ticked the salaries you paid. If you untick any, write a reason of at least 10 characters.
  4. Enter the date you paid, choose Bank transfer or Other, and enter a reference such as your bank batch number.
  5. Click Continue to confirm. Nothing is saved yet.
  6. On the next page, check the list and total, tick the confirmation box and click Confirm: record as paid outside SpireSlip.

Each recorded salary then shows "Recorded by (name) as paid outside SpireSlip on (date)" with the method and reference, and the run shows how many salaries were recorded this way and that SpireSlip did not send this money. Payslips are sent to those employees at once, the same as when SpireSlip pays them, and each payslip says it was paid outside SpireSlip. A recorded salary can never be paid through SpireSlip afterwards, so it cannot be paid twice. Salaries that are being sent or have failed cannot be recorded this way; a failed transfer should be retried or checked first. Recording cannot be undone in the app; if you recorded a salary by mistake, contact SpireSlip support. If you pay from your own bank, SpireSlip can give you a file to upload there first: see Paying salaries from your own bank.

Leaving one person out of a send

If one person on an approved run should not be paid by this send, for example because their bank account is not verified yet, you can leave them out and send everyone else. The same people can do this as can record a salary as paid outside SpireSlip: an owner or admin, or only the owner if your company pays salaries through SpireSlip.

  1. Open the run and click Review disbursement.
  2. Next to the person, click Leave out of this send. If a bank that is not verified stops the send, the same link is shown next to each name in the red box.
  3. Check the name, the amount and the new send total, write a reason of at least 10 characters, tick the box and click Leave out of this send.

The person is not paid and gets no payslip while they are left out. Their salary shows "Left out, not paid" with your name, the date and the reason, and the run shows how many salaries are left out of this send. The run is not marked as paid while anyone is left out. When you are ready, either click Put back in this send so SpireSlip pays them the next time you send the run, or pay them yourself and record it with Record as paid outside SpireSlip. You cannot leave someone out while salaries are being sent, or once part of their salary has gone to one of their accounts.

Split payroll

For employees with multiple bank accounts, SpireSlip initiates a separate transfer per account, one to the primary, one to each split. See Split payroll for the full mechanics.

Test mode

While the entity's Paystack key is a test key, SpireSlip does not send salaries, see Test mode disbursement for what to expect. Switching to live mode is covered in Switching to live mode.

The hash check

Before any transfer is submitted, SpireSlip re-computes the approval hash and compares it to the one stored at approval time. If they don't match, meaning the payroll lines have been tampered with, disbursement aborts. This is your safety net against silent data corruption between approval and pay-out.