Albo Book a demo

Payroll and HR software

Payroll that follows your rules, right every month

Albo works out every employee's pay from the rules in your conditions of service, has each run approved before it posts, and produces the payslips, bank file and statutory returns that follow. It runs on your own server, so your payroll never leaves the building.

  • PAYE
  • NAPSA
  • NHIMA
  • Skills levy
  • WCF
The Albo dashboard for a sample mining company: 351 employees, February's net pay, and the last five pay runs.
50,000employees in one pay run, by design
6approval steps at most, each by its own role
0tax rates typed by hand
Everychange kept, with who made it and when

Why payroll teams choose Albo

Most payroll software makes you choose between the power to write your own rules and the safety of a system that checks itself. Albo gives you both.

Your rules, not ours

Allowances, deductions, overtime, loan interest and terminal benefits are formulas you can read. A collective agreement fits as it is written, without a developer.

Rates nobody types

PAYE bands, NAPSA, NHIMA, the skills levy and WCF arrive in signed rate packs, dated from the day the law changes. Nobody in the office can alter a rate.

Final once posted

A posted run is never edited. A mistake is put right with a reversal or an adjustment run, so last year's payslips still say what was paid.

Four eyes on every run

The person who prepares a run cannot approve it. With Professional, pay runs, loans and leave each follow their own chain of up to six steps.

Built for 50,000 people

The run works through staff in chunks of 1,000, written to the database in one go, so a mine's payroll runs the same way as a small office's.

Yours, on your server

Your payroll never leaves your building. If a licence year lapses, Albo keeps paying people. Wages are never held back.

Albo in under a minute

Formulas, the month's run, approvals, rate packs and loans, start to finish.

No sound. The figures are worked examples and the staff are made up.

Your rules, as formulas

Your conditions of service, set up once

Every allowance and deduction carries a formula over basic pay, days worked, hours, shifts and the figures in each grade. A collective agreement fits the system, instead of the other way round.

  • Plain words: basic, units, daysWorked, workingDaysPerYear
  • IF, MIN, MAX and ROUND for caps, tiers and conditions
  • One rule over a set of grades, effective from a date
  • Test any formula against sample figures before a run uses it

Pay components Examples

Housing allowance Grades J1 to J5
basic * 0.12
Normal overtime Hours entered each month
basic * units * 1.5 / workingHoursPerMonth
Fuel allowance Grade EX, units each month
380 * units
Leave commutation Days sold back
basic * 12 * units / workingDaysPerYear
Transport allowance With a cap
MIN(basic * 0.05, 2500)
Private pension Employer's share
basic * 0.15

One month's payroll, start to finish

Six steps from the first overtime sheet to the last return. Albo checks each one before the next can start.

Step 1

Prepare the month

Overtime hours, shifts, new starters, leavers and one-off payments go in, by hand or from a spreadsheet. Albo checks every row before it accepts the file.

Rated units, February Imported

EmployeeComponentUnits
Abel MwambaNormal overtime12.00
Bupe MubangaSunday overtime8.00
Twaambo MalamboFuel allowance28.10
Yande NgulubeNormal overtime6.50

Step 2

Every payslip worked out

Each person's formulas run, then PAYE on the year to date, NAPSA, NHIMA and the skills levy from the rate pack in force, then loan instalments and other deductions.

Computing February Running

Payslips
350 of 350
Gross pay
K 18,914,451.21
Net pay
K 11,015,313.05

Step 3

Albo flags what needs a look

Before anyone approves, the run lists what is unusual: someone on hold, a loan instalment held back to protect take-home pay, and how this month compares with the last.

February, before approval

  • 1 person on holdOn a no-pay hold all month, so no payslip this run.
  • 2 loan instalments held backTaking them would leave the person below the least take-home.
  • Net pay up 0.1% on JanuaryHeadcount unchanged at 350.

Step 4

A second person approves

The person who prepared the run cannot approve it. Each step is taken by someone holding that step's role, and Albo tells them when it is their turn.

