Clearwater Analytics: investment operations, Enfusion and Beacon

Clearwater Analytics supplies investment data, accounting, trading and risk technology to institutional investment teams. Its current family includes the Clearwater investment operations platform, Enfusion for portfolio and order workflows, and Beacon for quantitative development and risk. These components address different jobs within the investment process; a group brand does not by itself define which modules, services or datasets a customer has bought.[3][1][2]

The accounting platform reconciles investment information across custodians, managers and internal systems, then supports books prepared on different bases, including GAAP, statutory, IFRS and tax reporting. Its role-based workflows, approvals and version history are relevant when an accounting adjustment must be explained later. Journal outputs can be mapped into an organisation’s general ledger. Regulatory reporting templates are part of the software’s output capability; the accounting basis, entity perimeter and review process still have to match the reporting institution.[3]

Beacon gives quantitative developers an environment to build, test and deploy their own models alongside supplied components. Its published asset scope includes rates, foreign exchange, credit, commodities, equities and structured instruments. The attraction for a firm with proprietary pricing or risk logic is the ability to inspect and extend models while using shared valuation, scenario and portfolio infrastructure. Model ownership, validation and the approval of production changes therefore belong in the implementation design, rather than being reduced to a choice of risk dashboard.[2]

Clearwater’s data management offering ingests, normalises and reconciles investment information, with lineage and exception handling supporting subsequent use. The integration design should establish which source wins when a custodian, manager and internal system disagree, and where a correction enters the downstream record. Clearwater describes prebuilt connections to data suppliers and investment systems, but the relevant deliverable is the agreed feed, field mapping, reconciliation rule and receiving application for each customer workflow.[5]

Welton Investment Partners provides a useful example of coexistence with an established trading environment. Clearwater’s undated client case records managed-services adoption in January 2021 and a portfolio-management go-live in October 2022. It describes APIs connecting Enfusion with LSEG TORA and Bloomberg, alongside Enfusion’s own execution tools and relationships with prime brokers and administrators. The operating sequence reconciles trades, positions and cash before investment teams rely on the resulting records. The case’s morning processing deadlines describe Welton’s arrangement; they are not a published service commitment for every client. Its practical lesson is that the agreed integration perimeter can preserve external execution applications while centralising investment records and operations.[20]

Enfusion’s public schedules disclose commercial mechanics, while the customer agreement’s Products and Pricing section sets purchased quantities and charges. General Terms version 4.3, effective 17 December 2025, permits an annual 6% increase, normally in January, with first-cycle proration. It also says product-specific terms prevail where they conflict with the general terms. That precedence matters because the currently linked software schedule contains a different escalation formula.[6]

Software Terms version two, effective 1 July 2023, fixes user and service fees for the first year, then specifies the higher of 3% or the stated annual US CPI measure. A quotation should identify the incorporated versions and resolve the applicable formula explicitly.[7]

Enfusion Managed Services is a defined operations engagement. Its December 2023 schedule limits work to the selected tasks and Client Profile components in the agreement. Customers and supporting brokers, custodians or administrators must supply timely, accurate information, while the customer reviews reports and promptly identifies errors. A useful acceptance plan therefore assigns each input, reconciled output and exception to an owner, with the selected service tasks written into the contract. The published framework does not make every back-office function part of a standard subscription.[8]

The Orange and Corgi deployments also illustrate why implementation should follow the investment business. A structured-credit manager needs its instrument and portfolio workflows represented correctly, while an ETF issuer has creation and redemption activity to coordinate with portfolio trading and operations. The releases provide evidence of those different use cases, rather than a universal migration recipe or a fixed number of weeks to production.[18][19]

Support is organised by product. Enfusion publishes workstation and mobile access routes, client-portal access and support contacts; customers can also work through their account manager. Clearwater’s core platform has a support-request route, while Beacon directs existing users to its portal. Keeping the product and affected workflow in the ticket helps route an accounting-data incident differently from an execution-screen or quantitative-development problem.[14][15][16]

