Release Notes - Version 4.10

AppSource Release Date: 07.11.2023

Fixes

BNKP-56 BIC/SWIFT should not be mandatory in SEPA Credit Transfer

The requirement to have the Recipient SWIFT Code (BIC) filled in the payment lines in SEPA payments has now been removed.

Note. For payments to recipients outside Finland, the recommendation is to have as complete information about the recipient as possible filled in the Vendor Card or Customer Card, including the Recipient SWIFT Code on the relevant Bank Account Cards. There are bank-specific differences in how banks handle payments to recipients outside Finland. A missing Recipient SWIFT Code (BIC) may result in the payment being rejected or additional costs being charged.

BNKP-307 Payment - payment discount not handled correctly on the payment line

This fix addresses the issue where payment discounts were not being included on the payment line when using the Suggest Vendor Payments feature.

Payment Discount. The change means that when the payment date is before or on the same day as the last possible payment discount date, the discounted amount will be added to the payment line. When posting, the payment is posted according to the rules set up.
Payment Discount Tolerance. If a payment discount tolerance has been set up and the payment date falls within that time frame, the full amount will be shown in the payment line. If posting with the full amount, both vendor ledger entries will be closed, and the Payment Discount will be discarded. If the Payment Discount amount is subtracted from the amount before posting the payment, both vendor ledger entries are also closed, and the Payment Discount is taken into account and posted according to the settings set up in BC.

Payment Discount, and possibly it's Tolerance settings (if used), is handled in the same way as if you would post it using a standard BC payment journal and should render the same results.

BNKP-308 Payment - transfer between customer´s bank accounts handled incorrectly (OP)

The fix affects payments made within the company where the user selects Recipient Type Internal Bank Account and the receiving account is in OP. Previously, these payments were given the category purpose code “INTC”, which affected how the payments were written to the bank statements. From this version onwards, these payments no longer receive the category purpose code “INTC”.

BNKP-335 IBAN, SWIFT and BBAN should be editable in Payment subform

If an incorrect Recipient IBAN, Recipient BBAN or Recipient SWIFT Code is filled in on the Vendor Bank Account Card or on the Customer Bank Account Card, the information can be corrected in the payment lines. The corrected information is included in the payment file, but the information needs to be corrected separately in the relevant Bank Account card.

BNKP-340 Bank Communication - when selecting and downloading multiple files in the Download To File page, only the first file is imported

This fix addresses the issue where a user in the Bank communication, Download To File function, selected multiple files but only one file was downloaded.

BNKP-343 Danske Bank - certificate renewal error

The fix addresses a problem that could occur when Danske Bank's certificates were to be renewed. The problem did not affect Web Services communication with Danske Bank in general.

New Features

BNKP-125 Extended Remittance Info (ERI) support

With the support of the payment standard pain.001 version 3 (pain.001.001.03), it will be possible to bundle more payments into a single payment. When the recipient of the payment, payment date, currency code and recipient's address details are the same in several payments, the payments are bundled into a single payment. In total, 999 payments and/or credit invoices can be bundled into one payment.

Note. To use this function, the payment standard pain.001 version 3 (pain.001.001.03) needs to be activated on the Bank card.
Good to know. The user does not have to take any action for the payments to be bundled; they are automatically bundled when the right criteria are met. If the payment standard is not changed on the Bank card, the payments will be bundled as before and a total of 9 payments, including at least one credit invoice, can be bundled into one payment. Note that the recipient, payment date, currency code and recipient's address details must be the same in all payments (credit invoices) for the payments to be bundled into one payment.

BNKP-221 Additional information for currency payments

As of this release, it is possible to create currency payments with recipient type External Bank Account. It will now be possible to fill in, among other things, the recipient's address information, information relating to the recipient's bank, such as Recipient Bank Clearing Code, Recipient Bank Clearing Standard and the recipient bank's address information.

Note. Our recommendation is to fill in as complete information as possible about the recipient of the payment on the Vendor Card or Customer Card. The information is then automatically displayed in the payment line when the vendor or customer is selected.

BNKP-339 Move Real Time Statements to their own tables

A new table has been implemented for the Bank Real Time Statements and we have also made some minor improvements.

BNKP-341 Add Feature Usage telemetry

Internal improvement.

BNKP-358 Material types - pain.001.001.02 and pain.001.001.03 - update the bank specific list

Some banks use different material type codes depending on the format in which the payments are created (pain.001.001.02 or pain.001.001.03). This also affects the material type code with which the payment status reports are retrieved from the bank. Banks affected by this are Danske Bank and OP.

Important. If the receiving bank is either Danske Bank or OP and you want to activate the new payment standard pain.001 version 3 (pain.001.001.03), permissions need to be added to the material types “pain.001.001.03” (“Upload”) and “pain.002.001.03” (“Download”) for all Bank Pro users who shall be able to send payments and download their payment status reports.

BNKP-152 Payment - show BBAN account number in payment lines

A new field "Recipient BBAN" has been added to the payment lines, in which the BBAN account number is automatically displayed if it is filled in the Vendor Bank Account Card or Customer Bank Account Card. The recipient BBAN can also be filled in for manual payments.

BNKP-180 Payment - add field for display of invoice due date

A new field "Due Date" has been added to the payment lines, showing the due date of the purchase invoice.

BNKP-181 Support for SEPA version 3 (pain.001.001.03) and SEPA payment status reports (pain.002.001.03)

With this release, it will be possible to create payments in the pain.001 version 3 payment standard (pain.001.001.03). The payment standard is changed on the Bank card of the bank concerned.

Note. If the bank to which the payments are sent is either Danske bank or OP, permissions for new material types need to be added for all Bank Pro users who shall be able to send payments in the new payment standard and retrieve their payment status reports.
Good to know. When the payment standard is changed on the Bank card, the Payment Status version is also automatically updated.

BNKP-201 Download To File - show notification message when there are no files to retrieve

Previously, no notification message was displayed if a Bank Pro user downloaded a list of materials, such as bank statements, via the Bank Communication, Download to File function and there were no materials to download. From this version onwards, a notification message is displayed to clarify in these cases that there are no materials to retrieve according to the specified criteria.

BNKP-292 Bank Statement transactions - display transactions from all bank statements on new page

Based on customer feedback, there is now a new page where transactions from all bank statements are displayed as separate transactions. The transactions are listed in the order in which they were downloaded from the bank and are sorted by bank statement, main transaction, and sub-transaction.

BNKP-387 Payment - change the default position of the Currency Code field

The default position of the Currency Code field has been changed to appear before the Amount and Amount (LCY) fields in the payment lines. When registering manual payments, this enables the correct EUR amount to be displayed immediately in the Amount (LCY) field after the user has entered the currency code and the currency amount.

BNKP-261 Enable the choice of who (debtor, creditor or shared) bears the charges

As of this release, it will be possible for Bank Pro users to choose which party bears the costs in currency payments. Options to choose from are “Shared”, “Debtor” or “Creditor”