Release 1.40.0

Release Date: 27.02.2024 8pm - 11pm (UTC+1)

In version 1.40.0 of ReconHub, our primary focus has been to continue enhancing the matching experience. We've implemented several improvements of the transaction match rule configuration and some other changes that make your workflow smoother. Dive into the details below to explore the latest enhancements designed to elevate your experience.

Exact and Tolerant Transaction Match Rules

In the previous release, we introduced separation between exact and tolerant Transaction Match Rules. This was a first step towards our goal to increase matching efficiency and transparency, while still preserving the existing flexibility of tolerant matching.
With this update, we take the next step towards this goal, focusing on enhanced clarity around how transactions are matched and how data quality impacts your reconciliation.

Refresher: A Closer Look at Exact and Tolerant Rules

Here is a quick refresher, if you have not yet made yourself familiar with Exact and Tolerant Rules:

• Exact Rules
  These rules embody precision, leading to a singular, pinpoint match. Ideal for scenarios where unambiguous matching is possible, Exact Rules have no tolerances and do not support multi-matches.
  The result? A match is a match, unequivocally.
• Tolerant Rules
  The rules as they were always used in ReconHub. These rules accommodate for tolerances and support multi-matches. Perfect for lower quality data or scenarios lacking unique matching elements.
  Our multi-match feature continues to select the optimal match as best as possible, as it always has.

During matching, ReconHub will prioritize Exact Rules, followed by Tolerant Rules. This prioritization strategy streamlines the process, minimizing tolerance-dependent matches and increasing overall efficiency. Rule priorities remain, but with a twist: they're now assessed separately during Exact and Tolerant matching, ensuring a more organized and efficient workflow.

A Simpler View for Separated Exact and Tolerant Rules

We have now added a switcher to conveniently switch between exact and tolerant rules. This enhancement allows you to easily view and manage the rules separately.

Payment Processor View

Additionally, we have extended this feature to the Payment Processor page, offering the same view for matching rules. By consolidating all payment processor's rules in one place and organizing them by type, we have made it even more efficient for you to manage and maintain your rules.

Same Minute Matching Exact Match Rules

In some occasions, payment terminals and sales systems do not share the exact same time. This makes it hard to use the transaction time as a match key, even though an exact match would otherwise be possible.
Therefore, we are introducing an option on Exact Transaction Match Rules that allows matching a date by the minute, ignoring the seconds. In contrast to a tolerance, this option does simply change the resolution of time used for the matching, is very simple to configure and still allows a highly efficient matching algorithm under the hood. If you need more tolerance, want to add or subtract some time value, or allow multi-matching, please use a tolerant rule instead.

Merchant Number For Bank Payments

Some payment processors do provide the corresponding Merchant Number for their bank payments. This merchant number is then part of the bank statements that ReconHub ingests.

With this release, we are introducing the capability to filter bank payments based on their merchant number. This makes it easier to find payments for a certain merchant number.

Business Date for EFT Transactions

We have resolved an issue of mismatched dates between ECR and EFT transactions, due to the business day threshold time configuration. In some cases, this lead to the setting of the wrong business day for EFT transactions.

With this update we make it possible to provide the business date for EFT transactions during the data import. This makes it possible to set the business date according to the transaction source.

This granular control enables smoother reconciliation processes, as transactions align seamlessly based on the defined date, streamlining workflows and reducing potential errors.

Change Logs

See all change logs for this release.

• Related Articles

• Release 1.32.0

  Release Date: 18.04.2023 With ReconHub version 1.32.0 we release updates to different areas. The most significant changes are described in detail below. Standard filters for simplified rule creation To simplify the creation of rules, default filters ...

• Release 1.43.0

  Release Date: 08.07.2024 8pm - 11pm (UTC+2) Introducing Version 1.43.0 of ReconHub! This release brings a notable change to ledger accounts: the ability to add multiple currencies to a single account. Explore this update to enhance your transaction ...

• Release 1.35.0

  Release Date: 21.08.2023 8pm - 11pm (UTC+2) With ReconHub version 1.35.0 we release updates to different areas. The most significant changes are described in detail below. Improved Navigation & Workflow on ReconHub To enhance your ReconHub ...

• Release 1.41.0

  Release Date: 11.04.2024 8pm - 11pm (UTC+2) Introducing Version 1.41.0 of ReconHub! With this release, we are introducing HeuRekon, our AI assistant, available to support you whenever questions arise. We have also added support for more data feeds ...

• Release 1.31.0

  Release Date: 09.03.2023 With ReconHub version 1.31.0 we release updates to different areas. The most significant changes are described in detail below. Optimisations & new functions New Sales API with online developer help With this release, a new ...