Saphyre: institutional account onboarding and settlement workflows

Saphyre addresses the operational work between an institutional client, its broker, custodian and other service providers. Its capital-markets offering organises account data, documents and outstanding tasks so teams can see what is preventing a relationship from becoming ready to trade. This is particularly relevant where a broker must coordinate legal, credit, tax and settlement setup for multiple funds and counterparties.[1]

Saphyre’s April 2026 Northern Trust announcement illustrates the lifecycle emphasis. It describes expanded, rules-based workflows for Northern Trust’s Investment Operations Outsourcing clients, covering complex account changes and transitions as well as initial opening. Its stated purpose is consistent data, visible responsibilities and auditability across the organisations involved.[14]

The FXall arrangement makes the division of work clear: asset owners and managers share FX account data, while liquidity providers return KYC, tax, credit, legal and operational statuses. Readiness is visible for the particular account and provider. The connection is therefore useful before trading and during account changes; it does not make every counterparty available to every client.[11]

Microsoft’s March 2024 customer story describes Saphyre as an Azure-based cloud application and identifies Defender for Cloud, Sentinel, Intune and Purview within its security and administration stack. This is a dated architectural description, not a customer-specific commitment to a hosting region or recovery time.[15]

Saphyre’s public commercial route is an organisation-specific meeting or demonstration. The pages do not publish a platform price, per-account or per-user rate, API-call charge, minimum spend or standard contract term. Its enquiry page says the first meeting is tailored to the organisation’s needs; a demo request is not evidence of an included trial or free production licence.[20]

The February 2023 website terms expressly exclude the enterprise portal and its products and services, referring those to the customer’s master servicing agreement. The website’s liability, termination and backup language consequently does not establish the corresponding subscription obligations. Commercial renewal, support and exit rights belong to that separate customer agreement.[22]

The asset-servicer workflow starts with custody account details, including market openings, currencies, FX standing instructions, reporting and routing instructions, and corporate-action preferences. Templates reuse that information for other service providers. Bulk maintenance can then add or remove markets, currencies or routing instructions across accounts. This is a shared-data implementation model, not a requirement to re-key the entire account separately for every team.[8]

Aigent adds an alternative intake route. The June 2025 launch describes parsing an email and attachments, extracting data and requesting missing material. Once complete, the request passes to the broker’s operations team for final review and approval, followed by internal API processing.[10]

The product’s legal workflow also accommodates different signing methods. Teams can use DocuSign or download documents for a wet signature, track completion and attach newly opened accounts to existing digital master agreements. Terms may be cloned or amended in bulk across funds and counterparties, with version control maintaining the shared agreement record.[4]

The current company page identifies a Director of Client Success and a Head of EMEA alongside its sales leadership. The public routes below provide business contact and demonstrations. Neither those pages nor the general website terms publish a production incident severity matrix or contractual response and restoration clocks.[16][20]

Securities Funding Management calculates currency obligations from affirmed securities trades, excludes trades covered by custodial standing instructions and can aggregate the remaining requirements at the buy side’s chosen time. The resulting FX requirement goes to an OMS/EMS and its liquidity providers. Saphyre links the FX transaction to the securities allocations it funds, giving the custodian context. The documented allocation of responsibilities places pricing and execution with the selected trading workflow.[7]

For settlement data, Saphyre describes entitlement-based creation and editing, multi-level maker/checker verification and sharing only across an established trading relationship. Instructions are not presented as an unrestricted directory available to every platform user.[5]

The platform lists single sign-on, multifactor authentication, IP allowlisting, encryption, action logging, third-party penetration testing and SOC 2 Type II compliance. These are supplier descriptions of controls; they do not confer a broker licence or guarantee the financial counterparty’s performance.[2]

Saphyre, Inc. was founded in 2017 by Gabino Roche Jr. Its original onboarding and account-management tools became Saphyre1; the company says its SaphyreX post-trade suite followed in 2024. Gabino Roche is listed as CEO and founder, and Stephen Roche as president and co-founder.[16]

In July 2025 Saphyre announced a closed USD 70 million growth-equity investment from FTV Capital, intended to support product development, distribution, international expansion and integrations. The announcement also stated that FTV partner Mike Cichowski would join the board. This was a funding transaction, rather than a published price for an outright acquisition.[17]

FTV’s current portfolio page lists Saphyre as a current investment with an investment year of 2025. HCAP Partners separately announced its equity exit in August 2025; its earlier financing participation belongs to the company’s funding history.[18][19]

Operator

Saphyre, Inc.

Service scope

Institutional account onboarding and maintenance, legal workflows, settlement-instruction controls and post-trade coordination across permissioned counterparties.

Customer types

Brokers and liquidity providers; Investment managers and asset owners; Custodians; Middle-office and other asset servicers

Delivery

SaaS; API

Pricing publication

Not disclosed

Platforms

Saphyre1; SaphyreX; Aigent

Pricing scope

No numerical platform, user, account or API tariff is displayed on the public enquiry pages; the enterprise agreement is separate from website terms.

Implementation

Shared reference-data workflows with firm-specific terminology, task rules and integrations; Aigent is enabled only on request.

Support

Named Client Success and regional leadership; public business-enquiry and demonstration routes.

Permissions and regulatory scope

Workflow software supports institutional KYC, agreement and settlement operations. FX obligations are routed to the firm’s trading system and liquidity providers; the documented role does not establish Saphyre as the executing broker or clearinghouse.

Provider metadata checked 21 Oct 2026Source 1Source 22Source 14Source 8Source 15Source 20Source 2Source 9Source 16Source 7Source 10

The exception dashboard covers more than a confirmation mismatch. Listed triggers include incorrect allocations, inventory or place-of-settlement problems, absent SSIs, incomplete account setup, expired KYC evidence and NAV-related termination events. Buy-side and sell-side post-trade teams can work in context; unresolved issues can be escalated to the front office. Users can then edit allocations and affirm the trade once ready. Affirmation is a workflow state, not proof that cash and securities have already settled.[6]

Saphyre says the agent itself retains no memory. Its platform description separately says submitted data and documents are saved for reuse. Those are different statements about different components; the agent wording is not a deletion promise for the shared account record. In-context communications can be exported for internal compliance monitoring, and the action log records the actor and timestamp.[9][2]

The public privacy notice expressly covers the informational website and excludes the enterprise portal, referring portal processing to the customer’s subscription services agreement. It therefore does not establish a production-record retention period, hosting region, bulk-exit export format or deletion deadline. Those specific service conditions remain separate from the documented communication-export feature.[23]

The planned FICC connection is also separate from clearing membership. Its announced role is transmitting validated onboarding material and reconciling entity/fund data with the Onboarding Hub. The March 2026 release does not establish that a Saphyre account itself grants access to FICC clearing or that the integration is already enabled for every customer.[13]