Bank Operations

Bank Operations

Bank Operations is the interface for manually executing EBICS order type requests against the bank server. While scheduler jobs handle routine tasks automatically — such as daily statement downloads — Bank Operations gives you on-demand control for ad-hoc requests, testing, and troubleshooting.

Use Bank Operations when you need to:

• Fetch the latest account statement outside of a scheduled job

• Download bank parameters or public keys for a new connection

• Upload a payment file or SEPA document to the bank

• Test connectivity with the EBICS Server Stub

• Retrieve audit trail or usage reports

Payment Builder and  Library

The Payment Builder composes multi-order SEPA documents order by order: pick the operation — Credit Transfer or Direct Debit — and format (pain.001 for credit, pain.008 for debit), build the orders, and generate a schema-validated ISO 20022 XML document in one step. The Payment Library archives those documents — stored encrypted, searchable, and ready to be loaded, edited, executed, or deleted at any time.

Open Payments Library

The Payments Library is opened from Banking → Payments Library. The home page offers two ways to start:

• New Payment — Opens the builder to create a SEPA document from scratch.

• Load from Library — Picks a saved payment to continue working on it.

Create Or Edit Payment

The builder composes the document from orders, each entered in a three-step wizard:

1. Select Creditor — The creditor (payment recipient) account is chosen from the saved bank parties, searchable by name; each entry shows the account name and its connection ID.

2. Select Debtor — The debtor (payment source) account, which must belong to one of your EBICS connections.

3. Set Amount — The amount (currency taken from the selected account) plus an optional description — the remittance information, up to 40 characters. Create Order adds the payment to the document.

The operation and SEPA format are selected before generation, with the format list filtered by the operation. Generate Document then produces the SEPA XML file, validated against ISO 20022 schemas by the server.

Each order lands in the order summary, with more addable up to 500 per request; New Order appends another payment and the total is shown at the bottom. An existing SEPA XML file can also be uploaded from the toolbar menu — the system parses it, extracts all orders, and resolves IBANs to the stored bank parties.

An order can be changed: the wizard reopens pre-filled with that order’s creditor, debtor, amount, and description — any step can be modified, and Update Order applies the changes.

Add Bank Account in Payment

When the creditor or debtor is not among the saved bank parties, the plus icon next to the field — in either wizard step — opens the Add Bank Account dialog without leaving the form.

Creditor vs. debtor. The debtor must be an account on one of your EBICS connections; the creditor can be any party you hold an account for.

Store Payment to Library

Once generated, Store to Library saves the document — encrypted and searchable — and opens its Edit Payment page for later reuse or modification.

In-place updates. For a payment loaded from the library, Store to Library updates the original file in place instead of creating a new one.

Bank Operations Integration

For upload order types (CCT, CDD, CIP, FUL, BTU and similar), the file field’s folder icon opens the Choose Payment dialog, so a stored library document can be sent to the bank without downloading it first. The selected file — from disk, the library, or the Payment Builder — is displayed in a file block with Preview and Remove actions.