Change history

Version 1.16.50


  1. Open the .log file under Help

    Under Help there is now a menu item to open the .log file directly, to look for the cause of an error, for example.

  2. Display of two-factor authentication in user administration

    In the user administration, you can see if a user has enabled two-factor authentication (2FA) in the user overview. When resetting a user with 2FA enabled, there is an option to remove or keep the user's 2FA.

Payments and sent files

  1. Support of SEPA format versions, the use of which is recommended by the DK standard as of 19/11/2023

    It is now possible to record and send SEPA credit transfers and express credit transfers in the pain.001.001.09 scheme and SEPA direct debits in the pain.008.001.08 scheme. Furthermore, it is possible to send SEPA container files in the schema container.nnn.001.GBIC4, which contain credit transfers and direct debits in the new schemas. In addition, payment status reports can be processed in the schema pain.002.001.10.

  2. Extension of filtering options for sent files

    For sent files, it is now possible to filter by submitter. In addition, it is also possible to filter by states such as Booked, which might result from the processing of payment status reports and account statements. When filtering by payment type, there is a new option unequal.

  3. Extension of filtering options for payments

    In the views for periodic payments and payment templates, there is now also a filter function. In all payment overviews it is now possible to filter by account. In the signed payments, it is possible to filter by the state, just like in the sent files.

  4. Folder for periodic payments and payment templates

    In the views of periodic payments and payment templates, folders can now be created, as with open payments, with the help of which periodic payments and payment templates can be grouped and thus a better overview can be achieved.

  5. "Change payments" function for periodic payments and payment templates

    It is now possible to change multiple periodic payments and payment templates at the same time. For this purpose, there is an entry accordingly in the context menu of the respective overview.

  6. Display of the recipient account in the payment overviews

    In the payment overviews, the account number of the recipient is now displayed next to the recipient name.

  7. Display of signers in the transmission report

    In addition to the submitter, the other signatories of a payment order are now also displayed in the transmission report.

  8. Save recipient for SEPA transfers without intended purpose

    When entering a SEPA transfer, you can select when saving the recipient whether the recipient is to be saved with or without an intended purpose.

  9. New option in the permissions for salary payments: "See payments, without details".

    In the permissions for salary payments there is a new option User may see salary payments (without details). A user with this permission may send and sign a file with salary payments, but will not see any details about the included payments.

Account information

  1. Placeholder for the account group during automatic export and for the export directory for PDF statements and other PDF documents

    For the filename of an automatic export and the export directory for PDF statements and other PDF documents, now the placeholder $(ACCOUNTGROUP) can be used, so that it is possible to generate exported files also per account group.

  2. Delete files after successful account statement import

    For the account statement import there is now the option as with the payment import to automatically delete the selected file after a successful import.

  3. Display of further information on bookings from camt.053 account statements

    For camt.05x transactions, the unique reference is displayed in the booking details. For a camt.05x transaction to a batched booking the number of single bookings is displayed.

  4. Display of the retriever of retrieved files

    In the view Retrieved files the user who has retrieved the file is now displayed. You can also filter by this user.

Version 1.15.52


  1. Display of the permission profiles given by the bank from other users

    Under the bank properties, an administrator can view the permission profile (HTD) of other users given by the bank. If the corresponding user is selected on the page User profile, his permissions are displayed, in particular also his signature classes. This profile can also be printed.

Payments and sent files

  1. Foreign transfers on the base of the ISO 20022 standard

    As of November 2022, the DK standard supports foreign transfers based on the ISO 20022 standard. These international XML payments could be recorded in BL Banking already for some time, but now even in the pain.001.001.09 schema stipulated by the DK standard. The hitherto existing DTAZV format for foreign transfers will only be supported until November 2025.

  2. Note on no longer supported SEPA versions

    According to the SEPA LifeCycle of the DK standard, SEPA files in the schemas pain.001.003.03 and pain.008.003.02 will only be supported until the end of November 2022. When such a file is sent, a note appears that this format is no longer supported. The user can still send the file or convert it to a current schema using the payment import.

  3. SEPA container files in the schema container.nnn.001.03

    It is now possible to send SEPA container files in the schema container.nnn.001.03, which is supported from 20/11/2022, according to the DK standard.

  4. Entry of a SEPA reversal transfer for a transaction out of an account statement

    A SEPA reversal transfer can be entered directly for a transaction out of an account statement. If the transaction is selected in the transactions overview and you click on the entry Create SEPA credit transfer for this transaction in the context menu, the entry dialog for the SEPA transfer opens, in which the fields are already pre-filled with the data from the transaction.

Account information

  1. Breakdown of batched transactions in the account statement that belong to outgoing payments

    Batched transactions in camt.053 account statements consisting of outgoing payments can contain references (msgId and pmtInfId) to the original payment file. If the matching signed payments are found for such a batched transaction, a virtual batched transaction file is created from these payments. Subsequently, the batched transaction can be broken down into individual transactions. Until now, this was only possible for incoming payments, since usually only in this case banks provide batched transaction files in camt.054 format.

  2. Assignment of account statement information to signed payments

    If a transaction is found in the account statement for a signed payment, the status is set to Posted. The printout of the signed payment will then additionally show the posting date, value date and the account statement number.

  3. Detailed display of fees for transactions from camt.053 account statements

    Multiple fees may apply to a payment, e.g. the fees from your own bank and the charges from the other party's bank. If the camt.053 account statement contains this information, the individual fees are displayed under Posting details and, where applicable, also with information on the charging bank.

  4. Display of further information on transactions from camt.053 account statements

    If there are ultimate recipients or originators or ultimate payers or payees in the transactions of camt.053 account statements, these are displayed in the posting details. Likewise, ISO bank transaction codes (short: ISO BTCs) are now displayed, too.

  5. Ignore advised transactions in PDNG state when calculating balances

    It is possible that a transaction is contained in a first advice in the pending state PDNG and in another advice again in the state posted. In order to avoid that this transaction is considered twice in the calculation of the value date balances, it is possible to set per bank that advised transactions in the PDNG state should be ignored in the calculation.

Version 1.15.20

Payments and sent files

  1. Check payments in XML format

    Besides the international transfer in XML format, the corresponding check payment in XML format based on the ISO 20022 standard is now also supported.

  2. Swizz domestic payments according to the Swiss Payment Standards (SPS)

    The payment types for Swiss domestic transfers in pain.001 format according to the Swiss Payment Standards (SPS) are now also supported. A special feature is that in the entry dialog you can set whether a payment should appear in the camt.054 batched transaction file with details, without details or not at all.

  3. SEPA instant payments in pain.001.001.09 format

    SEPA instant payments can now also be generated in the pain.001.001.09 format, which is recommended according to the current specification of the DK (German Banking Industry Committee). The setting of this format can be done per bank on the page Send parameters in the new column Scheme.

  4. Country-specific presetting of standard order types and standard BTFs

    The default order types and default BTFs are different for Germany, Austria and Switzerland. To avoid to have to set these values individually and to reduce the administration effort, you can select for the bank the country code DE, AT or CH to control that the order types and BTFs are preset according to the country-specific mapping documents. This concerns both the send parameters for payment types and the fetch parameters for account statements, advices, batched transaction files and messages.

  5. Structured addresses

    Structured addresses can now be entered for originators and recipients for international XML payments, Swiss domestic transfers and SEPA payments, e.g. separate address fields for street, house number, postal code and city instead of unstructured address lines.

  6. Payment reference (ISO 11649) for SEPA payments

    When entering a SEPA payment, a payment reference can now be entered instead of the intended purpose. Via a new preference you can optionally check that only valid ISO 11649 references are allowed.

Version 1.14.4


  1. Changeover from chip card to key file

    Users who use a smart card as a key medium can now conveniently switch to a key file by clicking on the entry Change to key file... under Actions. With the help of the wizard that then opens, new keys can be generated, which are stored in the file system and encrypted with a new password to be assigned. Subsequently, an automatic key change is carried out at all banks, where the newly generated keys are immediately active without the need for approval by a bank employee.

Version 1.14.0


  1. Note on too short EBICS keys

    According to the Krypto LifeCycle defined in the EBICS standard, EBICS keys with a length shorter than 2048 bits are only allowed until the end of November 2021. If a user has keys that are too short, a note will appear at program start with the recommendation to change the keys. The new keys generated during the key change are active immediately, i.e. they don't need to be released by a bank employee.

  2. Display of the key lengths under bank properties.

    The current key lengths are displayed under Bank properties on the Bank page.

  3. Display of further information on AWV notifications

    The overview of AWV notifications now shows whether an AWV notification was created manually or generated automatically by an outgoing payment or a transaction in the account statement. If the AWV notification was generated automatically, the account, payment order or account statement and the originator or recipient are also displayed. This additional information should facilitate the creation of the AWV notifications.

  4. Locking a user

    In the user administration, the access of a user can be temporarily locked. This can be useful if a user is absent for a longer period of time.

