Payroll arriving two days late in June is an irritation.
Payroll arriving two days late on 23 December, to someone who has family arriving, presents to buy and a landlord expecting rent, is a different thing entirely. It's the kind of thing people remember about an employer, and it's the kind of thing that gets discussed.
For businesses paying staff or contractors overseas, December combines three risks that don't normally coincide.
Why December is harder
Payroll usually runs early. Many businesses bring December's pay date forward so it lands before Christmas — the 18th, 19th or 20th rather than the usual month-end. That compresses the whole cycle: approvals, funding and processing all have to happen sooner, often while people are already taking leave.
It lands in the thinnest banking week of the year. Reduced staffing at your bank, at correspondent banks, at your provider and at the receiving bank. A payment that needs human attention gets it more slowly than it would in October.
The consequence of being late is at its worst. Everything that depends on that money — rent, bills, travel, family — is concentrated in the same ten days.
Add an international leg and the margin for error narrows further.
The dates to work to
Taking the UK bank holidays as fixed — Friday 25 December, Monday 28 December, Friday 1 January, plus Monday 4 January in Scotland:
By Friday 4 December — confirm your December pay date with everyone, in writing. If you're bringing it forward, say so now. People plan around it.
By Wednesday 9 December — have payroll data finalised and approved. Any change of bank details, any new starter, any leaver with a final payment. Chasing an approval on the 17th when the approver is already away is how this goes wrong.
By Friday 11 December — fund the account. Not on the pay date. The inbound leg from your own bank is subject to the same thin staffing as everything else, and an unfunded account on pay day is the most common single cause of a late international payroll.
By Tuesday 15 December — instruct payments to less common corridors. Anywhere requiring supporting documentation, anywhere you've seen a payment held before, anywhere with a materially different banking calendar.
By Thursday 17 December — instruct everything else, for a pay date of the 18th or later.
Those dates are deliberately conservative. The cost of being early is zero. The cost of being late, this month, isn't.
Practical things that prevent the common failures
Verify any changed bank details by phone, now. An employee or contractor emailing new account details in mid-December, with a request to use them for this month's pay, is a scenario fraudsters actively exploit — urgency is built in and verification is hard when half the team is away. Call a number you already hold. This applies to people you know well.
Use local payment rails where they exist. SEPA in Europe, ACH in the US and equivalents elsewhere are faster, cheaper and far less prone to correspondent deductions than international wires. A salary arriving short because an intermediary bank took a cut is a bad conversation in any month; in December it's worse.
Batch the conversion, not the payments. Converting currency individually per employee is priced worse than a single bulk conversion followed by local distribution. Convert once, pay many.
Check the receiving country's calendar. Your pay date isn't a pay date if the destination banking system is closed. Japan's New Year closure runs into early January. Several European markets treat 24 December as a holiday or half day.
Tell people what to expect. If pay is landing on the 18th rather than the 31st, say so. If a payment might arrive a day either side because of the holidays, say that too. Most of the frustration in a late payment is the not knowing.
The bigger version of this question
December payroll is a scheduling problem. The underlying currency exposure isn't.
If you pay overseas staff every month, you have a recurring, predictable, foreign-currency cost — twelve or more known amounts on known dates, stretching as far ahead as you employ those people. It's the clearest hedging case most businesses have, and the one most frequently left open.
A business paying £400,000 a year in overseas salaries is exposed to every move in the relevant pair. Sterling weakening 7% over a year raises that cost base by £28,000, without anyone receiving a pay rise.
Worth looking at in January, when the immediate scramble is over and you're setting next year's budget anyway.
And one thing worth naming
If you fix an overseas employee's salary in sterling while they live and spend in another currency, they are personally carrying your currency risk. Their real income moves month to month through no fault of their own.
Paying people in the currency they actually live in, and managing the exposure on your side, is better practice and better employment. Your finance function can hedge. Your developer in Kraków cannot.
William Fuller, Co-Founder of Orbis Exchange Group contact on 0203 918 5622
Ben James, Co-Founder of Orbis Exchange Group contact on 0203 918 5621