This release contains a major change in how carry-over exceptions are handled, and two related enhancements to improve your workflow, file management and investigation process in generic processes.
- Include duplicates in the run
- Mark a run as failed
- Run results based carry over
For some recs, you may struggle to identify a good combination of fields that can be used as record tracking key (e.g. limited data from counterparty). As a result, there are many items identified as duplicates in Duco after each run, that may in fact be individual items that need to be reconciled and investigated.
Now you can mark these items as not duplicates. They will then be included in the run and become exceptions. They will be carried-over to next run if remain unresolved, and will not be treated as duplicates again in subsequent runs if new records matching the same tracking keys are submitted.
Mark a run as failed
A file with bad data may get submitted by mistake or unintentionally (e.g. through automatic submission) and trigger a run in Duco. This could result in many incorrect matches, new unwanted exceptions that may be mixed up with legitimate exceptions carried-over from previous run.
You can now mark the run as failed. Duco will then close all the new exceptions created, re-open exceptions from previous successful run, and restore their workflow statuses.
As part of this, a new global role has been introduced, and only users with this role will be able to mark a run as failed. You can only mark the last successful run as failed.
Run results based carry over
The above changes are powered by run results based carry-over. This enhancement in how Duco stores and uses carry-over items will have no impact to your existing processes, but will bring you the following benefits:
- you can now add fields to data inputs and carry over items will have empty values for new fields
- you can change matching field types that are compatible such as date to text
However, any change to field transformation or reported fields will not be applied to carry-over items.
Cash reconciliation enhancements
In addition, for our continuous effort in cash reconciliation, we have the following new features in this release:
- Showing transactions from ungrouped accounts
- Export global account overview into Excel file
- Manually start matching
- Submit files from both sides
Transactions from ungrouped accounts
With the feature released earlier in the year that creates accounts automatically from submissions, you may have many accounts that are not yet grouped until you have time to process them. During the time, you may continue to receive statements for these accounts, and the associated transactions accumulate.
Now these transactions can be accessed from the transactions screen, shown in a new category. You can monitor the total number of such transactions, and click to see the records. No manual actions are allowed on these, until the account are grouped and therefore include in the next matching process.
Export global account overview
Similar to cash transactions matching results, you may want to take a copy of the account proofing status from the account overview page. You can then store it for record keeping, or as snapshot of the statuses at a particular point in time.
You can now export it into an Excel file from the UI, or through a new API.
Manually start matching cash transactions
After some user actions, such as grouping new accounts and marking a statement as not a duplicate, there may be new transactions that become available for matching. You can now initiate a matching process manually from the UI.
Submit files from both sides
During your testing cycles, you may want to submit two files from both sides at the same time and see how the transactions are matched. You may also do that repeatedly by using the same files and check the match rate after each configuration change iteration.
You can now submit the two files from the UI, which will trigger one matching process.
Data platform enhancements
We have also continued to roll-out enhancements to Data Platform, empowering you to extract valuable data from the platform:
You can extract data related to all files submitted into Duco, including submissions for generic processes, reference data table file uploads, and cash statements for cash processes. For each submission, you have access to when it was submitted, file size, error code if applicable and other information.
Runs and exception state counts
For generic processes, you can now retrieve the latest run status, as well as high level information about that run such as submitted, matched, ignored counts. You can also then use the time series views to see how these change over time.
Duco reports all the fields that are causing a particular break. This information is now available in Data Platform, allowing you to pinpoint data quality issues, analyse for each counterparty which field is causing most problems, etc..