EBICS 3.0 is gradually replacing EBICS 2.5 at European banks. The 3.0 specification has been available since November 2018, and Austrian banks moved to EBICS 3.0.2 from November 2023. Elsewhere, the pace depends on each bank. For a business, the question is not whether migration will happen, but when its bank will require it, and what it actually changes for the connection and for the team.
EBICS in brief
EBICS (Electronic Banking Internet Communication Standard) is the protocol that connects a company's systems to its banks to exchange files: credit transfers, direct debits, statements. The company is a bank "subscriber", identified by three elements: the bank server address (Host ID), a customer ID (Partner ID) and one ID per user (User ID).
Each user holds three keys: one to sign orders, one to authenticate, one to encrypt. They are sent to the bank during initialization through the INI order (signature key) and the HIA order (authentication and encryption keys), then confirmed with an initialization letter. The bank then activates the subscriber, which usually takes a few days.
What does not change
EBICS is a transport layer. The files it carries are the same in 2.5 and 3.0: pain.001 for credit transfers, pain.008 for direct debits, camt.053 for statements (see pain.001 vs pain.008). Distributed electronic signature (VEU), which lets several signatories approve an order, exists in both versions too (see VEU electronic signature).
Treasury processes are therefore not called into question. What changes is how orders are named and how keys are managed.
The main technical differences
| Topic | EBICS 2.5 | EBICS 3.0 |
|---|---|---|
| XML schema | H004 | H005 |
| Order naming | Three-character codes, often national (CCT, CDD, STA in Germany; FUL and FDL in France) | BTFs (Business Transaction Formats): an upload (BTU) or download (BTD) order described by parameters shared across Europe |
| Keys | RSA keys, with or without certificates depending on the country | X.509 certificates for all keys, self-signed or CA-issued depending on the bank |
| Scope | National variants | One specification for the whole EBICS community |
The most significant change is the BTF. In 2.5, the same SEPA credit transfer had a different name in Germany and in France. In 3.0, the order is described by standard parameters: the service (for example a SEPA credit transfer), its scope, an optional variant, and the name of the ISO 20022 message carried. The EBICS SC publishes a mapping between the old codes and BTFs.
What migration means for the business
- Certificates: depending on the bank, you need new X.509 certificates and a new INI/HIA initialization, with a new initialization letter. Some banks accept self-signed certificates; others require a certificate authority.
- Software: the banking communication tool must support EBICS 3.0 and know the bank's BTFs.
- Signatories: every person who signs orders through VEU is affected by the key renewal.
- Timing: during the switch, the subscriber may be unavailable for a few days. Avoid payroll dates and month-end.
Migration timeline
There is no single regulatory date. Each bank announces its own timeline to its business clients, usually several months in advance. In France and Switzerland, the switch happens bank by bank, and some banks keep EBICS 2.5 running in parallel during a transition period. A multi-bank group can therefore have some accounts on 2.5 and others on 3.0 for several months.
Checklist before migrating
- Ask your bank for the EBICS 2.5 end-of-support date on your contract.
- Confirm the version offered (3.0 or a later release such as 3.0.2).
- Check which certificates are accepted: self-signed or CA-issued.
- List the orders you use today (credit transfers, CORE and B2B direct debits, camt.053 and camt.054 statements) and get their BTF equivalents.
- List your VEU signatories and their rights.
- Plan a test period, then a cut-over date outside peak activity.
- Allow for the bank's activation lead time after it receives the initialization letter.
Use cases
- Single-bank SMEs: migration often comes down to a new initialization, scheduled with the bank.
- Multi-bank, multi-entity groups: each bank migrates at its own pace. The challenge is to avoid running two tools or two procedures side by side.
- Accounting firms: one firm manages EBICS subscribers for clients whose banks move at different speeds.
Security and control
Moving to X.509 certificates strengthens signatory identification, but shifts part of the risk to key management: where keys are stored, who can use them, how they are renewed. Migration is a good time to review the separation between preparers and signatories, and dual-approval thresholds.
How Arkaio handles both versions
Arkaio does not force a choice: each bank's EBICS connection is configured to match what that bank requires, 2.5 or 3.0, and can change without touching the Sage Intacct setup. In a multi-bank group, both versions coexist with no separate configuration to maintain. VEU is supported, and users' signature certificates are kept in an HSM. The full connection is described on the EBICS Connector for Sage Intacct page; to choose between EBICS and bank APIs, see Open Banking vs EBICS.
Frequently asked questions
Do I need a new EBICS contract to move to 3.0?
It depends on the bank. Some update the existing contract, others require a new subscription. Either way, a new key initialization is common.
Do payment files change with EBICS 3.0?
No. pain.001, pain.008 and camt files stay the same: only the way they are named and transmitted changes.
Can EBICS 2.5 and 3.0 be used at the same time?
Yes, with different banks, as long as your communication tool supports both versions.
In summary
- EBICS 3.0 replaces national order codes with BTFs and makes X.509 certificates the norm.
- Payment and statement files do not change.
- The timeline depends on each bank: ask for the EBICS 2.5 end-of-support date.
- Prepare the list of your orders and signatories, and a cut-over date outside peak activity.