Gresham: data management, reconciliation and reporting connectivity

Gresham supplies financial-data management, reconciliation, connectivity and regulatory-data software, supported by managed services. Its institutional use spans the records that feed trading and risk systems and the post-trade processes that compare internal books with external evidence. A broker can therefore use different parts of the portfolio for different problems: mastering data, moving messages, detecting breaks or operating a data process on its behalf.[1]

Control Cloud supports matching across three or more independent sources in one reconciliation. Its investigation tools link related exceptions so a common cause can be handled together. Operational views show matched and unmatched records, open or ageing breaks, file and account status, and assigned responsibility. Rules can resolve exceptions within configured parameters. That makes the design of tolerances, ownership and approval steps part of the control, alongside the matching algorithm.[4]

Opus EDM’s product-and-account master supports multiple hierarchies and workflows with access entitlements and four-eyes approval. The Data Dictionary exposes definitions, provenance, ownership and change history through a web portal, including sources outside the platform. Its Trade Hub consolidates, transforms and validates transactions before acknowledged distribution; the Data Hub performs similar integration for general feeds. The dictionary and processing hubs have different jobs and need separate configuration decisions.[3]

Prime EDM’s data store uses Apache Cassandra and Spark, with integration into Python, R and analytical or business-intelligence applications. Its dashboards expose quality exceptions and threshold breaches; Data Quality Intelligence captures process and risk metrics through the data lifecycle. The integration design should preserve the selected record’s lineage and validation state when it reaches a downstream trading, valuation or risk application.[2]

Connect’s public message-library catalogue distinguishes maintained implementations from deprecated ones. FIX/FIXML, FpML, ISO 20022 and SWIFT MT/MX libraries are listed as supported. The catalogue marks several older libraries, including its FedWire and NACHA entries, as deprecated. Those labels describe this library catalogue, not the availability of every possible payment connection. A project should identify the exact message version, connector and supported implementation instead of treating a standards name as a complete integration specification.[12]

Pulse Data collects records from external providers and makes their delivery status visible. Its dashboard shows accounts by custodian, the most recent delivery and support tickets for account or feed onboarding. Managed Data Services adds collection on the customer’s behalf, normalisation and file delivery into reconciliation, accounting or performance systems. Feed onboarding, missing-record investigation and business approval are distinct responsibilities that should be allocated in the operating arrangement.[7][11]

Connect Cloud describes FIX capture from order or execution-management systems, FINRA TRACE and MSRB reporting, and connectivity to BNY Pershing clearing for US broker-dealers. For institutional users, its role can instead be delivery of reconciled data to reporting, risk or finance systems. These are technology routes: the broker’s reporting status and clearing relationship determine which workflow it can put into production.[6]

Gresham offers a demonstration and business-scoping process. The reviewed public pages do not provide a universal numeric licence tariff, minimum contract value or common volume allowance. The commercial scope needs to identify the products, environments and operating services supplied.[14]

Connect’s broker-dealer page uses comparative pricing language against larger bundled platforms, but supplies no actual rate card or standard fee. It cannot establish a price for a particular firm. A quotation should define reporting venues, connectivity, clearing interfaces and any associated reconciliation scope.[6]

The DevOps offering covers public- or private-cloud deployment and names experience with Google Cloud, AWS, Oracle Cloud Infrastructure and Azure. It can be provided independently or alongside managed services. Scope includes development tools, infrastructure, security, user and API management. That breadth does not mean every product is available in every configuration; the selected platform and environment need an agreed architecture and operating model.[9]

EDM services distinguish operating the platform from operating the data process. The former includes monitoring, workflow configuration and performance tuning. The latter includes provider onboarding, cross-reference mapping, validation, enrichment and exception handling by data specialists. A transition plan should identify which tasks move to Gresham, which approvals stay with the customer and how outstanding exceptions pass between the teams.[8]

Control Studio was announced as available on 1 October 2026. It lets business users configure sources, matching rules, validation and exception workflows against sample data, with AI suggestions for keys or checks. The generated configuration is then used by Control’s deterministic rules engines. Evaluation should therefore test both the proposed configuration and the results on representative records before a control enters production.[5]

The support page advertises global 24/7 access and publishes emergency numbers separately from incident-progress lines. It also offers Connect and Control training certifications. Product documentation and EDM support have distinct entry points, so a customer should use the route assigned to its product and contract. The public material does not publish universal severity-specific response or resolution targets.[13]