Payments and sent files

  1. Information on SEPA recalls in camt.029 format

    When SEPA payments are recalled using the camt.055 format, the bank can provide information about the processing status of these recalls in the camt.029 format. This information is retrieved in the same way as pain.002 status reports (e.g. when updating the overview of sent files) and is displayed in the Notifications view. In addition, the status of a sent file or signed payment is updated based on the camt.029 information. In case of a successful recall, the new state of a signed payment, for example, is Cancelled by recall.

  2. Display of the collector reference and message ID in the printout of a signed SEPA payment

    In the printout of a signed SEPA payment, the collector reference and message ID now appear in addition to the order number. This simplifies the mapping of signed payments to batched transactions in the account statement, since the account statement also contains the collector reference (and not the order number).

  3. Conversion of CSV and Excel files into the international payment formats

    CSV and Excel files can now be converted to international transfers in XML format (ISO20022) or MT101 format when sending and importing payments.

  4. SEPA salary payment as an additional payment type

    For SEPA salary payments there is a new payment type, for which you can set your own bank-specific sending parameters. This makes it possible, for example, to send salary payments to the bank with a different order type than normal SEPA transfers (e.g. with XCT instead of CCT).

  5. Display of account names when signing in the Electronic Distributed Signature (EDS)

    When signing a payment order in EDS, the name of the originator account is now displayed in the payment details instead of the IBAN. If this differs from the IBAN, the IBAN appears as a tooltip.

Account information

  1. Account and customer related information in PDF format (BKI)

    In the perspective Account statements there is a new view Other PDF documents, which displays account and customer related information in PDF format. This can be retrieved from banks with the order type BKI or the corresponding BTF. Possible documents are e.g. invoices, account closings or balance confirmations. If the view should be missing, it can be made visible via Window - Reset perspective.

  2. Support of the new camt.05x formats

    With this version, account statements, advices and batched transaction files can also be processed in the formats camt.053.001.08, camt.052.001.08 and camt.054.001.08 (ISO version 2019, DK standard format from November 2021), as well as in the formats camt.053.001.04, camt.052.001.04 and camt.054.001.04 (ISO version 2013, used in Switzerland).

  3. Automatic exports also for advices and batched transaction files

    With the help of automatic exports, advices and batched transaction files can now be exported automatically in addition to account statements. When creating an automatic export, the corresponding file type must be selected.

  4. Placeholders for account name and export time for automatic exports

    For the file name of an automatic export, the two additional placeholders $(ACCOUNTNAME) and $(NOW) can now be used, so that the file name of the exported file can contain the account name and creation time.

  5. Filtering transactions according to incoming and outgoing payments

    In the transaction filter, it is now possible to specify whether to filter by incoming or outgoing payments.

Version 1.13.28


  1. Adjustment of the migration to EBICS 3.0 (according to current specification)

    The migration from an older EBICS version to EBICS 3.0 has been adapted to the current EBICS specification or CR-EB-20-03, respectively. If a user already has sufficiently long keys on the older EBICS version, no key change is required when switching to EBICS 3.0 and the previous keys without certificates can continue to be used. Only users whose keys are shorter than 2048 bits must carry out a key change before the migration to EBICS 3.0, about which they are automatically notified.

Payments and sent files

  1. International payment in XML format

    With the international payment in pain.001.001.03 format, another payment type for international transfers is now supported in addition to the DTAZV payment and the MT101 payment. In contrast to the DTAZV payment, the originator does not need an account with a German account number and German bank code to use this new payment type.

  2. Austrian Postbar payment

    With the Postbar (postal cash) payment, another important Austrian payment method is now supported in addition to the tax office payment. Postbar payment offers the possibility to send money to a recipient who does not have a bank account.

  3. Execution priority of SEPA transfers

    In the SEPA entry dialog there is now the possibility to set the priority of the execution. The values normal (NORM) or high (HIGH) are possible.

  4. Specifying the originator address for SEPA transfers to the United Kingdom

    Due to the Brexit, the address of the originator must be specified for SEPA transfers to the UK. This address can be entered in the originator administration at the SEPA originator.

  5. Specification of the address for a payer from the United Kingdom

    As the UK is no longer part of the EU, for SEPA direct debits with a payer from the UK, the payer's address must be entered, as is the case for a payer from Switzerland, for example. This address can be entered in the mandate management.

Version 1.13.2


  1. EBICS 3.0

    The EBICS version 3.0, which will be obligatory for all German banks as of November 22, 2021, can now be used for communication with banks which also already support EBICS 3.0. When creating a new bank account, EBICS 3.0 can then be selected. Existing bank accounts can also be converted to EBICS 3.0. In this case, the user must change the keys, which however, runs automatically and does not require an approval by the bank. If there are other users for this bank access in the same installation, these employees must also perform a key change.

  2. Two-factor authentication with authenticator app

    With the authenticator app there is now another two-factor authentication method in addition to Yubikey. With this procedure, only an app needs to be installed on the smartphone; is not necessary to purchase a USB token. When creating one-time passwords with the app, an Internet connection is not required. The authenticator app can be set up under Preferences - Security - Two-factor authentication.

  3. Filter options for the customer protocol

    In the view for the customer protocol for a bank there is now a filter function. You can enter date, order type and order number as filter criteria, which allows you to search for specific orders, for example.

  4. Display bank connections next to payments and account statements

    The view Bank connections can now also be displayed in the perspectives Payments and Account statements. In existing installations, the respective perspective must be reset for this. This gives you direct access to the relevant bank properties, such as account information retrievals, without having to take the detour via the Jobs perspective.

  5. Unlocking a user

    A user who has been locked because he entered an incorrect password five times during login can be unlocked in the user administration. After that, this user has five more attempts to enter the correct password when logging in.

Payments and sent files

  1. Display of payment types instead of order types for send orders

    Since in EBICS 3.0, the previous business order types are replaced by Business Transaction Formats (BTFs) (e.g. CCT by SCT_pain.001), payment types are now displayed instead of order types in the overviews of EDS orders and sent files. For example, an order now appears as SEPA transfers ZZZZ instead of CCT ZZZZ.

  2. Setting of send parameters for payment types

    Under the bank properties there is a new page Send parameters where you can set, which BTF or order type is used to send payments to the selected bank after signing. For a bank with EBICS 3.0, the BTF is used, for a bank with an older EBICS version such as EBICS 2.5, the order type is used. The values are preset according to the German EBICS specification, so that for German banks, you normally don't have to change anything here. The situation is different, for example, if you set up a bank access to a Swiss bank. In this case, e.g. for the SEPA transfer, you must enter the order type XE2 instead of CCT and the order type XED instead of CDD for the SEPA base debit.

  3. Filter by payment type

    With the introduction of payment types, the filters in the views of open and signed payments, sent files, as well as signed and cancelled EDS orders have been extended, so that you can also filter by payment type.

  4. Payment filter extended by execution date

    For open and signed payments, the execution date can be selected as a further filter criterion.

  5. Filter for notifications and retrieved files

    There is now a filter function in the views Notifications and Retrieved files.

  6. Additional information in payment orders for EBICS 3.0

    When sending a payment order to a bank which uses EBICS version 3.0, the user can enter additional information in the signing dialog, which will then be visible for himself and other signatories of the order, but will not be forwarded to the payee or payer.

  7. Further information on the cancellation reason for C55 recall orders

    When recalling SEPA payment orders, in addition to the selectable reasons for cancellation, e.g. Wrong amount, further information on the cancellation reason can be given as free text.

  8. Further information in the transmission report and in the properties of a sent file, display of status messages in the transmission report

    The transmission report and the properties of a sent file now also show the approval method (Electronic signature or Fax release) and the status determined on the basis of the protocol. If pain.002 status messages exist for the sent file, furthermore, the date of the most recent status message and the state determined from the status messages are displayed. Additionally, the status messages also appear in the transmission report.

  9. Display of non-final states based on status messages

    If sent SEPA files and signed SEPA payments are in non-final states after processing status messages with status codes such as ACSP or PNDG, these are now also displayed in the overviews. This means that the new states Booking in preparation, Additional checks required, Partially booked and Partially rejected can occur. Previously, only the addition Notifications exist was displayed for these states.

  10. Display of payment details when sending and signing SEPA container files

    It is now also possible to display the signed payments for orders that have been submitted with another client and have only been signed in the EDS with the current client. To do this, you have to set the preference Extract send orders of other users from the customer protocol and click on Display details when signing the order. If you then select the signed order under Sent files and click on Show payments, the signed payments will appear in a separate view, just like for an order submitted with the current client.

  11. Display of payment details when sending and signing SEPA container files

    When sending and signing payment files in SEPA container format, it is now possible to display the payment details. Additionally, when printing the orders, a table with the payment details appears.

  12. IBAN only for SEPA payments in the entire SEPA area and for SEPA express payments

    Since the BIC of the recipient or payer is no longer mandatory throughout the SEPA area, SEPA transfers and SEPA debits can now be entered and sent without the BIC. SEPA express payments can also be entered and sent without the recipient BIC.

  13. Enhancements to the entry of MT101 payments

    An equivalent payment can now be entered for international payments in MT101 format. The BIC of the intermediary can also be specified.

