BD-17 — Corporate Services & Resources

Office: Cross-cutting — corporate.

Maturity: Provisional · 10 Service Domains for finance, HR, IT, facilities, procurement, and the corporate-services platform

The Business Domain of the corporate services and resources that run the firm. BD-17 decomposes the firm’s own finance — corporate accounting and controllership, financial planning and analysis, corporate treasury — its tax, both the tax that follows the money it invests and the tax it owes as a business, its people, its technology estate, and its oversight of the outsourced providers it depends on. It is the CFO / CTO / CHRO / COO shared-services-and-resources pillar — the resource base every investing capability runs on. It does not govern the firm — the board, the fund-governance machinery and the accountability reports are BD-16 — and it does not execute the control stack — risk, compliance, audit and the specialist control disciplines are BD-14.

Each Service Domain below is its own file.

Service Domains

The shared-services-and-resources pillar

BD-17’s organising line: it is the firm’s shared-services-and-resources pillar — the corporate functions and resources that run the institution, organised by the executive that owns each.

• The firm’s own finance (the CFO) — SD-17.1 Corporate Accounting & Controllership keeps the books and closes the period; SD-17.2 Financial Planning & Analysis plans the future and explains the variance; SD-17.3 Corporate Treasury manages the firm’s own cash, banking and corporate debt.
• Tax — SD-17.4 Investment & Portfolio Tax (the tax that follows the money the firm invests) and SD-17.5 Corporate Tax (the tax the firm owes as a business). Two distinct tax functions, one for the portfolios and one for the firm.
• People (the CHRO) — SD-17.6 Talent & Human Capital recruits, develops, compensates and retains the staff that are the firm’s capability.
• Technology (the CTO / CIO) — three Service Domains, plan / build / run: SD-17.7 IT Strategy & Enterprise Architecture sets the direction and standards; SD-17.9 Application Portfolio & Engineering builds the software; SD-17.10 IT Operations & Workplace runs the production estate and the workplace. The plan / build / run split reflects how a modern investment manager’s technology function actually decomposes, and brings OpenIM’s IT-management grain into line with BIAN’s IT Management Business Domain.
• Provider oversight (the COO) — SD-17.8 Vendor, Outsourcing & Service-Provider Oversight commercially oversees the outsourced administrators, custodians and vendors the firm depends on.

This is a recognised operating-model pillar — the corporate shared services every firm runs. BD-17 does not govern the firm (BD-16) or execute the control stack (BD-14); it provides the resources and runs the services those domains, and every investing domain, depend on.

Non-overlap — where the boundaries run

Service Domains are non-overlapping by construction. The boundaries inside and around BD-17 worth stating:

• BD-17 vs BD-16 Enterprise Governance & Accountability. BD-17 runs the firm’s corporate services and resources; BD-16 governs the firm and renders account. The accountability reports BD-16 produces consume BD-17’s outputs: SD-16.4 Financial Reporting & Disclosure builds the statutory accounts on the closed corporate ledger from SD-17.1 and the management accounts from SD-17.2; SD-16.3 Regulatory Reporting & Filings draws corporate and capital data from SD-17.1. BD-17 keeps the books and runs the services; BD-16 turns their output into the governed, assured external account.
• BD-17 vs BD-14 Enterprise Risk, Control & Assurance. BD-17 runs the resources; BD-14 controls and assures them. The IT trio (SD-17.7 / SD-17.9 / SD-17.10) plans, builds and runs the technology estate; SD-14.5 Cyber & Information Security is a control over it, SD-14.6 Operational Resilience & Business Continuity a resilience control over the production services SD-17.10 keeps running, SD-14.4 Model Governance & AI Governance the governance over the models built on SD-17.9’s engineering platform. SD-17.6 Talent & Human Capital manages the people; SD-14.2 Corporate Compliance & Conduct governs how they must behave — the code of ethics, personal-account dealing. SD-17.8 Vendor, Outsourcing & Service-Provider Oversight manages the provider relationship commercially; SD-14.7 Internal Control & Assurance reviews the provider’s control-assurance reports. BD-17 is the resource layer; BD-14 is the control layer over it.
• SD-17.1 Corporate Accounting & Controllership vs SD-17.2 Financial Planning & Analysis. SD-17.1 records what happened — the corporate ledger, the period close, the trial balance. SD-17.2 plans the future and explains the difference — the budget, the forecast, the variance analysis. Controllership is a periodic close; FP&A is a continuous planning loop — a different cadence and toolset.
• SD-17.3 Corporate Treasury vs BD-11 Treasury, Cash & Collateral (cross-Business-Domain). SD-17.3 manages the management company’s own money — its operating cash, working capital, corporate debt and intercompany funding. BD-11 manages the funds’ and portfolios’ treasury — their cash, liquidity and collateral. The owner of the cash decides the owner of the capability.
• SD-17.4 Investment & Portfolio Tax vs SD-17.5 Corporate Tax. SD-17.4 is the tax of the portfolios, funds and investors — withholding reclaims, tax characterisation, treaty positions, FATCA / CRS. SD-17.5 is the tax of the firm as a corporate entity — corporation tax, VAT, transfer pricing. The tax that follows the money the firm invests versus the tax the firm owes as a business.
• SD-17.4 Investment & Portfolio Tax vs SD-12.17 Tax-Lot Accounting (cross-Business-Domain). SD-17.4 sets the strategic tax rules — the tax-characterisation framework and the lot-relief-method election — and consumes the lot-level grain. SD-12.17 operates the per-lot accounting under those rules — opening and closing lots, wash-sale adjustment, the per-client tax record. SD-17.4 sets the rules; SD-12.17 runs the lots.
• SD-17.4 Investment & Portfolio Tax vs SD-12.7 Income & Distribution Processing (cross-Business-Domain). SD-12.7 captures the withholding-tax record on the income cash-flow event. SD-17.4 runs the reclaim and owns the investment-tax position. SD-12.7 books the withholding; SD-17.4 pursues what is recoverable.
• The IT trio — SD-17.7 / SD-17.9 / SD-17.10 — plan / build / run. SD-17.7 IT Strategy & Enterprise Architecture sets the technology direction and standards; SD-17.9 Application Portfolio & Engineering builds the software; SD-17.10 IT Operations & Workplace runs the production estate and the workplace. The handovers: SD-17.7’s architecture decisions are SD-17.9’s engineering targets; SD-17.9’s release pipeline produces the artefacts SD-17.10 deploys and runs.
• SD-17.7 / SD-17.9 / SD-17.10 vs SD-13.12 Data Platform & Integration Services (cross-Business-Domain). The IT trio owns the technology estate — the architecture, the application portfolio, the engineering practice, and the production platforms. SD-13.12 is the data estate — pipelines, the warehouse / lakehouse, the integration layer — which runs on the technology estate SD-17.10 operates, conforms to the architecture standards SD-17.7 sets, and uses the engineering practice SD-17.9 governs.
• SD-17.8 Vendor, Outsourcing & Service-Provider Oversight vs SD-12.5 Custody & Safekeeping Oversight (cross-Business-Domain). SD-17.8 is the commercial and relationship-level oversight of a provider — due diligence, the SLA, the outsourcing-risk and concentration assessment, exit planning. SD-12.5 is the operational, asset-level oversight of a custodian — confirming its holdings record, controlling safekeeping accounts. SD-17.8 manages the contract; SD-12.5 watches the assets. The same split applies against SD-12.16 Outsourced-Operations Oversight, which checks the administrator’s processing output — SD-17.8 manages the relationship, SD-12.16 checks the work.

