EBICS — Electronic Banking Internet Communication Standard

EBICS (Electronic Banking Internet Communication Standard) is the corporate-banking communication protocol dominant in Germany, France, Switzerland and Austria. EBICS enables companies to exchange payment instructions (SEPA Credit Transfers, Direct Debits) and receive bank statements through a standardised secure channel, with cryptographic signatures providing payment-authorisation. For DACH ERP-bearing organisations, EBICS is the most-common bank-integration mechanism for high-volume or treasury-operated environments.

How EBICS works

EBICS uses HTTPS as transport with XML-based message structure (ISO 20022 for SEPA, EBICS-specific for session management). Companies install EBICS client software (multi-bank capable) or operate EBICS through their treasury system or ERP. Order types: EBICS defines specific order types for each message category — CCT (Credit Transfer), CDD (Direct Debit), C53 (camt.053 bank statement), MT940 (legacy statement), URG (urgent transfer), among many others. Signatures: each payment file requires digital signatures from authorised individuals according to the company's signature rules. Multi-bank signature management is one of EBICS's strengths.

EBICS clients and integration

EBICS access happens through several routes. Standalone EBICS clients: ProfiCash (DG Verlag, popular for SMB), Multi-Cash (Cologne Intelligence), Star Money Business, eDokumente. Treasury platforms: SAP Multi-Bank Connectivity, Bellin TM5 / Coupa Treasury, Hanse Orga, BELLIN tm5, Kyriba, Treasury Intelligence Solutions (TIS) — for centralised group treasury. ERP-integrated: SAP S/4HANA Cash Management, Microsoft Dynamics 365 F&O Bank Statement Connectivity, NetSuite Bank Feeds. Cloud-API alternatives: increasingly, modern fintech tools (Klarna, Ramp, Spendesk for specific use cases) bypass EBICS in favour of PSD2 Open Banking APIs. For DACH mid-market, EBICS through ProfiCash or Multi-Cash remains the dominant choice for production payment runs; PSD2-API-based access is growing rapidly for specific use cases.

PSD2 as alternative

PSD2 (Payment Services Directive 2) introduced regulated APIs for Account Information Services (AIS) and Payment Initiation Services (PIS), enabling third parties to access bank accounts with customer authorisation. For corporate banking, PSD2 APIs offer an alternative to EBICS with several advantages: real-time data (versus EBICS's batch-oriented model), easier integration with modern SaaS tools, lighter operational footprint. However, EBICS retains advantages for high-volume bulk payments, multi-bank signature management and complex authorisation workflows. The two coexist in DACH corporate banking: EBICS for treasury-grade flows, PSD2 APIs for modern operational integration and analytics. Major banks (Deutsche Bank, Commerzbank, UniCredit, UBS, Credit Suisse, Erste) support both channels.

Practical implementation considerations

Three operational patterns. (1) Centralised treasury: group treasury operates a single EBICS infrastructure connecting to all group banks, with subsidiaries submitting payment proposals to treasury for execution. Standard for groups above 100 million EUR revenue with active treasury function. (2) Distributed banking: each entity operates its own EBICS connection to local banks, with ERP-side payment runs feeding the EBICS client. Common in DACH mid-market with simple group structures. (3) Bank-hosted SaaS: some banks offer hosted EBICS-replacement services through their corporate-banking portals, with API access for ERP integration. The choice reflects scale, treasury maturity and IT preferences.

Frequently Asked Questions

Is EBICS only used in Germany?

No. EBICS dominates Germany, France, Switzerland, Austria, with extensions to other European markets. International banks operating in DACH support EBICS for corporate clients regardless of bank-headquarter country. For multinational operations, EBICS plus SWIFT covers most needs.

Will EBICS be replaced by PSD2 APIs?

Coexistence rather than replacement, at least through the late 2020s. EBICS handles bulk-payment scenarios, multi-bank signature management and complex authorisation flows that PSD2 APIs do not match well. PSD2 APIs handle real-time data, modern SaaS integration and lightweight use cases better. Most DACH treasury organisations operate both channels.

How does instant payments integration work over EBICS?

EBICS supports SEPA Instant Credit Transfer (SCT Inst) as a defined order type. Companies submit SCT Inst orders through standard EBICS channels; the bank processes them within seconds rather than batching to next-day settlement. As Instant Payments mandates take effect across the EU from 2025 onwards, EBICS-channel SCT Inst usage grows.