Approval steps

  1. PreparedPayroll officer
  2. Payroll reviewPayroll manager
  3. FinanceFinance manager
  4. Sign-offManaging director

Step 5

Posted, and final

Posting closes the run for good. From then on it is a record: it is never edited, and a correction is a reversal or an adjustment run that sits beside it.

February 2027 is posted

19 Nov 2026, 21:57, by Lweendo Hachinda

Step 6

Pay people, then file

A bank file for each employer account, payslips to print, or to email with Professional, the month's returns for ZRA, NAPSA and NHIMA, and the journal for your ledger, all from the posted run.

Ready for February

  • Bank payment file350 people
  • Payslips350 PDFs
  • PAYE and skills levyZRA
  • Pension scheduleNAPSA
  • Health insurance scheduleNHIMA
  • Payroll journalYour ledger

See it working

The whole payroll year, in one place

Real screens from Albo, with a sample company's made-up staff.

Approved before it posts, final once it does

A run is a draft until someone other than the person who prepared it approves it. Albo flags what needs a look first: a person on hold, a loan instalment that would leave someone below their least take-home. Once posted, a run is never edited. A mistake is put right with a reversal or an adjustment run.

A posted February run for 350 employees with its four steps, and notes on a person on hold and loan instalments held back.

Every return, ready to file

What the month owes ZRA, NAPSA and NHIMA, with the employee and employer sides, and the full schedules to download for each authority. The WCF annual return comes from the same posted runs.

February's statutory returns: PAYE and the skills levy to ZRA, NAPSA and NHIMA, with the total to remit.

Every employee on one page

Grade and pay, bank details, leave, loans and every payslip. Bring your staff in from a spreadsheet with their year-to-date pay and tax, and start in any month of the year.

An employee's page: grade, basic pay, bank, the last payslip with gross pay, PAYE and net pay, and leave available.

Who changed what, and when

Every change to a person's record is kept: what it was, what it became, who made it and when. Nothing is quietly overwritten, and the history cannot be deleted.

An employee's change history: rated units entered each month, with who entered them and when.

Loans that look after take-home pay

House, car, personal and education loans, and salary advances, each with its schedule, recovered on the payslip. Lending rules stop an instalment from leaving anyone below the take-home you set.

Staff loans across the workforce: principal, what is still owed, the monthly instalment and the instalments left.

This month against last

Headcount, the wage bill, what the company pays on top and the averages per person, set against the month before, with every component and who joined or left. One download carries it all.

The payroll summary comparing February with January: headcount, gross pay, deductions, net pay and employer contributions.

Staff loans and salary advances

Loans that look after take-home pay

Lend to staff on your own terms, recover it on the payslip, and never leave anyone with too little to live on.

  • Five ways to charge interest: interest-free, flat, compound, reducing balance, or your own formula
  • Limits by grade, as a fixed amount or months of basic pay
  • Lending rules: a least take-home, a cap on advances, one loan of a type at a time, months of service before borrowing
  • Every new loan approved before it runs, and extra repayments by cash, bank or mobile money kept on record
  • One list of everyone already past your limits

Loans and advances come with Professional.

Personal loan

K 12,000.00 over 6 months, flat 12% a year

12,000 × 12% × ½ year = 720 interest. 12,720 ÷ 6 = K 2,120.00 a month.

Repayment schedule
MonthInstalmentStill owed
January2,120.0010,600.00
February2,120.008,480.00
March2,120.006,360.00
April2,120.004,240.00
May2,120.002,120.00
June2,120.000.00

When pay is short

Least take-home is 40% of basic. On K 9,000 basic, that is K 3,600.

This month's take-home before the loan is K 5,200. Taking K 2,120 would leave K 3,080, so the instalment is held back and the loan runs a month longer. PAYE, NAPSA and NHIMA are still taken.

Approvals

Approvals that follow your organisation

Set the steps once, each taken by a role you choose. Albo sends the work to whoever holds the next step, and nothing moves until they act.

  • Pay runs, loans and leave requests, each with its own steps
  • Up to six steps, each approved by its own role
  • Whoever keyed it can never approve it
  • Approvers see what waits for them as soon as they sign in
  • Every decision kept, with who made it and when

