How an NGO in Nigeria Can Distribute Data Bundles to Hundreds of Beneficiaries
If your programme includes a data stipend, whether for trainees on an online course, health workers submitting reports from the field, scholarship holders, or beneficiaries of a cash-plus-connectivity intervention, the distribution itself is usually the part nobody budgeted time for.
Doing it by hand does not scale. Three hundred beneficiaries across four networks, bought one at a time on a phone, is a full day of someone's work, produces no record a donor will accept, and guarantees at least a few wrong numbers.
This is what the process looks like when it is done as one batch, and what specifically goes wrong the first time.
The short version
- Collect phone numbers with the network written next to each one.
- Put them in a spreadsheet with three columns: Phone Number, Network, Amount.
- Fund one wallet with the total.
- Upload the file, review the cleaned-up list, confirm once.
- Export the per-recipient delivery report for your programme file.
One payment. One record. Up to 1,000 beneficiaries per upload, and as many uploads as your programme needs.
Why a spreadsheet, not a form
The thing that makes this work for an NGO is not speed, it is the audit trail.
A bulk batch produces one debit for the total and then one line per beneficiary showing whether that specific number received its bundle. That is the shape a donor report needs: a total that reconciles to your bank statement, and a schedule underneath it that accounts for every naira of the total. You cannot assemble that from three hundred individual purchases without a spreadsheet and an evening.
It also means a failure is visible rather than silent. If eleven numbers out of three hundred did not receive anything, you can see exactly which eleven, and the money for those eleven has already come back to the wallet.
Building the file
Three columns, exactly as in the downloadable template:
| Phone Number | Network | Amount |
|---|---|---|
| 08031234567 | MTN | 1000 |
| 09087654321 | 9MOBILE | 500 |
| 07051234567 | AIRTEL | 1000 |
| 08151234567 | GLO | 1000 |
Header matching is forgiving: case, spaces and underscores are ignored, and Phone, Number, Mobile or Recipient are accepted for the first column, Telco, Carrier or Provider for the second. What matters is that all three are present.
Each row carries its own network and its own amount, so a single batch can mix MTN, Airtel, Glo and T2 (9mobile), so you do not need four separate files, and beneficiaries on different networks can receive different bundle values if your programme tiers them.
The mistake that catches almost everyone: Excel eats the leading zero
Nigerian mobile numbers start with a zero. Excel and Google Sheets treat a cell of digits as a number, and numbers do not have leading zeros, so 08031234567 silently becomes 8031234567 the moment you type it or paste it in.
Format the Phone Number column as Text before you enter anything, or paste with "match destination formatting" off. If you are exporting from a programme database or a Google Form, check the column in the exported file rather than assuming, because this is the single most common reason an upload is rejected or a number fails.
If you would rather start from a file that is already shaped correctly, download the template:
Before you pay, every row is checked
An unusable number, a missing network or an amount outside the allowed range is flagged before payment is taken, so you fix it rather than pay for it. A number whose prefix disagrees with the network you entered is highlighted too, in case it has been ported.
De-duplicate the file yourself. Repeated rows are not removed automatically, so if the same number appears twice it gets two bundles, and that is deliberate, because sometimes you mean it. Beneficiary lists assembled from several sources reliably contain the same person twice, so sort by phone number and check before you upload.
You review the flagged list and the total, and only then confirm.
What happens after you confirm
The total is debited from the wallet once. Bundles are then delivered one beneficiary at a time, so a three-hundred-row batch completes over a few minutes rather than instantly. It is not stuck, it is working through the list. A full 1,000-row batch takes correspondingly longer.
Anything that fails is refunded per beneficiary, automatically. If a number is barred, out of service, or the network refuses the bundle, that one amount returns to your wallet with its own refund reference, and the beneficiaries who were served stay served. You do not raise a ticket and you do not lose the whole batch.
You can then retry just the failed recipients as a fresh, smaller batch once you have corrected their numbers, without re-charging for the ones that already succeeded.
Three things worth knowing before your first batch
1. Do not buy router-only plans for beneficiaries using phones
Some high-value bundles are sold by the networks for specific hardware. MTN's HyNetFlex and MiFi plans, for example, are provisioned for a router, not a plain SIM in a handset. Ordered onto a phone they fail the large majority of the time, and while the money comes back, your distribution day does not.
If your beneficiaries are on phones, choose standard monthly or mega bundles. If part of your cohort has routers, put them in a separate batch so one group's failures do not confuse the other's report.
2. Fund the wallet before the batch, not during
A batch is paid for in full at the point you confirm it. For a large distribution, move the money in advance and check the balance covers the total, including any beneficiaries added at the last minute. A short balance stops the batch rather than part-delivering it.
3. Collect the network, not just the number
Number portability means you cannot reliably infer the network from the prefix any more, and a number that looks like MTN may have been ported to Airtel years ago. Ask for the network on your intake form. It takes one extra field and removes a whole category of failure.
If the stipend repeats every month
Most data stipends are not one-off. If yours runs monthly, set the batch up once as a recurring schedule rather than re-uploading each cycle:
- Create the batch as normal, then set it to repeat monthly instead of running once.
- Each cycle is paid from the wallet when it runs, and you are notified before it does.
- Every run is logged separately, so your monthly report is already itemised.
- A schedule that keeps failing pauses itself rather than retrying silently.
- You can pause, edit or cancel it at any point, for instance when a cohort graduates.
That turns a recurring administrative task into something that happens whether or not anyone remembers it. Set up a recurring schedule →
What a donor report needs, and where to get it
For most grant reporting you need four things, and all four come out of one batch:
| What the donor asks for | Where it comes from |
|---|---|
| Total disbursed | The single wallet debit for the batch |
| Number of beneficiaries reached | The count of successful rows in the delivery report |
| Evidence per beneficiary | One line per phone number with its own outcome and reference |
| Treatment of failures | The refund reference against each failed row, back in the same wallet |
Keep the uploaded file alongside the exported report and the two reconcile to each other.
Frequently asked questions
How many beneficiaries can one batch reach? Up to 1,000 per upload, and you can run as many uploads as you need. There is no daily cap on the number of batches.
Can beneficiaries receive different bundle sizes in the same batch? Yes. The amount is per row, so a tiered stipend works in a single file.
Do beneficiaries need a VTUBOX account? No. They only need a working SIM. The account and the wallet are yours.
Can we send airtime instead of data? Yes. Bulk airtime works identically, with the same three columns and the same per-recipient refunds.
What if we need to prove delivery to a specific person months later? The batch and its per-recipient outcomes stay in the account's bulk history with their references, so an old batch can be re-opened and exported.
Ready to run your first distribution? Create a free account, fund a small amount, and test with five numbers before you run three hundred. The failure path is the part worth testing while the stakes are low.
Related reading: How to send bulk data in Nigeria · Bulk data for schools · Recurring airtime and data
Ready to buy airtime, data, pay TV & electricity bills?
Create a free wallet, send airtime and data to one number or a thousand, and get an automatic refund on anything that fails.
Continue reading
Bulk Data for Schools in Nigeria: How It Works for Students and Staff
How a school, college or training centre in Nigeria buys data for students and staff from one wallet: the file format, who should own the account, and how to make it repeat each term.
Bulk & BusinessHow to Send Monthly Staff Airtime and Data Allowances Automatically in Nigeria
Send airtime or data to 500 employees at once, then set it to repeat on the same day every month: the file, the approval controls, and what to check before the first run.
Bulk & BusinessHow to Send Bulk Airtime in Nigeria: Recharge Multiple Numbers at Once
A step-by-step guide to sending bulk airtime in Nigeria: recharge many MTN, Airtel, Glo and T2 (9mobile) numbers in one transaction with VTUBOX.
