We continue with enhancements to improve your workflow efficiency, cash reconciliation audit control and data prep processes.
- Quickly handover large number of exceptions
- Cash enhancements
- MT940 format update
- Data prep enhancements
- Bug fixes
Quickly handover large number of exceptions
Often during your exception resolution process, you may need to handover many exceptions to another team for next action or closure. We have now expanded the feature to act on all filtered items in your result view, to support the Allocate to group, so that you can do so much faster with just a few clicks.
Cash enhancements
Detailed matching audit
Cash reconciliations often involve manual matching and unmatching activities. In the previous release we enhanced the audit history so that you can see the history of any workflow actions during matching. In this release we have added specific entries for manual matching and break apart action including tracking the matching transaction IDs, providing a clean and transparent history of such activities.
Run matching only on unfinished accounts
Matching within Cash runs on an Account Group by Account Group basis as new data is submitted. There are times however when matching might need to be triggered manually, for example after grouping an Account, deleting statements or if matching fails on a particular Account Group. Rather than running matching manually for all Accounts or waiting for the next submission you can now trigger matching for just those Accounts.
MT940 format update
New fields have been added to our MT940 format definition, to expose more data around balances. Any existing process using this format will have these new fields added to your data input field set as part of the release, which you can then choose to use for matching or reporting. Since these are balance level information, the same values will be repeated for each transaction row within that statement.
|
Duco field name |
Duco field type |
SWIFT message tag |
|
Opening Balance Date |
Date |
60a (option M) |
|
Closing Balance Date |
Date |
62a (option M) |
|
Available balance date |
Date |
64 |
|
Available balance |
Decimal |
64 |
|
Forward available balance date |
Date |
65 |
|
Forward available balance |
Decimal |
65 |
|
Transaction Reference Number |
Text |
20 |
|
Related Reference |
Text |
21 |
|
Data type |
Text |
"Transaction" |
New features available in Data Prep
Extract file header data for transformation
The same option you can already use in reconciliation processes, you can now also choose to use header data in delimited files in your transformation rules within data prep. This for example enables you to extract a date or other meta data that is embedded in the first few lines of your input file, and use a transformation rule to repeat that for every row of data in the file.
Process balance as separate output lines when using MT940
If you use a SWIFT MT940 as one of the inputs for your data prep process, you now have the option to choose to only output transaction lines (default option), or also include balance data as output lines. When using this option, transaction and balance lines are distinguished by a new field called Data type, which you can then use to process as balance within data prep with the Map balances feature, or pass them all to the recon processes.
More information in recon processes
You can now see which data prep process is feeding your recon process in both the UI and PDF configuration export.
Bug fixes
|
Issues addressed |
Description |
|
First line of data omitted in reference data |
After configuration change for reference data files, a new file submission has been incorrectly parsed by the system and was omitting first data set’s record |
|
Filtering by date working incorrectly on results page |
Filtering by date working incorrectly when using “is not between” operator |
|
Process export failure |
Unable to export process when reference data table linked to process is being uploaded with large data set |
|
Inability to remove user role when 4 eyes control is enabled |
Removing a user role from process permissions ends up with error 500 |
|
Inability to rerun using previous data in some cases with data prep |
Inability to rerun using previous data when both data inputs are Data Prep processes |
|
Data prep submission issue after changing file delimiter |
Data Prep files submissions failing after delimiter for the generic file has been updated |
|
Cannot use data prep data after copying process |
Problem with using data prep data after making a copy or staging copy of a reconciliation process |
|
Disabling recon process promotion when using data prep |
We are temporarily stopping recon processes using data prep as input to be promoted, until an upcoming enhancement to support this becomes available. |