Change log 1.53.0
Change log 1.53.0
Release Date: 25.09.2025
DB Version: 1.53.0.0
New features
- GDPR restrictions can now be enabled for a tenant. If enabled, the following restrictions apply:
- Bank payment files cannot be downloaded by non-elevated users
- Skipped bank payments cannot be posted
- A custom retention time can be configured for skipped bank payments. If configured, a skipped bank payment will be deleted by the DB cleanup after it exceeds the retention time. The reference date for this new retention time is the Create date (UTC) of the bank payment.
Enhancements
Website
- The current export sequence number will now always be displayed on Posting export rules
- The previous document number will now always be displayed on Posting export rules if the rule supports a document number format
- The payment processor is now preselected for the transaction filter when manually matching bank payments
- Removed unused field Column value type from column filters in all rule edit views
- Renamed the field Payout date to Additional date in the bank payment and bank payment processing configuration views
- Renamed the field Match date to Match key date in the settlement match views
- Renamed the field Value date to Value date (Bank) in the transaction views
- Added a filter for the source type to the skip rule list view
- Added a filter to exclude deleted terminals to the terminal usage view
- (Cloud only): The custom fields of organizational units can now be selected as columns in the outstanding receivables transaction list
- (Cloud only): The custom fields of organizational units are now listed in the details of the outstanding receivables transaction list
Modules
- The Generic import modules now support named capture groups in regex filters of source field mappings
- Multiple formats can now be specified in the source fields in the Generic import modules
- Extended the Generic import modules with the ability to identify record types using multiple source fields
- The field Mandator alias on ECR and EFT transactions is now available for transaction matching
- Ensured that the Bank EBICS collector module sends ReconHub as system identifier (instead of Subsembly)
- All ECR and EFT import modules now use the payment processor of the import configuration as a fallback value
- Added a new UID pattern to the EFT GRRCN import module
- Added a custom field to the Ledger Abacus export module
Processing
- Extended the field length of the following properties to 100
- Bank payment: Account number, Account servicing institution reference, Creditor account, Creditor bank, Debtor account, Debtor bank, End-to-end reference, Instruction reference, Message reference, Transaction reference, Settlement ID, Statement ID
- ECR transaction: Authorisation code, Order ID, Transaction reference, Transaction sequence counter, Terminal ID
- EFT transaction: Authorisation code, Order ID, Settlement ID, Transaction reference, Transaction sequence counter, Terminal ID
- Terminal: Name, Terminal ID
- Extended the field length of the following properties to 500
- Export rule: Document number format, Unique export ID format
- Improved placeholder logic in the posting export processor for the Unique export ID
- Improved performance of the double charge processor
- The bank payment processing can now filter by bank accounts. If a bank payment processing configuration is assigned to a bank account, only bank payments belonging to that account are processed by that configuration.
- The bank payment processing is now able to handle numbers in all common formats (e.g. also with a comma as thousands-separator) correctly
Bug fixes
Website
- Some control characters were displayed in the source data for the proposed terminals
- The payment processor was not displayed anymore when adding a posting rule on manual creation of an adjustment
Processing
- Transaction with amount zero are no longer classified as Purchase in all Import modules