Cross-border payments

Cross-border payments are financial transactions that move funds between parties in different countries through banking or non-bank payment-institution rails.

For global payroll and contractor teams, cross-border payments are the settlement layer that moves salary, contractor fees, EOR invoices, and gross-up tax remittances across jurisdictions. Each transaction triggers overlapping regulatory frameworks covering anti-money laundering, sanctions screening, FX disclosure, and tax-information reporting.

The cost layer most often missed is FX spread. Non-bank payment institutions typically charge 0.5 to 1.5 percent over the interbank rate on the FX leg of each international transfer. On €100,000 of monthly Eurozone payroll funded from a USD operating account, a 1 percent spread is €1,000 per cycle and €12,000 per year before any per-transaction fee.

Regulatory enforcement intensified through 2024. Global AML fines reached $4.6 billion in 2024 alone, with regulators shifting from supervision to active enforcement against the payment-infrastructure providers buyers depend on. The FATF Travel Rule, DAC7 reporting, and PSD2 strong customer authentication all attach to standard payroll flows.

What do cross-border payments mean in payroll?

In payroll, cross-border payments are the funding rail that delivers gross salary, employer contributions, and EOR fees from the buyer's treasury to the host-country worker or authority. Three operational features matter for the buyer.

The rail-selection question

Four rails carry most cross-border payroll flows. SWIFT correspondent banking handles two-to-three-business-day international wires through bank-to-bank settlement. SEPA covers single-business-day Eurozone transfers in EUR.

ACH (US) and Faster Payments (UK) cover domestic-only flows; cross-border equivalents route through SWIFT. Non-bank payment institutions (Wise, Airwallex, Revolut Business) offer faster settlement and tighter FX spreads but operate under PSD2 / FCA safeguarding rules. See the payroll funding window entry for the timing impact on working capital.

The FX spread layer

Every cross-border payment that crosses currencies absorbs an FX spread between the interbank mid-market rate and the rate the rail provides. Big-four banks typically run 1.5 to 3 percent on standard treasury wires. Non-bank payment institutions run 0.3 to 1.5 percent. Wise quotes the lowest at 0.3 to 0.6 percent in major corridors.

The spread compounds across the cycle. A 50-worker EUR payroll funded from USD at a 1 percent spread costs $12,000 per year in FX cost before fees. See the FX spread entry for the rail-by-rail comparison.

The regulatory overlay

UK Payment Services Regulations 2017 require authorised payment institutions to safeguard client funds. EU PSD2 Directive 2015/2366 sets strong-customer-authentication requirements and authorisation rules. DAC7 Directive 2021/514 introduced platform-reporting obligations from January 2023 at €2,000 or 30 transactions per worker.

FATF Travel Rule requires originator and beneficiary information on transfers above $1,000 across most jurisdictions. The OFAC sanctions screening attaches to US-dollar transactions globally even when neither counterparty is US-based.

How do the rails compare on speed, cost, and regulatory coverage?

The rail choice decides the funding window, the FX cost, and the regulatory exposure. Each rail has its own settlement window, fee structure, and counterparty risk profile.

SWIFT remains the standard for treasury-to-EOR funding wires above $100,000. Non-bank payment institutions like Wise have taken meaningful share for contractor and small-team payroll because of the FX spread differential.

SEPA Instant is changing the EUR-zone payroll funding calculation. A 10-second EUR transfer effectively eliminates the funding-window working-capital cost for Eurozone payroll inside an EOR or global payroll provider. See the multi-currency payroll entry for the broader currency-management mechanic.

How does the cross-border payment cost stack build?

The total cost of a cross-border payment runs across four layers. Each layer compounds and the per-transaction cost rarely captures the full picture.

The intermediary correspondent fee is the line most often missed. SWIFT routes through correspondent banks that each charge a per-hop fee, often $10-$40, deducted from the gross amount in transit. A single payment can pass through three or four hops, with the worker receiving a net amount $40-$160 below the gross sent.

Provider MSAs usually treat correspondent-chain shortfalls as the buyer's problem, with no top-up obligation on the provider. The contracting clause to read is the wording on "amount in the worker's hands". If the contract guarantees only the gross sent, the buyer absorbs the deduction. See the net-to-gross payroll entry for the parallel gross-up mechanic on guaranteed-net packages.

