Change log 1.49.0

Release Date: 10.04.2025

DB Version: 1.49.0.0

New features

In-app notifications:
ReconHub now features a sidebar to notify users about specific events. Notifications appear in the sidebar and can be marked as read or unread by the user. Certain notifications can also be displayed as a banner at the top of the page. Users can subscribe to in-app notifications for the following events:

If no selection start and end have been defined for a posting export, no data is now displayed instead of 01.01.1753 resp. 31.12.9999
Exact transaction matching keys of tolerant transaction match rules will not be displayed in the matching analysis container on unmatched transactions anymore
The organizational unit tree can now be expanded and collapsed in the outstanding receivables views
After manually resetting a transaction the user will now be redirected to the EFT transaction if available, otherwise to the ECR transaction
All structured lists now have a sticky header

Added a new placeholder Yesterday to the Ledger generic export module
In the Ledger generic export module source fields can now be used that are ignored when writing the file. This can be used, for example, to ensure that entire records are not written to the file under certain conditions.
Added retries of 15 minutes with a maximum of 3 retries and an interval factor of 2 to the EFT Stripe collector and EFT UberEats collector in case of an unexpected error

An offset can now be configured for date match keys of settlement match rules
For balance matches, the business date of the transactions on the ECR side is now taken over to the transactions on the EFT side, if the business date is unique
Removed parallelism from posting reprocessing for a better user experience. The mass manual posting of bank payments or the application of posting rule templates led to failing scheduler executions due to too many posting reprocessings being triggered in parallel.
Reduced the count of data warehouse processings in order to improve performance
The computation of business dates has been improved to also cover the use case where a transaction, that takes place after a certain threshold time, is included in the following day:

If threshold time defined on the organizational unit is before or equal to 12pm: The business date of transactions before the threshold time is set to the day before
If threshold time defined on the organizational unit is after 12pm: The business date of transactions after or equal to the threshold time is set to the day after

The Job system cleanup job now reads its parameters from the app settings instead of its arguments
A monitoring configuration can now be configured to include detailed scheduler errors in its status email

Fixed a bug that prevented creating new users with a plus sign in their email addresses (cloud-only)
Ensured that queries without currency filter are not executed in the outstanding receivables by transaction view
Fixed a bug where the OU tree in the Bluemoon OU sidebar was not ordered correctly
Fixed a bug that caused manual skipping of transactions to fail, if the state of a transaction changed during the skipping
Amounts in the filters of ECR transaction, EFT transaction and transaction list views are now limited to int min/max values (-2147483648 to 2147483647) to prevent conversion errors
Fixed a bug where some filters got lost when navigating in outstanding receivables views
Fixed a bug where the bank payment processing config on bank payments was not reset when resetting the settlement matching of a bank payment
Fixed the links from the matching overviews to include the settlement match state N/A for matched transactions so balance matched ECR transactions are also listed
Ensured that values of column filters are displayed correctly in the transaction match rule views
Fixed a bug that prevented entering values for a date range column filter in the transaction match rule edit view
Fixed a bug where EFT RAF Collector job triggers had their start time set to 00:00:00 if their start date was overwritten by their merchant range identifier

Fixed a bug in the Bank BAI import module where records could not be imported, if they had an unexpected number of optional columns
Fixed a bug in the Email upload module where splitting multiple recipients from an upload configuration failed
Fixed a bug in the Generic import module that made it impossible to map empty values to a brand or payment processor

Fixed a bug when creating match rule delegates where empty strings and white space strings where not correctly recognized by Is empty and Is not empty operators

The design of emails sent by ReconHub has been updated

Related Articles
Change log 1.42.0
Release Date: 23.05.2024 DB Version: 1.42.0.0 New features Exception list view showing all unmatched transactions Simplified one-to-one matching of transactions Balance matching, with which several ECR transactions can be matched with several EFT ...
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 ...
Change log 1.48.0
Release Date: 27.02.2025 DB Version: 1.48.0.0 New features Outstanding receivables: The outstanding receivables now contain the following views: By payment processor: Shows the outstanding receivables grouped by payment processor and optionally by ...
Change log 1.47.0
Release Date: 19.12.2024 DB Version: 1.47.0.0 Enhancements Website New roles for manual corrections are introduced. All of these roles are subroles of the role Manual corrections but can be assigned separately: Manual transaction matching: Users with ...
Change log 1.45.0
Release Date: 26.09.2024 DB Version: 1.45.0.0 New features A new detail view for transaction matches was introduced Enhancements Website The net and gross settlement amounts have been added to the open item list view and report. In the report, these ...