Managed reconciliation goes beyond software incident support by assigning reconciliation work to Gresham’s operating team. The service is described as tailored to the customer while retaining customer control. Its delivery agreement should distinguish a missing input, an unmatched record, a proposed adjustment and final business approval: each can require a different owner even when the same platform tracks the work.[10]

The trade-reporting proposition supplies transformation, connectivity, reconciliation and customisation around regulatory-data workflows. A connection to a reporting venue does not itself establish the customer’s permission, reporting responsibility or accepted submission. The production design needs the relevant entity identifiers, report scope and feedback-handling process, including investigation of rejected or corrected records. These responsibilities should remain explicit when reporting preparation or operations are outsourced.[26]

The privacy policy is dated September 2024 and addresses website, premises, enquiry and support-contact information. It identifies the relevant Gresham group company as controller and supplements other notices. It is therefore useful for understanding contact-data handling, but it does not by itself specify the customer dataset, storage region, retention schedule or processing terms for a deployed service.[16]

The website’s legal notice identifies a group of operating entities, including Gresham Technologies (UK) Limited, Gresham Technologies (US) Inc., Asset Control entities and Electra Information Systems. The supplier for a deployment should be taken from its contract, particularly where an older product or acquired business is involved.[15]

Companies House records Gresham Technologies Limited, number 01072032, as an active private company at Aldermary House, 10–15 Queen Street, London. The record retains the former Gresham Technologies plc and Gresham Computing names. Gresham Technologies (UK) Limited is a separate active company, number 01059069, at the same address. These are corporate identity records, rather than financial-services authorisations.[17][18]

The 19 September 2024 announcement records the completed take-private transaction and merger with Alveo, followed by unified Gresham branding. Prime EDM came from the Alveo portfolio; Pulse Data was formerly Electra Data. Alveo’s former investor separately documents its earlier Asset Control name and December 2020 rebrand. These histories explain why older contracts and technical materials may carry different names.[19][22]

Gresham announced completion of the S&P Global EDM business acquisition on 12 January 2026. The specific acquired platform was renamed Opus EDM on 30 March; its previous names included Cadis, Markit EDM, IHS Markit EDM and S&P Global EDM. The announcement says Opus and Prime continue on their existing product roadmaps. Institutions should therefore establish which platform and delivery model their agreement covers.[20][21]

Operator

Gresham group; entities include Gresham Technologies Limited and Gresham Technologies (UK) Limited.

Service scope

Institutional financial-data management, reconciliation, transaction connectivity and related managed operating services.

Customer types

Banks; Broker-dealers; Asset managers; Custodians

Delivery

SaaS; Hosted; API; Managed service

Pricing publication

Quote only

Platforms

Prime EDM; Opus EDM; Control Cloud; Control Studio; Connect Cloud; Pulse Data; Data Dictionary; Clareti; Connect Message Services

Integrations

FIX/FIXML; FpML; SWIFT MT/MX; ISO 20022; FINRA TRACE; MSRB; BNY Pershing connectivity; Python; R; Apache Spark

Pricing scope

No universal public numeric tariff; selected platforms, interfaces and operating services require agreement.

Implementation

Product-specific architecture, source onboarding, configuration, validation and operating handover.

Support

Published 24-hour global support routes; product-specific escalation and incident targets remain contractual.

Permissions and regulatory scope

Technology and operating services supporting the customer’s reporting and control obligations.

Provider metadata checked 21 Oct 2026Source 1Source 15Source 17Source 18Source 21Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 13Source 14Source 26Source 22Source 24Source 23Source 25Source 12

Control Studio’s AI assists with authoring a reconciliation control: it can suggest relationships, matching keys, search expressions and enrichment rules while users inspect effects on sample data. That is different from allowing an agent to take every production decision. The launch describes deterministic execution and retained governance. The implementation should make the boundary between a generated suggestion, an approved rule and a resulting accounting or operational action visible to users.[5]

Gresham’s product pages include throughput, savings and implementation-speed claims. Those figures are vendor descriptions of capability or deployments, rather than a service level for every customer. For Control Cloud, the meaningful acceptance evidence is how the agreed source records, matching rules, exception priorities and review controls behave together under the customer’s actual operating load.[4]