A second person approves every run in both editions. Chains of several steps come with Professional.

Tax rates nobody has to type

PAYE bands, NAPSA, NHIMA, the skills levy and the WCF rates come to you in a rate pack from eLucive. It is signed, so it cannot be altered on the way, and nobody in your office can change a rate by hand.

  1. The law changes

    A budget or a statutory instrument sets a new band or rate, and the day it starts.

  2. eLucive signs a pack

    The new figures, checked against the Act or the notice, dated from that day.

  3. Albo checks the signature

    A pack that has been touched is refused. Every install is kept on record.

  4. The next run uses it

    Months before the change keep the old rates, so a back-pay run is still right.

Switching to Albo

Leave the old system behind. Keep everything it knew.

Moving payroll is the part people dread. With Albo it is your own spreadsheets, checked row by row, one month run side by side, and a go-live. Nobody's tax starts again from zero.

  • Your spreadsheets, as they are

    Upload a file or paste rows straight from Excel. People and grades are matched by the staff numbers and grade codes you already use.

  • Every row checked before anything is saved

    You see what a file will do first. One wrong row stops the file and names its line, so nothing is ever half loaded.

  • Tax carries on in the middle of the year

    Year-to-date pay and PAYE come across, so cumulative PAYE carries on from the right figure in whichever month you switch.

5,000 staffloaded in under a second, with every one of them on the record.

The same month, two ways

Pick a moment every payroll office knows.

The budget changes the tax bands

An old system

  1. Someone finds the new bands in the budget papers
  2. They type them into a table, often after hours
  3. A few payslips are checked by hand
  4. Everyone hopes nothing was mistyped

Albo

  1. eLucive sends a signed rate pack, dated from the day the law starts
  2. Albo checks the signature and keeps a record of the install
  3. The next run uses it, and earlier months keep the rates they were paid on

Nobody types a rate

A run went out wrong

An old system

  1. Someone opens the posted month and edits it
  2. Or last night's backup is restored and the month done again
  3. The record no longer shows what people were actually paid

Albo

  1. The posted run stays exactly as it was paid
  2. A reversal or an adjustment run puts it right, approved like any other run
  3. Tax is worked out again from the year to date, so the next payslip is right

Every kwacha paid stays on the record

The auditor asks who changed a salary

An old system

  1. The system holds today's figure, not the one before it
  2. Nobody can say who changed it, or when
  3. Someone searches old emails for the instruction

Albo

  1. Open the person's history
  2. Every change is there: who made it, when, and what it was before

The answer is on the screen

Someone leaves in the middle of the month

An old system

  1. Final pay is worked out on a calculator
  2. Leave days are counted by hand from a file
  3. ZRA's leaver's certificate is typed up separately

Albo

  1. A settlement pays them to their last day, with leave owed and terminal benefits
  2. It is approved and posted like any run
  3. ZRA's leaver's certificate comes out of the payroll, filled in

Paid right on the way out

The payroll is ready to pay

An old system

  1. The person who prepared it approves it too
  2. Nobody else sees it before the bank does

Albo

  1. A second person approves before it posts, and whoever prepared it never can
  2. With Professional, up to six steps, each taken by its own role
  3. Every decision is kept, with who made it and when

Four eyes on every run

The returns are due

An old system

  1. Totals are copied from reports into each authority's template
  2. They are added up again to check
  3. A figure that differs from the payslips is found later, if at all

Albo

  1. PAYE, NAPSA, NHIMA, skills levy and WCF come straight from the posted run
  2. Each authority's schedule downloads ready to file

Filed from the same figures you paid

Your payroll stays in your building

Albo is installed on your own server. Not a website you rent, and not someone else's cloud.

Your data stays with you

On a Linux or Windows server in your building or your data centre. Albo sends none of your employees' data to eLucive or anyone else, and it does not need the internet to run a payroll.

Nothing to install on desks

