FINBOURNE: investment data, operational applications and fund servicing

The current offering combines investment management, enterprise data automation and fund servicing. This makes the product scope relevant to investment operations and technology teams as well as portfolio managers. Different modules address different records and work queues.[1]

The IBOR and accounting functions answer related but different questions. The IBOR supports investment-position and lifecycle views; fund accounting adds NAV, accruals and fund-structure processing. An implementation should identify which view each consuming team needs and how its valuation and reporting conventions are configured.[4][6]

LUSID records both the business-effective time of information and the time it entered the system. A correction can therefore preserve the original business date while creating a later system-time version, allowing a user to reconstruct the view before or after the correction. Scope and code together identify most data items; scopes also support access restrictions. Users and automated services receive no access until it is explicitly granted. These mechanisms make historical reconstruction and data entitlements part of the design.[7]

Luminesce is FINBOURNE’s data-virtualization engine. It queries supported sources where the data resides, can combine their results with LUSID data and can write back where the relevant provider supports that operation. It also works independently of LUSID. Users can use SQL-based tools or connect familiar BI applications, including Power BI, Tableau and Excel. Access requires the appropriate licence and permissions; a source needs a supplied or customer-created Luminesce provider.[8]

Production purchasing is negotiated. FINBOURNE’s AWS Marketplace listing offers a 12-month Standard dimension through a Private Offer. Its displayed price is US$0.001 for that dimension, but the public table does not define a commercially usable unit or an institution’s required quantity. It therefore cannot establish an annual platform budget. The agreed offer needs to specify the purchased usage and term; the listing says entitlements expire when the contract ends unless it is renewed or replaced.[13]

A practical integration starts with enablement for the selected source, then an instance in the Integrations dashboard. The configuration exposes imported fields and transformations and permits additional properties while retaining mandatory ones. Each run has a unique identifier and counts mapped, loaded, skipped, failed and missing attributes. Operators can inspect partial loads and error stages. An IntegrationRunEnded event can trigger a workflow or notification, but it is emitted for both success and failure, so the consuming process must inspect the result.[10]

FINBOURNE launched its Forward Deployed Engineering programme on 26 August 2026, with initial engagements already under way. Engineers work within client teams to connect source systems, configure controls and address specific operational processes. The announced approach uses reconciliation to compare migrated records with their sources and retain the control in production. The programme targets a first go-live in three to six months; that is a programme target, not a delivery date established for every contract.[17]

The technical-support guide directs users to Help > Contact Support in the LUSID web application and to Help > Support Inbox for tracking. A ticket should explain the issue and include enough detail to reproduce it. Correspondence remains attached to the ticket, and a closed ticket can be reopened if the problem recurs or the resolution is unsatisfactory. Support may request customer-granted access to relevant data for investigation.[18]

API maturity matters to ongoing support. The release-lifecycle guide distinguishes opt-in Early Access endpoints, Production endpoints and Deprecated endpoints. Production APIs have full documentation and a stated no-breaking-changes policy; Early Access may change with notice. The guide says service-level agreements apply to paid accounts, not trials. It does not publish one response-time or uptime commitment for every customer in that page.[19]

FINBOURNE supplies technology for investment operations. The customer retains the underlying execution, custody and fund-administration arrangements; the evaluation terms place responsibility for necessary authorisations on the customer.[14][5]

FINBOURNE’s February 2025 Data Processing Agreement separates data responsibilities: the customer is controller and FINBOURNE processor, or FINBOURNE is a sub-processor where its customer is itself a processor. The addendum covers customer personal data used in the service and prevails over conflicting main-agreement terms, subject to the specified transfer-clause precedence. On termination it provides for return, deletion or destruction at the customer’s choice, with legal-retention exceptions. These are contractual processing provisions, distinct from the website’s privacy notice.[16]

The current privacy notice, updated in February 2026, identifies FINBOURNE Technology Limited as the operator supplying LUSID as a software service. Its contact page lists London at 1 Carter Lane, EC4V 5ER, with additional offices in Dublin, New York, Brisbane, Sydney and Singapore.[2][20]

The November 2025 Yield Book announcement describes LSEG’s 2021 strategic investment in FINBOURNE and adoption of LUSID. The cited relationship combines platform use, an investment and the later analytics-integration partnership.[11]

Operator

FINBOURNE Technology Limited

Service scope

Investment-data management and software for enterprise data automation, investment records, portfolio/order workflows and fund servicing; clients may adopt modules alongside existing systems.

Customer types

Asset managers; Asset owners; Asset servicers; Hedge funds; Private-market investment teams

Delivery

SaaS; API

Pricing publication

Quote only

Headquarters

London office: 1 Carter Lane, London EC4V 5ER, United Kingdom

Platforms

LUSID; EDM+; Luminesce; FINBOURNE OMS; FINBOURNE IBOR; FINBOURNE Fund Accounting

Integrations

REST APIs; Python, C# and Java SDKs; Luminesce providers; Power BI, Tableau and Excel; Configured third-party data integrations; Alkymi partnership

Pricing scope

Production contracts are negotiated, including Private Offers through AWS Marketplace. Public evaluation pages contain dated 90-day and older 30-day terms; the terms accepted for enrolment govern the trial.

Implementation

Enable selected integrations and external data rights; configure mappings, properties and operational controls, inspect run-level results, and reconcile migrated data. The announced FDE programme embeds engineers in client teams.

Support

LUSID in-app Contact Support and Support Inbox; public knowledge base and API reference. Paid-account service-level terms are distinct from evaluation access.

Permissions and regulatory scope

B2B investment software and data infrastructure. Customer authorisations, execution and custody arrangements remain separate. The cited DPA defines FINBOURNE’s processor or sub-processor role for customer personal data.

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

OMBA provides a named production example. FINBOURNE’s page dated 10 September 2026, with a 9 September release dateline, reports that OMBA had run its agents in production for six months. The listed work includes portfolio reconciliation, performance review, daily loading and quality checks, valuations and portfolio commentary. OMBA combined core agents with custom MCP capabilities. The release says agents call the same APIs and inherit the same entitlements as human users, with calls logged. It reports at least a 20% reduction in operational burden; that is the companies’ stated outcome for this deployment.[21]

The 23 June 2026 Summit Group release describes a different stage: selection of FINBOURNE for a fund-administration programme beginning with its open-ended-fund business. EDM+ was to consolidate instrument, price, holdings and transaction data, with IBOR, fund accounting and transfer agency above that foundation. It supplies evidence of the intended operating scope and migration sequence, rather than confirmation that the entire programme had already gone live.[22]