No articles found for “”.
How SpireSlip works
Three concepts make up the whole of SpireSlip: entities, employees, and payroll runs. Once you understand how they fit together, the rest of the product is just detail on top.
Entity
Your company. Or, if you're an accountant, each client company. All data in SpireSlip is scoped to an entity, employees belong to one entity, payroll runs belong to one entity, reports belong to one entity. Multiple entities under the same login means multiple companies kept entirely separate.
Employee
Anyone on your payroll. SpireSlip stores the data needed to pay them correctly and compliantly: salary structure (basic, housing, transport), bank account, NIN and TIN (encrypted), PFA name and code, identity verification status, contract.
Payroll run
A single pay cycle. You create a run for a period (monthly is the default; weekly, bi-weekly, and custom are also supported), SpireSlip computes PAYE and every statutory deduction for every employee, you review the figures, approve them, and disburse. After disbursement, payslips are emailed automatically and filing schedules become available.
The payroll lifecycle
Every payroll run moves through four states:
- Draft → Computed → Approved → Disbursed.
Each step is deliberate. SpireSlip never moves money without your explicit approval, and the cryptographic hash captured at approval is checked again at disbursement to confirm nothing changed in between.
Nigerian compliance is automatic
PAYE brackets, pension rates, NHF, and NSITF are applied without any configuration from you. Rates update annually when the Nigeria Revenue Service or PenCom issues new figures. Historical runs always re-compute with their period's rates, never the current ones, so re-opening last March's run shows last March's numbers exactly.
Records are permanent
Payslips, payroll runs, and filing reports are retained permanently. Even after an account is cancelled, statutory records remain available, see Data retention policy.