Account information

  1. Credit advice for SEPA instant payments

    To notify a payment recipient of the receipt of a SEPA instant payment, the German Banking Industry Committee has specified the credit advice in camt.054 format. In addition to the previous advices, these credit advices are now retrieved from all banks using the action Retrieve advices and are displayed in the views of the perspective Account statements. You can configure the retrieval of credit advices per bank under Bank properties - Account statements.

  2. Options Newest account statements and Account statements in period when exporting account statements and exporting the balance overview

    If you select accounts in the view Account statements and click on Export, you have the option to export the newest account statements or the statements of a specific period of the selected accounts. Using the new standard conversion Salden.txt, you can export the current balances of the selected accounts, that is, the balance overview.

  3. Options Newest account statements and Account statements in period when printing account statements

    If you select accounts in the view Account statements and click on Print, you have the print to export the newest account statements or the statements of a specific period of the selected accounts.

  4. Printing the transactions overview

    If you select transactions in the view Transactions, you can print them as an overview using the context menu item Print transaction overview. Under preferences Account information - Print settings you can set that the transactions are grouped by accounts.

Version 1.12.2


  1. New permissions in the user administration (assignment of roles)

    There are a number of new permissions in the user administration, such as User is authorized to record payments, User is authorized to sign orders in the EDS or User is authorized to view account statements. If these permissions are revoked from a user, he cannot see any data in the belonging views and cannot start any actions connected with them. In addition, he cannot make any changes to the corresponding preferences and bank properties. This way, it is now possible to assign certain roles to employees in a multi-user installation, such as Payment typist or EDS signatory.

Payments and sent files

  1. Automatic retrieval of status notifications when updating sent files

    The pain.002 status notifications provided by the banks contain information on the processing status of SEPA payment orders that go beyond the information from the bank protocol (PTK, HAC) and can be very important for users. These can be information on payments that were not executed, but also positive reports on postings that took place. When updating the view of the sent files, the status notifications are automatically retrieved from all banks just like the customer protocol. Under the bank properties, there is a new page Notifications where you can carry out settings for these retrievals.

  2. Assignment of status notifications to sent files and signed payments

    When processing pain.002 files, the status notifications contained therein are assigned to the corresponding sent files and signed payments. Afterwards you can view the status notifications for the respective order or payment via the context menu entry Display status notifications. Vice versa, in the overview of notifications, the send order, to which the status notification refers, is displayed. The column Notification type then contains for example Status report (CRZ) for order CCT ZZZ0.

  3. New states Booked and Rejected for sent files and signed payments

    The evaluation of the status notifications also serves to determine the status of sent SEPA files and signed SEPA payments. Because of the additional information available from the status notifications, there are now the new states Booked and Rejected in addition to the previous states, such as Signatures complete. In the case of non-final status codes, such as PNDG (pending status) or different status codes within one order, the addition Notifications exist is displayed with the previous state.

  4. Notes on errors reported in the customer protocol during order processing

    If entries are found in the customer protocol (HAC, PTK), which cause a send order being put into the status Error, a dialog box opens automatically, which informs the user of this error. The error message is then saved as a notification and is therefore also visible later in the Notifications view.

  5. Colored representation of the states of sent files and signed payments

    Sent files and signed payments are displayed in different colors depending on their state. The longer the associated order is in the EDS, the more red it becomes. Under Preferences - File transfers there is the setting Display states in colour, with which the colors can be switched off again.

  6. Presentation of SEPA payments to be signed in tabular form

    When SEPA payments are signed during sending files or from the EDS overview, the payments contained in the file can now also be displayed in a table. This table is displayed when you click on the Table button in the payment details. Since this table can also be sorted by columns, it is now possible to find a payment with a certain amount or a certain recipient very quickly, even if there are many payments.

  7. SEPA instant payments with time

    When recording SEPA instant payments (SCT inst), you can now optionally specify the time, at which the payment shall be executed. If the time has been set, the payments are saved in the format pain.001.001.08, which is intended for this purpose, and sent to the bank.

Account information

  1. Printing of batched transaction files as overview

    With the preference Print batched transaction files as overview you can print newly retrieved batched transaction files directly as an overview, that is without the transactions contained therein.

Version 1.11.42


  1. Two-factor authentication with YubiKey security key

    To further increase security, the two-factor authentication recommended by the German Federal Office for Information Security (BSI) can be activated. One or more YubiKey security keys from the Yubico company can be added under Preferences. In addition to the previous password ("know"), the user also needs the YubiKey ("have") to generate the additional one-time password required for logging on and signing. The YubiKey uses the USB interface and, unlike the chip card, does not require a reader or driver software.

  2. Separate passwords for login and electronic signature

    As a further password guideline, it can be set that users should use separate passwords for the login and the electronic signature (ES).

  3. Resetting users

    If a user has forgotten his password, it can be reset in the User administration. The user's bank connections, account authorizations, and other rights (e.g. for salary payments) are retained. After resetting, the user must reinitialize himself at the banks and can continue to work as before after the bank has activated the access. If separate passwords are used, it is possible to reset only the login password for a user who has only forgotten his login password. If the user then confirms the newly created logon password with the previous ES password, it is not necessary to reinitialize at the banks.

  4. Text filter with new option "does not contain"

    In the filter dialogs for transactions, payments and sent files, the text filter has been extended by the new option "does not contain", so that you can search for entries that do not contain a certain text.

Payments and sent files

  1. SEPA real-time transfers

    SEPA real-time transfers (SCT inst) in pain.001.001.03 format can now be processed. There is another wizard for entering these payments. After signing, SEPA real-time transfers are submitted to the banks with the order type CIP.

  2. Swiss SEPA

    Payments that exist in the Swiss schema can now be processed, too. If this schema is selected for a bank on the page SEPA payments, the payment files are generated in this schema and sent to the bank via order type XE2 after signing. Under preferences, you can also specify that SEPA payments can be entered in a currency other than EUR, e.g. in CHF.

  3. Recipient recording with four-eyes principle

    A new new preference can be used to set the four-eyes principle for recording and editing payment recipients. This means that payments can only be sent to recipients that have been entered by one user and confirmed by another user. The right to confirm recipients can be set individually for each user in the User administration.

  4. Display names for recipient and mandate import

    When importing recipients and mandates, the display name can be imported as an additional field if the CSV file contains a corresponding column.

Account information

  1. Additional columns in the account overview

    In the Account overview there are three new columns Opening balance, Total debit transactions and Total credit transactions, which can be displayed or hidden via the menu or the corresponding user profile under Display settings.

  2. Printing the account overview

    If the new columns Total debit transactions and Total credit transactions are displayed, they also appear in the printout. If the columns Credit limit and Free liquidity are displayed instead of these columns, they are printed. If none of these optional columns is displayed, the columns for the value date balances for today, tomorrow and the day after tomorrow appear in the printout as before.

  3. Collective fetch and configurability of retrievals for legally binding PDF account statements

    Under Actions there is now a new entry Retrieve PDF statements, which you can use to start a BKA collective retrieval from all banks. This retrieval also starts, when the overview PDF Statements is updated using the update icon or with the F5 key. In the bank properties on the page PDF statements the properties of the retrieval can be set for each bank, e.g. the retrieval method or the date of the last fetch.

Version 1.11.13


  1. Configuration of password requirements

    There is a new window Passpword requirements under Preferences - General, where an administrator can configure the policies for a password, e.g. the password length and the minimum number of certain characters.

  2. PostgreSQL as another database

    In addition to the databases H2, MySQL, MS SQL and Oracle, now a PostgreSQL database can be used, too.

