LSEG Capture Integration

The Arctera LSEG connector is a file-based integration that captures, preserves, and supervises LSEG (formerly Refinitiv) communications, including person-to-person messages, group chats, attachments, and disclaimers, for regulatory compliance, audit, and eDiscovery. It is designed for compliance, legal, and IT teams that require a complete and reviewable record of market communications.

Request a Demo

/content/eds-arctera/contact-us

style

py-0

What Is the Arctera LSEG Integration?

The Arctera LSEG capture integration processes Eikon Messenger and SI Dealing data delivered as structured file sets from LSEG. It ingests messages, attachments, and CSV files through scheduled batch processing, and transforms message content, attachments, and metadata into complete, archive-ready records for supervision, retention, and discovery.

Within the Arctera Unified Platform, these records preserve communication context and structure, enabling compliance, legal, and IT teams to maintain consistent, defensible records while handling nonmatching or unsupported files through validation and quarantine controls.

t-body

style

bg-grey

Technical Specifications

The following technical details summarize how the Arctera LSEG connector operates within regulated environments and how message file feeds are ingested, processed, and delivered for governance workflows.

t-b-s

Attribute
1. Integration Type
2. Data Ingestion Method
3. Authentication Method
4. Deployment Model
5. Archive Destination
6. Supported Editions
7. Captured Scope Summary
8. Policy Enforcement Stage
Detail
1. File-based integration processing LSEG (Refinitiv) message file feeds
2. Scheduled batch import of delivered source files
3. Access to configured file source with optional PGP decryption
4. Private cloud or self-hosted Capture deployment
5. Configured archive target within Arctera Unified Platform
6. Requires LSEG Eikon Messenger / SI Dealing data delivery
7. Messages, chats, attachments, disclaimers, and metadata
8. Applied during Capture processing before archive delivery

style

pt-0

What the LSEG Connector Captures

arrow: Person-to-Person Messages: Captures direct communications between users within LSEG messaging environments.

arrow: Group Chats: Captures multi-participant chat conversations across trading and communication workflows.

arrow: Attachments: Captures files shared within LSEG communications when included in delivered file sets.

arrow: Disclaimers: Captures message disclaimers required for regulatory completeness and audit workflows.

arrow: Message Metadata: Captures timestamps, user information, message IDs, and event types for context and traceability.

style

pb-0, pt-md

How the LSEG Connector Works

The LSEG connector operates as a scheduled batch ingestion pipeline that processes delivered message file feeds, validates and formats records, and delivers normalized output into the Arctera Unified Platform archive for supervision, retention, and eDiscovery workflows.

t-b-s

Step 1: File Feed Delivery

LSEG provides Eikon Messenger and SI Dealing message data as file sets delivered to a configured FTP source or hosted archive environment.

Step 2: File Source Configuration and Access

Configure Capture to access the file source, including folders, optional scripts, and optional PGP decryption for secure file processing.

Step 3: Scheduled File Ingestion

Capture executes scheduled batch import jobs to ingest supported messages.zip, attachments.zip, and CSV files from the file source.

Step 4: Message Processing and Formatting

Apply configurable processing such as merging messages by thread, splitting messages by day, and selecting message body display modes.

Step 5: Normalization, Filtering, and Archive Delivery

Transform message content and metadata into standardized output, apply filters and routing logic, and deliver records to the configured archive target. Nonmatching files may be quarantined.

style

pb-0

Supported Environments

The LSEG integration operates across LSEG external feed and hosted archiving environments with Capture deployed in private or self-hosted infrastructure.

t-b-s

small,bright,shadow

LSEG External Feed and Hosted Archive Environments

The integration processes LSEG message data delivered via FTP-based external feeds or hosted archiving services. It retrieves structured file sets including messages, attachments, and metadata for processing.

Private Cloud and Self-Hosted Capture Deployment

Capture is deployed within a private cloud or self-hosted environment. It processes LSEG file feeds, applies validation and formatting logic, and delivers normalized records to the archive target.

style

pb-3xl, pt-3xl, bg-borange-005

Compliance & Regulatory Use Cases

t-b-s

event-one,no-badge,no-location,no-datetime

Retain LSEG trading communications for compliance

Compliance and Risk Teams

When traders communicate through LSEG platforms, the Arctera LSEG connector captures messages, chats, attachments, and disclaimers and preserves them in the Arctera Unified Platform. Teams can retain communications to meet SEC, FINRA, and CFTC recordkeeping requirements.

alt

Investigate trader conversations and attachments

Compliance and Legal Teams

When investigating trading activity or misconduct, the Arctera LSEG connector captures message content and attachments. Teams can reconstruct conversations and review shared files, resulting in more complete investigations.

alt

Apply legal hold and eDiscovery to LSEG data

Legal and eDiscovery Teams

When legal matters require communication review, the Arctera LSEG connector captures messages, attachments, and disclaimers and preserves them in the archive. Legal teams can search, hold, and produce records for eDiscovery workflows.

alt

Provide audit trail of market communications

Compliance and Audit Teams

When auditors require visibility into communications, the Arctera LSEG connector captures message activity and metadata. Teams can provide a structured and reviewable record of regulated communications.

alt

Frequently Asked Questions

t-b-s

What LSEG (Refinitiv) content does the integration capture?

The integration captures person-to-person messages, group chats, attachments, disclaimers, and associated metadata from LSEG (formerly Refinitiv) file feeds. It processes structured message files and preserves them as normalized records in the archive. Output can include timestamps, user information, message IDs, and attachment references.

Does the integration capture LSEG data in real time?

No. The integration processes delivered file feeds through scheduled batch ingestion. It does not intercept or monitor live communications. Data is captured after it is delivered to the configured file source.

How quickly is LSEG data available in the archive?

Data is available after file delivery and scheduled ingestion runs. Timing depends on the delivery cadence of the LSEG feed and the configured collector schedule. Once processed, records are available in the archive.

How is access to LSEG data secured?

Access is controlled through the configured file source, such as FTP or hosted archive delivery. Optional PGP decryption can be used to secure source files during ingestion.

How does this support compliance and audits?

The integration preserves LSEG communications, attachments, disclaimers, and metadata as normalized archive-ready records. These records support retention, supervision, investigation, and audit workflows.

How is the connector deployed?

The connector is configured in Capture by defining the file source, folders, optional scripts, and decryption settings. Processing options such as message threading and formatting are applied before scheduled ingestion.

How does this differ from native LSEG retention?

LSEG delivers communication data as file feeds or hosted archive exports. The Arctera integration processes these files, applies formatting and normalization, and delivers them to a centralized archive, enabling consistent supervision and review.

style

pb-0