Paying staff abroad looks like a payments problem, but the real risk sits in local tax rules. Our respondents say to agree currency and pay dates early, and keep compliance local.

Global payroll has never looked easier from the outside. A business can now pay a developer in Bengaluru and a designer in Melbourne from one screen. Still, the leaders we spoke to describe a gap between paying someone and paying them correctly. As a result, global payroll mistakes surface late, as short pay, missed super or a tax bill. For the treasury side of the same problem, see our roundup on cross-border expansion payments.

We asked one question: what is the hardest part of paying contractors or employees in other countries, and how has your business solved it? We wanted founders, HR and finance leads with international teams, and we asked for first-hand experience over vendor pitches. Four leaders answered in this round, and we used all four. None of them runs a global payroll platform, so their views come from the paying side.

Fintechbits analysis

Why cross-border pay still costs more than expected

The transfer itself still carries a cost. In early 2025, sending $200 abroad cost 6.49% on average, according to the World Bank’s Remittance Prices Worldwide report. That was up from 6.26% three months earlier. That benchmark tracks consumer remittances rather than global payroll. However, it shows how fees and exchange margins still eat into smaller cross-border payments.

Meanwhile, demand for global payroll tools keeps growing. Deel said it passed $1.5 billion in annual recurring revenue in the first half of 2026, Tech Funding News reported. It also says more than 40,000 organisations use it. Deel sells these services, so its figures show demand for global payroll, not how well it works for buyers.

Agree the currency, cover the fees

Ankit Sarawagi of CFO Matrix describes paying people in India.

“The main thing to get clear was what people were being paid. We’d agree the money would come from a US company in US dollars. But by the time it reached India, exchange rates and intermediary bank fees meant people saw a different amount in rupees, which led to a few awkward conversations on payday. To fix it, we agreed three things: we’d pay in local currency, we’d cover all exchange and transfer fees, and we’d pay on fixed dates each month.

Every month we run a reconciliation with one line per person. It isn’t an exact science, because statutory contributions differ from country to country. Before we pay anyone in a new country, I make sure I know the rules by speaking with a local adviser.”

Ankit Sarawagi, Curator, CFO Matrix

His fix matches the cost data above. Intermediary banks can take fees out of a payment before it lands, so a fixed dollar amount rarely arrives intact. Paying in local currency moves that risk onto the payer. That makes global payroll costs less predictable, but fairer for the worker. Also, his monthly reconciliation matters more than it sounds, because one line per person catches short payments early. Still, he gives no figures, and CFO Matrix is an information resource rather than a global payroll provider.

Fix the pay date, not the time

Conor Smart is a director at Arklavo, an apparel business with overseas suppliers.

“International payments are tricky because they usually involve some guesswork. When will it get there, and how much will arrive? That’s especially true of traditional bank transfers. You only find out later what the exchange rate and fees were, so the person on the other end gets a few dollars less than they expected and has to write and ask why.

We sell into many countries, so we receive money in lots of currencies and pay suppliers and freelancers abroad in others. First, we agree the currency upfront. For us, it’s usually the other person’s currency, so we carry the exchange rate risk, but at least they know exactly what they’ll get. Second, we agree a day, not a time. We try to pay on the same day each month, so we know roughly when fees will land and people can plan their cash flow around it. Nobody’s impressed when money arrives quickly, but they’ll be put out if it isn’t there when they expected it. Before the first invoice, ask how they’d like to be paid and in what currency. It might save you both some confusion later.”

Conor Smart, Director, Arklavo

His original answer said that paying in the supplier’s currency made costs predictable for Arklavo. That has the logic backwards, because the payer takes on the currency swing. We’ve edited the line to match his point. The fixed pay date is the more useful lesson for global payroll, since it lets both sides plan cash flow. However, Arklavo is an apparel business, not a fintech. Its payments are supplier and freelancer runs rather than full global payroll for employees.

Global payroll dashboards can hide compliance gaps

John Mac founded Exit Evidence, a firm that advises Shopify founders on selling.