Payments and sent files

  1. Electronic recalls of SEPA payments (camt.055)

    From this version onwards, it is possible to initiate electronic recalls for SEPA payment orders that have already been completely signed. For this purpose, camt.055 messages are sent to the bank. As a prerequisite, the respective bank must support this feature. It is possible to recall single payments as well as entire collectors (logical files). The callback can be started for signed payments and sent files via the context menu entry Recall SEPA payments.

  2. Individual permissions for salary payments

    Individual authorizations for salary payments can now be set in the user administration. There are the following three settings: The user is allowed to view and enter salary payments, the user is only allowed to see salary payments without amounts when signing, or the cannot see salary payments at all.

  3. For SEPA payers outside the EU/EEA area, address fields must be specified

    Due to an EU money transfer regulation, the address of the payer must be specified for SEPA direct debits with a payer outside the EU/EEA area - e.g. from Switzerland. In order to be able to enter the address, the mandate administration must be activated in the preferences under Payment recording - SEPA payments. The address of the payer can then be entered when recording a mandate. If you choose this mandate subsequently, when you enter a SEPA direct debit, the address fields are taken in the payment. A tooltip displays the address in the payment recording and also when signing.

  4. Recording ISO-SEPA payments with foreign currency

    If you turn on the preference Allow foreign currencies under Payment recording - SEPA payments, a drop-down list for the currency appears during SEPA payment entry. This makes it possible to enter ISO-SEPA payments in a currency other than EUR. If you then enter foreign currency payments there, they are sent to the bank with the order type XCT.

Account information

  1. Display of the descriptions in the field Text key addition for MT940 transactions

    In addition to the numeric code, the belonging description is shown in the field Text key addition for MT940 transactions, e.g. 901 - Incorrect IBAN.

Version 1.10.86

Payments and sent files

  1. Support for MT101 as a further payment format

    In addition to SEPA and DTAZV payments, international payments in MT101 format (RFT) can now also be recorded and imported. When sending MT101 files, the details of the individual payment records are now displayed.

  2. Simultaneous change of multiple payments

    The new context menu item Change of payments allows you to make simultaneous changes to several open payments. In addition to the change to the execution date, the change of the originator account and the originator is now also possible. In addition, substitutions can be made in the intended purposes of the selected payments.

Account information

  1. Retrieval of legally binding account statements in PDF format (order type BKA)

    In the Account statements perspective, there is a new view PDF Statements, which displays legally binding account statements retrieved with the order type BKA. If the view is missing, you can make it visible via Window - Reset Perspective.

Version 1.10.72

Payments and sent files

  1. Conversion of Excel files to DTAZV files

    During sending files and importing payments it is possible to select Excel files and convert them into the DTAZV format. The Excel file does not need to conform to any fixed format, because BL Banking is able to learn the new format. To do this, a window appears, when an Excel file with a new format is opened the first time, where the columns of the file can be mapped to the DTAZV payment fields. Payment fields, for which there are no columns, can be filled with constant values. If valid values were allocated to all payment fields, the DTAZV file for sending or importing can be generated. The next file with this format can be sent or imported directly. However, it is also possible to check the field mapping again and adjust it if necessary.

  2. Conversion of CSV files to DTAZV files

    Similar to Excel files, CSV files can be converted to DTAZV files, too.

  3. Extended check during sending SEPA files

    When sending SEPA files, additional checks are performed, including checking for invalid characters. If an intended purpose contains an exclamation mark, for example, a corresponding error message appears and the file cannot be sent. Furthermore it is checked that for SEPA express payments a BIC is specified for the recipient. You can turn this extended check off under Preferences - Payment recording - SEPA payments.

  4. Search functions in the views for recipients, accounts and mandates

    In the views for recipients, accounts, and mandates, there is now the option to filter for entries that contain a specific search term.

  5. Austrian tax office payments

    There is a new recording wizard for Austrian tax office payments in the SEPA format, which allows to record several types of duties (e.g. VAT) for different time periods. At the same time the intended purpose is generated automatically, as it is described in the specification.

Account information

  1. Display of credit limit and available liquidity

    In the account overview, there are new columns for the credit limit and free liquidity. These columns are optional and can be displayed via a corresponding preference. If these columns are displayed, the total credit limits and total free liquidity are also displayed for the balance lists.

  2. Extended transaction filter by type, posting key and transaction code

    In the transaction filter dialog it is now possible to filter for one of the types "transfer", "direct debit", "reversal transfer" and "return debit note". Additionally one can filter for values of the posting key or the transaction code.

  3. Hiding obsolete advised transactions in the transactions view

    If an account is selected in the account overview, only current advised transactions for this account are displayed in the Transactions view. Obsolete advised transactions are hiden. In the Adviced transactions view all advised transactions are displayed.

  4. Do not process statements for certain accounts

    It is now possible to not process statements for certain accounts so that they are not visible in the account overview. For this purpose, there is the new setting "Don't process account statements" in the account properties.

Version 1.10.56


  1. Open the workspace directory under Help

    Uner Help the is now a menu entry to open the data directory directly. Under Windows for example the Explorer opens here.

Payments and sent files

  1. SEPA mandate administration

    As of this version, the mandate administration is set by default for the recording of SEAP debits. During updating the software, SEPA payers are converted to SEPA mandates and displayed in the view Mandate administration. When recording SEPA debits, these mandates can then be selected.

  2. Change of SEPA mandates

    If changes are made to one of the five fields Payee, Creditor identifier, Mandate reference, IBAN and BIC of the payer, they are saved separately in the mandate. In the next SEPA debit that is recorded for this mandate, these changes are accepted once and transferred to the bank when they are sent.

Version 1.10.49


  1. Assignment of non-initialized bank connections to employees with bank access

    In the user administration, users with bank access can be assigned additional bank connections, for which they don't need to initialize. Users can then work "locally" with these bank connections, e.g. view account statements and record payments.

Payments and sent files

  1. SEPA version 3.0

    The SEPA version 3.0 valid from Nov. 20, 2016 is supported. This version features simplifications for mandate changes and reduced time limit for the CORE base debit. In this regard the COR1 base debit with reduced time limit is dropped out. The belonging DK schemas pain.001.001.03 and pain.008.001.02 can be set in the bank properties.

Account information

  1. Balance lists with advice information and credit limit

    In the view Balance lists you can now either see value date balances or posting balances. In addition, there you can set via a menu whether the balances shall be displayed including advice information and credit limit. The view Value date balances was renamed to Balances and contains an additional column for the posting balance.

  2. Value date balances without transfer postings (for Cash-Pooling)

    If cash pooling is used, you can display the value date balances for the subsidiary accounts without transfer postings (= cash concentrating postings with GVC 833 and 834). For this purpose you need to set the corresponding checkbox in the account properties of the respective account and enter opening balance and date.

Version 1.10.46


  1. Support for the encryption protocol TLS 1.2

    As of this version, the TLS 1.2 encryption protocol recommended by the BSI is supported for the EBICS transport encryption.

Payments and sent files

  1. SEPA mandate administration, change of mandates

    If the preference Use mandate administration (under Payment recording -> SEPA payments) is checked, SEPA payers are converted into SEPA mandates and displayed in the new view Mandate administration. When you record SEPA direct debits, you can then select these mandates. The fields belonging to the mandate can be changed in an extra dialog window during payment recording. The changes made there are stored in the SEPA payment files and can thus be transferred to the bank.

  2. Conversion of SEPA transfers into SEPA express payments

    With the help of a new context menu entry, you can convert SEPA transfers into SEPA express payments and also vice versa SEPA transfers in SEPA transfers.

  3. EDS settings per bank

    Under bank properties, there is a new page EDS, where you can set for each bank bank whether amounts shall be displayed (HVZ) and whether the EDS history shall be detected from the protocol. In addition, the EDS can be deactivated for the selected bank.

  4. Check of originator accounts during file transfer

    When sending a payment file, it is checked whether the originator accounts are known in BL Banking and belong to the selected bank. This prevents, amongst others, that a payment file is accidentally sent to the wrong bank. This check can be turned off via the preference Allow unknown originator accounts during transmission of external files under Payment recording.

Account information

  1. Automatic retrieval of advices

    Like with the automatic retrieval of account statements, there is now also an automatic retrieval of advices, which can be configured under the preferences.

Version 1.10.35

Payments and sent files

  1. Conversion of Excel files to SEPA files

    During sending files and importing payments it is possible to select Excel files and convert them into the SEPA format. The Excel file does not need to conform to any fixed format, because BL Banking is able to learn the new format. To do this, a window appears, when an Excel file with a new format is opened the first time. There, the columns of the file can be mapped to the SEPA payment fields. If valid values were allocated to all payment fields, the SEPA file for sending or importing can be generated. The next file with this format can be send or imported directly. However, it is also possible to check the field mapping again and adjust it if necessary.

  2. Conversion of CSV files to SEPA files

    Similar to Excel files, CSV files can be converted to SEPA files, too. Previously this was only possible if the CSV files corresponded to a format given by BL Banking.

  3. Deactivation of recipient recording

    With the new preference Allow recipient recording BL Banking can be configured that during payment recording only existing recipients can be selected and new recipients cannot be recorded. Furthermore, then payment files with unknown recipients cannot be sent or imported.

