Bloomberg Capture Integration

The Arctera Bloomberg connector is a file-based integration that captures, preserves, and supervises Bloomberg communications, including Instant Bloomberg messages, emails, attachments, and disclaimers, for regulatory compliance, audit, and eDiscovery. It is designed for compliance, legal, and IT teams that require complete and validated records of trading communications.

Request a Demo

/content/eds-arctera/contact-us

style

py-0, pb-0

What Is the Arctera Bloomberg Integration?

The Arctera Bloomberg capture integration processes Bloomberg-generated file sets, including .ib, .msg, .att, and .dscl files, to ingest and standardize trading-related communications. It performs scheduled batch ingestion, validates attachments and disclaimers, and transforms content into complete, archive-ready records for supervision, retention, and discovery.

Within the Arctera Unified Platform, these records are preserved with full context and auditability, enabling compliance, legal, and IT teams to maintain consistent, defensible communication records while managing incomplete or corrupted files through validation and reprocessing controls.

t-body

style

bg-grey

Technical Specifications

The following technical details summarize how the Arctera Bloomberg connector operates within regulated environments and how Bloomberg file sets are ingested, validated, processed, and delivered for downstream 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
9. Regulatory Alignment
Detail
1. File-based integration processing Bloomberg-generated file sets
2. Scheduled batch import of delivered file sets
3. SSH key authentication for file transfer with optional PGP decryption
4. Private cloud or self-hosted Capture deployment connected to Box SaaS
5. Configured archive target within Arctera Unified Platform
6. Requires Bloomberg-generated source files
7. IB messages, emails, attachments, disclaimers, and metadata
8. Applied during validation and processing before archive delivery
9. Supports SEC, FINRA, CFTC, and global communications compliance requirements

style

pt-0

What the Bloomberg Connector Captures

check-circle: Instant Bloomberg Messages (.ib): Captures IB chat messages and invites from Bloomberg-generated file sets.

check-circle: Bloomberg Email Messages (.msg): Captures email communications associated with Bloomberg messaging workflows.

check-circle: Attachments (.att): Captures attachments delivered within Bloomberg file sets when present and validated.

check-circle: Disclaimers (.dscl): Captures Bloomberg disclaimers required for regulatory completeness and audit review.

check-circle: File-Level Metadata: Captures metadata used for routing, filtering, and associating records within workflows.

check-circle: Firm-Level Data Files: Captures firm-level Bloomberg data delivered through configured file sources for processing.

style

pb-0, pt-md

How the Bloomberg Connector Works

The Bloomberg connector operates as a scheduled batch ingestion pipeline that processes Bloomberg-generated file sets, validates completeness, normalizes records, and delivers them into the Arctera Unified Platform archive for supervision, retention, and eDiscovery workflows.

t-b-s

Step 1: File Receipt and Access

Receive Bloomberg-generated file sets from a configured file source within the organization’s environment. Access the file source using SSH authentication and prepare files for ingestion and processing.

Step 2: Decryption and File Preparation

Decrypt source files using PGP where configured and prepare file sets for processing. Ensure required message, attachment, and disclaimer components are available for validation.

Step 3: Validation and Integrity Checks

Validate file sets to confirm attachments and disclaimers are present and correctly associated. Incomplete or corrupted records may be quarantined for review and reprocessing.

Step 4: Normalization and Processing

Transform file-set content into standardized, archive-ready formats. Normalize message structures, metadata, and relationships for consistent indexing and downstream workflows.

Step 5: Policy Processing and Archive Delivery

Apply filters, routing logic, and policy identifiers, then deliver normalized records to the configured archive target within the Arctera Unified Platform.

style

pb-0

Supported Environments

The Bloomberg integration operates within internal Capture deployments that process Bloomberg-delivered file sets. It supports secure ingestion and processing within private or self-hosted environments.

t-b-s

small,bright,shadow

Bloomberg File Delivery Environment

The integration processes Bloomberg-generated file sets delivered to a configured file source. These file sets include IB messages, emails, attachments, disclaimers, and associated metadata. Data availability depends on Bloomberg delivery and file completeness.

Private Cloud and Self-Hosted Capture Deployment

Capture runs within a private cloud or self-hosted environment under organizational control. It accesses file sources, performs validation and normalization, and delivers processed records to the configured 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

Capture Bloomberg broker-trader communications for supervision

Compliance and Risk Teams

When traders communicate through Bloomberg, the Arctera Bloomberg connector captures IB messages, emails, attachments, and disclaimers and preserves them in the Arctera Unified Platform. Teams can supervise trading communications and maintain a complete record required for SEC, FINRA, and CFTC compliance.

alt

Investigate trade-related communications

Compliance and Legal Teams

When investigating trading activity or misconduct, the Arctera Bloomberg connector captures and preserves Bloomberg messages, emails, and attachments. Teams can reconstruct conversations and review associated content, resulting in faster investigations and defensible outcomes.

alt

Apply legal hold and eDiscovery to Bloomberg data

Legal and eDiscovery Teams

When legal matters require review of trading communications, the Arctera Bloomberg connector captures Bloomberg file-set content and preserves it in the archive. Legal teams can search, place data on hold, and produce records, resulting in defensible eDiscovery workflows.

alt

Ensure completeness of regulated communications

Compliance and Audit Teams

When regulatory requirements demand complete records, the Arctera Bloomberg connector validates attachments and disclaimers during

alt

Frequently Asked Questions

t-b-s

What Bloomberg content does the integration capture?

The integration captures Bloomberg-generated file sets including Instant Bloomberg messages and invites (.ib), email messages (.msg), attachments (.att), and disclaimers (.dscl). It also captures metadata used for routing and processing. These file sets are processed and transformed into standardized records for archive storage. Content outside supported Bloomberg file formats is not captured. Capture depends on the completeness of delivered file sets.

Does the integration capture Bloomberg data in real time?

No. The integration processes Bloomberg-delivered file sets through scheduled batch ingestion. Data is captured after files are delivered to the configured file source. This approach ensures that capture does not interfere with Bloomberg platform operations or live communication workflows. The timing of availability depends on file delivery and configured import schedules.

How quickly is Bloomberg data available in the archive?

Bloomberg data becomes available after file delivery and scheduled import runs. The timing depends on when files are generated and

transferred, as well as the configured ingestion schedule. Once processed and normalized, records are delivered to the archive and are immediately available for supervision, search, and eDiscovery workflows.

How is connector access secured?

The integration uses SSH key authentication to access Bloomberg-delivered file sources. Optional PGP decryption can be applied to secure source files during ingestion. These controls ensure that data transfer and access are secured without requiring user-level credentials or in-path interception of communications.

How does Arctera support regulatory audits?

The integration preserves Bloomberg messages, emails, attachments, and disclaimers as normalized records within the archive. Validation controls ensure required components are present, and quarantine and reprocessing workflows allow incomplete records to be corrected. This creates a more complete and defensible record for regulatory audits, investigations, and compliance reviews.

How is the Bloomberg connector deployed?

The connector is configured within Capture using file source settings, authentication configuration, and processing options such as PGP decryption and validation controls. Once configured, scheduled import jobs process file sets and deliver normalized output to the archive target. Deployment occurs within private or self-hosted Capture environments.

How does Arctera differ from native Bloomberg retention?

Bloomberg provides raw file-set data for retention. The Arctera integration processes these file sets, validates attachments and disclaimers, and supports quarantine and reprocessing workflows. It also applies routing and normalization before delivering records to the archive, enabling consistent supervision, retention, and eDiscovery across systems.

style

pb-0