Your team uses Albo from a web browser on the company network, and each person sees only what their role allows. With Professional, they sign in with your Active Directory.

Wages are never held back

If a licence year is not renewed, Albo keeps running. You can still pay people and read your records. Only new rate packs, updates and support stop.

Everyone you employ

From 50 staff to 50,000, on one payroll

Permanent staff, fixed-term contracts, casuals paid by the day and shift workers paid by the unit. Each is paid the way their terms say, and all of them in the same run.

50,000
people: the size every run is built for
10,000+
people in one run, reviewed on one screen
One rate
per person, whatever your size
  1. 50A school
  2. 500A factory
  3. 5,000A mine
  4. 50,000A group of companies

The same screens, the same rules and the same price per person at every size.

Payrolls like these

  • Mines and quarries
  • Manufacturers
  • Farms and estates
  • Construction
  • Hospitals
  • Schools and colleges
  • NGOs
  • Groups of companies

Getting started

From first call to first payday

We set Albo up with you, a step at a time. Your old payroll keeps running until Albo has matched it payslip for payslip, so nobody's pay is ever the experiment.

Bring these to the first meeting

  • A recent payslip and the month's payroll report
  • Your conditions of service, or the collective agreement
  • The staff list, as a spreadsheet
  • Year-to-date figures, if you switch in the middle of the year
  • Loan and leave balances
Book the first meeting
  1. Step 1

    See it with your own pay rules

    eLucive
    Shows Albo with a sample company, then sets up a few of your own components as formulas.
    Your team
    Tells us how you pay today, with a payslip to work from.
  2. Step 2

    Install and set up

    eLucive
    Installs Albo on your server and sets up grades, components, roles and approvals with you.
    Your team
    Provides a Linux or Windows server on your network, and names who approves what.
  3. Step 3

    Bring your data across

    eLucive
    Loads staff, bank details, year to date, loans and leave, every row checked.
    Your team
    Exports the spreadsheets from the old system.
  4. Step 4

    Run a month side by side

    eLucive
    Runs the same month in Albo and compares every payslip with yours.
    Your team
    Runs the old payroll as usual, and agrees any difference.
  5. Step 5

    Train, and go live

    eLucive
    Trains the people who prepare, approve and post, and stays close for the first runs.
    Your team
    Prepares, approves and posts the first month in Albo.
  6. First payday

    Your people are paid from Albo, and the returns are filed from the same figures.

Editions and pricing

Two editions. One price per person.

Both pay people lawfully, end to end, with every statutory return. Professional adds what larger and more complex payrolls need.

Standard

Everything it takes to pay people right

For payrolls paid mostly by the month, with one person to approve each run.

  • Pay components written as formulas
  • Monthly staff and casuals paid by the day
  • The monthly run, approved by a second person
  • Payslips and bank payment files
  • PAYE, NAPSA, NHIMA, skills levy and WCF returns
  • Leave, leavers and terminal benefits
  • The payroll journal for your ledger

Ask about Standard

Professional

Everything in Standard, plus

For larger payrolls with shifts, staff loans and approvals across departments.

  • Loans and advances, with lending rules
  • Hours, shifts and piece work paid by the unit
  • Approval chains of up to six steps
  • Sign-in with Active Directory or LDAP
  • Payslips emailed to each person
  • Management reports: cost by unit, coinage, loans
  • Group reporting across your companies

Ask about Professional

How the price works

  • Per employee in service

    Counted each year at renewal. Everyone in your office who uses Albo is included.

  • The same rate at every size

    No price bands, so one more hire never makes the price jump.

  • A yearly licence, with a minimum

    Signed rate packs, updates and support are part of it.

  • Groups pay less

    Several companies in a group take a discount on each install, never a surcharge.

If a year is not renewed, Albo keeps paying your people. Only new rate packs, updates and support stop.

Setting up and bringing in your data is quoted with the licence, by the size of your payroll. Ask us for a quote

Compare the editions, line by line