Account information

  1. New view for advices

    There is a new view Advices, which displays only adviced transactions. Transactions from account statements (= posted transactions) do not appear here. If this view is not available, it can be made visible via Window - Reset Perspective.

  2. Automatic Export of account statements to PDF format

    Account statements can now also be exported to the PDF format via the automatic export. For this purpose, the conversion Create PDF file must be selected when creating the automatic export. When writing the PDF document the print settings from the preferences are used.

Version 1.10.26


  1. Menu item for displaying views

    Via the new menu item Window - Show view you can add all available views to the currently opened perspective. Vice versa, all views can now be closed, so that everyone can configure the user interface according to his wishes. Via Window - Reset perspective the original look of the perspective can be restored at any time.

  2. Transfer the keys of another bank access

    Via the new context menu item Copy bank access and transfer its keys you can set up a new bank access and at the same time transfer the keys of another bank access, without performing an initialization. This is necessary for banks, where a user has multiple bank connections and for which the initialization of one access would result in an initialization of all other connections. If in such a configuration you change the keys of one bank access, you must change the keys of the other bank connections with the help of the new function Transfer the keys of another bank access.

Payments and sent files

  1. Sorting of SEPA payments to be signed by amount

    During signing of SEPA payments, the same can now be sorted by the amount, so that the payments with the largest amounts are at the foremost positions in the payment details. This sorting function can be called directly from the details view via a new menu, which is located to the right of the Next button.

  2. Initialization of account and originator with default values

    When recording a new payment, account and originator are by default initialized with the values, which were entered during the previous recording. Via the new preference Initialize account and originator with the previous values this mechanism can be turned off, so that account and originator are always initialized with the same default values.

  3. Import of DTAZV recipients

    For the import of recipients, DTAZV recipients can now be imported from a CSV file in addition to SEPA recipients. Hereby, the address fields as well as account number, bank code and intended purpose can be imported.

Account information

  1. Balance lists

    There is a new view Balance lists, which shows the balances for a specified period for selected accounts, including a summary row. The user can set the selection of accounts and the time interval directly in this view. If this view is not available, it can be made visible via Window - Reset perspective.

Version 1.10.24


  1. Users without bank access ("local users")

    In the user administration, users can be created, which do not have to be known to the banks and for which an initialization is not required. These "local" users may record payments and view account statements if a user with administrator rights has assigned certain banks and accounts to them. The user administration can now be reached via the Edit menu.

  2. Import users from other installations

    In the user administration, there is now the possibility to import users from other installations and thus combine single-user installations to a multi-user installation.

  3. Display of the entire bank protocol

    Using the new item Show bank protocol in the context menu of the bank, you can view the entire protocol (HAC or PTK) for a bank access.

  4. Cleanup of the bank protocol

    For the bank protocol a cleanup with an interval (Older than ...) can be configured under Preferences - File transfers.

  5. Information about the installation

    Under Help - About BL Banking - Installation Details, there is now the new tab Details, which shows important information about the installation in concise form. Here you can find for instance the license number, Java version and the data directory (workspace).

Payments and sent files

  1. Filter function for sent files

    In the view Sent files you can now filter by specific orders. The filter function can be launched from the new filter icon. The filter criteria bank, order type, order number, status and transfer date can be entered.

  2. Filter function for for open payments

    In the view Open payments you can now filter by specific payments. The filter function can be launched from the new filter icon. The filter criteria text and/or amount can be entered.

  3. BIC check during recording SEPA payments

    When recording SEPA payments, it is checked whether the entered BIC is included in the SCL directory and thus can be reached via the SEPA clearer.

  4. Accompanying tickets for ZZV payments

    When sending the German Postbank-specific ZZV files (payment instructions for clearing) a special accompanying ticket is displayed.

Account information

  1. Account groups

    Account groups can now be created in the account overview, which allow to group accounts and thus achieve better clarity.

  2. Filter functions for accounts and account statements

    In the account overview you can now filter by specific accounts and account statements. With the help of the account filter that is launched via the filter icon, the view is limited to accounts, which name or account number (IBAN) contain the entered search term. Using the account statement filter that is launched via the calendar icon, the view is limited to statements, which statement date is within the specified time interval. An account, for which there are no statements in the set time interval, is not displayed in the account overview.

  3. Cleanup of account statements, advices and batched transaction files

    Account statements, advices and batched transaction files can now be cleaned up automatically. Under Preferences - Account information - Cleanup cleanups can be activated and the cleanup intervals (Older than ...) can be configured.

  4. Graphic displays of value date balances

    In the view Value date balances, there is now a graphic display in addition to the tabular representation of the value date balances. If you select an account in the account overview, the value date balances are displayed as a curve chart in the new view.

Version 1.10.14


  1. Database support

    For data storage now a database is used instead of files as before. This leads to significant performance improvements in many areas. The software comes with a H2 database, which is used by default. For multi-user installations it is recommended to use a separate database. For this purpose, the databases Oracle, MySQL and Microsoft SQL Server are supported. The user of a multi-user installation can set the database at this first start of the program. Under preferences, the database can be changed later, too.

  2. AWV notifications in CSV format

    In addition to the XML format AWV report files can now be created in CSV format.

Payments and sent files

  1. Direct cancellation of sent files and signed payments

    Sent files and signed payments can now be cancelled directly with the new context menu item Cancel. Previously, users first had to change to the perspective Electronic distributed signature. Deleting sent files and signed payment is now only possible via the adjustment in the preferences.

  2. Display details of sent files

    Via the new context menu item Properties you can view the details of a sent file. In the new view, the signature information is shown, which previously could only be found in the customer protocol. In addition, here you can navigate through the payment details, just like when signing an order.

  3. Display payments of sent files

    Via the new context menu item Display payments you can view the payments of the selected sent files.

  4. Setting of the BatchBooking flag during SEPA payment import

    During the SEPA payment import you can now set that the imported SEPA payments shall be shown as single transactions in the account statement. This setting is effective both during import of SEPA files, and CSV or DTAUS files. The global setting in the preferences is not available anymore.

  5. Folder for open payments

    In the view of open payments, folders can be created now, which help to group payments and thus get a better overview.

  6. Direct conversion of recipients to SEP recipients

    By means of the new context menu item "Convert to SEPA recipient" DTAZV and DTAUS recipients can now be converted directly to SEPA recipients. Up to now, the conversion took only place, when a DTAZV or DTAUS recipient was selected during recording a SEPA payment.

Account information

  1. Display of all transactions

    If there is neither an account nor a statement selected in the account overview, all existing transactions are displayed in the transactions view. Previously, transactions were only displayed, when accounts or statements were selected. Note: On Windows, a selection can be undone by using the keyboard combination Ctrl+space.

  2. Improvement of the transaction search

    Using the transaction filter it is now possible to search through all transactions, without having to select accounts or statements before.

  3. Display all accounts of the user profile (HTD)

    If the checkbox of this new preference is ticked, all accounts from the user profile will appear in the account overview, even accounts, for which there are no statements available.

  4. Account selection for automatic exports

    Automatic exports can now be configured so that account statements and transactions are exported only for certain accounts. The selection of the accounts can be made on the second page of the wizard for automatic exports.

Version 1.9.66

Payments and sent files

  1. Individual setting of the BatchBooking flag in SEPA payments

    In the SEPA payment recording dialog you can now set that this payment will be shown as an individual transaction in the account statement. So far this could only be controlled by a global setting in the preferences.

  2. Discontinuation of DTAUS transfers and DTAUS debits

    It is no longer possible to record DTAUS transfers and DTAUS debits.

Account information

  1. Display only accounts for which payment permissions exist

    With the help of this new preference a user with administrator rights can configure the program, so that users can only see statements for those accounts, for which they have payment permissions.

Version 1.9.50

Account information

  1. Display of additional fields for transactions

    In the transaction details and printouts of transactions, additional fields are displayed, which come from the original SEPA payments, such as mandate reference, creditor identifier and end-to-end ID.

Version 1.9.37

