Deferred revenue on vehicle software features is the portion of a car sale that an automaker cannot recognize as revenue at the moment of delivery because it has promised to keep delivering something — software, connectivity, or services — after the customer drives away. Under the U.S. revenue standard, Accounting Standards Codification Topic 606, Revenue from Contracts with Customers, a single transaction is broken into distinct performance obligations, and revenue is recognized for each obligation only as that obligation is satisfied. The hardware (the vehicle) is delivered up front, so its revenue is recognized when control transfers. But features delivered over time — driver-assistance software updated over the air, in-car internet connectivity, ongoing maintenance of a feature set — are satisfied over a period, so the cash collected for them is parked as a liability called deferred revenue and released into income as the company performs.

Tesla, Inc. lays out exactly this structure in its Annual Report on Form 10-K for the year ended December 31, 2025, filed with the U.S. Securities and Exchange Commission. The filing identifies the recurring software and service elements of a vehicle sale as separate obligations under ASC 606.

"We recognize revenue on automotive sales, net of any discounts or financial subsidies, upon delivery to the customer, which is when the control of a vehicle transfers."— Tesla, Inc., Form 10-K (FY2025), source

What gets deferred, and why

The vehicle revenue is recognized at delivery, but the same sale bundles obligations that are not complete at delivery. Tesla's 10-K describes performance obligations under ASC 606 that include 'access to our internet connectivity, access to our FSD (Supervised) features and their ongoing maintenance, free Supercharging programs and over-the-air software updates.' Each of these is a promise to provide something over time rather than to hand over a finished good once. Because the customer has paid (in the vehicle price or a separate fee) for a benefit the company will deliver across future periods, the matching logic of ASC 606 requires the related revenue to be allocated to those obligations and recognized as they are satisfied — connectivity over the connectivity period, over-the-air updates as they are delivered, and so on. Until then it sits on the balance sheet as deferred revenue.

The scale is not trivial. Tesla discloses a deferred-revenue balance tied to these automotive software and service obligations measured in the billions of dollars, with a beginning-of-period balance of $3,599 million for the year ended December 31, 2025, plus additions during the year as new vehicles with these features are sold. The existence of that balance is what makes the accounting analytically interesting: it represents revenue the company has collected or earned the right to but has not yet recognized, which is simultaneously a future revenue tailwind (it will be recognized in later periods) and a measure of how much of the sale price is contingent on continued delivery of features rather than realized at the point of sale.

The mechanics of how that pool is built and drained are visible in the deferred-revenue rollforward the filing provides. The balance begins each period at a carried-forward amount — $3,599 million entering the year ended December 31, 2025 — and two opposing forces act on it. Additions increase it as new vehicles carrying deferred features are sold and as customers purchase feature access; Tesla discloses additions of $1,083 million during the year. Offsetting those additions, recognition draws the balance down as the company satisfies its obligations over time, delivering connectivity, pushing over-the-air updates, and providing ongoing maintenance of feature sets. The net of additions and recognition, adjusted for changes in liability on pre-existing contracts, determines whether the deferred pool grows or shrinks in a given period. A growing pool generally signals that feature-laden vehicles are being sold faster than past obligations are being recognized; a shrinking pool signals the reverse. Because the additions are tied to vehicle sales and the recognition is tied to feature delivery, the rollforward is the clearest place to see how the software side of the business is accumulating future revenue.

How to read the software-deferral disclosure

For the financial reader, the deferred-revenue footnote on software features answers a question the headline vehicle revenue cannot: how much of an automaker's reported sales is hardware recognized now versus software recognized later. Three elements are worth locating. First, the list of performance obligations, which tells you which features the company treats as delivered-over-time rather than delivered-at-sale; the longer that list, the more of each sale is subject to deferral. Second, the deferred-revenue rollforward — beginning balance, additions, and amounts recognized — which shows whether the deferred pool is growing (more feature-laden vehicles being sold) or being drawn down (past obligations being satisfied). Third, the recognition pattern, since features recognized ratably over a defined period behave differently from features recognized as discrete updates are pushed.

This accounting is also why a software-defined vehicle changes the shape of an automaker's revenue, not just its product. As more of a vehicle's value migrates to features delivered after the sale, a larger share of each transaction lands in deferred revenue and is recognized over time, smoothing and lengthening the revenue tail of a one-time hardware sale. The deferred-revenue balance becomes a running measure of that shift. None of this implies anything about whether the features will be profitable or whether customers will buy them; it simply reflects the ASC 606 requirement that revenue follow the satisfaction of each obligation. Every characterization here — that vehicle revenue is recognized at delivery when control transfers, that connectivity, FSD (Supervised) features and maintenance, free Supercharging, and over-the-air updates are treated as performance obligations, and that the related deferred-revenue balance began the period at $3,599 million — is drawn directly from Tesla's filed Form 10-K, which remains the primary source for the specific figures.