What do buyers consistently get wrong on cross-border payments?

The recurring mistakes cluster into four moves visible across multi-country procurement reviews that have rebuilt the payment architecture after a year-one variance event.

The first is treating per-transaction fees as the headline cost. The FX spread layer dominates total cost on any cross-currency payment above $5,000. A "free transfer" with a 2 percent FX spread costs more than a $50 fee with a 0.3 percent spread.

The second is missing the safeguarding obligation. UK Payment Services Regulations 2017 and EU PSD2 require authorised payment institutions to segregate client funds. Verify that an EOR or payroll provider holding funds in transit holds an FCA or equivalent EU authorisation, and that the trust account is genuine segregation rather than commingled.

The third is missing the FATF Travel Rule attachment. Transfers above $1,000 require originator and beneficiary information. Provider compliance failures cascade onto the buyer when the rail's KYC process delays the payment cycle past the host-country pay date.

The fourth is missing the DAC7 reporting trigger. EU Directive 2021/514 introduced platform-reporting obligations from January 2023 at €2,000 or 30 transactions per worker per year. Contractor-management platforms now share data with EU tax authorities; payment data alone can trigger a misclassification audit.

What does an EOR or payments provider handle on cross-border payments?

Global payroll providers and EOR providers bundle cross-border payments inside their service fee. Contractor management platforms handle the contractor-payment leg separately and increasingly include FX-spread disclosure on each transaction.

EOR providers absorb the rail-selection and FX-conversion layer inside the per-seat fee. Contractor management platforms typically expose the FX spread per transaction, giving buyers visibility but not control. Global payroll providers operating their own treasury infrastructure (Papaya, Rippling, CloudPay) negotiate corridor-specific rates that can sit below standard bank wires by 50 to 70 percent.

See the UAE WPS entry for the country-specific compliance rail that overlays cross-border salary payments into the UAE, and the payroll reconciliation entry for the variance-tracking discipline that catches FX drift in-cycle.

Cross-border payments FAQs

What is the difference between SWIFT and SEPA?

SWIFT is the global network for cross-border wire transfers between banks. Settlement runs 2-3 business days through correspondent banking with per-hop fees and FX spreads.

SEPA is the Eurozone-specific network for EUR-denominated transfers between EU member states plus a small set of associated countries. Settlement runs 1 business day under standard SEPA and ≤10 seconds under SEPA Instant. SEPA has no FX leg between EUR-only accounts; SWIFT typically does.

How much does FX spread cost on a typical cross-border payroll?

FX spread typically runs 0.5 to 1.5 percent over the interbank rate at non-bank payment institutions and 1.5 to 3 percent at big-four banks. On €100,000 of monthly Eurozone payroll funded from a USD operating account, a 1 percent spread costs €1,000 per cycle and €12,000 per year.

The spread compounds with per-transaction and receiving-bank fees. Non-bank rails (Wise, Airwallex) typically beat banks by 100-200 basis points before fees.

What is the FATF Travel Rule and how does it affect payroll payments?

The FATF Travel Rule requires payment institutions to capture and pass on originator and beneficiary information for transfers above $1,000 across most jurisdictions. For payroll, this means the worker identity, address, and account details must be fully captured before the first transfer.

KYC verification delays at the rail can push payroll past the host-country pay date and trigger late-pay incidents. Verify worker KYC documentation completes before the first payroll cycle, not at the wire instruction step.

Does DAC7 affect cross-border contractor payments?

Yes. EU Directive 2021/514 (DAC7) introduced platform-reporting obligations from January 2023 at €2,000 or 30 transactions per worker per year. Contractor-management platforms operating in the EU report contractor identity and payment volume to the relevant member state's tax authority.

The shared data can trigger a misclassification audit if the contractor's volume and exclusivity profile fits an employment pattern under the relevant national tests.

Should cross-border contractor payments go through the global payroll engine?

Not without classification risk. Global payroll engines are built for W-2/employee payroll with statutory withholding and employer contributions. Contractors typically self-pay social security and income tax in their home country.

Running contractor payments through the employee payroll engine creates a paper trail that supports a misclassification finding. Use a dedicated contractor-management platform for genuine 1099, Partita IVA, or Gewerbeschein workers.