Release 1.38.0

Release 1.38.0

Release Date: 12.12.2023 8pm - 11pm (UTC+2)
In version 1.38.0 of ReconHub, we've made enhancements in various sections, introducing updates to elevate your experience. Check out the details below for the main changes.

More Efficient and Transparent Transaction Matching

We're excited to announce a streamlined update in ReconHub's Transaction Match Rules: The introduction of Exact Rules and Tolerant Rules. This nuanced enhancement increases matching efficiency and transparency, while preserving the beloved flexibility of tolerant matching. It's an evolution, not a revolution.

A Journey Towards Enhanced Matching and Transparency

This update is the next step of our goal to boost both efficiency and transparency in ReconHub. It's designed to speed up your matching process, whether ReconHub handles it automatically or you match manually. We're also enhancing clarity around how transactions are matched and how data quality impacts your reconciliation. It's a streamlined step forward, focusing on making ReconHub more efficient and transparent for your daily tasks.

A Closer Look at Exact and Tolerant Rules

  • Exact Rules
    A new feature in ReconHub. 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 familiar rules you've grown to trust. They retain their versatile nature, accommodating tolerances and supporting 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.

How Will This Enhance Matching?

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.

Will This Change Impact Your Current Matching?

No. Existing rules with tolerances naturally evolve into Tolerant Transaction Match Rules. Those without tolerance seamlessly transform into Exact Transaction Match Rules. You might notice a few additional rules in your setup — these are auto-generated Exact Rules based on your existing tolerant configurations. Rest assured, these are designed to refine your matching process without changing your existing results.

Acquirers Become Payment Processors

In ReconHub, we recognize the need to adapt our terminology to reflect our expanding capabilities. While the role of traditional 'Acquirers' remains unchanged in the wider payment industry, ReconHub has evolved to support a broader spectrum of payment-related entities. This includes marketplaces, e-commerce PSPs, delivery services, and cash handlers, among others.

To accurately represent this diversity within ReconHub, we're transitioning from the term 'Acquirer' to 'Payment Processor'. This update is more than just a change of name; it's an acknowledgement of ReconHub's enhanced functionality. 'Payment Processor' now encompasses all entities that manage payment transactions and pay out the proceeds to your accounts, aligning our language with the expanded range of services supported by ReconHub.

Streamlined Matching with Payment Processor-Linked Rules

With this release, we're enhancing the efficiency of both transaction and settlement matching by linking the matching rules with Payment Processors.

This integration offers two key advantages:

  1. Simplified Rule Configuration: By associating rules with Payment Processors, we've made the configuration process more straightforward. Now, you can easily filter and organize rules based on the Payment Processor, streamlining setup and management.

  2. Improved Matching Efficiency: With rules explicitly linked to Payment Processors, ReconHub can more effectively determine which rules to apply for each transaction. This targeted approach ensures faster, more accurate matching, tailored to the specific characteristics of each Payment Processor.

Of course, ReconHub still supports match rules that are not linked to a Payment Processor. In the matching process, ReconHub will always first run through all rules linked to Payment Processors, and as a last step, process the rules that are not linked.

Enhanced Visibility with Payment Processor View

Understanding the specific configuration of ReconHub for each Payment Processor just got easier. Whether you're navigating through numerous Transaction Match Rules and need to focus on those relevant to a particular Payment Processor, or you're curious about the imported files and how they align with the matching rules, our new feature has you covered.

Introducing the Payment Processor View:

  • Centralized Overview: Upon accessing this feature, you're presented with a list of all configured Payment Processors. This immediate overview simplifies your initial navigation.

  • Detailed Insight with a Click: Selecting any Payment Processor from the list takes you to a dedicated detail page. Here, you'll find all configurations linked to that specific Processor - from imported files to associated matching rules and more.

This new view provides a streamlined, at-a-glance understanding of how each Payment Processor is configured and functioning within ReconHub, making it simpler to manage and optimize your payment processing configuration.


New Transaction Type

We've added a new transaction type for fees to better handle cases where some payment processors have fees not on transaction level. These fees are now loaded as a separate EFT Transaction, ensuring effective bank matching.  A specific transaction type increases the usability and ease the filtering.
Transactions with a 0 transaction amount and a settlement amount less than 0 are now automatically identified and marked as fees.


Improved Organizational Structure Export

Now, the export will display the actual OU names instead of the OU-IDs, providing a more user-friendly and informative experience.

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 ...