Asset Manager Business Information Model

This business information model maps the asset management sector's core data entities — the funds, accounts, holdings, and transactions that portfolio management, operations, and compliance all have to define the same way. Entities are grouped into foundational (reference and master data), transactional (trading and settlement activity), and informational (performance, risk, and reporting) categories, with the relationships between them laid out explicitly. It's delivered as an editable Word document.

Where a Generic Data Model Breaks Down

A generic "customer/product/order" template doesn't survive first contact with a fund's actual structure. A single fund can issue multiple share classes with different fee and currency terms, so "client holds fund" is really "client holds share class," and getting that wrong throws off every NAV and performance calculation downstream. Securities carry overlapping identifiers — CUSIP, ISIN, SEDOL, ticker — that have to resolve to one instrument record without collapsing distinct securities into each other. Benchmarks and fund-of-fund holdings both need effective-dated, look-through relationships — what a benchmark or fund was actually composed of on a given date — that a flat entity list has no way to represent.

What's Inside

• Foundational entities — funds, accounts, securities, counterparties, custodians, benchmarks
• Transactional entities — trades, settlements, corporate actions, subscriptions and redemptions
• Informational entities — positions, performance, risk exposures, NAV, compliance and mandate data
• Entity relationships connecting the foundational, transactional, and informational layers
• Editable Word format — reorganize, rename, or extend entities to match your own architecture

How Teams Use It

• Scope data architecture and master data management programs for portfolio and client data
• Align build-vs-buy decisions for order management, portfolio accounting, and performance systems
• Define integration contracts between front-, middle-, and back-office platforms and custodians
• Provide a shared reference model for onboarding new funds, share classes, or investment vehicles

Who It's For

Built for data architects, business architects, and IT leaders at asset management, wealth management, and fund administration firms who need a sector-specific data model rather than a generic financial services template.