UBS’s $13.2bn integration savings are gross while 90% of apps refers to a defined subset

UBS says it has delivered $13.2 billion of gross cost reductions from integrating Credit Suisse and fully decommissioned around 90% of legacy applications selected for closure. Both figures signal substantial progress. Yet the company's own investor presentation defines the savings as a cumulative annualised exit-rate reduction, not $13.2 billion of cash realised or net profit accumulated, while the application percentage relates to an identified in-scope population, not every system operated by the enlarged bank. The distinction changes the way the merger's economics and remaining operational work should be assessed.[1][2]

The quarter ended September 30, 2026 has put UBS close to several planned end-year milestones. It reported strong wealth-management asset flows and an integration programme substantially advanced. The investigative question is not whether the bank made progress—it clearly reports measurable milestones—but what its measurements actually encompass. The first involves the unit of time applied to a cost-saving figure; the second involves the denominator of an IT application count. Neither can be interpreted accurately from a standalone percentage or headline dollar amount.[1][2]

The savings figure is an exit-rate, not cash already earned

UBS's October 28 fixed-income presentation describes $10.7 billion in cumulative annualised exit-rate gross cost reductions at the end of 2025, $13.2 billion by the third quarter of 2026 and a forecast of approximately $13.7 billion by year-end. In this formulation, 'cumulative' refers to progress against an accumulating programme of annualised reductions. It does not mean that $13.2 billion of savings was booked as cash profit across the three years since the Credit Suisse transaction. A run-rate reduction approximates the annual benefit once corresponding changes are fully reflected; the amount already realised during a particular quarter may be different.[1][2]

The arithmetic implied by management's forecast is straightforward: $13.7 billion minus $13.2 billion leaves about $0.5 billion of additional annualised gross savings capacity to deliver after September. That does not mean $500 million will appear in fourth-quarter net profit or cash. Savings may be delivered at different times, and the income statement includes a wider operating base, compensation, litigation, financing costs and revenue changes. An exit-rate target is valuable for comparing programme milestones, but it should not be recorded as if the full annual amount entered the bank's account during the quarter.[1][2]

UBS also said $0.6 billion of additional gross savings was achieved during Q3 itself. A poorly labelled story might add that number to the $13.2 billion and double count it. The disclosed $13.2 billion is the accumulated exit-rate figure after the quarter's savings. The earlier year-end starting point was $10.7 billion; the increase by September was $2.5 billion. This is programme progress measured in one consistent definition, not a set of independent cash receipts to sum together.[1][2]

The separate integration-cost ledger is crucial

The same investor presentation shows cumulative integration-related expenses of approximately $15.2 billion by September 2026, including foreign-exchange effects, compared with $13.4 billion at the end of 2025. It forecasts about $15.7 billion by the close of 2026. That number is not interchangeable with the annualised gross saving. It describes integration-related costs incurred across time, rather than a yearly rate of future expense reduction. Because the two measures have different time dimensions, subtracting $15.2 billion from $13.2 billion and announcing a '$2 billion net loss from integration' would be mathematically neat but economically unsound.[1][2]

The distinction also works in the other direction. A presentation saying '$13.2 billion saved' without mentioning the integration expense programme could exaggerate near-term net benefits. Restructuring a global bank entails systems migrations, legal-entity changes, personnel costs and other one-off expenditures. Whether integration delivers a positive cumulative financial return depends on when gross reductions flow through to operating expenses, what it cost to implement them, the lost or gained revenues associated with restructuring, and how far into the future the improved cost base persists.[1][2]

UBS's footnote adds another comparison constraint: the annualised gross cost figures are presented at constant foreign-exchange rates fixed in September 2023. The integration-expense bars show amounts with and without foreign-exchange effects. Using two differently translated figures as if both were actual-period US-dollar cash entries would introduce a second mismatch on top of the timing problem. The presentation is clear enough to avoid it; an outside reconstruction must be equally clear about rate, period and scope.[1][2]

What 90% of application decommissioning really means

In its quarterly reporting, UBS said that nearly all legacy Credit Suisse applications in scope for decommissioning were no longer used, and around 90% of those applications had been fully decommissioned as of September 30. The qualifying phrase defines the denominator. There is no basis in that statement for claiming that 90% of the combined bank's software was shut down, or that the remaining 10% of the in-scope list represented 10% of technology cost, computing capacity, cyber exposure or transactions.[1][2]

