Reduce manual errors in a bulk airtime recipient list
Before sending a bulk airtime order, check that every row has the required fields and an eligible recipient. Flag duplicates and formatting problems, then let the campaign owner resolve them. Approve the final row count and face value against the exact file you plan to submit.
Keep the original file and do the checks on a separate copy. Name the person who owns the list and restrict access to staff preparing, approving or sending it. Save one clearly marked approved version so the wrong attachment cannot be sent by mistake.
Preflight checklist
| Check | Example issue | Action |
|---|---|---|
| Required fields | Missing destination or amount | Return row for correction |
| Format | Malformed number or unexpected characters | Validate against approved rule |
| Duplicate | Same internal ID appears twice | Ask owner whether both are intended |
| Eligibility | Person outside approved rules | Resolve with campaign owner |
| Product and value | Unapproved denomination | Compare with signed brief |
| Final count | Row count differs from budget | Reconcile before approval |
By Freepaid · Published
Keep source, working and approved versions clear
Retain the received source in an approved location and create a dated working copy for validation. Mark which version is authoritative and who has approved it. If a correction arrives, do not silently replace a row after approval. Log the change and have the relevant owner recheck eligibility, count and value. This gives finance a traceable path from request to submitted batch.
Use only fields required for fulfilment and campaign reconciliation. If staff need a unique employee or customer ID to detect duplicates, use that rather than adding extra personal information. Limit access based on the task and follow the organisation's privacy and retention requirements. Do not use real recipient data in training examples. Use synthetic values instead.
Worked example: duplicate in a 50-person batch
A file can have all 50 rows you expect and still contain only 49 unique employee IDs. Flag the repeated ID for the campaign owner, who can check whether the employee qualified for two separate benefits or was entered twice by mistake. Record the decision, recalculate the count and get the revised value signed off.
At R20 per person, a corrected count of 50 comes to 50 × R20 = R1,000 in face value, before fees. The example assumes one R20 reward per eligible person. Recalculate the amount whenever the count or reward value changes.
Validate without guessing
Follow the supplier's current accepted format and documented field rules. Do not invent phone-number validation rules or alter a number to make it pass a local check unless the recipient confirms the correction through an approved process. A format check can find missing digits or extra spaces, but it cannot establish that a number belongs to the intended person or is currently active.
Check whether the proposed product is correct for the recipient and campaign objective. Airtime, data and voucher distribution have different inputs and recipient actions. Confirm the current catalogue and denomination with the supplier before final approval. If a row is unclear, hold it for review rather than silently substituting a different product or amount.
Submit and reconcile carefully
- Freeze the approved file and record its owner, date, count and total value.
- Transfer it only through the agreed secure route.
- Keep the submission batch reference and any supplier response.
- Match returned order references and statuses to the approved list.
- Separate completed, rejected, pending and unknown outcomes.
- Investigate uncertain outcomes by original reference before considering any new order.
Once the supplier responds, record how many rows it accepted, how many completed and which are still open. Give every open case an owner and keep the corrections and approvals with the report. For customer-facing support and receipts, see the prepaid receipt guide.