Direct Banking
Technical release notes 2025
Banks are preparing for the new PSD3 features . One of the new features is the validation of the Payee Name. When you are exporting with the Payment Journal you can encounter issues. This is caused by the business central export preparation. The proposal will use the vendor name instead of the account holder name of the vendor bank account card.
Version | Release Date |
|---|---|
27.0.5.0 | 27-11-2025 |
The following improvements have been implemented |
In some cases the direct banking extensions did not update correct to the latest version. This is fixed in this release. Please check after the update if the Direct banking setup is in the correct Localization and if the Client en Secret ID fields have a value. Re-enter or change if needed. |
Version | Release Date |
|---|---|
25.6.3940.0 | 31-07-2025 |
The following issues have been resolved: |
There was an issue with the visibility of the Cobase False Batch flag in the direct banking account |
Version | Release Date |
|---|---|
25.6.3929.0 | 29-06-2025 |
The following improvements have been implemented: |
For the Cobase solution it’s now possible to export a batch which is flagged false. You can manage this setting in the specific direct banking account |
For the Cobase solution some international banks require additional bank information. The tags are now included in the export file. |
For the Cobase solution it’s now possible to export payments in different currencies in the NL and W1. (depending on your settings and requirements) |
The following issues have been resolved: |
There was an issue with re-processing posted and archived transactions. This is no longer allowed. |
Cobase Status Update of exported transactions is updated |
Version | Release Date |
|---|---|
24.6.3856.0 | 29-05-2025 |
The following issues have been resolved: |
There was an issue with the creation of the bank account from the bank/giro journal and the payment application journal |
Version | Release Date |
|---|---|
24.6.3645.0 | 27-03-2025 |
The following improvements have been implemented: |
|---|
For the Cobase Single Entity solution the Bank Accounts are now initially inserted in the staging tables. As a result only the relevant Direct Bank Accounts are shown, also in the company where the transactions are imported. Mapping of Direct Banking Accounts in this company now works in the same way as for the other companies. For more information see this topic. |
For Cobase and the Dutch Localization a new option “default” has been added to the “Execution Date Payments” field on the bank account. This new default value will not change the dates in the proposal, because Cobase supports execution dates in the future. This is only applicable to batch payments. |
The following issues have been resolved: |
The transactions imported from Cobase are now shown in the same sequence as they are presented on the Cobase portal. |
Bank Accounts with Non-IBAN bank account numbers are now correctly imported from Cobase. |
There was an issue with the reconciliation when matching with text to account and dimensions. |
In the Dutch Localization the Document No. in the Bank/Giro Journal skipped a number from the Number Series. |