Payment Processing and Management

Various options are available for entering payments, such as manual entry, online submission via EBICS or import from the booking system

The following checks are carried out during import depending on the format supplied: Format checks, check digit calculation for account number and IBAN, check of bank code and BIC for existence, check of valid text keys, blocking. If the check is negative, an automatic return can take place depending on the configuration.

The documents (deposit/withdrawal slips, bank and postal cheque office statements, bills of exchange and cheque copy books) are compared with the entries made in the accounts.

The revision requirements for 4- or 6-eye control are fulfilled. All activities are logged and archived at individual transaction level.

Customer bookings that fulfil a certain criterion can be held up in this workflow step. As long as the customer booking has not been released, the associated recipient bookings will not be processed any further.

The routing can be determined taking into account various criteria, e.g. booking system, amount, account number or IBAN of the payee/payer, bank sort code or BIC of the payee/payer, text key.

Output interfaces are available for the customer, core banking system, clearing system (Bundesbank and EBA), correspondent banks and archive

The following formats are supported here, for example: SEPA formats (pacs and pain), DTAUS format, DTAZV format, various “DTA dialects”, SWIFT formats (MT103 and MT202 or MT202 COV), CSV format, proprietary formats (POF, WINGS etc.), BAPI.

If authorised for revision purposes, individual work steps can also be carried out automatically.

The processed payment orders are archived in the payment archive. A search function in the short-term archive allows you to view the payment transaction history within a defined period. For long-term archiving, the data is stored in the long-term archive.

Checks can be carried out based on predefined criteria (e.g. recipient or sender country), e.g:

• Check against EU embargo name list
• Check against US embargo name list
• Check against customer-specific embargo name list
• Check based on the country list
• Checking the completeness of the client data
• Recipient account number comparison

In the event of an anomaly, a corresponding workflow is provided to ensure that the payments are only authorised after approval by the compliance employee (if necessary, taking into account the 4-eyes principle).

Bank identification codes or BICs of banks can be stored to which payments may only be forwarded after manual authorisation.

Continuous order management is available for payments in DTAUS and DTAZV formats.

As part of the daily closing, the processed payments are transferred to the archive. Starting from a transaction, all revision-relevant information is archived (details of which employees have processed these files, details of changes, etc.)

In addition to the details of individual transactions, the input and output files are also archived. In the case of complex payment orders (AZV), all relevant payment items are archived and can be searched.

The archive forms the basis for extensive reports, such as the ZV-statistics.

As part of ISE processing, it is possible to perform matching between the clearing records (DTA) and the incoming and outgoing images.

Customer-specific requirements, such as purpose analysis to determine the account number and house bank procedure (fee correction for ATM orders) can be provided.