Change log 1.50.0

Change log 1.50.0

Info
Release Date: 22.05.2025
DB Version: 1.50.0.0

New features

  1. 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:
    1. Matching: Overview of matched and unmatched bank payments and transactions based on the value date or the expected value date
    2. Forecast: Overview of the projected payout amounts based on the expected value date of the transactions
This feature is currently in beta.

Enhancements

Website

  1. Filtering by order ID of transactions is now possible for manual settlement matching
  2. In the export rules, it is now possible to specify whether postings without accounts or postings with two identical accounts (in debit and credit) are permitted. This can be used, for example, for exports whose target system is not an accounting system.
  3. Added an ou filter to settlement match rules

Modules

  1. Changed mappings to the additional data for delivery transactions in the ECR TLD import module

Processing

  1. The performance of transaction matching has been improved

Bug fixes

Website

  1. Fields without any value are now also shown in the accounting data of the posting detail view
  2. Fixed a bug when editing an EFT RAF collector configuration where the collector execution date was lost if all merchant range IDs had their specific start date set
  3. Fixed a bug that occured on import retry if a file already existed in the import folder
  4. Fixed a bug that prevented the organizational unit structure from being updated after relocating a terminal or account
  5. Fixed a bug where duplicating an inactive posting rule created an active posting rule

Modules

  1. Fixed a bug in the EFT RAF collector module that occurred one day after the daylight saving time changeover if the data collection was executed exactly at the time of the changeover
  2. Fixed a bug in the FTP collector module that sometimes caused a file to not download completely if the file was being uploaded at the same time
  3. Fixed a bug in the Tenant import/export module that caused the import and export to not work if a DATEV upload was present

Processing

  1. The field Additional statement information of bank payments has been enlarged to a maximum length of 500 characters
  2. The field Merchant ID of bank payments has been enlarged to a maximum length of 100 characters
  3. Fixed a concurrency issue in the heartbeat pulser of the job execution worker
  4. Fixed the summation of inverted amounts in the posting documents of exports

Notes

Abrantix email addresses will now be obfuscated for non-abrantix users.