Applications are not equal units of operational importance. One small specialist application might process little data; another may support critical processes, interfaces or regulatory records. A programme can decommission a large percentage by count while having complex remaining work. It can also retire many applications that have already ceased to be used, leaving residual infrastructure and legal dependencies separate from the count. That observation is not evidence of a control weakness at UBS. It is a mathematical limitation of the metric being used: the number of applications is not a risk-weighted measure of the infrastructure estate.[1][2]

There are also different definitions inside the bank's materials. One presentation charts progress on 'NCL applications' to be decommissioned, while the quarterly narrative refers to legacy Credit Suisse applications selected for closure. Without a fully documented mapping of the populations, these percentages should not be treated as conflicting or summed. They may describe distinct subsets or calculation points. The independently verifiable conclusion rests on the wording of the quarterly disclosure: the bank reports around 90% of the specifically identified legacy applications fully decommissioned.[1][2]

Technology integration is not finished when a counter reaches 100%

UBS separately discusses decoupling former Credit Suisse operating entities from infrastructure and progressing legal-entity integration. Those are not identical tasks to closing application instances. A retired application may still leave records, interfaces, backups, regulatory retention duties and contractual dependencies; a transferred customer account may continue to rely on technology operated by the combined group. None of this proves a presently vulnerable system. It simply means that a full integration assessment should examine services and control responsibilities as well as the count of software packages formally switched off.[1][2]

Conversely, it would be unfair to dismiss the application metric because it is imperfect. Removing duplicate systems can reduce maintenance and complexity; migrating customers onto supported platforms can simplify operating controls over time. A 90% measure that is clearly labelled tells readers something real about programme completion within its intended boundary. Its value lies in tracking progress against the original selected population, with changes of scope documented. It should not be stretched into claims about every remaining technology or regulatory risk.[1][2]

Strong operating results do not eliminate accounting distinctions

UBS reported $55.1 billion of Global Wealth Management net new assets in Q3 2026 and invested assets across the group of approximately $7.3 trillion. It also described $12.5 billion in new commitments to its Unified Global Alternatives initiative. These numbers support a separate account of client activity while the integration proceeds. Yet commitments to future fund or alternative-investment vehicles are not the same as settled money already counted in net new assets, nor do they automatically equal assets under management recognised on the balance of the reporting period. The timing and legal nature of a commitment must be established before making such a reconciliation.[1][2]

The bank's profit disclosure also distinguishes reported and underlying performance. Certain legacy legal-settlement gains and integration adjustments can affect the relationship between the two. A high underlying profit-before-tax figure is not proof that gross savings translate one for one into reported earnings. The appropriate examination would take the issuer's reconciliation between reported and underlying income, then identify the integration-specific items explicitly. This report does not treat a management-adjusted measure as a replacement for the statutory results.[1][2]

A critical alternative interpretation deserves testing: perhaps gross annualised reductions are the best available leading indicator of durable value, since the true savings will persist after one-off costs end. That is plausible. But the claim becomes verifiable only when the ongoing expense base actually falls relative to an appropriate baseline while services and regulatory obligations remain intact. It is possible for a business to deliver major cost saves while total expenses rise because of growth, litigation or inflation. The saving project and the consolidated income statement answer different questions.[1][2]

The exact questions for the next disclosure

A useful year-end audit would request the exit-rate gross savings reached, the full-year operating expense base on a comparable currency and accounting basis, cumulative integration expenses, and any residual one-time obligations. It would also seek an unchanged definition for in-scope application closure, a count of remaining critical migrations, and evidence about infrastructure and legal-entity cutover milestones. Those questions focus on governance and economic completeness, not on unpublished technical configurations or exploitable details.[1][2]

UBS's documented achievement is material: the programme was approaching its stated year-end reduction target, with most identified legacy applications shut down. The equally material caveat is that the frequently quoted $13.2 billion and 90% figures do not mean what a casual reading might suggest. They measure annualised gross exit-rate savings and a defined app-retirement population. Both are useful evidence of execution; neither is a complete cash-payback calculation or an assurance that all integration risks have disappeared. The bank's own footnotes make those limits inspectable.[1][2]

Report an error or submit an update