Submit payments

Under "Submit payments", you can transfer manually created payment orders to the bank.

Selection of files

In the upper table, the payment orders are grouped by payment type and ordering party account. You can select one or more groups of payment orders that you would like to transfer. You will then find the individual payments from the group listed in the lower table. If you do not select a group, clicking on Transfer will automatically transfer all outstanding payment orders.

If you have selected one or more groups of payment orders above, you can select the individual payments you wish to transfer in the table below. Then click on Transfer in the toolbar of the bottom table to initiate the transfer.

If you click on the Transfer button in the bottom table without selecting a single payment, all files from the bottom table are transferred at once.

Filtering payments by date

The date filter button in the toolbar narrows both lists on the page – the group list and the list of single payments – to the payments of a date range. Without a filter, the button shows All payments.

A click on Submit without a selection, or after selecting all payments, submits only the payments in the chosen range. Payments that were selected individually stay selected, even if a range chosen afterwards hides them, and are submitted as well.

Choosing the range

The range is set with a slider from overdue through today to 14 days ahead and later. Both ends are open: overdue covers all overdue payments, later all payments after day 14.

While the range is being set, the filter shows the number and total of the payments in the range and how many overdue payments it hides. The total adds up the amounts regardless of their currency. If the range contains overdue payments, the filter points out that they get the next possible execution date when submitted. The lists change only with a click on Apply; Reset selects the whole range.

The button names the range relative to the current day, for example “overdue – today” or “today – 10/30”; the heading of the filter also shows today’s date. The range is saved per user and applied relative to the current day on the next visit. The date of the konfipay server is decisive.

If the range extends to later, the filter points out that banks may reject payments dated far in the future: direct debits may be submitted no earlier than 14 calendar days before the due date, and scheduled credit transfers are subject to the limit of the respective bank.

While the filter hides payments, a hint such as “120 of 5000 payments” appears next to the button. A warning icon indicates that overdue payments are among the hidden ones. A click on the hint opens the filter; the cross next to it removes the filter.

Latest submission or Execution/Due

When the list contains direct debits, the range can refer to:

If the list contains no direct debits, the choice is not shown.

Overdue payments

A payment is overdue if its date lies in the past or – for direct debits – the lead time of one business day can no longer be met. konfipay moves overdue payments to the next possible execution date on submission. A date on a weekend or TARGET2 holiday is also moved to the next business day, but does not count as overdue.

• Overdue payments are shown in red; the tooltip names the date the payment gets on submission.

• Payments whose latest submission is today are shown in bold.

• The highlighting applies to open payments only, not to files already submitted.

Group list: one row per execution date

The group list shows one row per ordering account, payment type, purpose code, currency and execution date – the way the files reach the bank. Overdue payments appear in the row of the date they get on submission; the row is then shown in red, and its tooltip names the number of overdue payments and the date of the file. If the stored dates of a row differ for another reason, for example a date on a weekend, the tooltip names the stored date.

The count and total of a row always match the payments listed when the row is selected – also with a date filter, a search or a column filter. The submit window shows the execution date per group as well.

Execution/Due column

In the list of single payments, Execution/Due is the first column; the column Latest submission can be shown in addition. In the group list the column follows the IBAN.

Configure transmission

After you have selected the payments to be transferred and clicked on Transfer, you can configure a few more details for the transfer in the transfer window:

Individual or batch booking

In the bottom left at Booking as... you can specify whether the payments are to be transferred individually or as a batch booking. Batch bookings serve to simplify electronic payment transactions. All individual payments that match (same payment method and client account) are combined into one batch booking.

Batch bookings appear bundled as one item on the account statement, the individual payments are not shown. By default, payments are transferred as batch bookings. The use of batch bookings offers several advantages, such as potential savings on fees, the bundling of sensitive individual payments (e.g., in the area of wages and salaries), and the clarity of account statements even with large amounts of data.

The execution of payment orders as individual payments generally requires an agreement with the bank. Without this agreement, the bank will generally ignore this information and automatically book the payment orders as batch bookings.

Configure verification of payee

