Every year, more than $200 billion in employer-originated wages crosses international borders. That is not a niche workflow for a few global enterprises. It is the quiet, recurring economic bloodstream of multinational work, and it is moving through something that looks suspiciously familiar: a patchwork of local banks, regional payroll vendors, and manual compliance processes.

The kicker is that this setup is not new. Anyone who managed international payments in 2005 would recognize the structure. The money grew. The borders stayed. The compliance burden stayed. But the underlying infrastructure, the “plumbing,” largely did not. And the article is blunt about why that matters: this is not a minor inefficiency. It is a structural constraint on speed, cost, and reliability, with downstream effects that show up long after the transfer itself.

To understand why this continues, zoom out for a second. Cross-border payroll is not one payment. It is a chain. Employers originate wages. Then the flow has to traverse multiple jurisdictions with different rules for taxation, reporting, and compliance. Even when payroll systems are modern on the front end, the “settlement” and regulatory handling frequently rely on local rails: banks that operate where the worker lives, payroll or remittance partners who understand regional process requirements, and human-driven steps when automation cannot safely cover the edge cases.

That patchwork creates a frustrating reality for operators: you can digitize payroll once, and still end up with manual work at the margins. When a process depends on compliance interpretation, documentation, and jurisdiction-specific handling, the last mile becomes the bottleneck. The article frames the key problem clearly: the system resembles the 2005 approach, even though the scale now exceeds $200 billion annually. When a workflow scales without upgrading the underlying infrastructure, every payroll run becomes a bigger stress test. Small inefficiencies do not stay small. They compound.

Now bring in incentives. Banks and regional payroll vendors are set up around local connectivity and local compliance. That is a defensible business model, but it also encourages fragmentation. Each provider optimizes for its own lane: a bank that does well in settlement and liquidity, a vendor that owns certain regional payroll compliance steps, and a set of manual processes that can cover uncertainty when rules or data do not fit neatly into automation.

But from an executive perspective, fragmentation is expensive even when it seems “manageable.” It drives higher operational overhead, increases the number of parties involved in each transaction, and creates more opportunities for errors or delays. When compliance is manual, the risk profile changes. Not because someone is trying to be careless, but because human processes introduce variance: different interpretations, inconsistent documentation, slower turnaround when exceptions appear.

And exceptions do appear, because cross-border work rarely behaves like a spreadsheet. Employment can change mid-cycle. Countries can update reporting requirements. Currency movements can affect timing and calculations. Even if the payroll logic is sound, the compliance and settlement steps can lag. That is exactly the kind of mismatch the article is pointing at when it says the scale changed, but the plumbing did not. The “pipes” decide how smoothly the water moves.

The second-order consequence is strategic: executives and boards should treat international payroll infrastructure as more than an operations issue. When payroll is handled through patchwork systems and manual compliance processes, the organization becomes more dependent on vendor networks and institutional process knowledge. That can limit bargaining power and slow down change. It can also make growth harder, because expanding into additional countries increases the number of rails and the complexity of compliance handling, without necessarily improving automation.

There is also a resilience angle. In a world where payment delays, compliance backlogs, and operational failures can quickly become reputational problems with employees, a system that relies heavily on manual processes is inherently harder to stress. The article’s framing, comparing modern scale to the 2005 setup, implies a structural gap between what the industry can do and what it is doing today. When payroll operations do not modernize their underlying infrastructure, the business inherits avoidable friction every payroll cycle.

The strategic stakes for peers are clear. If international payroll is effectively still running on the same basic model that people recognized in 2005, then decision-makers who assume they can “optimize” their way out of cost and risk may be missing the real constraint. The bottleneck is not just pricing or vendor selection. It is the architecture of how cross-border wages move and how compliance is handled. For executives trying to expand globally, reduce operational drag, and improve reliability for employees, that is the question that matters: will the plumbing evolve beyond the patchwork, or will $200 billion-plus continue to flow through an unchanged system that was never designed for this magnitude?