Shield Connectors

Thomson Reuters Chat Connector

Back To Connectors Page

Financial Messaging | Connector for Thomson Reuters Chat

Request a Demo

What Is the Shield Connector for Thomson Reuters Chat?

Thomson Reuters Chat — also known as Reuters Messaging — was the real-time messaging service embedded within the Thomson Reuters Eikon terminal and the broader Thomson Reuters financial data infrastructure, enabling financial professionals to communicate directly with counterparties, colleagues, and clients within the same environment as the market data and analytics they used to make trading decisions. Widely used across banks, asset managers, broker-dealers, and hedge funds prior to the Refinitiv rebrand, Thomson Reuters Chat was a primary financial messaging channel for a generation of market participants — carrying price negotiation, order coordination, market colour, and client-facing communications in the compressed, informal register of financial markets.

Following the 2018 sale of Thomson Reuters’ financial data business to Blackstone, the platform was rebranded as Refinitiv — and Thomson Reuters Chat became Eikon Messenger under the Refinitiv brand. The platform subsequently passed to LSEG following the 2021 acquisition of Refinitiv. Firms that operated Thomson Reuters Chat during this period retain compliance obligations for historical data generated under the Thomson Reuters brand — either because regulatory retention periods extend back to that period, or because legacy records are required for ongoing investigations, litigation holds, or regulatory examination responses.

Shield’s connector for Thomson Reuters Chat ingests historical and legacy Thomson Reuters Chat message records and associated metadata directly into Shield’s compliance platform, making every captured communication immediately available for AI-powered surveillance, investigation, and eDiscovery alongside every other channel the firm uses. From the moment data enters Shield, it is available within a single unified platform — without manual exports, without siloed review workflows, and without the blind spots that arise when legacy financial messaging data is managed separately from current-generation communications.

Why Thomson Reuters Chat Compliance Is Complex

Thomson Reuters Chat presents compliance challenges that reflect both the specific characteristics of the platform and the legacy nature of the data it generated. Several issues arise consistently across regulated firms:

  • Legacy data within active retention windows. Many firms operated Thomson Reuters Chat between 2010 and 2018. Under SEC Rules 17a-3 and 17a-4, broker-dealers are required to retain business records for a minimum of six years. Under MiFID II and MAR, retention periods extend to five to seven years. Under CFTC regulations, five years. For firms subject to ongoing investigations, litigation holds, or regulatory examination responses, Thomson Reuters Chat records may remain in scope regardless of when the platform was decommissioned. Gaps in historical capture are a live compliance risk.
  • Platform succession complexity across three brand iterations. Thomson Reuters Chat was succeeded by Eikon Messenger under the Refinitiv brand, which in turn sits within the LSEG data and analytics platform. Firms that have operated the platform across its full lifecycle hold data generated under three different brand and infrastructure iterations — Thomson Reuters, Refinitiv, and LSEG — each with potentially different data formats, metadata structures, and export mechanisms. Compliance archives that treat these iterations separately, or that cover only the most recent platform version, produce fragmented records that cannot support cross-period investigations.
  • Historical capture gaps. Not all firms that operated Thomson Reuters Chat had compliant archiving in place during the period of deployment. Firms that relied on Thomson Reuters’ own data retention tools, or that deployed generic archiving solutions not specifically built for the platform, may have gaps in their historical Thomson Reuters Chat archive. Identifying, remediating, and integrating these gaps into the current compliance programme requires a connector capable of ingesting legacy data as well as supporting ongoing capture.
  • Financial language context for historical surveillance. Surveillance of historical Thomson Reuters Chat data — whether in response to an investigation, an examination request, or a retrospective compliance review — requires AI models that understand the financial context of the communications, not just keyword search across archived text. Generic text search tools are insufficient for the fast-moving, jargon-heavy language of financial messaging; accurate historical surveillance requires the same NLP capability applied to current channels.
  • Cross-channel continuity across the full communication history. Thomson Reuters Chat conversations did not exist in isolation. The same traders and salespeople communicating on TR Chat were simultaneously using Bloomberg IB, email, and voice — often about the same trades and positions. Historical investigations that require a complete picture of communications around a specific event must be able to correlate TR Chat records with Bloomberg IB, email, and other historical channels in a single review workflow.

