Skip to main content
SpireSlip

Paying a bonus or other one-off payment

A one-off payment is an extra amount paid to one employee on one payroll run: a bonus, a 13th month payment, arrears, final pay when someone leaves, or any other one-off amount. Commission is entered in the same place but is treated as pay, not as a one-off; see Paying commission. Add it to the run the employee is already on. You do not need a separate run, and an employee can only be on one run for a period.

Adding a one-off payment

  1. Open the payroll run while it is a draft or computed. Approved and paid runs cannot be changed.
  2. In One-off payments, choose the employee and the type.
  3. Enter the amount in Naira, for example 150000 or 150,000.50. Entering 1000000 means one million Naira.
  4. Leave Taxable ticked unless the payment is genuinely exempt. A payment that is not taxable needs a note saying why.
  5. Click Add payment, then compute the run again. Every change to a one-off payment sends the run back to draft, so it must be computed again before it can be approved.

If an amount is more than 3 times the employee's monthly gross salary, SpireSlip asks you to tick I have checked this amount before saving it. This catches typing mistakes such as an extra zero.

Adding many payments at once (CSV)

On the run page, under One-off payments, choose Add many payments from a CSV file. Download the CSV template first. The columns are employee_email, type (bonus, thirteenth_month, arrears, commission or other), amount_naira, taxable (yes or no), note (needed when taxable is no) and confirm_large (write yes for an amount more than 3 times the employee's monthly gross). Amounts are in Naira, for example 500000 or 500,000.50. For commission you can leave amount_naira blank and fill percent and basis_naira instead (see Paying commission). A file can have at most 500 rows. Final pay cannot be imported; use Add final pay.

Uploading only checks the file: you see every payment, the total for each type and the overall total before anything is added. If any row has a problem, nothing is added and each problem is listed by row and column. Two identical rows in one file (same employee, type and amount) are refused as a likely double entry; if you really mean two identical payments, upload them in two files or add one by hand. A row that matches a payment already on the run is flagged "may already be added", so uploading the same file twice is caught. Confirm and add adds the payments once: pressing it again, or going back and resubmitting, adds nothing more. The file only adds payments; it never changes or removes the ones already on the run. Compute the run again afterwards. The person who uploads the file counts as having changed the run's one-off payments, so a different person must approve the run.

How one-off payments are taxed

  • A taxable one-off payment is taxed once, in the pay period it is paid. PAYE is worked out on the employee's annual taxable income with the payment added, minus the PAYE without it, so only the extra tax the payment causes is taken. It is not treated as if it were paid every month.
  • One-off payments are not pensionable and are not part of gross salary, so pension, NHF and NSITF do not change.
  • A payment that is not taxable is added to net pay in full, after tax.
  • SpireSlip taxes arrears in the period they are paid.
  • Contractors: a taxable one-off payment is paid and has withholding tax (WHT) taken at the contractor's WHT rate, once, in the period it is paid. WHT is worked out on the contractor's payment and the one-off together, so a taxable one-off of one fifth of the payment raises the WHT by one fifth too. A non-taxable one-off is added to their net payment with no WHT. Taxable gratuity and leave encashment are not paid to contractors: when a contractor has some, the run and the approve page show a warning with the amount.

On the payslip, one-off payments appear together under One-off payments, and the tax on them appears as its own line, PAYE on one-off payments.

Final pay when someone leaves

When the entity has gratuity turned on, Add final pay on the run adds the employee's gratuity, worked out from the entity's gratuity settings. Whether it is taxed follows the entity's gratuity setting. Add final pay before terminating the employee: a terminated employee cannot be added to a later run. After the run is paid, the run page offers to mark them as terminated. Nothing is terminated automatically.

An offboarding run already adds gratuity for everyone on it, so Add final pay is not offered there.

Who can approve a run with one-off payments

  • Anyone who added, changed, removed or copied a one-off payment on the run, or added final pay, cannot approve that run. A different owner or admin must approve it.
  • The account owner can still approve their own change by writing a reason of at least 10 characters. The reason is kept in the audit log, and the other approvers see a notice that the owner approved the run with an override. Admins cannot override.
  • If only one person on the account can approve payroll for this entity, the check does not apply, so a business with a single owner is never stuck. The approval is recorded in the audit log.
  • A run with one-off payments cannot be approved through the API. Approve it in SpireSlip.

If a run is voided

The one-off payments stay on the voided run as history. On the new draft run for the same period, Copy one-offs from voided run copies them across. Any payment for an employee who is no longer active, is not on the new run, or is now paid in another currency is not copied, and SpireSlip lists it with the reason.

Limits

  • One-off payments are for employees paid in Naira.
  • They cannot be added to test runs.
  • Every add, change and removal is recorded in the audit log with the amount and who made it.