EBICS 3.0 is gradually replacing EBICS 2.5 across several European countries, at different speeds depending on the bank and national banking landscape. For a business, the question isn't whether migration will happen, but when its bank will require it — and what that actually changes on the connection side.

What both versions have in common

EBICS remains, in both cases, a secure bank communication protocol using certificates to authenticate and sign file exchanges (transfers, direct debits, statements). The general logic — a user ID, a partner ID, typed bank orders (CCT for transfers, CDD for direct debits, STA for statements) — doesn't fundamentally change between the two versions.

The main technical differences

EBICS 3.0 unifies bank order formats at European level (through the "BTF" concept — Business Transaction Format — which replaces the old, inconsistent national order types), strengthens certificate security requirements, and changes certain communication mechanisms. For the end user, the most visible change is often the need to regenerate certificates and reconfigure the EBICS subscriber with their bank.

Migration timeline by country and bank

In Germany, EBICS 3.0 has been the standard for several years already. In France, the switch has rolled out bank by bank, with some institutions keeping EBICS 2.5 running in parallel longer than others. There's no single date: each bank communicates its own timeline to its business clients, generally with several months' notice.

How Arkaio handles the coexistence of both versions

Arkaio doesn't force any choice: a company's EBICS connection stays configured according to what its bank requires, 2.5 or 3.0, and can evolve without any change to the Sage Intacct-side setup. For a multi-bank group where some institutions are already on 3.0 and others still on 2.5, both coexist without any separate configuration to manage manually.

What to check before migrating

Three points to confirm with your bank before any switch: the end-of-support date for EBICS 2.5 on your account, whether you'll need to regenerate your INI/HIA certificates, and whether the specific bank orders you use (international transfers, B2B SEPA direct debits) are properly covered by the BTFs offered in 3.0.

In summary

EBICS 3.0 unifies bank order formats at European level and strengthens security requirements
The migration timeline depends on each bank, not a single regulatory date
Arkaio adapts to whichever version each bank requires, with no Sage Intacct-side reconfiguration
Check with your bank on the end-of-support date and whether certificates need regenerating