Key Features of the Shield Thomson Reuters Chat Connector

Historical and Legacy Data Ingestion. Shield ingests Thomson Reuters Chat message records — including historical data generated during the period of Thomson Reuters brand operation — preserving full message content, file attachments, and every metadata field associated with each communication. Legacy TR Chat data is indexed and made fully searchable within the Shield platform alongside current-generation channel data.

Full Metadata Preservation. Shield retains and enriches the complete Thomson Reuters Chat metadata layer, including sender and recipient identifiers, conversation thread identifiers, timestamps, message IDs, room and channel context, and participant data. This metadata is preserved in its original form, made fully searchable, and stored as part of the immutable compliance record — ensuring that investigations, regulatory examination responses, and eDiscovery productions are accurate and legally defensible.

Platform Lifecycle Continuity Across TR, Refinitiv, and LSEG. Shield supports ingestion from Thomson Reuters Chat alongside Refinitiv Eikon Messenger and the current LSEG platform into the same unified compliance archive. Firms that have operated the platform across its full lifecycle can maintain a continuous, searchable messaging record spanning all three platform iterations — ensuring that historical TR Chat data is available for investigation and examination alongside current Eikon communications without gaps, fragmentation, or separate access workflows.

Immutable, Audit-Ready Archive. All Thomson Reuters Chat data ingested by Shield is stored in a tamper-evident, WORM-compliant archive with a complete audit trail of every access and action taken on the record. Data is indexed for rapid search and retrieval, supporting regulatory examination responses, eDiscovery requests, and internal investigations. Retention periods are fully configurable to meet jurisdiction-specific requirements — including the six-year standard under SEC Rules 17a-3 and 17a-4, the five-to-seven-year requirements under MiFID II and MAR, and the five-year requirements under CFTC Regulation 1.35.

AI Surveillance Models for Financial Messaging. Shield applies pre-configured AI surveillance models to Thomson Reuters Chat data, targeting behaviours including market manipulation, information leakage, MNPI sharing, front-running, and personal misconduct — calibrated to the specific language patterns of terminal-based financial messaging. This enables firms to apply consistent surveillance standards to historical TR Chat archives, not just to current-generation platforms.

Unified Cross-Channel Surveillance. Thomson Reuters Chat data does not exist in isolation. The same traders and salespeople who used TR Chat were also communicating over Bloomberg IB, email, and other channels — often about the same trades and positions. Shield ingests Thomson Reuters Chat into the same unified compliance platform as every other channel, enabling compliance teams to correlate historical TR Chat records with communications from all other sources in a single investigation workflow. This cross-channel context is essential for complete historical trade reconstruction and defensible regulatory responses.

Data Governance and Chain of Custody. Shield’s Thomson Reuters Chat connector preserves a complete, verifiable chain of custody from ingestion through archiving and retrieval. Every stage of data handling is logged, auditable, and reportable — giving compliance officers and legal teams the confidence that TR Chat records are admissible, complete, and unaltered throughout their lifecycle.

Regulatory Coverage

