
Jim Chanos warns that AI capital expenditure accounting may artificially boost S&P 500 EPS through 2027. Monitor depreciation trends to verify real growth.
The recent discourse surrounding artificial intelligence capital expenditure has shifted from questioning the validity of the investments to analyzing the mechanical impact on corporate financial statements. Short-seller Jim Chanos recently pointed to a structural quirk in how these massive outlays are treated, suggesting that the current wave of AI spending is poised to artificially inflate earnings per share (EPS) estimates for the S&P 500 through 2026 and 2027.
The core of the issue lies in the divergence between revenue recognition and cost accounting. When major cloud service providers and tech giants deploy billions into AI infrastructure, they are not immediately expensing the full cost of that hardware and data center construction. Instead, these outlays are capitalized, meaning the costs are spread out over the useful life of the assets through depreciation.
Conversely, the revenue generated by the services enabled by this infrastructure is recognized immediately. This creates a temporary mismatch that Chanos describes as a form of profit magic. During periods of aggressive capital deployment, the income statement reflects the full benefit of the new revenue streams while the associated costs are deferred. For investors, this means that EPS growth figures in the near term may be more a function of accounting methodology than pure operational efficiency or organic demand growth.
This accounting dynamic is particularly relevant given the scale of the spending currently underway. JP Morgan has projected a $200 billion surge in AI-related capital spending among top U.S. cloud service providers. This figure is not merely a reflection of operational costs but a strategic commitment to infrastructure dominance. For firms like META, MSFT, and GOOGL, the ability to maintain high EBITDA margins while scaling this infrastructure is the primary metric that separates sustainable growth from speculative bloat.
Analyst Barton Crockett has argued that for companies like Meta, the high capex is justified by the tangible revenue growth and strong EBITDA margins observed to date. This perspective suggests that while the accounting treatment creates a tailwind for EPS, it is supported by actual cash flow generation. The skepticism that previously surrounded AI profitability has largely been replaced by a focus on the return on invested capital. As these companies continue to scale, the market will need to distinguish between earnings growth driven by genuine productivity gains and growth that is simply a byproduct of capitalized depreciation schedules.
Investors should remain cautious about the sustainability of EPS growth if it relies too heavily on the timing of capital expenditures. If the pace of investment slows, the depreciation of previously capitalized assets will begin to hit the income statement more aggressively, potentially creating a drag on future earnings growth. This transition period will be the ultimate test for the current valuation multiples of the major tech players.
Within the current landscape, META holds an Alpha Score of 62/100, while GOOGL sits at 71/100 and MSFT at 64/100. These scores reflect a moderate sentiment, acknowledging both the strength of the underlying businesses and the risks inherent in the massive capital cycles they are currently navigating. Understanding the difference between accounting-driven earnings and cash-flow-driven earnings is essential for any market analysis of the technology sector. The next concrete marker for this thesis will be the evolution of depreciation schedules in upcoming quarterly filings, which will reveal how quickly these massive infrastructure investments are being cycled through the income statement. If revenue growth fails to outpace the eventual rise in depreciation, the current EPS expansion will prove to be a temporary phenomenon rather than a structural shift in profitability.
AI-drafted from named sources and checked against AlphaScala publishing rules before release. Direct quotes must match source text, low-information tables are removed, and thinner or higher-risk stories can be held for manual review.