EBICS Banking Interface

Banking & payments

EBICS Banking Interface

Payments belong automated — without portal logins and without media breaks. Our self-developed EBICS interface communicates as a central server directly with EBICS-capable banks in the EU: account statements and current transactions come in automatically, transfers and direct debits go out in a controlled way — from DocuWare, your accounting, your ERP or your own systems. The solution is fully standalone: DocuWare is just one of many possible use cases.

What the interface delivers

Direct bank communication via EBICS

EBICS is the banking standard for corporate payments: the interface talks directly to the bank — no portal detours, no manual up- and downloads. TAN and approvals happen where the work happens: in the application. Currently tested and used by customers with, among others:

Erste Bank and Sparkassen (Austria)
Raiffeisen (Austria)
Austrian Anadi Bank (Austria)
Deutsche Bank (Germany)
extensible to all EBICS-capable banks in the EU

All important business transactions per banking standard

The interface covers the common EBICS transaction types:

CAMT.052 — current transactions (intraday)
CAMT.053 — electronic account statement, including PDF statement
SEPA transfers (domestic & EU) and urgent transfers
Direct debits
further transaction types as needed

Standalone — with or without DocuWare

The interface is fully decoupled from DocuWare and designed as one central, easy-to-understand solution that covers everything around EBICS. Technically a small Docker container with a UI for administrative tasks and an API for your applications — for integration into accounting software, ERP, customer systems and, of course, DocuWare. Extensive logging and API authentication are built in.

Productive in daily use

The interface is already integrated in customer projects: payment information is fetched automatically every day and transfers are generated automatically — fully logged and traceable.

SEPA XML payment files straight from DocuWare

Even without EBICS we automate your payments: IBAN and payment details are captured in the DocuWare workflow, and our program creates the SEPA XML file from the selected, approved documents — ready to upload into your banking software, such as ELBA, George/George Pro, BusinessLine or Anadi Banking. Only what has been verified and approved gets paid — without retyping IBANs.

Process

Four steps to automated payments

From the EBICS access to regular operation — statements in, payments out under control.

Setup

Set up EBICS access with your bank; the server runs as a Docker container in your environment or hosted.

Connection

Your systems — DocuWare, accounting, ERP — use the interface’s API, secured by authentication.

Test phase

Account statements, test payments and approval processes are verified together.

Regular operation

Transactions come in automatically, payments go out under control — fully logged.

At a glance

Direct banking standard EBICS — no portal detours
CAMT.052 / CAMT.053 incl. PDF statement
SEPA and urgent transfers, direct debits
In use with Erste Bank & Sparkassen, Raiffeisen, Anadi, Deutsche Bank
Fully standalone — usable without DocuWare
Lean Docker container with admin UI and API
Extensive logging, API authentication
Alternative: SEPA XML from DocuWare for ELBA, George & co.

Frequently asked questions

Do we need DocuWare for the EBICS interface?

No. The interface is fully standalone and also available for use cases without DocuWare — the idea is one central, easy-to-understand interface that covers everything around EBICS. We are happy to discuss which systems you want to connect in an initial consultation.

What does EBICS offer compared to the banking portal?

Direct communication with the bank instead of manual portal work: account statements and transactions come in automatically, payments are generated from your systems, and TAN or approval happens directly in the application. Several banks and accounts can be handled centrally via one server.

Which banks does the interface work with?

In principle with every EBICS-capable bank in the EU. Currently tested and in customer use are, among others, Erste Bank and Sparkassen, Raiffeisen and Austrian Anadi Bank in Austria as well as Deutsche Bank in Germany.

How is the interface operated?

As a lean Docker container — in your environment or hosted. Administrative tasks run via a dedicated UI, your applications use the API with authentication. All operations are extensively logged.

Can we generate payments from DocuWare without EBICS?

Yes — with our SEPA XML solution: payment details are captured in the DocuWare workflow, and the approved documents become the XML file for your banking software (e.g. ELBA, George, George Pro, BusinessLine, Anadi Banking). The step up to a fully automated EBICS connection remains open at any time.

Let's Talk

Automate your payments now

We will show you the EBICS interface live — from account statement to transfer.