Over the past decade, CFOs have proudly advanced financial digitalization: ERP systems run in the cloud, treasury management relies on real-time dashboards, and liquidity data can be dissected across multiple dimensions before lunch. Yet, when it comes to paying the employees who actually keep the business running, most companies quietly fall back to legacy infrastructure designed for a single country, a single bank, and employees with a single identity.

This structural gap is the root cause of why global employees are forced to chase their own pay, and finance leaders are saddled with payment risk and noise they would never tolerate anywhere else in their tech stack.

The new workforce no longer depends on your local payment rails

Take a look at who you are actually paying: they are no longer "HQ employees" plus a few expatriates, but rather:

  • An engineer coding remotely from Belgrade this year and Lisbon next year;
  • A designer in Lagos invoicing three clients across three continents simultaneously;
  • A contractor in Bogotá earning in US dollars while living entirely within the Colombian peso system.

They move effortlessly across countries, currencies, and client portfolios. Their lives are already globalized, but their money is not. When they talk about "getting paid," they don't care about your internal processes—they care about: Will the money land in an account I can actually use? How much will fees and FX costs eat away? Will it arrive before my landlord loses patience?

You call it"cross-border payroll", and they just call it "another Tuesday"—but it's all too fragile.

We've normalized what should never have been normal

Money evaporating in fees, getting stuck in intermediary states for days, or arriving in inaccessible forms—these issues should not be inherent features ofglobal payments, especially when the recipient is your employee.

This is a decision embedded in the pipes.

Every hop between banks, every opaque FX spread, every day of funds being tied up—all of it is value flowing away from workers into a system not designed for them. Employees absorb uncertainty, contractors bear FX risk, and those in the "wrong" country get the worst payroll experience.

On the CFO's screen, this shows up as "operating costs," "timing differences," and "network limitations"; on the employee's phone, it looks like: I did the work, so why is my money missing like a lost suitcase?

First, payroll is not an HR issue

For too long, we've filed the payment experience under HR, "employer brand," or some soft corner of the business. I think that's outdated.

If your company depends on a global workforce, paying people clearly and reliably is afinancial responsibilityas important as managing liquidity or credit risk. Here's why: the consequences of getting it wrong are anything but "soft"—your best contractors stop working with you, it creates negative ripple effects on other contractors, and it damages your reputation for attracting new talent; certain markets become "no-go zones" because of your poor payment reputation; leadership teams abandon otherwise attractive expansion plans because they "can't trust the payment rails."

These all eventually show up in churn rates, hiring costs, and the markets you quietly avoid. This is a capital allocation problem, and it belongs on the CFO's desk.

Who's to blame? Legacy architecture.

It's easy to blame compliance. Yes, the alphabet soup of KYC, KYB, AML, tax, licensing, local reporting is real. Of course, you can't just wire money globally and hope for the best.

But compliance and speed are not opposites. The problem is that we're trying to graft 2025-levelregulatory complexityonto 1980s assumptions about how money moves. The underlying architecture still assumes:

  • A single entity primarily pays local employees;
  • Banks are the only meaningful access point;
  • "Cross-border" is a rare exception, not the default state.

No wonder everything groans under the weight of the modern workforce. We're asking a rotary dial network to run a streaming service.

My advice: start from the employee, not from the wire transfer

Fintech has mostly stayed at the interface layer: pretty apps, friendly dashboards, smooth onboarding flows. These have value, but if the underlying pipes are still old, it's just surface work—putting lipstick on a pig.

Quality infrastructure likePapaya Globalcan help, but only if it operates as a regulated, programmable backbone that assumes from day one that your workforce is global and runs accordingly. You don't need to build or manage it yourself—we're doing that for you.

If you start from your employees' reality—whether they're salaried employees, independent contractors, gig workers, or anything else—rather than from the bank's perspective, different needs emerge:

  • Income should land somewhere that feels like a real account or wallet, not a half-baked solution that only works "if the local bank cooperates this week";
  • FX and fees should be transparent and predictable, not an unexpected penalty for living in the "wrong" country;
  • Compliance should be embedded in the process, not stitched together heroically by the payroll team every cycle;
  • Every payment should generate clean, real-time data that finance can use directly, not a reconciliation nightmare two weeks later.

In other words, money in motion should automatically becomedata in motion—for you and for the people you pay.

A preview of what I'm building at Papaya Global

Payroll is the one area where you can't avoid this question: does this infrastructure serve both the company and the employee? When the end result is someone's rent or food, there's no such thing as "good enough."

AtPapaya Global, I'm building a new type of infrastructure specifically designed for this tension. The goal is to eliminate the distance between "doing the work" and "getting paid," without asking CFOs to turn a blind eye to risk or give up control of cash. When we succeed, your global payments will no longer feel like a fragile "chain of favors."

Instead, your finance team will get a calmer, clearer view of liquidity. And your employees—no matter who they are or where they are—will no longer need to be their own "finance department" just to get paid.

The workforce has already globalized. The money will follow, one way or another. I'd rather we design that future deliberately, with infrastructure that respects the people at the edge of the network as much as the numbers at the center.

Royi Carmeli is an accomplished Israeli professional known for combining strategic vision with hands-on leadership in global technology operations. Based in Israel, Royi is recognized for driving teams to deliver scalable cross-border solutions.

He is deeply involved in the convergence of technology and workforce services, shaped by a mindset of problem-solving, collaboration, and operational excellence. Beyond the boardroom, Royi is active in professional networks and drives connectivity across the global payments and workforce ecosystem.