The trading workflow can include an external execution provider. Clearwater’s Lombardi Capital case describes orders moving from the portfolio manager to operations for staging and checks, then back for final manager approval before FIX transmission to an outsourced execution desk. The case also distinguishes the fund’s swap trading from cash equities in a separately managed account added in 2025. Those instrument, account and restricted-list differences are represented in the workflow. The example establishes software-supported order preparation and transmission; it does not identify Clearwater as the executing broker or demonstrate a blanket financial-services permission for the group.[21]

Enfusion’s current product page also draws a specific boundary around its AI functions: analysis, compliance simulation and order staging remain subject to human review and approval before execution. An institution evaluating those features should test the approval path and user permissions for its own account structure and order workflow.[1]

Clearwater’s privacy policy, effective 1 January 2026, addresses personal information from website and SaaS users, including processing by service providers and group companies. Its existence does not settle a client’s complete outsourcing or data-residency design. The relevant operational questions are which product receives personal information, which users and service teams need access, and which contractual processing terms cover that deployment.[17]

The current corporate statement identifies Clearwater Analytics, LLC as the US-based parent of Clearwater Analytics, Ltd., its UK subsidiary. Enfusion’s General Terms separately give Enfusion Ltd. LLC as the legal-notice recipient. These names should not be collapsed into a single assumed supplier across all products: the applicable agreement establishes the contracting entity, licensed products and purchased services. The UK statement is signed in April 2026 and covers the financial year ended 31 December 2025.[10][6]

Operator

Clearwater Analytics, LLC and group companies; the contracting entity depends on product and agreement

Service scope

Investment data and accounting infrastructure, with Enfusion portfolio and order workflows, Beacon quantitative risk technology and selected managed operations.

Customer types

Asset managers; Hedge funds; Insurers; Banks; Institutional investment operations teams

Delivery

SaaS; API; Managed service

Pricing publication

Public and quoted pricing

Platforms

Clearwater investment accounting; Clearwater IBOR; Enfusion; Beacon

Integrations

Snowflake Direct Data Access; Custodian and data-vendor feeds; General ledger outputs; FIX execution workflows

Pricing scope

Subscription and service configurations are agreed commercially. Enfusion publishes user, interface, data and service charging conditions, including a dated training rate and differing general/software escalation formulas.

Implementation

Product and workflow-specific data integration, accounting configuration and acceptance. Managed operations cover selected contractual tasks; named completed Enfusion deployments include Orange Investment Advisors and Corgi Funds in 2026.

Support

Separate Clearwater, Enfusion and Beacon support routes. Enfusion software, managed-service and data schedules specify different weekly support windows.

Permissions and regulatory scope

Investment technology and contracted operations. Execution can route to an external broker or desk; product controls, market-data entitlements and a customer’s financial-services permissions remain distinct.

Provider metadata checked 20 Oct 2026Source 10Source 6Source 1Source 2Source 3Source 5Source 8Source 18Source 19Source 14Source 15Source 16Source 21Source 12Source 13Source 7Source 4

The distinction between an investment book and an accounting book affects downstream use. Clearwater’s IBOR incorporates opening positions, trades, orders and anticipated investor or corporate-action cash flows to support trade-date decisions. Projected cash in that view is therefore not necessarily settled bank cash. A dealing team, treasury team and accounting team should agree which time basis and transaction state each report represents before using similarly named balances for different decisions.[4]

Data access and retention also have their own commercial perimeter. Enfusion’s real-time data terms restrict use to the permitted product context rather than granting an unrestricted redistribution or historical-database right. They provide limited reporting-extract exceptions, so those permissions should be assessed against the proposed output. On termination, the schedule calls for cessation of use and removal of covered data and copies, with a destruction certificate available on request. Licensed market data should consequently be identified separately from the customer’s own investment records when designing an export or exit process.[9]