This release brings improvements to how you manage exceptions, enhances collaboration with shareable dashboard views, faster and easier data platform, and pre-configured SFTR EU transaction reporting solution.
Reconciliation
Enhanced flexibility in managing exceptions with new multiple manual matching feature
You’re no longer limited to one-to-one manual matches! With multiple manual matching, you can now match many records from Side A to many records from Side B at once, which provides more flexibility in managing complex exceptions.
This feature supports both 1-to-many and many-to-many matching and is available in the 2-sided reconciliations only.
Use multiple manual matching to handle such scenarios like combining several small fees that appear as separate lines in a statement but are recorded internally as one combined amount.
Check the Multiple manual matching Help Centre article to learn how to enable the feature and how to use it.
Smarter cash matching with proposed and subset matches
Proposed matches now work seamlessly with subset matching in cash processes, providing more accurate and efficient reconciliation by intelligently suggesting matches even when dealing with grouped transactions. This means users can now enable both “Find matches within roll-ups” and “Generate proposed matches” at the same time within a given process, to identify and propose matches involving subsets of roll-ups.
This enhancement reduces manual effort and improves overall matching rates, especially in scenarios where individual cash transactions might be grouped or split.
Solutions
Streamline SFTR EU transaction reporting with preconfigured templates
We’ve launched the SFTR EU template - a preconfigured solution that simplifies post-reporting processes and strengthens compliance under the securities financing transactions regulation (SFTR).
Streamline reconciliation, enhance data accuracy, and reduce manual effort with a ready-to-use preconfigured solution for regulatory precision.
To learn more or enable SFTR(EU) template, please reach out to your Client Success manager.
Reporting
Introducing the faster, easier Data Platform: unlock your reconciliation data with speed and scale
We are thrilled to announce the general availability of the new Data Platform, our powerful cloud-native analytics solution.
This reporting capability is a powerful data warehouse built specifically for your Duco data. It serves as your centralized hub for accessing and analyzing reconciliation results, designed to power your business intelligence (BI), reporting, and advanced analytics needs.
What's new
Top improvements include:
- Significantly faster performance As part of this change, we have moved to AWS tooling which brings massive improvements in performance and scalability. Query execution is up to 10 times faster, and data sync times for large runs (1–2 million rows) are just under 1 minute.
- A more powerful, user-friendly query interface The new reporting capability offers standard views that are easier to use and better structured for real-world analysis. Writing, running, and maintaining SQL queries is now significantly simpler, even for complex use cases.
- The foundation for next-generation reporting This new architecture doesn't just improve your current capabilities; it lays the foundation for a major leap forward in how you can analyze, understand, and report on your Duco data directly within the application in the future.
Manage and share your dashboard views with ease
We’ve made several updates to help you manage your dashboard views more efficiently and collaborate with your team more easily.
Share your dashboard views with others
You can now make any view public, allowing everyone with access to that dashboard to see it.
Public views are marked with an icon for owner and
for others with whom the view has been shared, making it easy to recognize and open shared views across your teams.
Set your personal default view
Now you can set any view - whether it’s one you created or a shared one – as your own default. This ensures your preferred setup always appears first, without changing what others see.
Keep track of unsaved changes
A * indicator now appears if you’ve made updates to a view that haven’t been saved. You’ll also see which view is currently active, helping you avoid confusion and keep your work organized.
These enhancements make dashboards more intuitive and collaborative - helping your team stay aligned while giving you more personal control over your workspace.
Fixed bugs
Issue Addressed |
Description |
| In the Data Prep process, the header row number and start/end row settings sometimes didn’t match between the data input configuration and the staging copy. | The staging copy now correctly uses the same header, start, and end row numbers that the user sets on the data input configuration page. |
| In some cases, the Data Prep submission page was very slow to load or respond. This happened because the system was scanning all database records instead of just the relevant ones. | The page has been optimized to avoid these full database scans. The user should now notice faster loading times and smoother interactions on the submission page. |
| When the “Field Name Parsing” feature was turned on, files with trailing spaces in the last column were not processed correctly. As a result, the last column’s data could be missed. | The system now ignores trailing spaces and processes all columns correctly. Files with “Field Name Parsing” enabled will now import completely and accurately. |
| When an exception category used in a process was removed from the global settings, the related records no longer showed that category in their details. | This has been fixed: users can now see the old option, remove it, and assign a new one as needed. |
| Some records showed strange symbols (like “&#”) in the History tab. | This has been corrected so those characters no longer appear, making the audit history easier to read. |
| When performing bulk updates in an NSR process, users were receiving duplicate notifications for each action. | The issue has been fixed so that only one notification is sent per update or action. |
| Opening the details panel in a child process sometimes caused a “500 error” in connected legacy workflows. | This error has been resolved — the details panel now opens correctly without interruption. |
| Some older cash transactions had missing dates saved in an invalid format (0000-00-00). When trying to export this data to Excel, the export would fail and show an error message. | The system was updated so that it can now handle these dates. You can export all transactions to Excel successfully, even if some older records don’t have valid dates. |
| Some workflow notifications related to cash processes weren’t being sent because a system setting was being sent incorrectly. This caused notifications to stop working for certain users. | The system now ignores that setting when it’s empty, so notifications are being sent correctly again. |
| After fixing or reordering statements, some accounts still showed an error status even though the issues had already been resolved. | The system now automatically updates each account’s status once errors are corrected. Account pages will now accurately show whether any errors remain. |
| Users couldn’t open their submissions because of an error caused by a new way of storing data. | The team found and fixed the issue using the improved data storage method. |
| When users copied Account IDs from the system, any zeros at the beginning of the ID were being removed. This caused problems when using those IDs elsewhere. | The system was updated so that Account IDs are always treated as text, making sure all numbers—including zeros at the start—are kept when copying and pasting. |
| When proposed matches, subset matching, and tolerance matching were all enabled, the matching process caused account groups to become locked and created pending changes with single transactions. | The issue was traced to a local environment configuration problem rather than the main system. After correcting this, the matching process now functions correctly, and proposed matches work smoothly with subset and tolerance matching enabled. |