Multi-currency payroll is a single pay cycle that settles people in more than one currency. The payment is the easy part. The cost sits in the conversion: which rate you use, when you lock it, and who absorbs the movement between approval and settlement. Get that wrong across a few hundred people and it is the most expensive line in your payroll that nobody has on a dashboard.
This guide covers what multi-currency payroll is, how a run actually works, the four ways to set the rate, what it costs, and the checklist to use before you choose a system.
What multi-currency payroll is
One cycle, many currencies
In a multi-currency run you fund payroll once, usually in USD or EUR, and each person is settled in the currency they were contracted in. Contracts, approvals, budgeting, and reporting stay in your base currency. Only the last step changes.
The alternative is running local payroll in every market: a legal entity, a local bank account, a local filing calendar, and a local provider per country. That is the right structure at scale. It is a poor fit for the first ten or fifty people in a new market.
Multi-currency payroll is not the same as international payments
A payments tool moves money. Payroll decides what is owed, withholds what has to be withheld, produces the record, and then moves money. If your provider only does the last step, the first three land back on your finance team as spreadsheets, and the exchange rate becomes something you discover after the fact instead of something you set.
How a multi-currency payroll run works
The five steps
- Approval. Gross amounts are approved in each person's contract currency.
- Funding. You transfer one lump sum in your base currency.
- Conversion. The provider converts into each payout currency at a defined rate.
- Settlement. Funds are delivered through local rails where they exist, and through international transfer where they do not.
- Reconciliation. You get one record with gross, rate applied, fees, and net per person.
Step 5 is the one that gets skipped, and it is the one that tells you what the run actually cost. If the rate applied per person is not on the report, you cannot audit your own payroll.
Where the delay comes from
Delay is rarely the conversion. It comes from cut-off times, correspondent banks, and local clearing windows, which is the same reason a domestic paycheck can take a day or three to land. If timing is your problem more than cost, start with how long payroll takes to hit a bank account.
The exchange rate decision
Four ways to set the rate
| Method | How the rate is set | Who carries the risk | Best for |
|---|---|---|---|
| Spot rate at payout | Market rate the moment each payment is sent | The company | Stable currency pairs, small teams |
| Rate locked at approval | Fixed when payroll is approved, applied at payout | The provider | Predictable cost per cycle |
| Fixed contractual rate | Agreed in the contract, reviewed periodically | The worker, between reviews | Long contracts in volatile markets |
| Pay in USD, worker converts | Set by the worker's own account or bank | The worker | Workers who save or spend in USD |
Who absorbs the movement
Every method above answers one question: between the day you approve payroll and the day money lands, who eats the difference. There is no neutral answer, only an explicit one. The failure mode is leaving it undefined, which means the worker absorbs it silently and raises it as a pay cut three months later.
Write the method into the contract. A person who knows their rate is locked at approval will not open a ticket every time the market moves.
What multi-currency payroll costs
The spread is the fee
Published transfer fees are the visible cost. The larger one is usually the spread: the gap between the mid-market rate and the rate you are given. It does not appear as a line item, because it is priced into the rate itself.
The arithmetic is worth doing once. On 500,000 USD of monthly cross-border payroll, every 1% of spread is 5,000 USD a month, or 60,000 USD a year, moving out of payroll and into someone's treasury desk. That is the number to ask about in a demo, and it is the number most quotes are built to avoid mentioning.
Costs that never show on the invoice
- Failed and returned payments. Wrong format, wrong local identifier, charged twice and paid late.
- Manual reconciliation. Finance rebuilding the run in a spreadsheet because the report has no per-person rate.
- Off-cycle corrections. Every fix is a second conversion at a second rate.
- Attrition. People leave over pay that arrives late or short. That cost lands in recruiting, not payroll.
Choosing a multi-currency payroll system
The buyer checklist
- Rate transparency. Is the mid-market rate and the spread shown per payment, before you approve.
- Rate policy. Can you lock a rate at approval, and is the policy the same for every market.
- Local rails. Does the provider settle through local payment systems in your markets, or only by international transfer.
- Coverage of the worker's side. Can the person receive, hold, and spend in USD, or are they forced to convert on arrival.
- Compliance artifacts. Contracts, classification, tax forms, and receipts produced in the same system that pays.
- One reconciliation file. Gross, rate, fees, net, per person, per cycle, exportable.
- Funding model. One transfer per cycle, or one per country and per currency.
Questions to ask in the demo
Ask for a sample payout report with the rate applied per person. Ask what happens to a payment that fails on a Friday. Ask who is on the other side of the rate. The answers separate a payroll system from a payments tool with a payroll screen.
Ontop is the Global Workforce Engine: financial infrastructure that hires, pays, and manages a global workforce in one place, with the rate, the fees, and the compliance record in the same system. If you want the cost side modelled before you talk to anyone, start with the employee cost calculator.
Latin America is where the rate decision bites hardest
Local currency or USD
In markets with high inflation or currency controls, the choice of payout currency is not an administrative preference, it is most of the compensation. A raise agreed in local currency can be gone in a quarter. The same amount delivered in USD holds.
This is why USD payout has become a retention argument in the region rather than a finance detail. Workers who hold their income in USD through an Ontop Global Account decide themselves when and whether to convert, which moves the rate risk to the person best placed to time it.
Contractors, not just employees
Most first hires in the region are contractors, and contractor payouts are where multi-currency gets messy: many currencies, many invoices, no single record. That is a solved problem, and it is worth reading how global contractor payroll handles it, or how teams structure nearshore hiring in Latin America before they have entities.
Frequently asked questions
How do you manage multi-currency payroll efficiently?
Fund once in your base currency, define the rate method in the contract, settle through local rails where they exist, and require one reconciliation file that shows the rate applied per person. Efficiency comes from removing the second conversion and the manual rebuild, not from chasing the last basis point.
How do you compare methods for handling multi-currency payroll?
Compare on four axes: who carries the rate risk, whether the spread is visible before approval, whether settlement uses local rails, and whether compliance artifacts come from the same system. Price alone hides the spread, which is usually the biggest number.
What is a multi-currency payroll system?
A multi-currency payroll system calculates pay in each person's contract currency, converts from a single funding currency at a defined rate, settles through local or international rails, and produces one record per cycle showing gross, rate, fees, and net.
Can you pay international contractors in their local currency?
Yes. The practical question is whether they want it. In stable currencies most people prefer local. In volatile ones many prefer USD and convert on their own schedule. Offering both is the answer that survives contact with a real team.
Do you need a local entity for multi-currency payroll?
No. Entities are required for local employment, not for paying in local currency. Companies that want employment protections without entities usually look at an alternative to an EOR for contractors first, and open entities once headcount in a market justifies the overhead.
What to do next
Run one audit on your last cycle: for each cross-border payment, find the mid-market rate on the day and compare it with the rate applied. The gap, times twelve, is your annual FX cost. Most teams have never seen that number, and it is the fastest argument for changing how payroll is run.
