BD-12 — Investment Operations & Servicing

Office: Back.

Maturity: Provisional · 17 Service Domains — the broad back office: IBOR / ABOR, settlement, custody, fund accounting, reconciliation, corporate-action processing, securities lending and proxy operations, plus per-client tax-lot accounting

The Business Domain that keeps the books and completes the processing behind every investment decision. Where the front office (BD-01 to BD-06) decides what to hold and the middle office (BD-07 to BD-11) measures, prices and controls it, Investment Operations & Servicing is the back office: it maintains the two books of record, settles trades, processes the events that change holdings — corporate actions, income, capital calls, distributions — strikes net asset value, reconciles the firm’s records against the outside world, and runs the operational work of custody, proxy voting, securities lending, the derivatives post-trade lifecycle and transfer agency — the fund investor register and investor dealing. It is the domain that turns decisions and market events into a trustworthy, reconciled record of what the firm owns and what it is owed.

Each Service Domain below is its own file: the definition, its Service Operations, the entities it consumes and produces, the external standards it conforms to.

Service Domains

Non-overlap — where the boundaries run

Service Domains are non-overlapping by construction. The boundaries inside and around BD-12 worth stating, because the topics look adjacent:

• SD-12.1 IBOR vs SD-12.2 ABOR — the two books of record. Both maintain a book of holdings (E-04), and the model deliberately keeps them as two Service Domains because the buy-side keeps two books and they are not the same number on the same day. SD-12.1 owns the real-time, intraday view the front office trades against — transaction-driven, updated as orders fill, start-of-day position generation. SD-12.2 owns the official, accounting-basis view — general-ledger posting, accounting rules, the periodic book close — used for NAV, financial reporting and audit. E-04 carries a book discriminator (ibor / abor) precisely so the two are distinct records, not one asserted position. SD-12.1 owns the ibor book; SD-12.2 owns the abor book; SD-12.10 reconciles the two.
• SD-12.6 Corporate Actions vs SD-12.7 Income & Distribution. SD-12.6 processes the event — it captures a corporate action (PB-07), validates it against the holding, manages the key-date calendar, and runs the election for voluntary and choice events. SD-12.7 processes the income receipt — when a dividend or coupon actually pays, SD-12.7 books the cash, runs the accrual, and applies withholding tax. A cash dividend is a corporate action SD-12.6 processes through to its terms; the cash that arrives on payment date is SD-12.7’s. SD-12.6 owns the event and its election; SD-12.7 owns the income cash and its accrual.
• SD-12.7 Income & Distribution vs SD-12.8 Capital Call & Distribution. Both have “distribution” in the name and the overlap is named deliberately. SD-12.8 owns the private-markets fund cash mechanics — processing a capital-call notice (PM-07), funding the drawdown, and capturing a fund distribution (PM-08) including its waterfall split and recallability. SD-12.7 owns income receipt across all asset classes — coupon, dividend, and the booking of the cash leg of a private-market distribution once SD-12.8 has captured the distribution event. SD-12.8 captures and classifies the fund distribution event; SD-12.7 is the income-and-cash receipt engine the cash flows through. The boundary: SD-12.8 is the fund-commitment event processor (PRIV-only); SD-12.7 is the income-receipt processor (BOTH).
• SD-12.9 Fund Accounting & NAV vs BD-09 Performance & Analytics. SD-12.9 strikes the NAV — it maintains the fund-level books, accrues expenses, prices the book, and produces the official net asset value of a vehicle the institution itself operates. BD-09 measures return from the NAV and cash-flow record SD-12.9 and the books produce. SD-12.9 produces the value; BD-09 turns a series of values into a return. SD-12.9 also differs from SD-08 Valuation & Pricing: SD-08 determines the value of an individual holding; SD-12.9 strikes the fund-level NAV that aggregates those holdings, nets fees and expenses, and divides by units.
• SD-12.9 Fund Accounting & NAV vs BD-08 Valuation & Pricing (cross-Business-Domain). BD-08 values the holdings — it produces the per-instrument marks under a governed valuation policy. SD-12.9 strikes the NAV — it takes BD-08’s marks, adds accruals, fees, expenses and the rest of the fund balance sheet, and produces the official net asset value per share or unit. A BD-08-governed, independently-verified set of marks is a precondition of a struck NAV.
• SD-12.7 Income & Distribution Processing / SD-12.8 Capital Call & Distribution Processing vs SD-13.6 GP & Manager Report Ingestion (cross-Business-Domain). SD-13.6 is the unstructured-data on-ramp — it parses the capital-account statement, the quarterly report, the capital-call notice into structured data and validates it. SD-12.7 and SD-12.8 then process the operational event — booking the cash, the accounting, the waterfall. SD-13.6 turns the document into data; BD-12 acts on the event. The split is data-capture versus transaction-processing.
• SD-12.9 Fund Accounting & NAV vs SD-12.2 ABOR. Both are accounting-basis bookkeeping. SD-12.2 maintains the accounting book of holdings for the institution’s own portfolios — the investor-side ledger. SD-12.9 maintains the books and strikes NAV for funds and vehicles the institution operates as a manager or general partner — the fund-administration side. An institution that only invests, and operates no funds of its own, activates SD-12.2 and leaves SD-12.9 dormant. The boundary is whose books: SD-12.2 keeps the investor’s; SD-12.9 keeps the operated fund’s.
• SD-12.11 Expense, Fee & Carry Processing vs SD-12.9 Fund Accounting & NAV. SD-12.9 accrues fees and expenses into the NAV as a line of the fund books. SD-12.11 calculates and verifies the fee, carry and expense amounts — the management-fee computation, the carried-interest waterfall, the independent check of a fee a manager has charged. SD-12.11 produces the amount; SD-12.9 books it. For an investor checking a fee an external manager has billed, SD-12.11 is the verification capability and there is no SD-12.9 involvement at all.
• SD-12.6 Corporate Actions vs SD-12.12 Proxy Voting. A shareholder meeting is announced as a seev-family event alongside corporate actions, and SD-12.6 captures the meeting event. SD-12.12 then owns the voting — ballot processing, vote-policy application, vote execution, and the engagement record. SD-12.6 captures the meeting; SD-12.12 votes it.
• SD-12.12 Proxy Voting vs SD-12.13 Securities Lending. A hard operational interaction, not an overlap: a security out on loan has its voting right transferred to the borrower, so to vote it the lender must recall it before the record date. SD-12.13 owns recall processing; SD-12.12 owns the voting decision that triggers a recall. SD-12.12 decides a vote matters enough to recall; SD-12.13 executes the recall.
• SD-12.13 Securities Lending Operations vs SD-11.8 Securities Finance & Funding (cross-Business-Domain). Securities lending is two Service Domains. SD-11.8 owns the programme and the financing book — whether to lend, on what terms, the operating model, lending-agent oversight, the funding book, and the reinvestment of cash collateral within the reinvestment-risk policy. SD-12.13 owns the operational loan book — loan open, recall and return processing, per-loan collateral management, lending-revenue accounting, and corporate-action handling on loaned securities. SD-11.8 decides and funds; SD-12.13 operates the book. Cash-collateral reinvestment and lending-agent oversight sit in SD-11.8 only; the operational loan book sits in SD-12.13 only.
• SD-12.14 Derivatives Lifecycle Processing vs SD-06.6 Derivatives & OTC Trade Management (cross-Business-Domain). SD-06.6 is front-office: it owns the negotiation and initiation of an OTC or structured derivative trade — booking the trade, referencing the ISDA / CSA. SD-12.14 is back-office: it owns the post-trade lifecycle of that contract — resets and fixings, novation and assignment, portfolio compression, the clearing lifecycle, and termination. SD-06.6 brings the contract into being; SD-12.14 processes its life. The boundary follows the trade / post-trade line, the same split as SD-06.x execution feeding SD-12.3 / SD-12.4 for cash instruments.
• SD-12.14 Derivatives Lifecycle vs SD-11.4 Margin & Collateral Operations (cross-Business-Domain). SD-12.14 processes the contract lifecycle events of a derivative. The collateral and margin against the derivative relationship — margin-call processing, collateral movement, the margin balance (DR-04) — is BD-11’s: SD-11.4 Margin & Collateral Operations. SD-12.14 processes a reset or a compression; the collateral consequence flows to BD-11.
• SD-12.5 Custody & Safekeeping Oversight vs SD-17.8 Vendor, Outsourcing & Service-Provider Oversight (cross-Business-Domain). SD-12.5 is the operational, asset-level oversight of the custodian — confirming the custodian’s holdings record, controlling safekeeping accounts, the day-to-day depositary interaction. SD-17.8 is the commercial, relationship-level oversight of the custodian as a service provider — the SLA, the service-provider due diligence, the outsourcing-risk assessment. SD-12.5 watches the assets; SD-17.8 manages the contract.
• SD-12.15 Transfer Agency & Investor Dealing vs SD-12.8 Capital Call & Distribution Processing. Both process fund investor cash events, and the split is by fund structure. SD-12.15 processes the open-ended registered fund’s investor dealing — subscriptions, redemptions and switches against a struck NAV, and the investor register. SD-12.8 processes the closed-end fund commitment’s cash events — the capital call and the distribution waterfall (PM-07 / PM-08). The two are different processing capabilities for the two fund structures; neither is the other tagged twice.
• SD-12.15 Transfer Agency & Investor Dealing vs BD-15 client management (cross-Business-Domain). SD-12.15 is the operational processing engine — the investor register and the subscription / redemption / switch dealing. BD-15’s client-management cluster (SD-15.13, SD-15.14) owns the commercial relationship with the investor — the servicing, the relationship, the commercial reporting. Transfer-agency processing is operations, BD-12’s; the investor relationship is BD-15’s.
• SD-12.16 Outsourced-Operations Oversight vs SD-12.9 / SD-12.10 / SD-12.5 / SD-17.8. SD-12.16 is the retained-organisation function — the operational oversight a firm keeps when it outsources its middle and back office. It runs against three adjacent capabilities and is none of them. vs SD-12.9 Fund Accounting & NAV: SD-12.9 strikes the NAV and keeps the fund books in-house; SD-12.16 oversees and independently re-performs them (the shadow NAV) when they are delegated to an administrator — a firm activates one or the other per function. vs SD-12.10 Reconciliation: SD-12.10 reconciles the firm’s own records; SD-12.16 reviews the administrator’s own reconciliation and break-resolution process. vs SD-12.5 Custody & Safekeeping Oversight: SD-12.5 oversees the custodian at the asset level; SD-12.16 oversees the administrator’s processing output. vs SD-17.8 Vendor, Outsourcing & Service-Provider Oversight (cross-Business-Domain): SD-17.8 is the commercial and contractual oversight of the provider — due diligence, SLA, exit planning; SD-12.16 is the operational oversight of the provider’s processing. SD-17.8 manages the relationship; SD-12.16 checks the work — the same split as the existing SD-12.5 ↔ SD-17.8 boundary.
• BD-12 vs SD-04.6 Deal Execution & Legal Closing (cross-Business-Domain). SD-04.6 owns the legal closing of a direct deal — the agreement, conditions precedent, signing, completion and the closing funds flow. BD-12 books and settles the resulting position from that closing onward: SD-12.3 / SD-12.4 confirm and settle the cash and securities legs of the closing, SD-12.1 / SD-12.2 record the resulting holding in IBOR / ABOR, SD-12.8 processes the subsequent drawdown and distribution mechanics of any associated fund commitments, and SD-12.5 oversees the custodian’s safekeeping. SD-04.6 completes the deal; BD-12 keeps the books from completion onwards.
• SD-12.12 Proxy Voting & Stewardship Operations vs SD-04.8 Portfolio-Company Stewardship & Value Creation (cross-Business-Domain). SD-12.12 is the minority-shareholder stewardship of a public-equity position — proxy ballot processing, vote-policy application, engagement record. SD-04.8 is active ownership of a controlled or significant direct holding — board representation, operating-partner placement, the value-creation plan. Different ownership positions, different capability: SD-12.12 votes a public-market holding it does not control; SD-04.8 steers a private-market holding the institution controls or significantly influences.