FeatureStandardProfessional
Paying people
Employees, grades and positionsIncludedIncluded
Pay components written as formulasIncludedIncluded
Monthly staff and casuals paid by the dayIncludedIncluded
Hours, shifts and piece work paid by the unitNot includedIncluded
Loans and advances, with lending rulesNot includedIncluded
The pay run
Run, review, approve by a second person, postIncludedIncluded
Reversals, adjustment runs and leavers' settlementsIncludedIncluded
Approval chains of up to six stepsNot includedIncluded
Paying and filing
Payslips and bank payment filesIncludedIncluded
PAYE, NAPSA, NHIMA, skills levy and WCF returnsIncludedIncluded
The payroll journal for your ledgerIncludedIncluded
Payslips emailed to each personNot includedIncluded
People and control
Leave, leavers and terminal benefitsIncludedIncluded
Roles, permissions and change historyIncludedIncluded
Sign-in with Active Directory or LDAPNot includedIncluded
Reports
Payroll and statutory reportsIncludedIncluded
Cost by unit, coinage and loans reportsNot includedIncluded
Group reporting across your companiesNot includedIncluded
Every year
Signed rate packs, updates and supportIncludedIncluded

Questions people ask us

Something else?

Ask us about your own payroll. A person at eLucive answers.

What happens when ZRA changes the tax bands?

eLucive builds a rate pack with the new bands, signs it so it cannot be altered, and dates it from the day the law takes effect. You install it, Albo checks the signature, and the next run uses it. Months before the change keep the old rates. Nobody types a tax band.

Can we move to Albo in the middle of the tax year?

Yes. We import your employees and their year-to-date pay and tax, so PAYE carries on correctly from the month you switch. We recommend running Albo beside your current payroll for a month and comparing every payslip before you go live.

Where is our payroll data kept?

On your own server, in your building or your data centre. Albo does not send your employees' data to eLucive or anywhere else, and it does not need the internet to run a payroll.

What do we need to run it?

A server or virtual machine with Linux or Windows Server, Java 21 and MySQL 8.4. Your staff use Albo from a web browser; nothing is installed on their computers. We size the machine with your IT team before the install.

How does Albo work out PAYE?

Cumulatively, on the year to date, from the bands in the rate pack in force. A back-pay or adjustment run is re-taxed through the year to date, so the tax comes out right without a special rule for arrears.

Can Albo handle staff loans and salary advances?

Yes, with the Professional edition. Each loan type has its own interest method, from interest-free to reducing balance or your own formula, limits by grade, and your lending rules. Instalments come off the payslip, and an instalment that would leave someone below the least take-home is held back for a month.

Can a pay run need more than one approval?

Yes. In both editions a second person approves every run. With Professional, pay runs, loans and leave requests each follow their own chain of up to six steps, each taken by a role you choose. Whoever prepared it can never approve it.

Does Albo handle leave?

Yes. Leave types with their own accrual, requests and approvals, balances, the leave year-end, and leave sold back paid on the payslip.

Can Albo pay casual and general labour?

Yes. Hours, shifts, days and piece work are entered as units each month and paid at a rate that follows each person's pay. This comes with the Professional edition.

We have several companies. How does that work?

Each company has its own install, so each payroll stays its own. With Professional, head office brings every company's monthly figures together and sees the group's payroll as one.

What happens if we do not renew the licence?

Albo keeps running. You can still pay people and read your records. What stops is new rate packs, updates and support, so the tax rates go out of date. Wages are never held back.

Who supports Albo?

eLucive, the team that builds it, from Lusaka. Rate packs, updates and support come with the licence; implementation and training are part of getting you live.

How is Albo priced?

By the number of employees in service, at the same rate whatever your size, with a yearly minimum. A group with several companies pays less per install.

Ask us for a quote

Is Albo only for large companies?

No. It suits a company of 50 staff, and the pay run is built for 50,000.

See Albo with your own pay rules

Tell us how many people you pay, how they are paid, and what you use today. We will show you Albo working on rules like yours, at your office or online.

Call
+260 979 068 878
Email
info@elucive.co
Office
Lusaka, Zambia