Shield Connectors

Saphyre Connector

Back To Connectors Page

Pre-Trade & Account Onboarding Communications | Connector for Saphyre

Request a Demo

What Is the Shield Connector for Saphyre?

Saphyre is a technology platform purpose-built to digitise and streamline the pre-trade infrastructure workflow — specifically the account onboarding, account maintenance, and legal documentation exchange processes that financial services firms must complete with counterparties, prime brokers, custodians, and other market participants before trading relationships can commence. Used by asset managers, hedge funds, prime brokers, and institutional investors globally, Saphyre replaces the traditionally paper-intensive and manual pre-trade setup process with a digital, AI-assisted platform that manages the exchange of account documentation, standing settlement instructions, ISDA schedules, KYC documentation, and other pre-trade infrastructure records between counterparties.

For regulated financial services firms, Saphyre communications and workflow records represent a specific compliance capture consideration. The messages, notifications, document exchange records, and workflow interactions generated within Saphyre in connection with account onboarding, counterparty due diligence, and pre-trade infrastructure setup may constitute communications related to regulated business activity — particularly where they involve the exchange of information that forms the documentary basis for trading relationships, the communication of standing settlement instructions, or discussions about legal documentation that governs derivative and other financial transactions. Firms that manage pre-trade infrastructure through Saphyre without integrating relevant communications into the compliance archive may have gaps in their counterparty relationship documentation record.

Shield’s connector for Saphyre ingests communications, workflow records, and associated metadata from the Saphyre platform directly into Shield’s compliance platform, making Saphyre data available for investigation, eDiscovery, and cross-channel context alongside every other channel the firm uses. From the moment relevant Saphyre data enters Shield, it is available within a single unified platform — ensuring that pre-trade infrastructure communications are not siloed from the trading and relationship communications they accompany.

Saphyre data does not exist in isolation. The counterparty relationships documented and onboarded through Saphyre form the foundation for subsequent trading activity, Bloomberg IB conversations, and other regulated communications. Shield ensures that Saphyre workflow records are available alongside those from every other channel in a single, unified investigation and examination workflow.

Why Saphyre Compliance Is Complex

Saphyre communications and workflow records present compliance considerations that reflect the specific nature of pre-trade infrastructure data and its intersection with counterparty relationship documentation, legal agreement administration, and trade regulatory requirements. Several issues arise consistently across regulated firms:

  • Pre-trade documentation as part of the regulatory audit trail. Saphyre manages the exchange of documentation that forms the legal and operational foundation for trading relationships — including ISDA schedules, account agreements, standing settlement instructions, and KYC documentation. This documentation is potentially material to trade reconstruction, counterparty due diligence records, and regulatory examination responses. The communications generated in connection with this documentation exchange — including negotiation messages, approval notifications, and workflow completion records — may constitute business records in scope for regulatory retention.
  • Counterparty onboarding and KYC compliance. Saphyre facilitates the exchange of KYC and due diligence documentation between counterparties as part of the account onboarding process. The communications generated in this process — including requests for documentation, receipt confirmations, review notifications, and onboarding completion records — may form part of the firm’s counterparty KYC compliance record, subject to AML record retention requirements alongside the underlying documentation.
  • Platform-specific workflow data and integration complexity. Saphyre’s workflow-driven architecture generates data in a format specific to the pre-trade infrastructure context — with workflow events, document status updates, counterparty identifiers, and agreement type references that differ from the message-centric data models of standard eComms channels. Archiving solutions designed for messaging data may not correctly handle or contextualise Saphyre’s workflow event data.
  • Cross-platform integration and data completeness. Saphyre integrates with multiple counterparty systems, prime broker platforms, and custodian networks — generating data flows that span multiple participants and that may require correlation across multiple platform integrations to produce a complete picture of any specific pre-trade onboarding or documentation exchange workflow. Compliance capture must handle this multi-party, multi-integration data environment consistently.
  • Cross-channel continuity. Pre-trade infrastructure negotiations and account onboarding discussions frequently accompany Bloomberg IB conversations, email correspondence, and voice communications about the same counterparty relationships. Compliance architectures that hold Saphyre workflow data separately from these other channels cannot reconstruct the complete picture of a counterparty relationship’s establishment and documentation history.

Key Features of the Shield Saphyre Connector

Complete Saphyre Communication and Workflow Record Capture. Shield captures compliance-relevant Saphyre communications and workflow records within scope — including messaging interactions, document exchange notifications, workflow approval records, onboarding completion records, and status update communications — alongside the full metadata layer generated by the Saphyre platform. All data is ingested in full, with zero data loss.

Full Workflow Metadata Preservation. Shield retains and enriches the complete Saphyre metadata layer — including counterparty identifiers, account and agreement type references, workflow stage and status data, document exchange records, participant identifiers, timestamps, and workflow event context. This workflow-level metadata is preserved in its original form, made fully searchable, and stored as part of the immutable compliance record — ensuring that Saphyre records are interpretable in their correct pre-trade infrastructure and counterparty relationship context.