Thomson Reuters Chat communications are classified as business records subject to capture, retention, and surveillance requirements across multiple regulatory frameworks. The Shield Thomson Reuters Chat connector supports compliance with:

  • SEC Rules 17a-3 and 17a-4 — requiring broker-dealers to capture, preserve, and produce records of all communications related to their business, stored in WORM-compliant, non-rewriteable format with an audit trail, for a minimum of six years.
  • FINRA Rules 4511 and 3110 — requiring member firms to archive all communications relating to their business as such — including email — with written supervisory procedures, supervision requirements, and full audit trail capability in place.
  • MiFID II Article 16(7) and Market Abuse Regulation (MAR) — requiring investment firms to record and retain electronic communications related to orders and transactions for a minimum of five years, with trade reconstruction capability within three days, and to monitor communications for indicators of insider trading, front-running, and market manipulation.
  • CFTC Regulation 1.35 and 17 CFR § 23.202 — requiring swap dealers, major swap participants, and futures commission merchants to retain records of all communications relating to commodity interests and swap transactions as part of a complete audit trail for trade reconstruction.
  • FCA Rules (SYSC 10A and MAR) — requiring FCA-regulated firms to record and retain relevant electronic communications, including email, for a minimum of five years, and to implement effective surveillance arrangements to detect and prevent market abuse.
  • GDPR and applicable data privacy regulations — Shield’s architecture supports data residency requirements and privacy-compliant data handling across jurisdictions, enabling firms with EU operations or EU data subjects to meet GDPR obligations alongside their financial services recordkeeping requirements.

Other Related Connectors

Shield’s connector portfolio spans the full range of eComms channels and trading platforms used across regulated financial institutions. All connectors feed into a single unified compliance platform — so Thomson Reuters Chat data is always reviewed in the context of every other channel your firm uses.

Frequently Asked Questions

Do firms still have compliance obligations for Thomson Reuters Chat records?

Yes. Regulatory retention periods under SEC Rules 17a-3 and 17a-4 require broker-dealers to retain business records for a minimum of six years. MiFID II requires five to seven years. CFTC regulations require five years. For firms subject to ongoing investigations, litigation holds, or examination requests, Thomson Reuters Chat records may remain fully in scope today regardless of when the platform was decommissioned or rebranded. The fact that a platform has been renamed or migrated does not extinguish the retention and production obligation for communications generated on it.

Does Shield support continuity across Thomson Reuters Chat, Refinitiv Eikon Messenger, and the current LSEG platform?

Yes. Shield supports ingestion from Thomson Reuters Chat alongside Refinitiv Eikon Messenger and the current LSEG messaging environment into the same unified compliance archive. Firms that have operated the platform across its full lifecycle can search, investigate, and produce records spanning all three brand iterations in a single unified workflow — without platform switching, data format reconciliation, or separate access workflows for each period.

What data does Shield ingest from Thomson Reuters Chat?

Shield ingests TR Chat message records, file attachments, and the full metadata layer — including sender and recipient identifiers, conversation thread identifiers, timestamps, message IDs, and room and channel context. Legacy data is indexed and made fully searchable within the Shield platform alongside current-generation channel communications.

Which regulations does the Shield Thomson Reuters Chat connector help firms comply with?

The Shield Thomson Reuters Chat connector supports compliance with SEC Rules 17a-3 and 17a-4, FINRA Rules 4511 and 3110, MiFID II, Market Abuse Regulation (MAR), CFTC Regulation 1.35 and 17 CFR § 23.202, FCA SYSC 10A, and applicable data privacy regulations including GDPR — covering Thomson Reuters Chat records within the applicable retention and investigation window.

Can Thomson Reuters Chat records be reviewed alongside Bloomberg IB and other historical channels during an investigation?

Yes, and this is central to the value of the Shield Thomson Reuters Chat connector for historical investigations. Business interactions that are the subject of regulatory examination or litigation frequently span multiple channels — a negotiation may have begun on TR Chat, continued on Bloomberg IB, and concluded over email. Shield ingests Thomson Reuters Chat into the same unified compliance archive as every other channel, enabling investigators to reconstruct the complete communication sequence surrounding any historical event across all channels in a single workflow.

How should firms handle data residency and privacy obligations for legacy Thomson Reuters Chat records?

Historical Thomson Reuters Chat records captured for compliance purposes are subject to the same data residency and privacy obligations as any other business record — including GDPR requirements for firms holding EU data subjects’ personal data in legacy archives. Shield’s cloud-native architecture supports configurable data residency controls and privacy-compliant handling of legacy data, enabling firms to meet their obligations for historical TR Chat records alongside their current communications compliance programme.

Related Terms