Search
Login
Subscribe
Archive
Subscribe
Cash & Chaos
IBM Q3 2026: Software growth and the tax effect
Oct 29, 2026
IBM Q3 2026: Software growth and the tax effect
15
30
00:00
11:49
1×
Listen on
Apple Podcasts
Apple Podcasts
Spotify
Spotify
Pocket Casts
Pocket Casts
Castro
Castro
Transcript
0:00
IBM's software business supplied most of its additional revenue, but lower tax expense supplied much of the jump in after-tax profit.
0:10
Those are two different improvements, and only one tells us directly about selling more software. Welcome to Cash in Chaos.
0:18
We're explaining IBM's third quarter of twenty twenty-six ended September thirtieth and reported October twenty-first. The figures describe that dated report. IBM's businesses have different revenue and cost patterns.
0:32
Software can produce license and subscription revenue. Consulting depends on delivering work for clients with people and utilization central to its economics.
0:43
Infrastructure brings product cycles while financing affects the balance sheet and cash flow presentation.
0:50
A stronger software quarter, therefore, doesn't establish that the entire company has accelerated in the same way.
0:57
We also need to distinguish revenue from businesses IBM already owned, revenue added through acquisitions and large contracts that move between reporting periods. All can contribute to reported growth.
1:10
Only some demonstrate a stronger recurring pace in the preexisting business. The income tax comparison adds a further layer below the operating result, which is why we'll follow both pre-tax and after-tax earnings.
1:25
Software supplied most of the additional revenue. IBM's October twenty-first results show a genuine operating rebound with two qualifications.
1:36
Acquisitions and delayed deals helped software, while an easier tax comparison amplified after-tax growth.
1:43
The company reported seventeen point one zero three billion dollars of revenue versus sixteen point three three one billion dollars a year earlier.
1:53
Software supplied five hundred and ninety-five million dollars of the seven hundred and seventy-two million dollar increase, or approximately seventy-seven percent by our calculation.
2:05
The segment bridge is more useful than applying one growth narrative to the entire group. Software consulting and infrastructure face different buying cycles, delivery costs, and investment requirements.
2:19
Their combined result can improve while a large individual business remains under pressure. The rebound includes deals delayed from second quarter.
2:29
In July, IBM described second quarter revenue headwinds and reported five percent software growth, with transaction processing down eight percent.
2:39
In the third quarter, reported software growth reached eight point two percent and transaction processing grew nine point three percent.
2:48
The September filing says a significant portion of large deals delayed from second quarter closed in third quarter. That is encouraging execution evidence.
2:58
A delayed transaction did not necessarily become a lost customer. It also limits extrapolation.
3:05
A catch-up quarter can benefit from business expected earlier, so the growth rate should not automatically become the next quarter's underlying demand assumption.
3:14
Separating the backlog of delayed deals from new demand makes the comparison more useful. A stable subscription base and a lumpy transactional component can coexist inside software.
3:26
We would read recurring activity and large contract closure together rather than label the whole business either predictable subscriptions or unpredictable one-off sales.
3:38
A tax comparison can change the earnings growth rate without changing the current quarter's customer activity. Imagine the earlier period included a significant tax charge and the current one didn't.
3:49
Even a modest increase in pre-tax profit could then become a much larger increase in after-tax profit.
3:56
The improvement belongs to shareholders, so it matters, but describing all of it as stronger operating execution would be wrong. The same reasoning applies to delayed software deals.
4:08
Closing work that slipped from June is commercially useful, but the catch-up shouldn't automatically become the growth assumption for every following quarter. These aren't reasons to disregard the result.
4:20
They are reasons to identify the source of each part before extrapolating it. The reported continuing operations bridge is particularly clear.
4:30
IBM earned about two point four billion dollars before tax in the prior year quarter, and about two point five billion in this one.
4:38
Tax expense fell from roughly six hundred and eighty-six million dollars to two hundred and ninety-eight million. The resulting after-tax increase was therefore much bigger than the pre-tax increase.
4:50
These are continuing operations figures, not a substitute for every total net income line. Keeping the scope attached prevents a tax bridge from becoming an exaggerated claim about underlying operating margins.
5:04
Confluent contributes revenue and adds a capital allocation test. IBM attributes data growth to Confluent, acquired in March twenty twenty-six. Software's recurring revenue measure also reflects that acquisition.
5:20
The reported increase, therefore, cannot be treated as an entirely organic expansion of IBM's previous product base. Acquired sales are economically real.
5:32
The question is whether the combination earns enough incremental profit and cash to justify the acquisition cost and integration work.
5:41
A purchase can strengthen a platform without making every dollar of acquired revenue an investment success. Conversely, excluding acquisitions from every assessment would ignore the strategy IBM has chosen.
5:56
This distinction also applies to constant currency. Adjusting translation effects improves one comparison but does not remove acquired revenue.
6:06
An analyst who equates constant currency growth with organic growth would still be mixing two different adjustments. Software profit improved while consulting remained a constraint.
6:18
IBM reported software growth of about eight percent with Red Hat up eleven percent, data up nineteen percent, and automation down three percent.
6:28
Consulting revenue was broadly flat, and its gross margin fell to twenty-seven point four percent from twenty-nine point three percent.
6:37
These contrasts are stronger evidence than a general claim that enterprise AI spending lifted every part of the company. Our interpretation is that the mix increasingly matters.
6:49
A software transaction can carry different economics from a consulting engagement requiring delivery capacity and specialized people.
6:58
Consulting can create opportunities for the platform, but that relationship does not guarantee an immediate improvement in its own revenue or margin.
7:07
The counter-evidence to an uncomplicated rebound is therefore inside the portfolio, not only outside it. Broadening the improvement would make the group's growth more resilient.
7:20
Continued weakness in consulting would leave more of the earnings burden on software and infrastructure. The after-tax comparison benefited from a prior year charge.
7:31
Continuing pre-tax income rose sixty-seven million dollars while tax expense fell three hundred and eighty-eight million dollars.
7:40
Continuing after-tax income consequently increased four hundred and fifty-five million dollars.
7:46
The filing primarily attributes the tax difference to a one-time non-cash charge in the third quarter twenty twenty-five associated with US tax legislation.
7:57
That charge did not affect IBM's operating non-GAAP tax expense. This improves the explanation beyond simply observing a lower tax rate.
8:07
The large GAAP earnings increase partly reflects a more difficult prior year comparison.
8:13
It does not imply an equivalent acceleration in the current operating business, and it is not evidence of aggressive current quarter tax accounting.
8:21
The appropriate conclusion is that reported and adjusted earnings tell related but different stories.
8:27
Use the reconciliation to understand the scope, then assess whether the operating improvement survives on a comparable basis. The cash flow definition changes the size of the improvement.
8:39
IBM defines free cash flow after removing financing receivable movements and deducting net capital expenditure, including software investment.
8:49
Using the filing's nine-month reconciliation, operating cash rose two point six three eight billion dollars, but one point nine zero billion dollars of that increase came from the financing receivables line.
9:02
After that adjustment and investment, company-defined free cash flow increased six hundred and five million dollars. The larger operating cash flow growth rate is not wrong.
9:13
It includes a cash movement that IBM's management removes when assessing free cash generation.
9:20
Comparing the two measures without their bridge would overstate how much incremental cash remained after financing activity and investment.
9:29
For an owner-oriented reading, acquisition payments and dividends still need separate attention.
9:35
Free cash flow is not the same as the change in the cash balance or a guarantee that every dollar is available for discretionary distribution. The revenue outlook held, the cash language strengthened.
9:49
July's full-year outlook called for four percent to five percent constant currency revenue growth and about one billion dollars of free cash flow improvement.
9:58
In October, the revenue range stayed at four percent to five percent, while the cash expectation became more than one billion dollars of improvement.
10:08
That is a change in management's cash outlook, not a raised revenue growth range. The unchanged sales range helps frame the rebound.
10:17
Third-quarter execution improved without management turning it into a higher full-year revenue target. The cash language is positive, but its importance depends on delivery against the company's stated definition.
10:31
We would avoid converting qualitative wording into a precise additional dollar forecast.
10:37
The most constructive interpretation combines software growth, completed catch-up deals, and improved expected cash generation rather than attributing everything to a broad AI spending boom.
10:50
Consulting's weaker conversion and the acquired revenue provide useful counterweights.
10:55
The next evidence should show whether new demand replaces the catch up, whether acquired capabilities retain customers on attractive terms, and whether the cash measure improves after its financing adjustment.
11:08
A larger acquired business can add revenue while still earning an insufficient return on its purchase price. A strong sales quarter and a successful acquisition are related questions, not interchangeable conclusions.
11:22
We can recognize the operating rebound while preserving that capital allocation test. That's Cash in Chaos. The original dated company release, filing, and full analysis are linked in the show notes.
11:36
Analysis is by Cash in Chaos research team. This is educational business analysis, not a recommendation to buy or sell shares. This episode uses a synthetic narrator.
New episodes, straight to your inbox.
Subscribe