At the bottom left of the transfer window, under Configure Verification of Payee (VOP) settings, you can check a box to manually configure settings for Verification of Payee (VOP) for this payment.

Select whether you want to perform recipient verification for this payment by checking the box next to Verification of Payee (if this is a single payment/individual booking, check the box next to Verification of Payee for single payments).

For documentation purposes, the payment overview shows for each payment whether it was transferred with or without payee verification and which user set this setting.

You can view the result of the recipient verification by calling up open VEU orders in konfipaySign. Payments that are transferred with recipient verification may require further verification before they can be executed. If a recipient name only partially matches (“close match”), you must still authorize this payment manually using konfipaySign before it can be executed.

Carry out transfer

Once you have made all the settings, you can transfer the payments to the bank by clicking on Transfer payments.

Alternatively, you can just create an output file instead of transferring it to the bank. To do this, click on the arrow next to Transfer payments and select Generate output files. In the process, konfipay creates a payment file as it would be sent to the bank - you can then download this file and save it locally on your PC.

Select transmission path

If several EBICS contacts for manual payment transfer are assigned to the ordering party account (see bank account management of EBICS contacts), in the next step you may have to select which transmission path (EBICS or SRZ) and which EBICS contact you would like to use for the transfer.

When transferring multiple batch payments, you can check the box labeled Automatically apply selection to subsequent payment groups at the bottom. This way, you won't have to configure the transfer route separately for each batch, and you can avoid having to enter the same EBICS key password multiple times.

Several criteria must be met for EBICS to be available here as a transmission channel:

• The EBICS contacts must be fully initialized before they are available for selection for transmission

• The user must have access to the EBICS keys of the contacts linked to the client account

Enter EBICS password

Depending on the configuration of the EBICS key of the selected EBICS contact, you may have to enter the EBICS password manually for each transfer. Check the automation settings of the corresponding EBICS contactif you want to change this setting.

Following finished transfer

Once the transfer of payment files is complete, you will see an overview of the transfer progress. Successfully transferred payments are displayed in green, failed payments in red, and payments with an unclear transfer status in orange. Click View Payments to see the details of a group's payments.

Payment transfer via FinTS/XS2A

If a bank account is connected via FinTS/XS2A, the transfer is not authorized using an EBICS key and EBICS password, but rather through your bank’s finAPI Web Form 2.0. To do this, konfipay opens the “Log In to Your Bank” window; the login and strong customer authentication (e.g., via PIN/TAN) take place directly with your bank.

In the transfer dialog, the bank details and the FinTS/XS2A banking interface are merely displayed (read-only) and cannot be changed.

If a FinTS payment is already pending authorization for an account, konfipay will ask whether this transaction should be continued.

Verification of Payee, (or VOP for short) is always enabled as an opt-in feature for FinTS/XS2A.

Tags

You can use tags to specifically label and better organize data in konfipay. To edit the tags for a payment, select that payment in the payment overview and click on Tags in the toolbar. You can then add or remove tags. Click Save to apply your changes.

To create a new tag, click the plus icon next to Tags.

If you want to add or edit tags for multiple payments at once, please proceed as follows: Select those payments in the payment overview and click Tags in the toolbar. Then choose which action you want to perform for the tags selected below:

• Set – the tags are applied to all selected payments. Any existing tags will be overwritten. Please note: If you click Save here without selecting a tag, all tags will be removed from the selected payments.

• Add – the selected tags are added to all selected payments, provided they do not already exist.

• Remove – the selected tags will be removed from all selected payments, if they are present.

To remove all tags from a payment, select Set as the action and do not select any tags. When you then click Save, all tags will be removed from the selected payments.

Troubleshooting & configuration

If you are expecting transaction files, but no new transaction files can be retrieved in konfipay, the bank may have changed the configuration. The same applies if you want to transfer payments but the transfer to the bank fails. Under Master data > EBICS you can view the configuration for retrieval or transfer of files for this EBICS contact and adjust it if necessary. You can find more information on the configuration for an EBICS 2.5 or an EBICS 3.0 contact under the links.