Wise Business does support batch payments: a verified account can upload one CSV or XLSX file with up to 1,000 payments, fund them with a single pay-in, and require an approver before anything is sent. What Wise does not do is work out each contractor's amount for the month. RemiPay handles that recurring part and the record; you still pay from your own Wise Business account.
Facts checked November 16, 2026.
An earlier version of this post said Wise lacks true batch payments. That was wrong, and this rewrite replaces it. The real question for a growing team is not whether Wise can send many payments at once. It can. The question is where the monthly amounts come from, who checks them, and what record is left behind.
What a Wise-only batch looks like
Wise documents the batch flow on its Help Centre. In short:
- Go to Payments and choose Batch (this is web-only).
- Download one of Wise's templates and fill in one row per payment.
- Save the file as.CSV or.XLSX and upload it.
- Review the transfers, then pay with a single pay-in that covers the whole batch.
- If your account requires approvals, a team member with approval permission approves the batch before it goes through.
A few constraints are worth knowing. Batch payments only go to recipients on your Recipient list, not to Wise Contacts. You need a verified Wise Business account. Batches can also be created through Wise's API.
For one-off or occasional bulk sends, that is a complete workflow. The friction shows up when the same team gets paid every month and the amounts are not all the same.
Where a recurring contractor run gets harder
Most agencies and small teams have a mix of pay types:
- Fixed monthly fees. The same amount each month, until a rate change.
- Hourly contractors. The amount depends on hours worked and approved for the period.
- Milestones or one-off extras. A bonus, a reimbursement, a project fee.
- Contractors paid outside Wise. Some prefer Payoneer, a local bank route or another provider.
Wise scheduled transfers can repeat on a set date with a fixed target amount, and on Wise Business they may need another user's approval depending on permissions. That covers the fixed-fee contractor well. It does not cover the hourly contractor, because the amount changes every month, and Wise does not let you edit a scheduled transfer (you cancel it and set up a new one).
So in practice, a Wise-only team rebuilds the batch file each month from somewhere else, usually a spreadsheet. That spreadsheet has to answer:
| Question before you upload | Where the answer usually lives in a Wise-only setup |
|---|---|
| Who is being paid this cycle? | Last month's file, edited by hand |
| What does each fixed-fee contractor get? | A rate column in a spreadsheet |
| How many hours were approved, and for which client? | A time tracker export, copied in |
| Who approved those hours? | Email, Slack or memory |
| Who is paid outside Wise, and was it sent? | A separate note or the other provider's dashboard |
| What does the bookkeeper get? | Wise statements plus the spreadsheet, reconciled later |
None of that is a Wise limitation exactly. Wise moves the money. The pay run is the work that decides how much money should move, and that work sits outside the batch file.
How a recurring run carries amounts into next month
A recurring run is easier to keep accurate when you treat it as a template that rolls forward, rather than a new file each month. A simple approach that works with or without software:
- Copy last month's run as the starting point. Same contractors, same routes, same currencies.
- Keep fixed amounts as they are unless a rate change has been agreed in writing.
- Replace hourly amounts with this period's approved hours times rate. Do not carry last month's hours.
- Add or remove one-off lines (bonuses, reimbursements, a contractor who finished).
- Review hours by client and project before approving, so you can see what the paid hours produced.
- Approve the run once, then pay each contractor from your Wise Business account (single transfers or Wise's batch upload) using the approved amounts, and mark every payment, Wise or not, paid in the same run.
- Close the run with a status on every line and hand one record to your bookkeeper.
This is the part RemiPay is built for. Each contractor record holds a pay type and rate (hourly or monthly), so fixed fees carry forward and hourly lines use the period's approved hours. Hours come from Hubstaff (connected by OAuth or a personal access token, and auto-approved), from RemiPay's own time tracker, RemiStaff, or from manual timesheets, which the founder approves. Before you approve, RemiPay shows hours by client and project, approvals and AI usage. Approving in RemiPay starts no transfer. You pay each contractor yourself from your Wise Business account, with single transfers or Wise's own batch upload, using the approved amounts, then mark each payment Sent, then Paid, in RemiPay (with an optional transfer reference). Funds never touch RemiPay. Payments made elsewhere, such as Payoneer, are marked paid the same way, in the same run.
What RemiPay adds on top of Wise
The comparison below is about roles, not about replacing Wise. If you use RemiPay, you still pay contractors from your own Wise Business account.
| Step | Wise Business on its own | Wise Business with RemiPay |
|---|---|---|
| Build the monthly amounts | You prepare the CSV or XLSX each cycle | Fixed lines use each contractor's monthly rate; hourly lines use approved hours times hourly rate |
| Review hours by client and project | Outside Wise (time tracker, spreadsheet) | Hours from Hubstaff, RemiStaff or manual timesheets, shown by client and project in the run before approval |
| Approval | Wise batch approval by a permitted team member | Only the account owner (founder) approves the run in RemiPay, with 2FA; RemiPay records who approved and when; any approval rules you set in Wise still apply when you pay there |
| Paying | Wise batch, from your balance | You pay from your Wise Business account (single transfers or Wise's batch upload) using the approved amounts, then mark each payment Sent, then Paid, in RemiPay |
| Payments outside Wise (e.g. Payoneer) | Tracked separately | Marked Sent, then Paid, in the same run |
| Bookkeeper record | Wise statements plus your spreadsheet | CSV export of payouts: Date, Contractor, Email, Country, Type, Amount, Target Currency, Status, Method, Pay Cycle ID, Pay Cycle Status |
| Subscription cost | None for batch payments (Wise account set-up fee applies) | Flat RemiPay subscription, from $19/mo (Solo, up to 3 contractors) to $199/mo (Team, up to 50) |
| Transfer and conversion fees | Charged by Wise | Still charged by Wise, paid to Wise |
Wise's U.S. business pricing page lists a one-time set-up fee and sending fees that vary by currency, starting from a small percentage, at the mid-market rate. Those fees are the same whether you upload a batch or send single transfers, with or without RemiPay tracking the run. RemiPay's subscription is separate and does not include Wise's fees.
Worked example: one month, four contractors
This is a sample, illustrative pay run for a fictional U.S. agency. Rates and hours are invented. Transfer fees are left out on purpose, because they depend on currency and amount on the day; check Wise's pricing page for live figures.
| Contractor (fictional) | Country | Pay type | Basis this cycle | Amount owed | Route | Status after run |
|---|---|---|---|---|---|---|
| Contractor A | Mexico | Fixed monthly | Same as last month | $3,000.00 | Wise | Paid |
| Contractor B | Poland | Hourly | 62.5 approved hours x $45 | $2,812.50 | Wise | Paid |
| Contractor C | India | Fixed monthly | Same as last month | $2,400.00 | Payoneer | Marked paid |
| Contractor D | United States | Hourly | 18 hours submitted, 12 approved, 6 under review | $660.00 | Wise | Pending |
What carried forward from last month: Contractor A's and Contractor C's fixed fees, everyone's routes and currencies. What changed: Contractor B's hours (their October hours were not reused), and Contractor D's line, which stays pending until the remaining hours are approved or rejected.
Before approving, the owner sees Contractor B's 62.5 hours split by client and project, for example 40 hours on one client's site build and 22.5 on another client's retainer. That is the "what did the paid hours produce" check. It is a billing check, not a performance review.
In a Wise-only setup, the owner would build a batch file with three Wise rows, pay Contractor C separately in Payoneer, and keep Contractor D's line in a spreadsheet until it is settled. In RemiPay, all four lines sit in one approved run. The owner still pays the three Wise lines from Wise and Contractor C in Payoneer, using the approved amounts, then marks each one paid, so every line has one status (Paid for the Wise lines, marked paid for Contractor C, Pending for Contractor D) and the bookkeeper gets one CSV export.
Common questions
Does Wise Business support batch payments? Yes. A verified Wise Business account can create up to 1,000 payments from one CSV or XLSX file, pay with a single pay-in, and require a team member with approval permission to approve the batch before it is sent.
Can Wise send the same contractor payment every month automatically? Wise scheduled transfers can repeat on a schedule with a fixed target amount. Wise suggests keeping some extra balance to cover rate movements. Amounts that change each month, like hourly pay, still need someone to calculate and update them, and scheduled transfers cannot be edited once set.
Do I need RemiPay to use Wise batch payments? No. Wise batch payments work on their own. RemiPay is for teams that want the monthly amounts, the hours review, the approval and the bookkeeper record put together in one run before they pay from their Wise Business account.
Who charges the transfer fees when I pay a RemiPay run through Wise? Wise. You pay each contractor from your own Wise Business account, so transfer and conversion fees are charged by Wise there. RemiPay charges a flat subscription separately and never handles the money.
Edge cases
- A contractor's bank details change mid-cycle. Confirm the change through a second channel before the run, and update the recipient in Wise. Never accept new details from an email alone.
- Batch recipients must be saved recipients. Wise batches cannot pay Wise Contacts, so add new contractors to your Recipient list first.
- Brazil-based businesses. Wise says batch payments are not available for Brazilian businesses. This does not affect U.S. companies paying contractors in Brazil, but check Wise's coverage for the destination currency.
- Disputed hours. Leave the line pending rather than paying a partial amount you have not agreed with the contractor.
Related guides
- Wise vs Payoneer for U.S. teams that pay contractors
- Wise fees for U.S. businesses in 2026: sending, receiving, card and how to read a quote
Next steps
- See a sample pay run: /blog/sample-contractor-pay-run
- Compare RemiPay and Wise on their own: /compare/wise
- Read the full guide to paying international contractors from the U.S.
- Check plans and the flat subscription: /pricing
Posts from the RemiPay editorial team. Have a question or topic request? Email hello@remipay.co.



