PayoutsNext

Run payouts with a second pair of eyes.

JSON or CSV runs, every line validated, maker-checker approval with PIN.

Next. Bulk payouts is built and on its way to Live. Tell us if you need it, and we'll tell you honestly when it will be ready for you.

Illustrative
Why it matters

What it will change.

Paying hundreds of people at once is where the biggest mistakes happen: a wrong file, a duplicated row, a run sent by one person with nobody checking.

Bulk payouts will take a run as JSON or CSV, validate every line, and need a maker and a checker to approve, each with their own PIN, before anything moves. People without an account will be able to claim their payout. It's built and on its way; it isn't confirmed live yet.

It is payroll runs, not a payroll product: it pays what you've calculated; it doesn't calculate pay, tax or pensions.

How it works

Step by step.

  1. Upload a run

    JSON or CSV, one line per payee.

  2. Every line validated

    Accounts and names will be checked before anyone is asked to approve.

  3. Maker and checker

    Two people will approve, each with their own PIN. The maker can't be the checker.

  4. Paid line by line

    Each line will be paid and reported on its own; a failure won't stop the run.

  5. Claimable payouts

    People without an account will be able to claim their money.

What it will do

Built in, not bolted on.

JSON or CSV

Upload runs from your own payroll or stipend system.

Validated before approval

Every line will be checked first, so approvers see a clean run.

Maker-checker with PINs

Two approvers, two PINs, and the maker won't be able to approve their own run.

Line-by-line results

Each line's status will be reported separately.

Claimable payouts

Payees without an account will be able to claim.

Signed status per line

Every line's outcome will arrive as a signed webhook.

  • Upload a run as JSON or CSV
  • Every line validated before anything is approved
  • Maker-checker approval, each approver with their own PIN
  • Claimable payouts for people without an account yet
Use cases

How businesses could use it.

Illustrative businesses, not customers. Figures are made up to show the flow.

A hospital group in Enugu · Payroll & HR platforms

Monthly payroll with two approvers

One accountant uploads and sends the payroll from the bank portal. The board wants a second approval before money moves.

  1. HR will export the month's payroll as CSV
  2. The run will be validated line by line
  3. The finance manager will approve with their PIN as checker
  4. Each staff member will be paid and reported on

No single person will be able to send the payroll.

Illustrative

An NGO running a youth skills programme in Kano · NGOs & government

Stipends for programme participants

Participants receive a monthly stipend; some have no bank account.

  1. The programme will upload the month's stipends
  2. Two officers will approve
  3. Participants with accounts will be paid directly
  4. Others will claim theirs

Every participant would get their stipend, account or not.

Illustrative

A ride-hailing company in Lagos · Marketplaces

Weekly payouts to drivers

Thousands of drivers are paid weekly from a spreadsheet.

  1. The weekly earnings file will be uploaded
  2. It will be validated, then approved by ops and finance
  3. Each driver will be paid, with failures reported per line

Weekly payouts would run on time with two approvals.

Illustrative
What it won't do

Honest limits.

  • It is payroll runs, not a payroll product: it does not calculate pay, tax or pensions.

Questions about bulk payouts

Is bulk payouts available now?

It's built and on its way; it isn't confirmed live yet. Tell us if you need it.

Does it calculate pay?

No. It pays runs you've calculated; it doesn't calculate pay, tax or pensions.

Can one person approve a run?

No. It will need a maker and a different checker, each with their own PIN.

Bridge for Business

Tell us what you're building.

We'll come back with what's live for you today, and what's next.