Corporate airtime lets a business pay for mobile credit on employees’ existing numbers, instead of buying individual vouchers or processing a claim for every top-up. In South Africa, a bulk recharge service can distribute airtime across Vodacom, MTN, Cell C and Telkom from one account. The employer decides who receives credit, how much they receive and when the purchase is submitted.
That becomes useful when a sales team, delivery operation or field programme has hundreds of numbers spread across networks. But the purchasing method matters: a cash allowance, a direct airtime recharge and a data bundle solve different problems. This guide compares those choices and works through the budget, distribution and reconciliation of a 500-person airtime run.
Cash allowance, vouchers or direct recharge?
Choose the method around the work employees need to do. If a delivery driver needs an app to stay connected during a shift, paying a cash allowance at month-end may leave the immediate connectivity problem unresolved. If a worker has an existing contract and needs reimbursement for an approved expense, sending prepaid airtime may not be appropriate.
| Method | Where it fits | What the employer must manage |
|---|---|---|
| Cash allowance or reimbursement | Employees arrange their own service; the business pays an agreed allowance or approved claim. | Expense policy, supporting records and payroll treatment. Payment alone does not establish that mobile credit was bought. |
| Airtime voucher PINs | A programme specifically needs a code that the recipient can redeem. | Correct network, secure delivery of codes, and the distinction between a code issued and a code redeemed. |
| Direct airtime recharge | Staff or contractors need a specified rand value on an eligible existing mobile number. | Correct recipient and current network, approved amount, and final delivery result. |
| Direct data bundle | The job depends on mobile apps, messaging, uploads or other data use. | Network-specific bundle, validity period, eligibility and expected usage. |
SIMcloud’s bulk airtime service uses direct, pinless recharge. The recipient receives mobile credit rather than an airtime PIN. Data orders use the selected network’s available products; a rand amount that is valid for airtime is not automatically a valid data bundle.
Keep payroll and tax decisions with your finance advisers. The distribution controls below concern purchasing and delivery, not the tax treatment of an allowance.
Worked example: R100 airtime for 500 employees
Suppose an employer approves R100 airtime for each of 500 employees once a month. The planned airtime face value is 500 × R100 = R50,000 per run, or R600,000 across 12 identical runs. This is an illustrative budget, not a customer case study or a quotation.
Calculate three figures separately:
- Approved allocation: what each eligible person is allowed to receive.
- Purchase cost: what the chosen products cost under the applicable pricing.
- Funding requirement: the available wallet balance needed before submitting the orders.
A company can approve R50,000 and still fail to complete distribution if its purchase wallet is underfunded. Assign a funding owner and check the available balance before the run. Use the current account funding instructions, including the correct payment reference, rather than copying banking details from an old spreadsheet.
For data, budget by product and employee group. Field agents uploading photographs may need a different bundle from staff who mainly use text messages. Check the current airtime and data products before committing to a bundle value or validity period.
Build a list that finance can reconcile
Maintain one approved source list containing an internal recipient ID, mobile number, current network, allocation, cost centre and eligibility date. Keep the business record even if the recharge file accepts fewer columns. It connects a supplier transaction back to the person and budget that authorised it.
SIMcloud’s bulk upload uses msisdn,network,value,reference. The airtime flow accepts R2–R999 per row and keeps the first 30 characters of the reference. A compact reference such as OPS-202609-E0042 is more useful than a long description that loses its identifying suffix when shortened. See the CSV preparation guide for the exact upload format.
- Remove leavers and suspend allocations that have not been approved.
- Keep mobile numbers as text so spreadsheet software preserves the leading zero.
- Check repeated numbers: two employee records may point to the same handset.
- Confirm changed or uncertain networks before buying.
- Freeze the approved file and give the run a unique name before upload.
A number prefix is not sufficient evidence of its current network. ICASA explains that number portability allows a subscriber to retain a number when changing operators. The network confirmation tool can help resolve an uncertain individual number.
Choose a batch, recurring order or API workflow
A reviewed CSV batch suits a distribution list that changes between runs or needs finance approval before release. Upload the prepared file, inspect recipient count and total, then confirm it once. Use the bulk airtime walkthrough for the ordering screens.
A recurring recharge suits a stable, repeated allocation. Check the configured frequency and start date carefully: an interval measured in days is not necessarily the same as “the first working day of every month”. Assign someone to stop or change the instruction when a person leaves or their entitlement changes.
An API integration suits purchases triggered by another system, such as an approved allocation or reward event. It adds development and operational responsibilities: your application must keep the request identifier, check final status and handle unresolved purchases. See the airtime API buyer guide before choosing that route.
What to do when only part of the batch succeeds
Return to the hypothetical 500-person run. At the time of review, assume 480 orders are delivered, 12 have failed and eight remain unresolved:
| Outcome | Recipients | Airtime face value | Action |
|---|---|---|---|
| Delivered | 480 | R48,000 | Record the result against the approved allocation. Do not resend. |
| Failed | 12 | R1,200 | Investigate the reason and verify the wallet treatment before a corrected purchase. |
| Unresolved | 8 | R800 | Retain on the exception list and establish the original outcome. |
| Total | 500 | R50,000 | All approved recipients remain accounted for. |
This table reconciles intended airtime value, not bank receipts or wallet debits. Check those separately. Do not count unresolved orders as failures, and do not upload the entire batch again: the 480 delivered recharges are already complete.
Give support the batch name, date, reference, number, product and displayed result for each exception. Keep a named owner for the unresolved list until every item has a final outcome.
Evaluate SIMcloud with one representative run
SIMcloud combines bulk airtime distribution, data bundle purchases and transaction reporting in one prepaid workflow. Before moving a recurring programme, evaluate a small approved group covering your network mix and products. Ask operations to prepare the list and finance to reconcile the results; both teams need to be able to work with the evidence.
Bring the recipient count, allocation frequency, expected monthly purchasing value and reporting requirements to the initial discussion. That is enough to establish the workflow without sending a full staff contact list.
Discuss a corporate airtime run with Dave, or create an account to inspect the portal.
Corporate airtime questions
Can one company recharge employees on different networks?
Yes. SIMcloud bulk airtime supports Vodacom, MTN, Cell C and Telkom. Each row must identify the recipient’s current supported network.
Do employees need to install an app to redeem the airtime?
The direct recharge delivers credit to the submitted mobile number. It does not require the employee to redeem a SIMcloud voucher PIN.
Can we send data instead of airtime?
Yes, using a valid network-specific data product. Select from the current catalogue and check its validity rather than assuming airtime and data values are interchangeable.
Does a completed upload prove everyone received their allocation?
No. Review the final result for each order. Upload, confirmation and final delivery are different stages.