We are excited to introduce Guided tours to help you get the most out of ReconHub.
These interactive step-by-step walkthroughs explain features directly within the platform, making it easier to learn new workflows and navigate the application. Whenever a guided tour is available for the current page, you can access it from the Help icon in the top-right corner.
We’ve added a new option to display the transaction time in its original time zone.
A new column Transaction Date (Origin) can now be enabled, showing the original transaction time based on the time zone where the transaction was created. This helps you better understand when the transaction actually took place in its source context.
In addition, we’ve added a tooltip that appears when the origin date differs from the default system time, giving you extra clarity in cases where the additional column is not displayed.
One-click Import Retry
We’ve improved the import process to reduce manual work when new terminals are added.
If an import fails because a terminal has not yet been registered, you can now retry the import with a single click once the missing terminal has been created in ReconHub. On the Proposed terminals page, click the Actions icon and select Retry import. All failed ECR and EFT files will be imported again. This eliminates the need to navigate through the system and ensures that the data is available more quickly.
Debit/Credit Filter for Bank Payments
A new Debit/Credit filter has been added to Bank payment processing.
You can now filter bank payments by incoming or outgoing transactions. This makes it easier to focus on the payments that are relevant for reconciliation, while excluding unrelated transactions.
Sort Exceptions by Organizational Unit
The Transaction Exceptions view can now be sorted by organizational unit within the same transaction date.
This gives you a more structured view of your exceptions and makes it easier to review and process large volumes of transactions. Instead of working through a long list, you can quickly group related exceptions by organizational unit and focus on the ones that matter most.
Account Placeholders in Posting Rules
You can now use placeholders for accounts in posting rules.
Instead of creating separate posting rules for different organizational units, you can reference account values dynamically using placeholders. For example, you can use the OU.Account placeholder to automatically use the default account configured for the respective organizational unit when creating postings.
This allows you to use a single posting template instead of maintaining multiple templates for different organizational units. It also makes it easier to add new locations without updating existing posting rules, reducing maintenance and making your posting configuration more flexible.
Our support team would be happy to assist you with the transition.