Duco: reconciliation, data preparation and controlled automation

Duco serves brokers, futures commission merchants and other institutions whose operational records arrive from different systems and counterparties. Its software brings ingestion, preparation, matching and exception handling into a controlled workflow. For a brokerage, the relevant use can be a trade or position reconciliation, cash control, collateral check or verification of regulatory-reporting data. The customer configures which records and differences require action.[2]

ETD clearing is a separate operational use case. Duco describes matching trades, positions and fees, and linking processes to produce a total-equity view across products. Its published examples include reconciliation against XTP, GMI and exchange records. This helps explain the role of the platform: it checks and connects the records generated by clearing workflows.[9]

Automated file delivery has timing rules. For a two-input process, Duco waits for both inputs, allowing asynchronous submissions. A sticky source retains its file after a run so it can be reused. SFTP setup requires an SSH key, server details and upload location. On AWS, submitted files are picked up immediately; clients that try to change file attributes after upload may need those actions disabled.[15]

Service credentials are provisioned through the Client Success Manager or support. Duco’s January 2026 guide describes encrypted 1Password sharing links, email verification and access that expires after viewing or seven days. API, SFTP and Data Platform credentials follow that route; ordinary platform-user access is handled through the customer’s internal Duco administrator.[21]

The reviewed current product materials do not establish a universal numerical tariff, minimum contract value or standard renewal and cancellation schedule. A commercial offer needs to identify the subscribed capabilities, capacity, implementation services and retention period. Duco does publish how some usage is measured, which is useful when defining the purchased volume.[13]

Clients with several production environments can obtain a consolidated volume report through the status page. The documented report is refreshed hourly and shows capacity, average and peak daily usage, per-environment figures and a 30-day chargeable-volume chart. These measurements help distinguish contractual capacity from an observed workload.[19]

A new process begins with a single-sided, two-sided or cash reconciliation, using the wizard or a template. The team sets inputs and match fields, adds enrichment and matching rules, configures exception tracking and tolerances, then sets submission notifications and change control. User or group permissions determine access. Reporting and dashboards follow the configured process, so the implementation includes both the matching logic and how unresolved items are owned.[6]

The SaaS product requires no customer installation. Duco describes straightforward reconciliations as taking hours to build, while more complicated requirements can take days or weeks. These are vendor deployment descriptions, shaped by the customer’s internal requirements. Customers may build processes themselves or engage Duco’s professional-services team.[4]

The EMIR template article describes the original April 2024 Refit preparation despite an April 2026 update timestamp. Its useful current detail is the versioned configuration mechanism: new processes use the latest release, while updates to existing processes require a choice. A document’s maintenance date should therefore be distinguished from the original reporting transition it describes.[12]

Support requests can be submitted through the Help Centre or by email. The form asks for email, subject, issue description and impact; a process URL and attachments help identify the affected workflow. Impact is used in triage. The public request procedure provides no universal acknowledgement or restoration clock.[20]

The status dashboard uses credentials separate from the ordinary platform login, arranged through the Client Success Manager. It reports service-component health and current incidents. The documentation names components including Data Prep, cash reconciliation, Data Platform, WebUI, SFTP and queuing. This is an operational information route for clients.[19]

Development-environment terms explicitly exclude Testing and Sandbox from the Support SLA and make support credits unavailable for those environments. That distinction matters when assessing a test incident against a production-service commitment.[14]

Duco’s reporting products supply controls over the data a firm prepares and reports. Its published coverage includes EMIR, MiFID II, SFTR, CFTC and other regimes. This scope describes reconciliation technology; a customer still needs to determine the applicable reporting obligation, required fields and correction process. The company record used here establishes a software business, rather than a financial-services permission.[11][24]

The security page states ISO 27001 certification and SOC 2 Type 2 assurance, with certificates available on request. It describes encryption in transit and at rest, AWS deployment across availability zones, single sign-on and granular user permissions. These are supplier-published security arrangements; the underlying certificates and audit report were not available in the reviewed public page.[18]

