Häufig gestellte Fragen
What is EBICS and what is it used for?
EBICS (Electronic Banking Internet Communication Standard) is an open, cross-bank standard for automated, encrypted data exchange between companies and their banks over the internet. It lets firms submit payment orders and retrieve account statements and status messages without logging in manually to an online banking portal. EBICS itself only governs secure transport; the business content is transmitted as SEPA or ISO 20022 files (pain for orders, camt for account information). For ERP and accounting systems, EBICS is the central channel for handling payment transactions directly from within the software.
Do I need a separate EBICS client alongside the ERP?
That depends on whether the ERP or financial accounting software supports EBICS natively. Larger ERP systems often integrate EBICS directly or use an integrated bank communication service as middleware that pools the sessions and multiple bank connections. Many mid-sized users, by contrast, continue to run specialised EBICS programs such as SFirm or BL Banking alongside the ERP. In practice, the exact set-up varies by industry, company size and the customising depth of the specific installation, which is why the scope of functions should be clarified with the vendor in advance.
What does an EBICS connection cost?
The costs break down roughly into ongoing bank fees and one-off integration work. Banks typically charge a monthly base fee for EBICS activation and use, sometimes supplemented by transaction-based charges; the exact terms differ considerably from bank to bank. On the ERP side, one-off effort is required for set-up, key management and testing the order types, the cost of which depends heavily on the system, multi-bank capability and degree of integration. Since these amounts vary substantially in individual cases, concrete figures should be agreed directly with the bank and the ERP vendor.
What is the difference between EBICS and FinTS/HBCI?
EBICS and FinTS (formerly HBCI) are both standards for electronic bank communication in Germany but target different user groups. FinTS/HBCI is aimed primarily at retail customers and smaller use cases such as individual transfers, standing orders and balance enquiries within the SEPA area, and usually uses a chip card with PIN/TAN for authentication. EBICS, by contrast, was developed specifically for corporate banking communication, relies on digital certificates and can handle large data volumes such as entire payment runs as well as bundling several bank connections over one channel. For companies with high transaction volumes and several banks, EBICS is therefore the established standard, while FinTS tends to cover the retail and small-business segment.
How does EBICS secure payments, and how does the four-eyes principle work?
EBICS uses a multi-layered security architecture: each participant holds their own cryptographic keys for authentication, encryption and electronic signature, allowing banks to verify the authenticity and integrity of every order. This separation of keys makes the procedure more robust than a simple portal login with a password, and the minimum requirement is RSA key lengths of 2,048 bits, which will be raised further in future. The four-eyes principle is implemented via the distributed electronic signature (VEU): one person submits the payment run and a second person approves it independently, if necessary from a separate workstation. This allows the segregation of duties between accounting and management to be enforced directly within the EBICS process.
What changes with EBICS 3.0 and the 2026 migration?
EBICS 3.0 (protocol version H005) harmonises the standard across countries, so the previous differences between Germany, France, Switzerland and Austria largely disappear. A key innovation is the uniform identification of order types via so-called Business Transaction Formats (BTF), which replace the earlier country-specific order types. Separate from this is the SEPA deadline in November 2026: from then on, banks will only accept the newer pain and camt versions, and address data must be captured in structured or hybrid form (at least town and country), as purely unstructured address lines will be rejected. Companies should therefore check whether their ERP system and EBICS software support EBICS 3.0 and the new ISO 20022 formats, and coordinate the migration with their banks in good time.