Investment Bank Business Information Model

An investment bank's data spans advisory deals, trading positions, and client relationships that don't share one shape. This Business Information Model maps the sector's core data entities — foundational, transactional, and informational — and the relationships between them, delivered as an editable Word document.

Why "Client" Isn't One Entity Here

A generic client entity doesn't survive contact with how an investment bank is actually organized. The same corporate client can be an M&A advisory client on one desk, a trading counterparty on another, and a lending client on a third — relationships that information barriers deliberately keep from freely sharing data with each other, so Client-to-Business-Line has to be modeled as a permissioned, siloed relationship, not a single unified record. Deal and Trade are structurally different entities with different lifecycles — a deal runs for weeks or months through origination, diligence, and closing, while a trade executes and settles in days — yet both can reference the same underlying Security, which itself carries overlapping identifiers (CUSIP, ISIN, ticker) that have to resolve to one instrument without collapsing distinct securities into each other. Position data compounds this: the same book of positions gets sliced by desk, by trader, and by legal entity for P&L, risk, and regulatory reporting, and those views disagree if the underlying position entity isn't modeled once and referenced consistently. And a single trade can be booked once but allocated across multiple client accounts after the fact, which means allocation has to exist as its own entity, separate from execution.

What's Inside

• Foundational entities — Client, Security/Instrument, Counterparty, Deal, Employee/Desk
• Transactional entities — Trade, Order Allocation, Deal Milestone, Settlement, Commission/Fee
• Informational entities — Position, P&L Attribution, Risk Exposure, Client Relationship Value
• Entity relationships across advisory, trading, and client domains
• Delivered as an editable Word document

How Teams Use It

• Reference model for CRM, OMS, or risk platform data architecture
• Baseline for client and security master data management
• Guides integration planning across front-, middle-, and back-office systems
• Framework for modeling information-barrier-constrained client data access

Who It's For

Data architects, business architects, and IT leaders at investment banks and broker-dealers who need deal, trade, and client data modeled with the actual organizational and compliance boundaries intact, not flattened into one CRM record.