Payments and sent files

  1. National SEPA payments with "IBAN Only"

    As of Feb. 1st 2014 in Germany only the recipient's IBAN is required for domestic SEPA payments. Therefore during the entry of such payments the BIC field is only optional.

  2. Discount function for SEPA payments

    Now there is a discount function for the entry of SEPA payments, which calculates the discounted amount. At the same time a note about the discount is written into the intended purpose field.

  3. Payment type for SEPA payments

    Now you can additionally select a payment type during the entry of SEPA payments. In contrast to the payment category, which is set on the logical file layer, the payment type is set on the transaction layer and can later be found in the account statement.

  4. Support for ISO formats for SEPA payments

    You can now transfer SEPA payments, which are on hand in the ISO formats pain.001.001.02, pain.001.001.03, pain.008.001.01 and pain.008.001.02. If you configure the schema accordingly in the bank properties, SEPA payment files can also be generated. However, you need to confirm with your bank, if these formats are supported, because usually in Germany only the ZKA formats are used.

Version 1.9.24

Payments and sent files

  1. Dialog for sending SEPA files

    There is a new dialog for sending SEPA files, wherein the user only has to select the SEPA file to be transferred. In contrast to the regular Send file to bank dialog band and order type are determined automatically from the file content. It is now also possible to send multiple SEPA files with different order type to different banks.

  2. Import of SEPA payer with mandate information

    The csv import of SEPA payers was extended. It is now also possible to import the mandate information required for SEPA debits mandate reference, mandate signing date and sequence type. The mandate signing date in the csv file must be available in the format YYYYMMDD.

  3. Conversion of DTAUS debits into SEPA debits

    Additionally to credits now also debits can be converted from DTAUS to SEPA. For this you need to select the DTAUS debit file and one of the SEPA order types CDD, CDB or CD1 in the send dialog. In order to successfully perform the conversion, the creditor ID must be available in the originator administration, as well as the mandate information in the recipient administration.

  4. Conversion of open and periodic DTAUS payments into SEPA payments

    Open and periodic DTAUS payments can be converted into SEPA payments via the new context menu item Convert to SEPA payment.

  5. Discontinuation of Euro standard transfer and DTAZV registration parts

    It is no longer possible to record Euro standard transfers (ESU) and registration parts for foreign transfers (AZV) and Euro express payment, because these are discontinued according to the DFÜ agreement. Instead of the DTAZV registration parts you can record AWV notifications in BL Banking since version 1.9.17.

  6. Special handling of salary payments

    By default the amounts of salary payments in DTAUS and SEPA format are no longer shown to the user. Furthermore, sent files, which contain salary payments cannot be opened or saved. Also the import of salary payments is not possible by default. These settings can only be changed by a user with administrator rights via the preferences Display amounts of salary payments and Allow import of salary payments.

Account information

  1. Provision method of advice files

    There are two different methods, how banks provide advice files to their customers. At some banks the current advice always contains all transactions of the day (the file grows), whereas for other banks there are only the latest transactions in the current advice. You can configure the provision method for each bank under Bank properties - Account statements with the setting Newest advice contains all bookings of the day, hence advised transactions neither are displayed twice nor are overwritten.

  2. BatchBooking flag in SEPA payments

    SEPA files can be configured, whether the payments inside appear as batched (default) or single transactions in the account statement. In SEPA files, which are generated by BL Banking, the BatchBooking flag relevant for this feature can be set to FALSE by clearing the checkbox Display transactions as batch bookings in the account statement in the preferences under Payment recording - SEPA payments. Please note that this additionally requires an agreement with the bank.

Version 1.9.17


  1. Online-Help

    The previous PDF-manual is replaced by an Online-Help. This can be displayed via the menu item Help - Display Help. In the appendix of the help under Questions and answers there is a large number of answers to frequently asked questions. Furthermore under Quick guides you can find instructions, which explain everyday tasks step-by-step. The entire manual is also published on a Website, which is constantly updated.

  2. Recording of AWV-notifications

    It is now possible to record registration parts according to the German foreign trade regulations (AWV). There is the new perspective AWV-notifications for this, which can be made visible via the menu item Window - Perspective - AWV-notifications. Also it is possible to generate these notifications from signed payments and account statements and then complete them. In the future, recording of registration parts in foreign transfers (DTAZV) won't be possible anymore.

  3. EBICS 2.5

    When creating new bank connections the EBICS version 2.5 can be selected now. Existing bank connections can be migrated to the corresponding protocol version H004. Beside the support of the protocol version H004 the customer protocols in XML format (HAC) specified in EBICS 2.5 can be processed.

Payments and sent files

  1. Evaluation of IBAN rules

    For the first time the current directory of bank codes publishes the rules for the conversion of a bank connection consisting of bank code and account number into a bank connection made up of IBAN and BIC. These rules are evaluated by the entry support during the SEPA payment recording and when taking over DTAUS and DTAZV recipients.

  2. Conversion of DTAUS payments into SEPA payments

    IBAN rules facilitate a reliable conversion of DTAUS payments into SEPA payments. When you select a DTAUS file in the send dialog and for this the SEPA order type CCT, DTAUS transfers will be converted into SEPA transfers. Also for recurring transfers a conversion from DTAUS to SEPA is possible.

  3. SEPA version 2.7, express payments and COR1 debits

    SEPA payments can now be generated in the schemes pain.001.003.03 and pain.008.003.02 too, which are valid from 4 Apr 2013. To use them these schemes must be set in the bank properties. Beside the new scheme versions the SEPA version 2.7 offers two new payment types, the same-day express transfer (URGP) and the core direct debit with shortened presentation deadline (COR1). For the express transfer there is the new wizard Express transfer (SEPA) under payment recording. COR1 payments can be entered with the help of the wizard Debit (SEPA) if COR1 is selected as the debit type. In order to record these payment types the user needs the permissions for the order types CCU or CD1 respectively.

  4. SEPA messages (pain.002)

    Banks can provide their customers information about rejected SEPA payments and SEPA payment orders in the form of SEPA messages in the pain.002 formats. These messages can be retrieved with BL Banking and displayed in the overview Notifications under the perspective Jobs. Furthermore it is also possible to import these messages directly. If new messages are retrieved or imported, the user is asked if he wants to print these messages.

Account information

  1. Descriptive texts for transaction code and posting key

    The descriptive texts in posting details and pdf print of transactions are now displayed, for instance 020 - Transfer and TRF - Transfer.

Version 1.9.2


  1. Remote Support using the TeamViewer software

    A TeamViewer session is started via the menu item Help - Remote support using Business Logics. This provides the Business Logics team with direct access to the user screen to provide fast and effective assistance with problems.

Payments and sent files

  1. Data entry tools for SEPA payments

    When entering SEPA payments, the associated BIC is automatically determined and entered into the BIC field after entering a German IBAN. The option also exists to enter a German account number and bank code (BLZ) which is then used to automatically determine the IBAN BIC.

  2. Transfer of DTAUS and DTAZV recipients into SEPA payments

    When entering SEPA payments, DTAUS and DTAZV recipients can also be selected from the recipient list if the IBAN and BIC can be determined for these recipients. If this functionality is not desired, it can be deactivated under Preferences - Payment recording - SEPA payments.

  3. Hiding payment details

    The payment details can be hidden during signing of payment orders and EDS orders. This can be set in the preferences with Display payment details under File transfers and EDS. These preferences can only be set by a user with administrator rights. Hence this setting can for example be used to hide details of salary payments from other users.

Account information

  1. Support for account statement information in camt.05x formats

    Account statement information can now also be processed in camt.05x formats. In addition to the already available MT940 and MT942 SWIFT formats, the account overview will also support account statements and notices in the camt.053 and camt.052 formats. The format and retrieval order type for account statements and advices can be set under bank properties. Batched transaction files in camt.054 format are shown under DTI information.

Version 1.8.27


  1. Page numbering in PDF documents

    In PDF documents (e.g. in transmission reports or account statements) there is now a page numbering.

Payments and sent files

  1. Print function for EDS orders

    When signing an EDS order you can now print the order data (similar to when sending a file or signing an open payment).

  2. Payment templates

    In the perspective Payments there is the new view Templates, where payment templates can be created, from which you can generate open payments when needed. (To make this view appear, you might first need to reset the perspective.)

  3. Replacement of the originator account during payment import

    If an unknown originator account is found during payment import, the program suggests to replace this account with a known originator account to allow a successful import of the payments.

  4. Definition of the bank access during payment import

    During payment import users can define an optional bank access from a drop-down list. Thereby you can enforce that the originator accounts of the selected bank access are allocated to the imported payments.

  5. Total amount for open and signed payments

    If more than one payment is marked in the view of the open or signed payments, the total amount of the selected payments is displayed in the row above the overview.

Version 1.8.9


  1. Smartcard support

    ZKA smartcards can be used as a new storage medium for EBICS keys. Existing installations can be converted conveniently from the existing key storage to ZKA smartcards.

