Change log 1.46.0
Release Date: 07.11.2024
DB Version: 1.46.0.0
New features
- Balance matching with ID:
Transaction match rules can now be configured to match by a balance (n:m) instead of just matching one ECR transaction to one EFT transaction (1:1). For these new types of matches a rule must contain a match ID (authorization code, order ID, transaction sequence counter or transaction reference). Additionally an OU can be defined to ensure all transactions of a match belong to the same organizational unit. - Outstanding receivables:
The open item list view has been redesigned and can be found under Accounting > Receivables > Outstanding receivables. The old list of open items is still available under Accounting > Receivables > Open items. - The transaction classifier is now also able to detect reversals for EFT transactions.
Enhancements
Website
- Collector directories can now be selected as source when configuring an upload configuration. This means that files can be uploaded to another location directly after being collected by the ReconHub.
- An export sequence number has been added to posting exports. This sequential number is unique for each posting export of a posting export rule. A unique export ID has been added to posting exports. The format of this field can be defined on the new field unique export ID format on the posting export rule. The resulting unique export ID must be unique within all exports of a posting export rule. It is also shown on the posting document.
- The date range picker for new views (analytics, transaction matching) now provides actions to navigate to the previous/next period
- On the job execution detail view a possible error message is displayed separately from the stack trace. The stack trace will only be visible to users with the Development role.
Modules
- The HTTP collector module can use client certificates and is able to check server certificates now
Processing
- The settlement matching has been extended to prevent matches without any transactions or adjustments. This was possible when the sum of the amounts of all bank payments of a match was zero and no transactions or adjustments were found for that candidate. Important: This is a breaking change and can lead to bank payments not being matched anymore if the above conditions are met.
Bug fixes
Website
- Fixed a bug which sometimes occured when a user displayed the old organizatonal tree before navigating to views of new modules
- Fixed a bug which prevented posting rules for EBIS exports to be saved
Processing
- Fixed a bug in the posting export processing which override the configuration of a posting export rule when a rule was changed by a user during the processing
Related Articles
Change log 1.33.0
Release Date: 31.05.2023 DB Version: 1.33.0.0 Enhancements Website The look of the application has been updated When creating a tenant, it is now possible to select from a default set of custom fields to be available for the tenant When creating a ...Change log 1.33.1
Release Date: 08.06.2023 DB Version: 1.33.0.0 Enhancements Modules The generic export module now supports json format Bug fixes Website Two default currency filters were incorrectly added to the posting rule, when the accounts of the posting rule ...Change log 1.50.0
Release Date: 22.05.2025 DB Version: 1.50.0.0 New features Settlement matching overview: Introduced a new settlement matching overview to provide a comprehensive view of the settlement matching process. This overview includes the following features: ...Change log 1.41.0
Release Date: 11.04.2024 DB Version: 1.41.0.0 Enhancements Website The transaction match rule edit view has been redesigned The default filters are now displayed again in the detail view of a transaction match rule The payment processors and brands ...Change log 1.34.0
Release Date: 12.07.2023 DB Version: 1.34.0.0 Enhancements Website Introduction of Data Analytics For missing terminals which were detected when importing transactions, there is now a list of proposed terminals to simplify the creation of the missing ...