Bulk payments let you pay multiple recipients in a single upload. This is ideal for payroll, vendor payments, and bulk disbursements. You can pay beneficiaries you've already saved and add new ones in the same file, so there's no need to add beneficiaries first.
đĄ Note: If you enter an account number, SWIFT/bank code and currency that match an existing beneficiary, the payment goes to that beneficiary and no new one is created. Only these three need to match, not every beneficiary detail. |
1. Click "Send money" from the Dashboard or Wallets page.
â
2. Choose Bulk payment (multiple).
3. Select the wallet you want to pay from.
â
âNote: if you send to beneficiaries in a different currency, the money is automatically converted to the beneficiaries' currencies and sent from the wallet you choose here.
4. Download the CSV template by clicking Download CSV template, or click here to download it. Fill it in using the guidance below. Each row is one payment.
5. Save the file as a CSV (max 10 MB) and upload it by clicking Select file or dragging and dropping it. Enter your authenticator code if asked. We validate each row and tell you what's wrong if there are any problems. You can fix the file and re-upload, or continue with the rows that passed.
6. Review the payments and make any edits needed using the edit icon on each row. If a row is in a different currency from your wallet, the current exchange rate is shown.
7. Click Confirm to process the payments to send all payments at once, or to send them for approval if your company requires it.
How to format your file
The second row of the template describes each column. Delete it if your upload doesn't accept it.
Payment columns (needed on every row)
Amount (required) - the amount you want the beneficiary to receive, in the beneficiary's currency. Numbers only, with no currency symbols.
Reference (optional) - e.g. an invoice number. Letters, numbers and spaces only, up to 35 characters. No hyphens or other symbols. It doesn't always pass through to the beneficiary's bank statement.
Purpose of payment (required) - a code from the list below. You can use a different purpose on each row.
Beneficiary (required) - either the beneficiary's RP reference or the full beneficiary details, never both. See below.
Who you're paying
An existing beneficiary: enter their reference (it starts with "RP-") in Beneficiary reference and leave all the other beneficiary columns blank. If you fill any in, they're ignored and the saved beneficiary is used as it is. You can find references under Beneficiaries in the sidebar, or export them to a CSV from there.
A new beneficiary: leave Beneficiary reference blank and fill in the beneficiary columns (below). We create the beneficiary and pay them in the same upload.
Beneficiary columns (new beneficiaries only)
Currency: 3-letter code, e.g. USD, GBP, NGN.
Payment method: local or international.
Beneficiary type: company, individual or myOrganisation (your own account).
Beneficiary relationship: operational, customer or nested.
Account company name: required for company and myOrganisation. Account first name and last name: required for individual.
Account number/IBAN and Bank code/SWIFT: the local account number or IBAN, and the local bank code or SWIFT/BIC.
Recipient address lines, state, city, zipcode and country code: required depending on the destination country.
Optional: beneficiary email address, Label/Tag, company registration number and recipient mobile number.
Purpose of payment codes
Use these codes in the Purpose of payment column. They aren't case-sensitive. A blank or unrecognised code fails that row.
Code | Purpose |
GOODS | Payment for purchase of goods / merchandise |
SERVICES | Payment for services (professional, contract) |
PROF_FEES | Professional fees payment |
PAYROLL | Payroll / salary / wages |
CONTRACTOR | Contractor / freelancer payments |
TRAVEL | Business travel & entertainment |
R_AND_D | Research & development payments |
ROYALTIES | Royalties / licence fees |
SUPPLIER | Supplier / vendor settlement |
INVESTMENT | Investment / capital injection |
LOAN_REPAY | Loan repayment |
LOAN_DISBURSE | Loan disbursement |
BILLS | Bill payments |
GOVT_TAX | Government fees / taxes |
OWN_ACCOUNT | Own account / subsidiary transfer (outbound) |
EDUCATION | Education payments |
MEDICAL | Medical payments |
GIFT | Gift |
CHARITY | Charity / donation |
REMITTANCE | Personal remittance |
Tips for specific currencies
NGN: enter the bank name (e.g. ACCESS BANK) in the Bank code/SWIFT column. See What bank names should I use for NGN when uploading a beneficiary CSV? for the list of accepted bank names.
KES: in the Bank code/SWIFT column, use a bank code starting with "KE" for local payments, or the SWIFT/BIC for international payments. For mobile money, enter the provider, which is always "mpesa". See the bank code mapping.
TZS: in the Bank code/SWIFT column, use the SWIFT/BIC for both local and international payments. For mobile money, enter the provider: "airtel" or "tigo". See the bank code mapping.
USD (United States): use the full state name, e.g. New York, not NY.
JPY: Account type (default futsuu) and Native company name (usually in Katakana) are required. Most Asian currencies: Branch code is required.
State: some countries require a state or region. If a row fails with "Recipient state is required", add it and re-upload.
Long account numbers: Excel may reformat these. Add an apostrophe (') in front, or format the column as text.
If some rows fail
After you upload, we tell you how many rows couldn't be processed, with a reason for each (for example "Recipient state is required" or "Could not find bank detail"). Failed rows are left out. You can fix the file and re-upload, or continue with the rows that passed.
Things that can't be uploaded by CSV
Payments that need a supporting document, including payments from ZAR wallets linked to an Investec account. Use Bill payment (single) so you can attach the documents.
New beneficiaries, if your account requires beneficiary approval. They can't be paid until approved. Add them first, then pay using their RP- reference.
Cryptocurrency payments aren't supported.