Design notes

• Seventeen Service Domains is a defended count. BD-12 covers the entire back office of an investment manager — the two books of record, the trade-lifecycle leg, fund administration (both halves: SD-12.9 NAV and SD-12.15 transfer agency), the four asset-servicing event processors (corporate actions, income, capital calls, derivatives lifecycle), reconciliation, fee and carry processing, the two stewardship-side operations (proxy voting, securities lending), custody oversight, outsourced-operations oversight, and per-client tax-lot accounting (SD-12.17). Each is a separately-tooled operational discipline with its own external standards, vendors and staff. Folding two together would assert a shared capability that the operating model does not have: an IBOR is not an ABOR (E-04 carries an explicit book discriminator), an open-ended TA register is not a closed-end capital-call processor (SD-12.15 vs SD-12.8), a derivatives-lifecycle event is not a cash-equity settlement (SD-12.14 vs SD-12.4), and per-client tax-lot accounting (SD-12.17) runs at a finer grain than the position-level ABOR (SD-12.2). The count is the consequence of modelling at the right elemental grain.
• Two books of record, two Service Domains. Splitting IBOR (SD-12.1) and ABOR (SD-12.2) is the most consequential structural choice in BD-12. It follows the entity model — E-04 Holding / Position carries an explicit book discriminator — and how the buy-side actually operates: a real-time intraday book the front office trades against, and an official accounting book struck on accounting rules for NAV and audit. They diverge during the day and are reconciled (SD-12.10). Collapsing them into one “position keeping” Service Domain would assert a single position the operating model does not have.
• PUB-tagged operations domains are not absences of capability for private markets — they are dormant. SD-12.4 Trade Settlement, SD-12.6 Corporate Actions, SD-12.12 Proxy Voting and SD-12.13 Securities Lending are tagged PUB because their processing mechanics — DvP settlement, the seev corporate-action calendar, proxy ballots, the stock-loan book — are public-markets operations. A private-markets-only allocator activates SD-12.1 / SD-12.2 / SD-12.3 / SD-12.5 / SD-12.7 / SD-12.8 / SD-12.9 / SD-12.10 / SD-12.11 and leaves the four PUB domains dormant; a listed-equity manager activates the inverse subset. The capability is the same capability; the tag marks where it applies.
• SD-12.8 is the one PRIV-tagged domain and it has no public-markets equivalent: the capital-call-and-drawdown mechanic of a fund commitment is a private-markets-only event type. Public-markets cash settlement is SD-12.4; the two are different processing capabilities, not the same one tagged twice.
• SD-12.14 Derivatives Lifecycle Processing is a Service Domain in its own right rather than being folded into trade processing, because the OTC and cleared post-trade lifecycle — resets, fixings, novations, compression, clearing — is a distinct, separately-tooled operational discipline with its own ISDA CDM lineage, materially unlike the settle-and-forget lifecycle of a cash equity trade.
• SD-12.15 Transfer Agency & Investor Dealing. Transfer agency — the fund investor register and the open-ended-fund subscription / redemption dealing — is a back-office operations capability, not a client-relationship one. It is the transfer-agency half of fund administration, the sibling of SD-12.9.
• SD-12.16 Outsourced-Operations Oversight. The buy-side outsources its middle and back office heavily; what stays in-house is the retained-organisation function — shadow NAV, independent fee verification, oversight of the administrator’s reconciliations. “Accountability cannot be outsourced”: the firm remains responsible and must demonstrate operational control. SD-17.8 oversees the provider commercially and SD-12.5 oversees the custodian’s assets; SD-12.16 owns the operational oversight of the administrator’s processing output. It is core for the asset manager / hedge fund / OCIO archetypes; partial for the asset-owner and wealth-manager archetypes, which outsource less of the operational stack.
• Fund wind-down is the terminal lifecycle of SD-12.9, not a separate Service Domain. Wind-down of an operated vehicle — controlled liquidation, terminal NAV, final audited accounts, terminal distribution and dissolution — is the operational bookend of fund administration, activated by exactly the institutions that operate funds and no others, so it follows SD-12.9’s activation switch rather than warranting a thin, episodic Service Domain of its own. The legal dissolution flows to SD-14.9, the LPAC consent and term extensions to SD-16.1, the final audit to SD-14.8.