Payments and sent files

  1. Amount column for transmitted files

    The overview of the transmitted files now also indicates the total amount of the payments included in the file.

  2. Import and export of recurring payments

    Import of recipients and payers from a recipients.ini file.

  3. Import function for SEPA recipients

    The option now exists to import a list of SEPA recipients. They must be available as a csv file, which includes the columns Name, IBAN, and BIC.

Account information

  1. Display of running balance in the posting overview

    The posting overview has a new column showing the current balance within the account statement.

Version 1.7.28


  1. Deactivating a bank

    A bank can now be (locally) deactivated via the context menu. Communication with this bank is no longer possible after deactivation, e.g. transmission and retrieval orders can no longer be initiated and the deactivated bank is no longer taken into account for batch retrievals (e.g. retrieve account statements). Deactivation is appropriate for instance when the client has canceled his bank access, but wishes to continue accessing his associated account statements. All account statements would be deleted if the bank were deleted.

Payments and sent files

  1. Wildcard for the date in standing orders

    Wildcards that are analyzed with the current date when the payment is created, can be entered for the intended purpose field in standing orders for DTAUS and SEPA payments. Example: The intended purpose entry Rent $ (DATE+1M MMMM yyyy) would be replaced by Rent November 2011 when analyzing for October 2011.

  2. Manual initiation of standing orders

    The context menu can be used to create an outstanding payment directly from a standing order. This does not affect the automatic processing of standing orders.

  3. Information about payments that were created from standing orders

    If new outstanding payments were created from a standing order during application start-up, this information is displayed to the user in the status line.

  4. Detail view for signed payments

    A double click displays the details for signed payments. This opens the same dialog used for open payments, but all fields are now read only.

Version 1.7.18

Payments and sent files

  1. Support for the new SEPA version

    A new SEPA payments page is located under bank properties. This is used for each bank to enter the SEPA version used to create SEPA payment files. By default, SEPA payment files are created in the present format (pain.001.001.02 for transfers and pain.008.001.01 for direct debits), but it is now also possible to convert to the the new SEPA version (pain.001.001.03 and pain.008.001.02)

  2. Search function for payments in transmitted files

    The Transmitted files view now has an option to search for certain payments in selected files or banks. The new Search for payments entry in the context menu is used for this. The amount and/or text can be entered as search criteria.

  3. Filter function for signed payments

    You can now filter for certain payments in the Signed Payments screen. The filter function is started via the new filter icon. The amount and/or text can be entered as filter criteria.

  4. Display of the amount in the EDS summary

    The Electronic distributed signature view now displays the amount and no longer the file size for orders.

Account information

  1. Flagging account statements and DTI files as read

    You now have the option to flag account statements and DTI files as read. This functionality can be activated via the new preferences Display read flag for account statements and Display read flag for DTI files. After an application restart, checkboxes appear to the left of the account statements and DTI files which are used to mark these as read.

Version 1.7.10

Payments and sent files

  1. Changing the execution date for several open payments

    The execution date for several open payments can be changed in a single transaction.

  2. IBAN and BIC addition to accounts from bank profile

    IBAN and BIC are determined dynamically for accounts from the bank profile (htd files) where IBAN and BIC are missing, so that these can be used as record originator accounts when entering SEPA payments.

Account information

  1. Display of account balances, including credit limit

    Account summaries can now display balances including the credit limit. The credit limit can be entered for each account.

  2. Configuration of retrieval order types for account statements and advices

    Order types for retrieving account statements and advices can be entered for each bank. The default order types for this are STA and VMK.

Version 1.7.1


  1. Networking capability

    BL Banking can now also be used as a multiuser version, e.g. several users can work on one installation. This has the advantage that files are stored only in a central location and that all users can access the same data inventory (e.g. the same payments, the same recipient lists, etc.). Other users can be created with the help of the User Wizard.

Payments and sent files

  1. Support for the new SEPA version for data transmission

    SEPA payment files can only be transmitted when they correspond to the new pain.001.001.03 and pain.008.001.02 ISO formats, meaning that the accompanying ticket and payment details are displayed for these new formats as well.

  2. New bank code reference

    A new bank code reference has been integrated which is valid as of March 7, 2011.

Version 1.6.44

Payments and sent files

  1. Entering a reference number for DTAUS payment jobs

    When submitting DTAUS payments, a sequential reference number is issued for each logical file, which is entered into field A10. This facilitates assigning the associated payment job to a (collective) posting from the account statements. This reference number is displayed in the new REF.No./Payment column in the signed payments screen.

Account information

  1. Lazy Loading of older account statements

    Older account statements are only loaded if they are selected by the user. This facilitates a fast display of the overview even if there is a large number of old account statements.

Version 1.6.37

Payments and sent files

  1. Discount function for domestic DTAUS payments

    A discount function is now available when entering domestic DTAUS transfers and domestic DTAUS direct debits. It can be used to calculate the amount minus the discount. This also writes a discount notice into the intended purpose field.

  2. Conversion of DTAUS transfer into Express DTAUS transfers

    A (standard) DTAUS transfer can be converted into an express DTAUS transfer by selecting DTE as the order type in the change dialog. Conversely, an express DTAUS transfer can be converted into a (standard) DTAU transfer by selecting IZV or IZG as order type.

  3. New bank code reference

    A new bank code reference has been integrated, which is valid as of 12/6/2010.

Account information

  1. Supplementing DTI information with account statement information

    If a collective transaction is found in an account statement that matches a DTI file, the value date from the account statement and the date and number of the account statement is displayed with the DTI file transactions.

  2. Displaying sums for account statements

    In the detail view of account statements, now also the sum of debit and credit transactions, the number of debit and credit transactions, as well as the highest and lowest debit and credit transaction are displayed.

Version 1.6.10

Payments and sent files

  1. Administering payer accounts

    The payment screen now includes the account view, which displays record originator accounts. (The screen must be reset so that this perspective appears after an update: reset window - perspective). In addition to the accounts specified by the bank (from HTD files), new payer accounts can be created here, which can then be selected when entering payments. This is important if the bank does not support the optional HTD order type.

Version 1.6.8

Payments and sent files

  1. Entering SEPA direct debits

    Only core direct debits (order type CDD) and B2B direct debits (order type CDB) can be entered and transmitted.

  2. Entering optional fields for SEPA transfers

    When entering SEPA transfers (order type CCT), the optional fields different originator, different recipient, and payment category can now also be selected.

  3. Deleting files after successful transfer

    The Send File transaction now also has a new Delete file after successful transfer checkbox If this box is checked, the selected payment file is deleted after successful transfer.

  4. Printing a summary of the signed payments

    The summary of selected signed payments can now also be printed in table format from the signed payments screen.

Account information

  1. Account statement printouts with display of Total Credit Balance and Total Debit Balance

    Beim Drucken eines Kontoauszugs werden jetzt auch Summe Haben und Summe Soll im Header angezeigt.

Version 1.5.4

Payments and sent files

  1. Manual approval (fax approval) for entered payments

    The order is submitted as a file when the check-mark for Manual Approval (Fax Approval) is set below the accompanying document when signing entered payments. The payment job must then be authorized using an alternate procedure, e.g per fax. Until now, this functionality was only available when submitting completed payment files.

  2. The execution date can be left empty when entering DTAUS payments.

    A DTAUS payment can now be entered without entering an execution date. This optional field is then not entered into the payment file.

  3. Text key when entering DTAUS payments

    The set of selectable text keys for entering DTAUS payments was expanded in accordance with the current specification. Custom text keys can also be entered.

  4. Payment detail tables in the transmission report

    The transmission report for DTAZV payments now also has a payment detail table for each logical file, thus also making the association of payments to logical files visible. The payment detail table of the transmission report for DTAUS payments now again displays all fractional digits.

Version 1.5.0


  1. New bank code reference

    A new bank code reference has been integrated which is valid as of 3/8/2010.

  2. Transmitting log file and EBICS traces

    The menu item Help - Transmit analysis data to Business Logics is used to send the log file directly, i.e. the user no longer needs to navigate in his file system. EBICS traces are also transmitted when these were activated.

  3. Activating EBICS traces

    The Log EBICS Traces checkbox under Preferences - General is used to activate EBICS traces, which are then logged into the workspace/ebicstraces folder.

  4. Marking defective files in the Retrieved Files screen

    If an error occurs in a retrieved file during post-processing (e.g. defective STA file), the file is marked with a warning icon in the Retrieved Files screen. The tool tip displays a detailed error report.

  5. Changes in protocol retrieval

    Updating transmitted files now always results in a from-to retrieval from the oldest transfer date of a file that has no final status (e.g. fully signed) as of today. The menu item Update All has been dropped.

  6. Display of signed and rejected files

    The authorized signatory is now given a list of his already signed/rejected files and can now see information such as sender, signing party, and file checksums.

  7. New status for transmitted files

    File canceled if file was rejected per EDS.

