SS&C Technologies: trading systems, FX controls and brokerage operations

SS&C’s broker-dealer menu covers omnibus subaccounting, alternatives processing and advisor servicing, with operational capacity for unusual or seasonal business events. These are separate processing services, allowing the buyer to define a particular operational engagement.[4]

The buy-side orientation of Eze matters to a broker assessing distribution access: OEMS helps an investment manager form and allocate orders, review exposures and route execution. Its vendor-neutral API design supports surrounding systems. The published product capabilities are more specific than a general “all-in-one brokerage” description: a dealing frontend, fund accounting and client onboarding are separate procurement questions.[5]

Eze EMS xAPI uses gRPC and supports Windows and Linux. The supplier lists C#/C++, Python, Java, Go and Ruby among compatible language choices. Applications can stage or route orders, work with pairs, lists and baskets, and retrieve balances, positions and executions. Routing reaches available brokers, dark pools, ATSs and MTFs through the EMS network. This is an interface capable of acting on orders, alongside read access to trading information.[15]

The EMS connectivity guide gives starting bandwidth figures of 256K per user and 64K per FIX connection, then explicitly requires a client-specific assessment for data rates, spikes and subscribed services. These are planning guidelines, not throughput or latency guarantees.[16]

Eze’s August 2026 OEMS update reports expanded REST coverage for portfolios, securities, user-defined fields, benchmarks, audit services, trading strategies and bulk positions. That is a separate integration surface from the gRPC EMS xAPI. API selection should follow the operation being automated and the purchased product entitlement.[24]

There is no single SS&C price for this group of services. The 2025 annual report describes service pricing that can depend on managed assets, instrument complexity, accounts, transaction volume and service scope. It describes typical service contracts of one to five years with monthly or quarterly payments and annual automatic renewal, alongside perpetual and term software licences. These are group commercial patterns, not a replacement for a product’s order form.[3]

The March 2025 amendment notice applies to EMS, its APIs, market data and associated interfaces. It expressly preserves agreements that cannot be changed through one calendar month’s website notice. A prospect should establish which signed version and order form will govern; the public amendment is not evidence that every existing customer has identical terms.[13]

Delivery is product-specific. Singularity’s treasury offering is a web platform hosted in SS&C’s private cloud. Its operational scope includes settlement and messaging, so the implementation needs to align transaction capture, payment instructions, rates and downstream processing rather than only replace the dealing screen.[8]

Middle-office services offer three different allocations of responsibility: hosting of technology and batch processing; outsourcing selected functions such as reconciliation or performance reporting; or broader business-process outsourcing. A customer can retain other processes internally. This distinction determines which team operates each daily control and resolves processing exceptions after migration.[11]

The EMS initial term ends after the calendar month following first login, then renews monthly. Termination notice must arrive before the last business day for month-end effect, without refund. Exit requires purging software and market data, with applicable terminal/source fees, taxes and removal costs.[12]

Eze’s DPA addresses Controller Personal Data: after the relevant processing services end, the controller may choose return or deletion, including existing copies, subject to retention required by law or Eze’s relevant policies. It does not specify a universal number of days or a complete export format for every trading record. Data conversion, permitted record retention and operational handover therefore require their own agreed scope.[19]

SS&C’s central directory provides service-specific support routes for Advent, Algorithmics, GlobeOp and other businesses. Its 24/7 statement concerns web support and client portals, where users can log and track tickets, read release notes and consult technical knowledge. Human response and restoration commitments need to be checked against the purchased service.[22]

Advent Managed Services separately advertises around-the-clock support and a communication portal, alongside reconciliation, reporting and performance-maintenance work. The same page says a SOC 1 Type II report has been issued for managed-services environments only. That is a scoped supplier statement; the underlying report and its control exceptions were not supplied in the public page.[21]

EMS permits internal staff, excluding customers. Eze Castle Software LLC is neither broker-dealer nor clearing provider. Market-data redistribution requires Eze/source permission.[12]

Market-data classification is consequential even when a firm uses the same software as an individual. The signup rules restrict nonprofessional status to qualifying natural persons using data personally and outside a business, with further restrictions on regulated functions, third-party assets and redistribution. A brokerage’s software procurement should use the professional route and identify the intended display and downstream use.[14]

