The inadequacy is rarely a failure of intent. Investment managers and wealth firms completed IBS identification exercises during the initial implementation phase, produced registers, and secured board acknowledgement. The problem is that the services most commonly selected sit at a level of abstraction that makes it impossible to map their dependencies, set meaningful tolerances, or design scenario tests that genuinely stress their resilience position. The IBS list looks complete because it names all of the firm's activities. What it does not do is identify the specific services where a disruption would cause genuine, material harm to real clients.
That distinction is precisely what the FCA's supervisory lens is now focused on. This article sets out what defensible IBS identification looks like for investment management and wealth firms, where the most common failures in current selections arise, and what the specific evidencing standard requires.
What FCA SYSC 15A.2 Actually Requires
FCA SYSC 15A.2 establishes the IBS identification requirement. The obligation is not to list all the services a firm provides. It is to identify those services where a disruption would cause intolerable harm to clients or counterparties, threaten market integrity, or create risks to the FCA's statutory objectives.
Three elements of that requirement carry specific implications for investment management and wealth firms that are frequently not reflected in initial implementation work.
The first is the customer harm test. An IBS is defined not by what the firm does, but by what would happen to clients if the service were disrupted. For an investment manager, the question is not "do we manage portfolios?" It is "what would happen to our clients if portfolio management were disrupted for 24 hours, 48 hours, or beyond? At what point does disruption cause harm that would be intolerable, irreversible, or that would constitute a material breach of our regulatory obligations?" Identifying an IBS requires working backwards from that harm analysis, not forwards from a service catalogue.
The second is the operational meaningfulness test. FCA SYSC 15A.2.4 requires IBS mapping to trace specific dependencies: people, processes, technology, facilities, and third-party relationships. A service that is defined so broadly that it encompasses multiple distinct operational processes, technology systems, and dependency chains cannot be meaningfully mapped. If an IBS cannot be mapped to a specific set of dependencies that can be stressed in a scenario test, it is too broad to serve the regulatory purpose. The IBS must be defined at a level of granularity that makes dependency mapping tractable.
The third is the review and maintenance obligation. FCA SYSC 15A requires firms to review and update their IBS identification as their operating model evolves. An investment manager that has restructured its client servicing model, migrated to a new portfolio management system, or changed its outsourcing arrangements since completing initial identification in 2022 has a material obligation to confirm that its current IBS selection still reflects its current operating model. The IBS register that was accurate in 2022 and has been carried forward without structured review is not compliant with the ongoing obligation.
The Three Most Common IBS Identification Failures in Investment and Wealth Firms
FCA thematic review activity in the investment management sector in 2025 and 2026 has consistently identified three failure patterns in IBS identification at mid-tier firms. Each pattern appears in a different type of firm, but all three share the same root cause: the IBS was selected for comprehensiveness rather than for customer harm relevance.
Over-broad service categories. The most common pattern across investment managers and platforms is IBS selection at the category level rather than the service level. "Investment Management" as an IBS encompasses portfolio construction, trade execution, settlement, client reporting, and custody reconciliation. Each of these activities has a distinct dependency chain, a distinct failure mode, and a distinct impact on clients. An IBS defined at the category level cannot be mapped to specific dependencies, cannot support meaningful tolerance setting, and cannot be tested in a scenario that genuinely stresses the harm it represents. The FCA specifically reviews whether IBS are defined at a level of granularity that makes the mapping and testing obligations tractable. Category-level selection fails that test.
Services selected for completeness, not harm. Several firms define IBS by mapping their service catalogue and asking "which of these activities should be in the register?" The right question is "which of these activities, if disrupted, would cause harm to clients that we could not tolerate or remediate within a reasonable timeframe?" The answer to the first question produces a long list of operationally important activities. The answer to the second question produces a shorter list of services where the client harm dimension is genuinely material. For a discretionary wealth manager, the second question will typically produce a different list to the first: client on-boarding may be operationally important without being harm-critical, while access to client funds or execution of time-sensitive instructions may be harm-critical even if they represent a small volume of the firm's activity.
Third-party dependencies excluded from selection scope. Investment managers, fund administrators, and platform operators carry material dependencies on custodians, transfer agents, fund accounting providers, and market data suppliers. The services that depend on these third parties are often where the highest harm exposure sits. Firms that selected IBS based on their own activities without examining where third-party failure would create client harm have a selection gap that the FCA's dependency mapping review will surface. The IBS identification process must include a review of where third-party failures would create harm the firm cannot absorb within its tolerance, and those services must be in scope.