Overview
Corporate and investment banking (CIB) is the division of a bank that serves large corporations, institutional investors, and governments. Unlike retail banking, CIB deals in complex financial products — from syndicated loans and bond issuances to derivatives and structured finance. Understanding how CIB operations work is essential for anyone building tools, processes, or transformation programmes in this space. The operational backbone of a CIB is what turns front-office deal-making into settled, reconciled, and reported transactions. It is a world of high volumes, tight deadlines, and regulatory scrutiny — where even small inefficiencies compound into significant cost and risk.
Organisational structure
A typical CIB is organised into three broad areas: the front office (sales, trading, advisory), the middle office (risk management, compliance, product control), and the back office (settlement, reconciliation, reporting). In practice, the boundaries between these areas are blurring. Modern operations teams increasingly sit closer to the front office, providing real-time support on trade lifecycle management. The Chief Operating Officer (COO) function has grown in importance, often owning technology strategy, vendor management, and transformation alongside traditional operations. Regional structures add another layer of complexity — a global bank may have operations hubs in London, New York, Hong Kong, and Mumbai, each with different regulatory requirements and local market conventions.
The trade lifecycle
Every transaction in a CIB follows a lifecycle: origination, execution, booking, confirmation, settlement, and reporting. In fixed income, a bond trade begins when a salesperson negotiates terms with a client. The trade is executed on a platform or via voice, then booked into a trade capture system. Confirmations are exchanged — increasingly via electronic platforms like MarkitWire or DTCC — and the trade moves to settlement, typically through a central securities depository. Along the way, middle-office teams validate pricing, check risk limits, and ensure regulatory compliance. Each step introduces potential for error, delay, or exception — and it is the operations team's job to manage these exceptions efficiently.
Technology landscape
CIB technology stacks are notoriously complex. A large bank may run dozens of booking systems across asset classes — Murex for derivatives, Calypso for treasury, proprietary systems for structured products. Data flows between these systems through message queues, ETL pipelines, and increasingly through APIs. The challenge is integration: ensuring that a trade booked in one system is correctly reflected in risk engines, accounting ledgers, and regulatory reports. Legacy technology is a persistent constraint — many core systems were built in the 1990s and carry decades of accumulated logic. Modernisation efforts must balance the desire for clean architecture against the reality of deeply embedded business rules.
Regulatory environment
Post-2008 regulation has fundamentally reshaped CIB operations. Basel III and IV impose capital requirements that directly affect how trades are structured and booked. MiFID II in Europe and Dodd-Frank in the US mandate transaction reporting, best execution, and transparency. BCBS 239 requires banks to demonstrate they can aggregate risk data accurately and quickly. For operations teams, this means every process must be auditable, every data flow must be traceable, and every report must be timely. The regulatory burden is not static — new rules around ESG reporting, digital assets, and operational resilience continue to expand the scope of what operations must deliver.