Happy new year. First release of this year brings you enhancements across the platform as well as bug fixes.
- Quickly remove labels from large number of exceptions
- MT950 format update
- New features available in Data Prep
- Bug fixes
Check out the last release note for Dec if you have not seen it yet.
Quickly remove labels from large number of exceptions
You can now remove labels from large numbers of transactions (in addition to the existing ability to add labels) supporting making workflow processes more efficient on high volume reconciliations. You can select one or more labels for removal from all records that have those labels applied. Once complete a message will show you how many transactions had 1 or more labels removed.
MT950 format update
Similar to the enhancement done to MT940, new fields have now also been added to our MT950 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 |
|
Transaction Reference Number |
Text |
20 |
|
Data type |
Text |
"Transaction" |
New features available in Data Prep
List of reconciliation processes and runs that used each snapshot
To provide additional data traceability, you can now see for each data prep snapshot, which reconciliation process and runs have used it as input.
Showing data prep input name in reconciliation rollup constituents
In a typical one-to-many reconciliation scenario such as internal data set vs multiple brokers, it’s important to be able to identify which broker the data comes from, even when they are grouped into a rollup.
If you have a reconciliation process that uses data prep input and the results contain rollups, when you look at the individual constituents, you will now be able to see which data prep input each line comes from.
Process balance as separate output lines when using MT950
Similar to the new option in MT940, if you use a SWIFT MT950 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.
Restrict submission routing for recon using data prep as input
For any reconciliation process input that is being fed by a data prep process, you will no longer be able to configure a submission routing for it, avoiding the error of incorrect submission.
Bug fixes
|
Issues addressed |
Description |
|
Data prep - link to new snapshot created is wrong |
After a new snapshot is successfully created, the link from notification is not going to the correct snapshot. |
|
Notification messages displayed in incorrect order |
The latest notification message should appear at the top of the list. |
|
Data prep - access process through URL |
Allow users to access data prep processes directly and easily using URL. |
|
Data prep - snapshot created before submission processing finished |
Snapshot was created before submission finished processing, and contains incomplete data. |