SEPA payments for payroll providers
Running euro payroll is not UK payroll with a different currency. The settlement calendar is different, the failure modes are different, and the rule that stops a client refusing an employee’s account is one most UK bureaus have never had to think about. This is what changes when a pay run crosses into euro.
- How to automate euro pay runs over SEPA without a separate provider
- Why euro payroll does not stop on UK bank holidays — and does stop on days the UK works
- How to scale from a handful of euro employees to several client countries
- What actually breaks in a euro run, and how to catch it before payday
The calendar problem
The single most common way a euro pay run goes wrong at a UK bureau is that someone applied the UK working-day calendar to it. Euro payments do not settle on UK bank holidays or UK working days. They settle on the TARGET calendar, run by the Eurosystem, and the two lists are not the same.
TARGET closes at weekends plus exactly six weekday dates a year: 1 January, Good Friday, Easter Monday, 1 May, 25 December and 26 December. Everything else is a settlement day. The consequences run in both directions:
| Date | UK | Euro settlement | What bureaus get wrong |
|---|---|---|---|
| Late August bank holiday | Closed | Open | Euro run delayed unnecessarily because the UK calendar says holiday |
| 1 May | Working day (unless it falls on the early May bank holiday) | Closed | Euro run scheduled into a closure; funds land a day late |
| Early May, spring bank holidays | Closed | Open | Same as August: avoidable delay |
| 2 January | Closed in Scotland; also in England and Wales when 1 January falls at a weekend | Open | Scottish clients assume the closure applies to euro too |
If you run both sterling and euro payroll, your scheduling logic needs two calendars, not one with exceptions. Treating euro as "UK plus a currency conversion" is the assumption that produces late salary payments. You can check any specific date against both calendars with our payment timing calculator.
Credit transfers need no mandate
A recurring confusion, and one worth settling early because it changes what you have to collect from employees. Paying a salary is a SEPA Credit Transfer: you push money to an account. It requires no authorisation from the recipient, no mandate, and no lodgement lead time. All you need is a valid IBAN and a beneficiary name.
Mandates belong to SEPA Direct Debit, where a party pulls funds from someone else's account. As a bureau you only enter that world if you also collect your own fees from client employers by direct debit, which is a separate arrangement with its own rules — our Direct Debit guide covers the UK equivalent, and the SEPA guide covers the euro scheme in full.
The practical implication: onboarding a euro employee is faster than onboarding a UK direct debit payer. There is no lead time to wait out before the first payment.
IBAN discrimination, and why bureaus meet it first
Article 9(1) of EU Regulation 260/2012 prohibits what is usually called IBAN discrimination: a payer cannot insist that the payee's account be held in a particular member state. An employer in Ireland cannot require an Irish IBAN; a German employer cannot refuse a Spanish one.
The boundary is the EU and EEA, not the whole SEPA area. This distinction is easy to get wrong and matters directly to UK bureaus. The regulation covers accounts in EU and EEA states; the UK, Switzerland and Monaco participate in SEPA but sit outside it. Since Brexit, an EU employer is not obliged under Article 9 to accept an employee's UK account, and a client asking about that case should be given the accurate answer rather than the reassuring one.
Bureaus tend to discover this before their clients do, because it surfaces as a technical failure rather than a legal question: payroll software validates the IBAN country against the client's country and rejects it, or a client's own policy says "employees must hold a local account". Both are contrary to the regulation for euro payments in the SEPA area.
Worth knowing precisely, because it is a question you will be asked by a client at some point, and the correct answer is that they may not refuse. You can validate any employee IBAN before it enters the file with our IBAN checker.
A euro pay run, step by step
-
Fix the value date against the TARGET calendar
Work backwards from the contractual pay date, not from your UK run schedule. Confirm the value date is a TARGET settlement day, and that your provider's submission cut-off for that day has not passed.
-
Validate the beneficiary file before you build the payment file
Check every IBAN's checksum and country length, and diff the file against the previous run: new accounts, changed accounts and removed employees are where errors concentrate. A structural check catches almost all typing errors at zero cost.
-
Fund the euro balance, not the sterling one
If you are converting from sterling, do it before the run and at a rate you have seen, rather than letting the conversion happen implicitly at submission. Holding a euro balance removes the conversion from the critical path entirely, and removes the FX margin from every individual salary payment — see what that margin costs on our FX calculator.
-
Submit as a batch, with the client's reference on every line
Employees see the remittance reference on their statement. For a bureau paying on behalf of many employers, that reference is what stops an employee ringing the wrong company. Use the client employer's trading name, not the bureau's.
-
Reconcile against returns, not against your own file
A submitted file is not a paid file. Match what actually settled, and treat every return as needing action before the next cycle rather than after it.
Where euro runs actually break
| Failure | When you find out | How to catch it earlier |
|---|---|---|
| Invalid or mistyped IBAN | At submission, or as a return | Checksum validation on file build; diff against last run |
| Beneficiary name mismatch | Verification of Payee warning at submission | Keep the legal name on file, not the payroll display name |
| Account closed since last run | Return, usually a day or two later | Act on the previous cycle's returns before building the next file |
| Value date on a TARGET closure | Payday, when nothing arrives | Schedule against the TARGET calendar, not the UK one |
| Insufficient euro balance at submission | Whole batch rejected, not one line | Fund and confirm the balance before submitting, not during |
| Sanctions or fraud screening hold | Delay of hours on an otherwise valid run | Submit with slack; flag unusually large or first-time payments in advance |
The pattern is that most failures are detectable at file-build time and expensive at payday. That asymmetry is the whole argument for validating early: an hour of checking before submission is worth more than a day of chasing afterwards, because after payday you are not fixing a payment, you are managing an employee who has not been paid.
Correcting a missed payment
When a single employee is missed or paid the wrong amount, a standard credit transfer will land the next TARGET business day, which on a Friday means Monday. SEPA Instant settles in under ten seconds and runs at weekends, which makes it the right tool for exactly this case even though it is the wrong tool for the run itself. Knowing your provider supports it before you need it is the point.
Scaling across client countries
The operational difficulty of euro payroll does not grow with the number of employees. It grows with the number of client employers and the number of countries, for two different reasons.
More client employers means more fund segregation. Running many employers' money through one euro balance makes reconciliation a manual exercise and makes a client query hard to answer precisely. The structural answer is one virtual IBAN per client employer, so funds arrive already attributed and a return is unambiguous about whose run it belongs to.
More countries means more local statutory obligation, and this is where the payment layer stops being the constraint. SEPA moves euro anywhere in the area on the same terms, so the payment itself does not get harder. What gets harder is the local tax and social-security filing that sits around it, which is a payroll question rather than a banking one. It is worth being clear with clients about that boundary: your account can pay an employee in Portugal on the day you say it will, which is not the same as being registered to run Portuguese payroll.
For the sterling side of the same operation, see our companion guide to BACS payments for payroll providers, which covers the three-day cycle, Service User Numbers and the bureau model.
Frequently asked questions
Do euro payroll payments stop on UK bank holidays?
No. Euro payments settle on the TARGET calendar, which closes only at weekends and on six weekday dates a year: 1 January, Good Friday, Easter Monday, 1 May, 25 December and 26 December. UK-only bank holidays, such as the late August bank holiday, are ordinary settlement days for euro payments. The reverse also catches bureaus out: 1 May is a normal working day in the UK but a full closure for euro settlement.
Does paying employees in euro require a SEPA mandate?
No. Paying salaries is a SEPA Credit Transfer, which is pushed by the payer and needs no mandate from the recipient. Mandates belong to SEPA Direct Debit, where the collecting party pulls funds. Payroll bureaus only need mandates if they also collect fees from client employers by direct debit, which is a separate arrangement.
Can a client refuse an employee's IBAN because it is from another country?
Within the EU and EEA, no. Article 9(1) of EU Regulation 260/2012 prohibits IBAN discrimination: a payer cannot require that the payee's account be held in a particular member state. Note the boundary carefully, because it is not the whole SEPA area. The regulation covers EU and EEA accounts; the UK, Switzerland and Monaco take part in SEPA but are outside it. Since Brexit, an employer in the EU is therefore not bound by Article 9 in respect of an employee holding a UK account.
How long does a SEPA payroll payment take to arrive?
A standard SEPA Credit Transfer arrives no later than the next TARGET business day, and frequently the same day. SEPA Instant settles in under ten seconds and runs around the clock, including weekends, which makes it the practical tool for correcting a missed or wrong payment on payday rather than for the run itself.
What is the most common cause of a failed euro payroll payment?
Beneficiary details, by a wide margin: an IBAN that fails its checksum, a name that does not match the account, or an account that has been closed since the last run. Since 9 October 2025, Verification of Payee has been mandatory for SEPA payment service providers under Regulation (EU) 2024/886, so a name mismatch now surfaces as a warning to the payer before submission rather than as a silent failure afterwards. A warning does not block the payment: if you proceed anyway, the liability shifts to you. All three causes are detectable before submission, which is why validating the beneficiary file against the previous run is worth more than any amount of chasing afterwards.
Written by the financeb2b editorial team · Scheme facts sourced from the European Payments Council and the ECB TARGET calendar · Last updated 31 August 2026 · Editorial policy
Euro and sterling payroll from one account
A Gemba account covers SEPA for euro and BACS, Faster Payments and CHAPS for sterling, with unlimited virtual IBANs so each client employer keeps its own segregated balance.
Open a Gemba account