Archetype activation

BD-17 is among the most archetype-neutral Business Domains in the model — every institution keeps its own books, owes its own tax, employs people, runs technology, and oversees providers. What varies is the weight on each Service Domain.

The common core, true of every archetype: the firm’s own books and period close; financial planning and corporate treasury; the firm’s tax and the portfolios’ tax; a human-capital function; a technology estate; oversight of the outsourced providers the firm depends on.

Why the manager-archetype row is split into sub-archetypes. The discriminator the sub-archetype rows divide on in BD-17 is whether corporate finance, tax and people are run in-house or as a subset of a sponsoring body’s — which itself reflects the firm-vs-arm-of-a-group structural shape. A third-party asset manager runs the full set in-house — fee-and-carry-driven corporate finance, cost allocation across funds and strategies, the full tax set, an engineering-significant technology estate, heavy provider oversight. A hedge fund’s BD-17 is idiosyncratic — pod economics, carried interest, deferred compensation, engineering-heavy quant infrastructure, investment tax weighted to fund structuring. A private-markets manager’s BD-17 is dominated by investment tax (fund and vehicle structuring, K-1 / PFIC investor reporting) and GP-commitment treasury, with episodic FP&A. An index / passive manager’s BD-17 is dominated by the technology estate at systemic scale (SD-17.10 / SD-17.9 under SD-17.7’s architecture). The in-house-vs-subset discriminator is what the sub-typing makes visible; collapsing it would assert one corporate-services shape across managers that the operating model — and the carried-interest, K-1 / PFIC and AIFMD / UCITS remuneration regimes — do not have.

Wider-source grounding

Grounded against external industry references:

• The corporate-finance and controllership body of practice — the close calendar, the journal-approval and account-substantiation disciplines, IFRS / national GAAP for the corporate ledger — SD-17.1.
• The management-accounting and FP&A practice — the budgeting cycle, the rolling-forecast discipline, the variance-analysis and cost-allocation methods — SD-17.2.
• The corporate-treasury and corporate-banking practice — the bank-mandate, covenant-monitoring and cash-forecasting disciplines, ISO 20022 and the banking payment rails — SD-17.3.
• The double-taxation treaties, the withholding-tax regimes, FATCA and the OECD Common Reporting Standard, and the fund-tax and vehicle-structuring conventions — SD-17.4; the corporation-tax and VAT / GST regimes and the OECD transfer-pricing guidelines — SD-17.5.
• The remuneration codes — the AIFMD and UCITS Remuneration provisions, the FCA Remuneration Code — and the SMCR senior-accountability regime, over a general human-capital baseline — SD-17.6.
• The IT-management frameworks, attributed across the plan / build / run trio: COBIT for IT governance and TOGAF for enterprise architecture — SD-17.7; the DevOps body of practice and the SDLC disciplines, including the DevOps Research and Assessment “DORA metrics” (deployment frequency, lead time, change failure rate, MTTR) — SD-17.9; ITIL / IT service management — SD-17.10. The EU Digital Operational Resilience Act (DORA, Regulation (EU) 2022/2554) is multi-layered: its ICT-risk-management framework and ICT-governance expectations are SD-17.7’s; its ICT-operations, change-management and incident-classification requirements are SD-17.10’s; its ICT-third-party requirements are SD-17.8’s; and the resilience-testing control is SD-14.6’s. The two “DORAs” are unrelated; the DevOps research is the DORA cited under SD-17.9, the EU regulation is the DORA cited elsewhere across BD-17 and BD-14.
• The outsourcing regulation — the EU outsourcing rules and the EU Digital Operational Resilience Act (DORA, Regulation (EU) 2022/2554) ICT-third-party requirements, the FCA outsourcing rules, the SEC outsourcing rule — SD-17.8.
• BIAN’s split of the corporate function — finance, HR, IT management and procurement modelled as distinct domains beneath a grouping tier — the reference-model precedent for treating corporate services as a Business Domain distinct from governance and from the control stack.

Design notes

• Cross-cutting placement. BD-13, BD-14, BD-16 and BD-17 are all cross-cutting — one corporate office across three of them.
• Elemental Service Domains for the CFO and tax functions. The CFO function decomposes into three elemental Service Domains — SD-17.1 Corporate Accounting & Controllership, SD-17.2 Financial Planning & Analysis and SD-17.3 Corporate Treasury — because record-to-report, planning-and-analysis, and treasury run on different cadences and toolsets. The tax function decomposes into two — SD-17.4 Investment & Portfolio Tax and SD-17.5 Corporate Tax — because the portfolios’ tax and the firm’s own corporate tax have different subjects and different regulation.
• Indirect tax and transfer pricing are Service Operations, not Service Domains. OpenIM’s hierarchy is deliberately shallow — two levels, Business Domain → Service Domain. VAT / GST and transfer pricing are Service Operations within SD-17.5 Corporate Tax, the firm’s single corporate-tax function, not Service Domains in their own right.
• The full plan / build / run IT capability is in scope — SD-17.7 / SD-17.9 / SD-17.10. A modern regulated investment manager is, increasingly, a technology business operating on capital and regulatory permissions; technology management is a substantial CTO / CIO function, and BIAN — OpenIM’s structural parent — models IT Management as a full business domain holding multiple Service Domains for the same reason. The plan layer is SD-17.7 IT Strategy & Enterprise Architecture, the build layer SD-17.9 Application Portfolio & Engineering, the run layer SD-17.10 IT Operations & Workplace.
• Corporate strategy and the firm’s own M&A are out of scope. A capability model decomposes what the firm does operationally, not the act of strategic leadership. Firm-level strategic management is the consumer of BD-17’s resources, not a capability within it.
• One maintained entity. BD-17 consumes fee, carry, cash-flow and ledger data from across the model and produces corporate finance, tax, people and technology artefacts. SD-17.8 maintains PM-03 Fund Administrator.
• Panel-substitution rationale — asset-owner collapse. The single “Asset owner (pension / SWF / endowment)” row collapses DBP and SWF-E — BD-17’s discriminating axis is whether corporate finance and tax are run in-house or as a subset of a sponsoring body’s, not the asset-owner sub-archetype. A DB pension, a SWF and an endowment all sit on the same Partial activation: corporate finance and tax are often a subset of a sponsoring body’s, investment-tax reclaim is light where assets are held tax-exempt, and technology and provider oversight are full. The Insurer keeps its own row (corporate services typically embedded in a larger group function) — it is not included in the collapse, because the group-embedded structure is the insurer’s defining BD-17 shape.

How BD-17 relates to the rest of the model

• Consumes the inputs the corporate services run on — the firm’s fee and carry income from SD-12.11; the withholding-tax records from SD-12.7 and the distribution data (PM-08) for SD-17.4; the data-feed-quality evidence from SD-13.4 and the asset-level custody evidence from SD-12.5 for SD-17.8; E-01 Legal Entity (the firm’s own entities, and the service providers); E-06 Cash Flow Event (the firm’s corporate cash flows); PM-03 Fund Administrator.
• Owns the firm’s corporate-service artefacts as process records — the corporate general ledger and closed trial balance, the budget and management accounts, the corporate treasury position, the investment-tax and corporate-tax positions, the human-capital and compensation records, the technology estate and application-portfolio record, the provider-oversight relationship and SLA record. SD-17.8 maintains PM-03 Fund Administrator. It owns no investment entity.
• Feeds BD-16 (the closed ledger and management accounts behind the statutory accounts and regulatory returns), BD-14 (the third-party risk picture from SD-17.8, consumed by SD-14.1), the regulators and tax authorities (the tax returns and the FATCA / CRS reporting), and every Business Domain that runs on the firm’s technology estate, employs its people, or relies on its corporate finance and treasury.