“This question hits the main problem with global payroll: it often hides the problem instead of solving it. In my view, the safe way to go global is to do it deliberately. Centralise reporting and payment, but not compliance.

A platform that says ‘everything’s fine, here’s a report of all payments made’ doesn’t tell you what problems you’re creating. In Australia, for example, getting an invoice from a contractor doesn’t necessarily save you from paying superannuation if you’re paying principally for that person’s labour. Other countries have other traps, and an ‘all complete’ status won’t tell you if you’re missing filing requirements anywhere you operate.

So we built a map that sits outside the payroll platform. Our source of truth is a spreadsheet that lists each country, who we’re hiring there, our tax obligations, and who’s responsible for each one. Each country manager owns the compliance issues for their country. We then use the platform only to make the payments that spreadsheet says are due. Every month, the country managers confirm their countries are clear for payment, and the CFO checks the payments against the list. We keep that record outside the platform, so if we ever switch providers, we don’t lose the compliance history. It’s not as neat as a dashboard that says everything’s good, but a dashboard can hide problems that are quietly building up in the background.”

John Mac, Founder, Exit Evidence

His Australian example checks out. The Australian Taxation Office says contractors paid mainly for their labour count as employees for super guarantee purposes. That has mattered more since 1 July 2026, when Payday Super began. Employers must now pay super with every pay run. Therefore, a global payroll platform that only confirms a transfer can’t tell you whether super was due at all. Exit Evidence is a small advisory, and he says he has held senior operations roles before. His country-manager model most likely reflects that earlier work.

Classification is the hardest rule to standardise

Abhinav Gupta leads Profitjets, an accounting firm serving US small businesses.

“Meeting several sets of rules at once is hard. For cross-border payments, you’re dealing with each country’s rules on tax, withholding and worker classification, and classification is the toughest of the three. Every country defines an employee differently, and treating a local employee as a contractor exposes a company to liability. That’s why classification decisions shouldn’t sit only with a central team. Our approach is to standardise where we can and localise where we can’t. Payments are relatively easy to standardise. Classification needs local knowledge, so that’s where most of our compliance effort goes.”

Abhinav Gupta, Founder, Profitjets

His point about classification is where regulators are moving fastest. In February 2026, the US Department of Labor proposed a simpler contractor test built on two core factors. We could not confirm a final rule. So the federal standard remains unsettled for global payroll teams with US contractors. Also, many US states apply their own tests. Profitjets supports payroll tools rather than running global payroll itself. His answer is general guidance, not a case study.

New rules shift risk to the payer

Other countries have also shifted risk towards the business that pays. UK umbrella companies now share liability for unpaid PAYE with a “relevant party”, usually the agency. That rule took effect on 6 April 2026, Grant Thornton explains. As a result, a business that hands payroll to a third party can still end up owing the tax. Australia’s Payday Super adds timing pressure too, since late super is harder to fix quietly at quarter end. Together, these rules make global payroll a compliance task first and a payments task second.

What works for global payroll teams

The four answers point to a clear order of work. First, agree the currency, the fee arrangement and the pay date before the first payment, as Sarawagi and Smart suggest. Next, decide who carries the exchange rate risk and write it into the contract. Then build a country-by-country compliance map outside your global payroll platform, as Mac describes. Give each country a named owner. Finally, reconcile every month with one line per person, and check classification locally before you pay anyone new. Our piece on compliance after launch makes the same point about embedded finance.

What to watch next

The next test for global payroll teams is regulatory. Watch whether the Department of Labor finalises its contractor rule. Also watch how the ATO enforces Payday Super after year one. Meanwhile, faster rails will keep arriving. Stripe pay, for example, offers free instant transfers between businesses. However, it only works inside Stripe’s network, in preview in the US and UK. Quicker transfers will cut the wait, yet they won’t settle who counts as an employee.

Above all, global payroll works when the business treats the transfer as the last step, not the first. The platform moves the money, but someone with local knowledge still has to confirm that the money is due.

FintechBits covers payments, banking and fintech developments for readers in the US and UK. This article is for information only and is not financial or legal advice. Views expressed are those of the FintechBits editorial team.