The Eze DPA makes the customer controller and Eze processor for covered personal data, or Eze subprocessor where the customer is itself a processor. Processing follows documented instructions and the applicable order. Personal-data breach notice is due without undue delay after awareness; this is not a fixed-hour incident SLA.[19]

The published Eze subprocessor list names affiliates in several jurisdictions and service providers including AWS, Equinix and Abacus. It warns that some entries apply only to a particular service, region or client. Those names therefore identify possible processing participants, not the confirmed location or hosting arrangement of every SS&C product.[20]

SS&C Technologies Holdings, Inc. is the top-level holding company; SS&C Technologies, Inc. is its wholly owned primary operating company. The group is headquartered in Windsor, Connecticut. A purchase must still identify the relevant product affiliate, as the separate Eze agreement demonstrates.[3]

The covered software businesses use the SS&C Advent and SS&C Eze brands; Eze Software is the acquired business name. These names identify parts of SS&C’s wider group, with product-specific agreements.[13][1]

ALTSERVE illustrates the service side of that model: the current offer includes an alternatives operations team and outsourced back-office processing. It is an operational engagement whose scope and handoffs should be defined, rather than an assumption that installing another SS&C application transfers responsibility for the brokerage’s entire back office.[10]

Operator

SS&C Technologies Holdings, Inc.; primary operating company SS&C Technologies, Inc., with product-specific affiliates

Service scope

Institutional trading, FX collateral controls, treasury processing and selected brokerage operations; product-specific scope.

Customer types

Broker-dealers; Banks; Investment managers; Hedge funds

Delivery

SaaS; API; On premises; Managed service

Pricing publication

Quote only

Headquarters

Windsor, Connecticut, United States

Platforms

Eze OEMS; Eze EMS; Eclipse; MarginMan; Singularity FX; ALTSERVE

Pricing scope

Order forms specify product fees; published EMS terms distinguish service, data and broker-connectivity charges.

Implementation

Deployment varies by product, from EMS workstations and APIs to hosted software or outsourced processing.

Support

Product-specific portals and regional EMS contacts; 24/7 managed-services support is a separate scoped offer.

Permissions and regulatory scope

This profile covers technology and operational services. EMS terms distinguish Eze software supply from broker-dealer and clearing functions.

Provider metadata checked 20 Oct 2026Source 1Source 3Source 23Source 5Source 4Source 8Source 15Source 12Source 17Source 11Source 18Source 6Source 7Source 10Source 13

Eze’s August 2026 OEMS update describes enhancements delivered during the first half of that year: internal matching of eligible crosses with pricing controls, coordinated cancellations across OMS and EMS, and synchronised trader ownership across multi-leg orders. It also reports inventory controls against overselling or over-allocation. These are concrete workflow controls; their effect depends on the installed version, configured rules and operating permissions.[24]

Eclipse’s August 2026 update draws an explicit line between modelling and execution. Its capital-flow models generate proposed rebalance trades, which remain editable before staging. No Cross Trade and Duplicate Order templates can operate before or after execution at portfolio or firm level. This documented workflow supports human review of proposed trades rather than implying that every generated portfolio adjustment is automatically sent to market.[25]

The same Eclipse update adds a Trial Balance Workspace with drill-down from balances to journals, four financial-statement views and Excel/CSV exports of summary and detailed data. It supports both dynamic accounting runs and closed-period reporting. These are useful operational exports, although their existence does not establish a full termination migration package.[25]

Within the broader middle-office service, SS&C describes trade affirmation and fails management, voluntary corporate-action instructions and acknowledgements over SWIFT, and collateral workflows for initial and variation margin using cash or securities. These are post-trade processing functions with distinct dependencies on custodians, counterparties and external utilities.[11]

MarginMan’s structured-FX capabilities extend beyond a simple cash balance: the product description includes butterflies, strangles, straddles and script-designed accumulators such as Pivot and TARN. The relevant implementation question is which structures and client rules the institution will enable, with the collateral and pre-trade controls attached to that configuration.[7]