How to Manage Beneficiaries and Staff Lists in Nigeria

Short answer: Your beneficiary list is the master record of everyone you pay: employees, contractors, vendors, and repeat contacts. Keep one verified list, use bulk upload for scale, and invite staff to register so you are not retyping bank details from chat screenshots.

"Beneficiary" sounds like banking jargon. In practice it is your people you pay file. Messy lists cause wrong transfers, double pay, and pay day panic.

Who belongs on your beneficiary list

Not everyone needs the same fields. Employees need full payroll context; a monthly cleaner might need only name, bank, and amount.

Build the list once, pay many times

Good habit:

1. Add person with legal name and role
2. Verify bank account name match
3. Tag company and pay type (salary vs contractor)
4. Pay from batch payroll or Quick Transfer
5. Archive when they leave (do not delete history)

Updating bank details should go through approval, not a random SMS to the founder.

Bulk upload when you have scale

If you are migrating from Excel or onboarding dozens of staff:

• Prepare CSV or JSON with names, accounts, and amounts
• Upload in one pass (Staff Pay supports up to 1,000 beneficiaries per bulk import)
• Review close name matches before confirm
• Fix misreads inline instead of silent wrong pay

Invite to register (self-service onboarding)

Instead of chasing account numbers:

1. Send invite link
2. Candidate or staff submits their own details
3. You approve or reject in one queue
4. Approved people land on the right company roster

Fewer errors, less WhatsApp archaeology.

Verification before first pay

For anyone new:

• BVN / NIN identity check where policy requires
• Bank resolve so account name matches ID
• Save results in Identity Book for audit

Paying an unverified account is how "wrong recipient" stories begin.

Quick Transfer vs full payroll

• Quick Transfer: several people, same or different amounts, great for bonuses or urgent pay without a full payroll run
• Payroll run: recurring salary with deductions, payslips, and schedules

Both should pull from the same beneficiary source of truth.

Cleaning a messy legacy list

Migration week checklist:

• [ ] Remove duplicates (same person, two spellings)
• [ ] Mark inactive leavers
• [ ] Confirm company assignment per person
• [ ] Run test micro-payment or resolve-only checks if policy allows
• [ ] Document who approved the go-live list

Staff portal link

When staff are on your roster and invited to the portal, they see their payslips and pay history. They cannot change bank details alone; they request, you update. That protects both sides.