What We Mean by 'Client'
Before centralising, ICBCS needs a shared definition of what a Client is. This has been confirmed by Global Markets. A Client is any external or internal legal entity with whom ICBC Standard Bank has a commercial, trading, credit, or operational relationship. Centralisation requires holding both the legal entity view and the relationship view simultaneously.
Legal Entity vs. Client Relationship
Legal Reality
Entity Hierarchy
Asset Manager Group → Asset Manager UK Ltd → Fund A, Fund B, Fund C. Each is a separate legal entity with its own LEI, KYC status, and credit limit. ICBCS contracts, trades, and takes credit risk with a legal entity, not a brand name.
Commercial Reality
Relationship Hierarchy
One Account Executive, one strategic conversation, one wallet size — managed at group level. Entity-level data drives regulatory, risk, and compliance work; group-level data drives commercial, strategic, and coverage work.
Client Segmentation
Every Client carries one segment descriptor, applied by priority. Where an entity could fit multiple categories, the highest-priority segment always wins.
| Priority | Segment | Description |
|---|---|---|
| 1 — Shareholder | Shareholder | Any ICBC or Standard Bank legal entity. |
| 2 — Revenue Client | Revenue Client | Directly revenue generating — clients, borrowers, issuers, sponsors, funds. |
| 3 — Market Counterparty | Market Counterparty | Trading counterparties and liquidity providers. |
| 4 — Infrastructure | Infrastructure | Custodians, nostro providers. |
| 5 — Risk Transfer | Risk Transfer | Insurers, guarantors (e.g., SBLC). |
| 6 — Other | Other | Any other external legal entity. |
Revenue Client Sub-segments
Within Revenue Client, three sub-segments capture lifecycle status. Each demands a date and rationale.
Revenue Client — Active
Full strategic engagement. No review required unless status changes.
Revenue Client — Monitor
Under review. Review date and justification must be recorded explicitly.
Revenue Client — To Exit
Marked for offboarding. Exit date and rationale must be captured.
Client 360 Attribute Domains
The full set of data attributes grouped into seven domains. Each shows the ICBCS source system. The complete register including data owners, stewards, mandatory field flags, and AI eligibility is maintained in the working spreadsheet.
Domain 1
Entity Identity
▼
| Attribute | Description | Most Likely Source |
|---|---|---|
| Legal Entity Name | Full registered name | Salesforce / GLEIF feed |
| LEI | Legal Entity Identifier — mandatory for regulatory reporting and trading | GLEIF automated feed |
| Registration Number | Company / fund registration number | Fenergo |
| Jurisdiction | Country of incorporation | Fenergo / GLEIF |
| Entity Type | Corporate, fund, SPV, trust, etc. | Fenergo |
| Country of Operation | Primary operating jurisdiction — may differ from country of incorporation | Fenergo |
| Country of Risk | Risk classification country — required for credit paper preparation | Adaptiv / internal rating system |
| Ultimate Parent | Top of ownership hierarchy — the entity at the head of the group structure | Salesforce / D&B / Bloomberg |
| Ownership Hierarchy | Full group structure: parent entity, subsidiaries, and affiliates | Salesforce / D&B |
Domain 2
Segmentation & Classification
▼
| Attribute | Description | Most Likely Source |
|---|---|---|
| Client Segment | Single descriptor per taxonomy — highest priority wins | Salesforce (manual, governed) |
| Sub-Segment | Revenue Client sub-type: Active / Monitor / To Exit | Salesforce (manual) |
| Industry / Sector | GICS or SIC code — enables sector-level analytics | Bloomberg / Salesforce |
| Client Tier | Strategic importance rating (Tier 1, 2, 3) — drives coverage prioritisation | Salesforce (manual) |
| Strategic Client Flag | Yes / No — drives executive engagement and board reporting | Salesforce (manual) |
| Onboarding Status | Prospect / Onboarding / Active / Exiting / Exited | Fenergo → Salesforce (sync) |
| Review Date | Next scheduled review — mandatory for Monitor and To Exit sub-segments | Salesforce (manual) |
| Review Rationale | Written justification for current segment status — must be explicit and dated | Salesforce (manual) |
Domain 3
Commercial & Financial
▼
| Attribute | Description | Most Likely Source |
|---|---|---|
| Revenue (Annual) | Actual revenue by year: 2024, 2025, 2026 YTD | Finance / GL system |
| Return on Capital (RoC) | RoC % by client — drives capital allocation decisions | Finance / GL system |
| RORWA | Return on Risk-Weighted Assets — required for credit review and regulatory capital reporting | Finance / GL system + Adaptiv |
| Products in Use | FX, Rates, Credit, Lending, Commodities, Structured Finance. Foundation for cross-sell whitespace. | Murex / Salesforce |
| Wallet Size Estimate | Total estimated client spend across all banks | Manual (initially); third-party feed (later) |
| ICBCS Market Share | Estimated % of total wallet captured by ICBCS — tracked quarterly vs. baseline | Calculated: ICBCS revenue / wallet estimate |
| Business Strategy Summary | Commercial thesis for the relationship — from last annual credit review, owned by AE | Salesforce (manual, AE-owned) |
Domain 4
Credit Workflow Detail
▼
New domain — added from credit team survey responses (Hayden Smith and Christi Kim). Distinct from compliance-oriented fields in Domain 5.
| Attribute | Description | Most Likely Source |
|---|---|---|
| Internal Credit Rating | ICBCS internal credit rating for the entity — primary risk classification | Adaptiv / internal rating system |
| S&P-Equivalent Rating | Internal rating mapped to S&P-equivalent scale — required for credit papers | Adaptiv / internal rating system |
| Sovereign Rating | Sovereign credit rating for the client's country of risk | Rating agencies via Bloomberg |
| Jurisdiction Rating | Credit rating for the client's incorporation or operating jurisdiction | Rating agencies via Bloomberg |
| CRMC Counterparty Status | Credit Risk Management Committee approval status — required for credit paper and trade approval | Internal compliance / credit systems |
| TAC Counterparty Status | Trading Approval Committee status — required for trade execution workflow | Internal compliance / credit systems |
| Credit Limit | Approved counterparty credit limit at entity level | Adaptiv |
| Credit Utilisation | Current exposure against approved credit limit — live feed preferred | Adaptiv (live feed) |
| Group Total Financing Limit (TFL) | Sum of Primary and Trading limits across all group entities with available headroom | Adaptiv |
| Group Total Settlement Limit (TSL) | Sum of settlement limits across all group entities with available headroom | Adaptiv |
| CLAG | Country Limit and Aggregate Group — displayed alongside group TFL and TSL for instant comparison | Adaptiv / internal limit system |
| Facility Purpose Field | For each credit facility: stated purpose, permitted products, and applicable tenors | Adaptiv |
| Credit Risk Appetite Summary | Narrative behind the approved limit — from last annual credit review | Adaptiv / credit platform |
Domain 5
Risk & Compliance
▼
AML risk rating and sanctions screening status are AI-restricted by default — they must not be surfaced by AI to roles outside compliance, regardless of the user's other access rights.
| Attribute | Description | Most Likely Source |
|---|---|---|
| KYC Status | Pass / Fail / In Progress — current KYC state of the entity | Fenergo |
| KYC Next Review Date | Scheduled next KYC refresh date — triggers automated reminder 90 days out | Fenergo |
| AML Risk Rating 🔒 | Low / Medium / High — current AML classification. AI-restricted: not surfaced to non-compliance roles. | AML compliance system |
| Sanctions Screening Status 🔒 | Clear / Flagged / Under Review. AI-restricted at all times. | Sanctions screening system |
| FATCA / CRS Classification | Tax classification for regulatory reporting purposes | Fenergo / Legal |
Domain 6
Regulatory & Documentation
▼
| Attribute | Description | Most Likely Source |
|---|---|---|
| ISDA Master Agreement | Yes / No / In Negotiation — status of master trading agreement | Legal database / ACL |
| CSA in Place | Yes / No — Credit Support Annex status | Legal database / ACL |
| EMIR Classification | Financial / Non-Financial Counterparty — determines reporting obligations | Fenergo / Legal |
| MiFID II Classification | Eligible Counterparty / Professional / Retail | Fenergo / Legal |
| Reporting Obligations | Applicable regulatory reporting requirements across all relevant regimes | Legal / Compliance |
| GTT Documentation Status | Status of documentation managed within GTT — legal transaction management | GTT |
Domain 7
Contacts & Coverage
▼
| Attribute | Description | Most Likely Source |
|---|---|---|
| Key Client Contacts | Name, title, email, phone — the named individuals on the client side | Salesforce (manual); LinkedIn enrichment |
| Account Executive | Primary ICBCS relationship owner — named individual | Salesforce |
| Product Sales Coverage | Named product coverage officers across FX, Rates, Credit, Commodities, Structured Finance | Salesforce |
| Credit Officer | Assigned credit contact for the relationship | Salesforce / Adaptiv |
| Recent Meetings | Date, attendees, summary, and action points — auto-captured from Outlook / Teams | Outlook / Teams → Salesforce (EAC) |
| Open Action Points | Outstanding items from prior meetings, flagged if overdue — visible to full coverage team | Salesforce |
| Group Name / Top Parent | Relationship-level name — displayed in the 360 record header | Salesforce |