| Version |
Release Date |
|---|
| 22.4.1961.0 |
30-05-2023 |
| The following issues have been resolved: |
|---|
Not all banks provide remittance information for bulk payments, but it was required for invoice matching.
A temporary fix has been implemented to also match these transactions.
As soon as Ponto allows it, a more permanent fix will be implemented. |
The performance of finding accounts using the transaction information has been improved.
For customers that have lots of accounts, it is possible to skip the time consuming parts of account information matching. |
| An error occurred when signing payments with Cobase. |
| When payments are exported using SEPA files in the Dutch localization, then it could happen that transactions for vendors and customer were mixed up. |
| Version |
Release Date |
|---|
| v. 22.4.1878.0 |
18-04-2023 |
| The following issues have been resolved: |
|---|
| In the Dutch and Belgium localization there was an issue with applying documents via the Bank/Giro Journal (NL) and the Financial Journal (BE). |
| Version |
Release Date |
|---|
| v. 22.4.1831.0 |
11-04-2023 |
| The following issues have been resolved: |
|---|
| For some banks the initiated bulk payments were not recognized during invoice matches in the Dutch localization. |
| The Identification that is set in the payment journal for invoice matching was not set correctly in all circumstances. |
| Translation improvements in the Dutch localization. |
| Version |
Release Date |
|---|
| v. 21.4.1666.0 |
06-03-2023 |
| The following issues have been resolved: |
|---|
| inaccurate matching on accounts. |
| Version |
Release Date |
|---|
| v. 21.4.1641.0 |
01-03-2023 |
| The following improvements have been implemented: |
|---|
| Direct banking integration with the W1 reconciliation and W1 payment journals is available |
| Improvement of the matching engine for enhanced reconciliation |
| Matching result and confidence better explained with extended logging |
| Priority setting on Text to g/l account mapping |
| Text to g/l account mapping option to stop remittance info matching if certain text is found, only suggest the customer/vendor account |
| Debugging is allowed from BC19 and higher versions |
*In the BC17 versions we unfortunately have a breaking change in the GetAccountTypesFound procedure of the “BCB Session” codeunit.
Therefore a Forcesync is required when upgrading runtime packages to 17.4.1641.0.
| The following issues have been resolved: |
|---|
| Description in the bank/giro journal not updated when remittance matching on description field of the bank transaction instead of the remittance info (Mollie). |
| Isolated storage improvements |
| Skip VAT check BE Enterprise |
| Payment history card cancel improvements |
Release Direct Banking xx.4.1083.0 (October 2022)
- Some banks seem to use the Duplicate End-to-End id in a improper manner.
It is now possible to disable the checks on duplicate End-to-End id’s on the account card
- The setup wizard now keeps into account that users might not have the proper permissions to create job queue entries.
*When upgrading to version xx.2.3.1, Ponto credentials have to be re-entered on the Direct Banking Setup card. Not re-entering this information will cause an error during importing transactions, exporting payments or syncing bank accounts.
*When upgrading the base app (Direct Banking) from and older version to xx.2.3.2 or newer, you will need to do a manual transaction import (for each account). You will be prompted to choose a from date. Select the latest date possible, making sure there is still an small overlap with the latest already imported transactions. This a one time manual action.
For example: Your last transaction import before the upgrade was done on April 7th 2021. You are upgrading the app on April 8th. To make sure there will not be a gap in your transactions, select the “First Day Current Week” option (= April 5th). Transactions will never be imported twice.
Note that when no transactions were imported during this manual import action, you will need to perform this action manually again once there are transactions available for import.
Release Direct Banking xx.4.960.0 (September 2022)
- The Bulk Payments functionality has been improved in the Belgium version, the matching of payments has been improved.
- From BC17 and onward we have implemented a new app where Direct Banking is dependent on.
This app contains base functionality for Idyn.
This is also referred to as a library app.
For On-Prem installations the new app must be added to the licenses.
When upgrading to this new version, please ensure that you refresh your development – and customer licenses.
Release Direct Banking xx.3.100100.0 / Direct Banking NL xx.3.100100.0 (July 2021)
- Added Bulk Payment (Both W1 and NL)
- Added Regex patterns to clean up Remittance Information (Both W1 and NL)
- Use Execution Date in Reconciliation, instead of Value Date (Both W1 and NL)
- Improvements in general performance of import actions
- Added line comment options to CBG Statement Lines (Bank/Giro Journal – NL)
- Fixed Job Queue error on blocked customer (NL)
- Correct order of transactions, imported from Ponto
Release Direct Banking xx.3.100125.0 / Direct Banking NL xx.3.100120.0 (February 2022)
- Resolved an issue with clearing the preferred Bank Account Code or the G-Account Code.
- Improved Dutch translations.