Payments and sent files

  1. Migration to new SEPA version

    In accordance with the new format version 002, the payment entry function now supports SEPA payments with the CCT order type.

  2. Importing payments for an EDS order

    The Import payment function exists in the context menu for an EDS order. It is used to import payments from the EDS order as open payments.

  3. One payment detail table per logical file in transfer report

    The transfer report has a separate payment detail table for each logical file, making the assignment of individual payments to logical files visible.

Account information

  1. Processing and identification of DTI files

    Post processing splits DTI files into logical files. A logical file is marked with date and Ref. No. (Field A10). If this optional Ref. No. is missing, the MD5 hash-value of the logical file takes its place as identification reference.

  2. Tolerant account statement processing

    Post processing of account statements and advices (Mt940 and MT942 files) was made more tolerant, so that account statements with non-standard-compliant specifics of the Volksbank and Sparkasse can be processed error-free.

Version 1.4.0


  1. User manual

    The new menu item Help - Open user manual is used to open the user manual.

  2. Change of key length for key updates

    The length of password and authentication keys can be set to EBICS 2.3. and EBICS 2.4. The length of the signature key can be set to EBICS 2.4 when A005 or A006 was selected as the signature version.

  3. New bank code reference

    A new bank code reference has been integrated, which is valid as of 12/7/2009.

  4. Modifications to support the MacOS X 10.6 operating system

    Modifications were made to support the MacOS X 10.6 operating system, so that the application again starts directly without the user having to make changes to the system settings.

Payments and sent files

  1. Display of payment type in summary of open payments

    The summary of open payments and the summary of standing orders shows a description text for the payment type in the order type column in addition to the order type, e.g. IZV (Transfer), IZV (Direct debit), AZV (International transfer) and AZV (EU Standard transfer). This is helpful, in particular when the order type does not indicate what payment type is used. This permits entering transfers but also direct debits with the order type IZV.

  2. Print function for signatures

    An order can be printed before signing. The signature transaction has a Print button for this purpose. The printout contains the accompanying ticket and the table with the payment details.

Account information

  1. Processing of DTI files and new DTI information screen in the Account statement view

    DTI files that were retrieved by the bank via a DTI retrieval order are split by record originator accounts, and displayed in the DTI information screen. The included transactions are shown in the transaction screen (analogous to MT940 transactions) and can be printed or exported into a CSV format. The transaction filter can also be applied to DTI transactions. It is also possible to import DTI files by selecting the new account statement (DTI) file type while importing account statements. In order to see this new screen also during an update it may be necessary to return to the window Reset screen.

  2. Summation function for amounts from selected transactions

    If several transactions with the same currency are selected in the transaction screen, the total amount of these transaction is displayed in the status line.

  3. Initiating automatic exports manually

    The automatic export can be initiated retroactively for account statements that did not get automatically exported for some reason during the retrieval process. This involves selecting the account statement in the account summary and clicking on the context menu item Initiate automatic exports.

  4. Print option Only print one transaction per page

    The option Only print one transaction per page is now available under Preferences - Account information - Print settings.

Version 1.3.0


  1. EBICS 2.4

    It is possible to create EBICS 2.4 banks with the log version H003 and the available EU versions A004, A005, A006. By changing the log version from H002 toH003, an EBICS 2.3 bank can be converted into an EBICS 2.4 bank.

  2. Saving the last column sorting

    The last column sorting is saved for all tables, so that this sorting is restored after a restart.

Payments and sent files

  1. Importing standing orders

    Payment files can now also be imported directly as standing orders.

  2. Number of executions for standing orders

    As an alternative to the last execution date, the number of executions can be specified for standing orders.

  3. Sorting outstanding payments

    After the creation date, payments are initially sorted by date of the last change (generally the creation date) for which there is no column. The latest payments are then shown at the very bottom. By clicking successively three times on the same column in the outstanding payments screen, the sorting is restored by date.

  4. User setting Transmit payments individually

    Mit Hilfe dieser Benutzervorgabe kann man erreichen, dass beim gleichzeitigen Unterschreiben mehrerer Zahlungen, jede Zahlung als eigener Auftrag an die Bank versendet wird. Hintergrund: Einzelne Zahlungen sollen im Kontoauszug identifizierbar sein und nicht zu Sammelposten zusammengefasst werden.

  5. Reference field is saved with the recipient

    The reference field is now a component of the recipient data and can be entered when creating a recipient.

  6. Copying open payments

    One or several open payments can be copied by using the copy and paste (CTRL-C, CTRL-V) functions.

  7. Saving signed payments as open payments

    The context menu can be used to save one or several payments as open payments.

  8. Printing signed payments

    Signed payments can now be printed. In contrast to open payments, order information is also printed.

  9. Transaction Enter other payments

    After a payment was entered, a dialog opens to determine whether another payment needs to be entered. This presently works only when the entry transaction screen was initiated via the context menu and not via the Action Bar.

  10. Print several payments per page

    Several payments can also be printed on one page by removing the check-mark for the new user preference "Only one payment per page".

Account information

  1. New view Automatic Exports The new view Automatic Exports was added to the Account statement screen. At the same time, the Automatic Export page was removed from the preferences. Several automatic exports can now be set up and used. If unique names are assigned for the automatic exports, the new EXPORTNAME wildcard ensures that each export writes to its own file.
  2. Expanded conversions The existing functionality was expanded as follows to render the standard conversions from other manufacturers.
    1. An empty fiel* can be added and removed.
    2. The following general purpose fields were added: Number of transactions, Total credit balance, Total debit balance.
    3. The following MT94-specific fields were added: Intended purpose field 2nd line to 14th line, payer/recipient 1st line and 2nd line
    4. In addition, the Auszug.txt and Umsatz.txt conversions are created by default when conversions are not yet in place under these names.
  3. Display of Conversion and Automatic export views The preferences have the Display Conversions and Display automatic exports flags, which can be used to show and hide the Conversions and Automatic export views.
  4. Transaction Print new account statements / advices? When new account statements or new advices are retrieved or imported, a new transaction screen opens that determines whether new account statements or new advices need to be printed.
  5. New Record originator / Recipient column in the transaction view The transaction summary now has a new column for Record originator / Recipient.
  6. Limitation of the number of account statements that can be loaded per account The number of account statements that can be loaded per account can be limited by the Max. number of account statements per account user preference. The 5 latest account statements are loaded by default when an account is clicked in the account summary. If an account has several account statements, an Older account statements entry is displayed in the account statement list, which can be used to load all older account statements.

Version 1.2.2

Payments and sent files

  1. Auto-complete when entering the recipient name

Account information

  1. Correct display of Umlauts, including when coded by code page 850
  2. Manual CSV Export
  3. Automatic export with CSV conversion

Version 1.2.1


  1. Interchanging text when encoding / decoding stored files.
  2. Encoded file storage also for payer, recipient, and standing orders.
  3. Export page under preferences no longer too wide.
  4. Date processing for retrieved and transmitted files is now more robust. If the date cannot be read, no date is displayed for the corresponding column.

Payments and sent files

  1. Display name is also transferred from MT940 plug-in for accounts that have account numbers with more than 10 characters and have leading zeros. (Please note that accounts with accounts numbers that have more than 10 significant characters cannot be used in DTAUS)
  2. The currency is NOT modified when another record originator account is selected for an AZV payment (previously, this was always set to the account currency). The following error message is shown when a non-EUR account is selected for the equivalent amount payment: An equivalent amount can only be paid into a EUR amount.
  3. A new ESU payment can now also be saved without having to proceed to the 2nd page (equivalent to EUE and AZV)

Account information

  1. Analysis of the dialog settings for account statement imports
  2. Posting details: Payer/recipient and his account number are now displayed correctly (contents from sub-fields 31 - 33 were previously not shown; bank code was shown as account number (content of sub-field 30)

Version 1.2.0


  1. Encoded storage
  2. Printing with Linux (indicating the print program)

Payments and sent files

  1. Printing open payments
  2. Display names for accounts (from MT940)
  3. Display names for recipients
  4. DTAUS payer (field length is 54 instead of 27)

Account information

  1. Importing account statements
  2. Deleting obsolete advices
  3. Printing advices and scheduled transactions
  4. Printing the bank name (when not determined by bank code (BLZ))
  5. Improved posting details (display of originating and fee amount, different layout for structured and unstructured field 86)