The July release brings a new home page to give you a better starting point each day, more precise filtering in two sided reconciliation, a faster way to revert multiple runs at once, a full audit history for exception workflow actions in the reporting and data access (formerly data platform), and early-access features for cross-process field normalisation.
Platform
Your new home in Duco
The Home Page is a new personalized landing page that opens when you log in. Instead of going straight to the Dashboards list, you now arrive at a screen designed around what you actually need to start your day: the items you were working on in previous session, the processes and dashboards you come back to most, and a direct line to Duco's agentic workspace - without navigating anywhere first.
The agentic chat interface at the centre of the page lets you ask anything about your reconciliations or describe a task. Use the @ Mention a process button to scope a question to a specific process without leaving the page.
Below the chat, Pick up where you left off shows your five most recently visited items across Duco, ordered by when you last accessed them. The Starred section keeps your most important processes and dashboards pinned in one place, regardless of when you last opened them. Click the Duco logo in the navigation sidebar at any time to return to home.
What that unlocks day-to-day:
- Ask questions about your reconciliations and kick off tasks without first navigating to a specific process.
- Instantly jump back into anything you were working on yesterday.
- Surface your most-used processes and dashboards without searching.
Note: What you see on your Home Page may vary depending on your Duco edition. The agentic workspace is currently in early access. If you don't see them, contact your Duco account team to find out more.
Reconciliation
AND / OR filter for latest comment
When reviewing runs, you may need a precise view of records based on their latest comment - finding rows where "closed" was added but "open" never was, for example. The previous latest comment filter lets you apply a ‘Contains’ condition or a ‘Does not contain’ condition, but not both at the same time. That meant filtering in separate steps and cross-referencing results manually.
You can now combine ‘Contains’ and ‘Does not contain’ in a single filter, connected by an AND or OR toggle. This brings two sided reconciliation in line with how the Cash latest comment filter already works, and lets you isolate exactly the records you need in one pass. Open the filter on the Latest comment column, enter values in either or both sections, set the toggle, and apply.
Revert a run - and everything after it - in one action
Marking a reconciliation run as failed was only possible on the most recent successful run. Rolling back further meant repeating the action for each run individually, and rapid repeated actions could fail in confusing ways due to the order of processing each request.
You can now select any earlier successful run from the All Runs table and revert to it in a single action. Duco shows you exactly how many subsequent runs will be marked as failed before you confirm, then marks them as failed all at once. The existing Mark as failed button on the latest run remains unchanged.
What that unlocks day-to-day:
- Recover from a data issue that affected multiple runs without repeating the same manual action over and over.
- See a clear summary of what will change before committing.
Available in: two sided reconciliation
Data Access
Full audit history for exception workflow actions
Duco's exception workflow history - every state change, label, comment, assignment, and category change made on an exception - was previously only accessible inside the UI. There was no way to pull it into BI tools, build automated audit reports, or query it programmatically alongside other operational data.
This release adds that data to the Duco's reporting capability as structured, queryable views. You can now identify whether a change was made manually by a user or triggered automatically by a workflow rule, and build dashboards and reports over the full lifecycle of every exception - without logging into Duco.
What's new:
- Workflow actions views (new) - full history of state changes, assignments, and category changes for two sided reconciliation and cash processes. Each record includes timestamp, exception ID, the user or rule that triggered it, action type, and old and new values.
Existing queries against record_comments and results_to_labels are unaffected - this release adds new tables only.
Normalise field names across processes
Processes often use field names specific to how each one was built - "Trade Ref" in one rec, "Reference ID" in another, "TRN" in a third - even when they all refer to the same concept. This fragmentation makes cross-process reporting difficult and means the same harmonisation work gets repeated every time a new process or report is set up.
The Reporting Field Mappings introduces a shared semantic layer that maps local process fields to canonical business fields once. Duco's agentic assistant suggests mappings based on field names, data types, and example values, with a confidence score and explanation for each suggestion. You review, approve, or override. Once mappings are in place, every report, dashboard, and agent that uses those fields benefits automatically - and all mappings are versioned and auditable.
These fields will be also available in your reporting database instance as dedicated columns for easier querying, rather than part of JSON results string. Access the Reporting Field Mappings from Administration.
Early Access - Contact your Duco account team to be included.
Action required: Amazon Redshift ODBC 1.x driver end of support
Amazon has announced that support for the ODBC 1.x driver for Amazon Redshift will end on 30 September 2026. The driver will continue to function after this date, but will no longer receive updates or technical support.
If you connect to the Duco's reporting capability using the ODBC 1.x driver, we recommend migrating to the ODBC 2.x driver before this date to stay on a supported version.
Migration steps depend on your connection method:
- DSN or script connections - download the latest 2.x driver: https://docs.aws.amazon.com/redshift/latest/mgmt/odbc20-install-win.html
- Tableau (Redshift connector) - follow this guide for installing the driver: https://help.tableau.com/current/pro/desktop/en-us/examples_amazonredshift.htm#driver-required
- Power BI (Redshift connector) - follow this guide for enabling the 2.x driver: https://learn.microsoft.com/en-us/power-query/connectors/amazon-redshift#redshift-connector-implementation-20. Note: Power BI's native Amazon Redshift connector currently uses the ODBC 1.x driver, and the driver version is controlled by the connector rather than by a setting you can change. If your tool continues to use the 1.x driver after migration, you can configure a connection through the generic ODBC connector pointing explicitly to the 2.x driver as an interim workaround.
- Any other tool - consult that tool's documentation or support team for migration guidance.