Granular Compliance Scope Configuration. Shield supports the application of granular, record-type-specific compliance policies to Saphyre data — enabling firms to capture and archive Saphyre communications that are genuinely compliance-relevant (counterparty onboarding records, KYC documentation exchange, ISDA and agreement workflow records) while applying appropriate retention policies to routine workflow status notifications that fall outside the regulatory perimeter.

Immutable, Audit-Ready Archive. All Saphyre data captured 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 counterparty due diligence 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 applicable AML record retention requirements.

Unified Cross-Channel Counterparty Relationship Record. Saphyre data does not exist in isolation. The counterparty relationships documented through Saphyre are the foundation for the trading and communication activity that follows — Bloomberg IB conversations, FX Connect executions, ICE Chat negotiations, and email correspondence with the same counterparties. Shield ingests Saphyre data into the same unified compliance platform as every other channel, enabling compliance teams to correlate pre-trade infrastructure records with the trading and communication activity they underpin.

Data Governance and Chain of Custody. Shield’s Saphyre 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 Saphyre records are admissible, complete, and unaltered throughout their lifecycle.

Regulatory Coverage

Saphyre communications and workflow records that relate to regulated business activity are subject to applicable retention and production requirements under multiple regulatory frameworks. The Shield Saphyre 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 — applicable to Saphyre communications and workflow records that constitute business records in connection with regulated counterparty relationships and trading activity, stored in WORM-compliant format for a minimum of six years.
  • CFTC Regulation 1.35 and 17 CFR § 23.202 — requiring swap dealers, major swap participants, and futures commission merchants to maintain records of communications relating to swap transactions — applicable to Saphyre workflow records involving ISDA documentation, swap counterparty onboarding, and related pre-trade infrastructure for derivatives activity.
  • MiFID II Article 16(7) — requiring investment firms to retain electronic communications related to orders and transactions — applicable to Saphyre records documenting pre-trade infrastructure setup that forms the operational basis for MiFID II-regulated transaction execution.
  • AML Record Retention Requirements (UK MLR 2017, BSA, and FATF) — applicable to Saphyre records that form part of the firm’s counterparty KYC and due diligence documentation, subject to minimum five-year AML record retention requirements following the end of the business relationship.
  • FCA Rules (SYSC 10A) — requiring FCA-regulated firms to retain relevant electronic communications and to maintain adequate records of business relationships and regulated activities — applicable to Saphyre workflow records in the context of FCA-regulated trading and counterparty relationship management.
  • GDPR and applicable data privacy regulations — Shield’s architecture supports data residency requirements and privacy-compliant data handling, applicable to Saphyre records that may contain personal data of counterparty representatives and beneficial owners.

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 Saphyre data is always reviewed in the context of every other channel your operations and trading teams use.

Frequently Asked Questions

How does the Saphyre connector differ from the CLM Portal connector? Both the Saphyre and CLM Portal connectors address counterparty or client documentation and onboarding record compliance, but in different contexts. The CLM Portal connector captures client lifecycle management records, with a focus on retail and institutional client onboarding, KYC, and AML compliance. The Saphyre connector captures pre-trade counterparty infrastructure records — focusing on account setup, legal documentation exchange, and operational onboarding for trading counterparties, prime brokers, and custodians. For firms that use both a CLM platform and Saphyre, both connectors may be relevant.

Which regulations does the Shield Saphyre connector help firms comply with?

The Shield Saphyre connector supports compliance with SEC Rules 17a-3 and 17a-4, CFTC Regulation 1.35 and 17 CFR § 23.202, MiFID II Article 16(7), UK MLR 2017 and BSA AML record retention requirements, FCA SYSC 10A, and applicable data privacy regulations including GDPR — to the extent that Saphyre records relate to regulated business activity or fall within the firm’s defined compliance scope.

Can Saphyre data be reviewed alongside Bloomberg IB and other channels during an investigation?

Yes. Shield ingests Saphyre data into the same unified compliance archive as Bloomberg IB, FX Connect, email, and every other channel. Trade reconstruction requests, counterparty due diligence investigations, and regulatory examinations may require access to Saphyre onboarding and documentation exchange records alongside the trading and communication records that followed. Shield enables compliance teams to correlate pre-trade infrastructure records with the full trading communication record in a single workflow.

How should firms approach the compliance scoping of Saphyre data?

Not all Saphyre activity generates compliance-relevant records — routine status updates and administrative workflow notifications may fall outside the regulatory perimeter. Shield supports granular, record-type-specific compliance policies for Saphyre data, enabling firms to define which workflow types, agreement categories, and counterparty relationship records are within compliance scope. Shield’s implementation team can advise on appropriate scoping for each firm’s regulatory profile and Saphyre deployment.

How should firms handle GDPR obligations for Saphyre data?

Saphyre records may contain personal data of counterparty representatives, beneficial owners, and KYC documentation subjects. GDPR obligations — including lawful basis for retention, data subject access rights, and retention limitation — apply to this data alongside financial services recordkeeping and AML retention requirements. Shield’s architecture supports privacy-compliant handling of Saphyre data, including configurable retention periods and data residency controls.

Related Terms