Exception investigation is supported by an action history: the help guide says actions are logged and results can be analysed through in-app dashboards or the reporting database. The customer can therefore connect a mismatch to its handling history, rather than relying only on a final matched/unmatched flag.[7]

Duco’s group privacy policy names UK, US, Belgian, Polish and Singapore entities and says the relevant controller or processor is identified when a service is ordered. Duco Technology Limited is responsible for the website. Production-data processing terms should therefore identify the particular entity and ordered service, rather than derive them solely from the website’s address.[23]

Companies House records Duco Technology Limited, company 05686389, as active, with software development as its business activity and a London registered office. It was incorporated on 24 January 2006 as Model Two Zero Limited and adopted its present name in January 2016. Those legal-entity dates are distinct from product-launch dates.[24]

Nordic Capital lists Duco in Fund X, with an investment date of 2021 and London as its head office. Its current company profile states that founder Christian Nentwich returned as chief executive in March 2026. It reports EUR 40 million of 2025 revenue. These are the investor’s company figures, with their stated period.[25]

Duco completed the Metamaze acquisition in February 2024, adding intelligent document processing for unstructured material such as documents and emails. The current group offer combines this extraction capability with preparation and reconciliation. Metamaze is treated here as an acquired part of Duco’s product history.[26]

Operator

Duco Technology Limited and relevant Duco group entity

Service scope

Data preparation, reconciliation, exception workflows and reporting controls for institutional operations.

Customer types

Brokers and FCMs; Banks; Asset managers; Asset servicers; Capital markets infrastructure firms

Delivery

SaaS; API

Pricing publication

Quote only

Headquarters

London, United Kingdom

Platforms

Duco platform; Agentic workspace; Adaptive IDP

Integrations

API and SFTP data transfer; MCP access for client agents; Single sign-on; Reporting outputs for BI tools

Pricing scope

Commercial rates and minimum commitments require an agreed offer; published usage units distinguish records from document pages.

Implementation

Cloud deployment with process configuration, data-feed integration and change control; separate development environments are an additional module.

Support

Help-centre tickets and [email protected]; the Client Success Manager arranges status-page access. Production incident terms require the service agreement.

Permissions and regulatory scope

Operational and reporting-control software. The profile establishes company identity and product scope, not financial permissions or regulatory approval of a customer’s reporting.

Provider metadata checked 20 Oct 2026Source 24Source 23Source 22Source 11Source 1Source 2Source 3Source 13Source 14Source 20Source 26Source 25Source 8

Export and archival access should be planned before the agreed retention period ends. The public retention article does not establish a separate post-termination retrieval window, exit-assistance price or entitlement to restore deleted data. Those exit terms require the service agreement.[17]

A successful manual rerun does not repair an automated submission queue. Duco documents how an older unmatched input can wait and then pair with the next day’s opposite-side file, leaving the newer file pending. Manual runs leave that queue unchanged. Its remedies include overwriting the stale side, deliberately discarding the queued input or consuming it in a controlled run; permanent submission windows can reduce recurrence. This is a useful operational distinction when investigating a recurring daily mismatch.[16]

The October 2026 release notes distinguish available features from access-limited and planned changes. Full-volume data-preparation previews accept files up to 50 MB, including ZIP files, but not AIDP inputs. The expanded three-way reconciliation view remains early access. A new Data deleter role for cash processes is planned for the November release; as of this check, Config admin still carries the described deletion authority.[27]

Duco’s 29 September 2026 Pacesetters report describes production trials with 12 selected clients and an average 76% reduction in manual reconciliation task time. That vendor-reported result is specific to the trial group and measured work. The release also states that agentic workspace is available to new and existing clients, including MCP access with customer agents. It does not provide a universal time-saving entitlement for every implementation.[28]