How to pay your team in bulk

From your Business Account you can pay your whole team from a single CSV file. You pick one of two payout methods at the start, and everything after that — the template, the fields, the review screen — adapts to the method you chose.

In short: choose how to pay → upload your file → review the breakdown → send.

Every bulk payment starts with the same decision. You can change method at any point.

Step 1: choose how to pay your team

Pay to nsave accounts suits teams who already use nsave, or who are willing to download it. Money moves almost instantly in USD, and each person withdraws to whichever local bank they prefer.

Local account or pickup point suits teams who should not have to install anything. You supply their local bank, wallet or phone details and the money lands in their own currency.

The practical difference is who does the work and who pays the fee. Tap Compare options for the full side-by-side:

Compare options, opened

Upload a CSV with one row per person: who to pay, and how much in USD. You can identify people three ways.

Pay to nsave accounts: choose an identifier, then upload and send

ntag is recommended — it is each person's nsave username without the @. One condition matters: it only works if they have switched their ntag on under Profile → Privacy → ntag in their personal nsave app. That switch is their consent to receive payments from you, so it cannot be enabled from your side.

Email uses the address they signed up with. nsave IBAN uses their USD account number, which they will find in the app under Account details.

Reference column: add one to tell each person what the payment is for, up to 35 characters. Leave it blank and we use “Sent from nsave”.

After sending you get a per-row result. Payments that went through are already on their way; anything that did not is flagged with the reason.

Result screen, with one row that could not be paid by ntag

A Can’t pay by ntag row means one of two things: the ntag is misspelled, or that person has not turned theirs on. Both are fixable without re-uploading the whole file.

Use Copy message for employee to get a ready-made explanation you can send them. Or use Retry by email to pay them with the email they use for nsave — amounts and references carry over untouched.

Retry by email: add the address and send again

The country you choose determines the template, the accepted banks and wallets, and the fields you need to fill in.

Pick the country where your employees are paid

Pay one country at a time — one file per country. If a country is not on the list, we cannot pay out there, but you can still pay those people to their nsave account.

Each country screen offers two tabs. Pay in bulk pays up to 500 people in one file, and anyone new is saved to your Contacts automatically so the next run is faster. Add beneficiaries in bulk saves people without sending anything.

One template covers both bank and wallet rows

The template rule that catches people out: write bank or wallet in the method column, then fill in only the columns for that method and leave the rest blank. A wallet row needs wallet and mobile_number; a bank row needs bank and account_number, which accepts either an account number or an IBAN.

Open Accepted channels to see every wallet and bank supported for that country. Names must match exactly — a near-miss will fail the row — so copy them from this list rather than typing from memory.

Accepted channels, and the full breakdown before sending

Before anything leaves your account you see Debited, Fees (included) and They receive, plus a per-row view of the amount sent, the fee, the rate applied and the exact sum that person receives.

Syria works differently from the other destinations. Your employees collect USD in cash from a Mada agent, bringing their ID and a pickup code.

Pickup codes are generated per recipient after the batch is sent

nsave generates one code per recipient once the batch is submitted, and you can download them all as a CSV.

You are responsible for passing each code to the right person. Anyone holding a code and matching ID can collect that cash, so send each code privately and only to its recipient. Your team will also hear from us directly about their code and next steps.

Saving people ahead of a payment run is worth doing when you are onboarding a new group — you can resolve any data problems before payday rather than during it.

Beneficiaries saved, with failed rows explained

Rows usually fail for one of two reasons: the bank name does not match our list, or the bank needs a branch number or SWIFT code that is missing. Both are visible per row.

Use Download failed rows to get just those rows, correct them, and upload again. The people who saved successfully are already in your Contacts, and you can pay them straight away without waiting.

How many people can I pay in one file?
Up to 100 when paying to nsave accounts, and up to 500 when paying to local accounts or pickup points.

Can I mix countries in one file?
No. Use a separate file for each country.

Who pays the fees?
For payments to nsave accounts, the employee does. For local accounts and pickup points, the business does.

Why can’t I pay someone by their ntag?
Either it is misspelled, or they have not switched it on under Profile → Privacy → ntag. Use Retry by email, or send them the copied message asking them to enable it.

Do the people I pay need an nsave account?
Only for the nsave account method. Local payouts need nothing from them but their existing details.

Where do I track payments after sending?
In the Transfers list, where every payout appears individually.

If you have any issue with a bulk payment, contact us through the in-app support chat.