Archetype activation

BD-12 separates the archetypes on one decisive switch — does the institution operate funds of its own? An institution that only invests activates the investor-side bookkeeping and leaves fund accounting (SD-12.9) and transfer agency (SD-12.15) dormant; a manager, GP or hedge fund that operates vehicles activates the full set. The public / private subset is a second, orthogonal switch driven by asset-class exposure (the PUB / PRIV tags).

The dormancy of SD-12.9 and SD-12.15 for the pure-investor archetypes is a clean model-is-a-union dormancy, stated in the Non-overlap and Design notes above — not a capability gap.

Wider-source grounding

The decomposition is grounded against external industry references:

• The securities- and investment-operations body of knowledge — the trade lifecycle, settlement, and asset servicing.
• The ISITC operational standards and the SWIFT ISO 15022 / 20022 message standards — behind trade confirmation, settlement and corporate-action processing (SD-12.3 / 12.4 / 12.6).
• The fund-administration model — fund accounting and NAV (SD-12.9) and transfer agency (SD-12.15) as the two halves of fund administration.
• The ISDA CDM and the OTC / cleared derivatives post-trade lifecycle — behind SD-12.14.
• The custody and depositary frameworks (the AIFMD / UCITS depositary regime) — behind SD-12.5.
• The ILPA Capital Call & Distribution Template for the call and distribution notice formats — behind SD-12.8.
• The buy-side platform operations modules (Aladdin, SimCorp, State Street Alpha, SS&C / eFront) as a completeness cross-check.

How BD-12 relates to the rest of the model

• Consumes the core book-of-record and event entities — Holding / Position (E-04, any book — SD-12.10 Reconciliation runs across both ibor and abor; SD-12.5 / SD-12.16 also read both; the live-position operators SD-12.6 / SD-12.7 / SD-12.12 / SD-12.13 read book = ibor; SD-12.9 Fund Accounting strikes the NAV from book = abor), Transaction (E-05), Cash Flow Event (E-06), Valuation (E-07, any method), Portfolio / Mandate (E-03), Legal Entity (E-01) — the public-markets trade-lifecycle and event entities — Settlement Instruction (PB-06), Corporate Action (PB-07), Income Schedule (PB-08) — the private-markets fund entities — LP Commitment (PM-06), Capital Call (PM-07), Distribution (PM-08), Fund & Vehicle (PM-01), Fund Terms (PM-10) — and the derivatives entities — OTC Derivative (DR-02), Master Agreement (DR-03), Margin & Collateral Balance (DR-04).
• Owns the spine of the operating-model entities: SD-12.1 owns E-04 (the IBOR book), E-05 and E-06; SD-12.2 owns the ABOR book of E-04; SD-12.4 owns PB-06; SD-12.5 co-owns the safekeeping partition of E-25 Account (co-equal with SD-11.7 for the cash partition and SD-15.4 for the register partition); SD-12.6 owns PB-07; SD-12.8 owns PM-07 and PM-08; SD-12.9 owns PM-13 Investor Capital Account; SD-12.10 owns E-24 Reconciliation Break; SD-12.12 owns PB-11 Proxy Vote; SD-12.13 owns PB-10 Securities Loan. Where a capability owns no master entity it is recorded explicitly in the SD file.
• Feeds the middle-office measurement and control domains — Investment Risk (BD-07), Valuation & Pricing (BD-08, which consumes the reconciled book), Performance & Analytics (BD-09, which measures return from the NAV and cash record), Investment Compliance (BD-10) — the front office (BD-05 Portfolio Management trades against the IBOR), the treasury domains (BD-11, which funds settlement and capital calls), and is reported through BD-13 (SD-13.10) and to governance and investors through BD-16.