In the technology industry, a common statement appears in the 10-K reports of companies such as Google, Facebook, Snap, Amazon, Spotify, Dropbox, Box, Pinterest, and Lyft: software development costs are not material, so the companies choose to expense them rather than capitalize them. This practice raises a core question: how do these companies conclude that the costs are "not material"? And how do their audit firms (all audited by EY, except Lyft, which is audited by PwC) sign off on this opinion? Conceptually, this is puzzling because these companies are engineering-driven and develop new technology around the clock.

To understand this decision, it is necessary to analyze it from both accounting standards and practical business perspectives. Under U.S. GAAP, development costs for internal-use software should generally be capitalized after reaching a certain level of technological feasibility. However, the standards also allow expensing when the cost amount is not material relative to the company's overall financial metrics. Large technology companies generally choose to expense for the following reasons:

1. Relative Immateriality of Cost Amounts

These companies typically have revenue scales of tens of billions or even hundreds of billions of dollars, and software development costs (especially for internal tools, platforms, or software that does not directly generate revenue) account for a very small proportion of total expenditures. For example, Alphabet, Google's parent company, spends more than $30 billion annually on R&D, but the capitalized costs directly related to internal-use software may account for only a very small proportion. When the amount falls below the materiality threshold (usually 5% of pre-tax profit or 0.5% of total assets), the company can reasonably judge it to be immaterial and thus not require capitalization.

2. The Particularity of Engineering Models

Software development in technology companies often adopts agile iterative models, with continuous integration and continuous deployment (CI/CD) keeping software in a state of constant modification. Capitalization requires a clear distinction between the research phase and the development phase, and costs must be reliably measurable. However, in rapid iteration, many development activities have both research and development characteristics, making it difficult to clearly separate them. For example, a new feature may be used simultaneously for internal testing and external users, leading to ambiguous cost attribution. Therefore, companies tend to treat all related expenditures as current-period expenses to avoid audit risks arising from subjective judgment.

3. The Audit Firms' Logic for Approval

EY and PwC, as auditors, base their opinions on a review of the "immateriality" judgment. Auditors assess whether the company's set materiality level is reasonable and test the accuracy of cost aggregation. Since these companies typically have sound internal controls and expensing is more conservative (it does not overstate assets), auditors often accept this practice. Moreover, if the capitalized amount has a minimal impact on net income (usually less than 1%), auditors will not regard it as a material misstatement.

4. Industry Practice and Comparability

A consensus has formed among large technology companies: expensing is more consistent with the substance of the business and facilitates investor comparison. For example, Facebook and Snap explicitly state in their 10-K filings that their software development costs are "not material" and therefore they do not follow capitalization requirements. This consistency reduces audit complexity and avoids profit fluctuations caused by different accounting policies.

5. Conceptual Paradox and Explanation

Although these companies are centered on engineering innovation, internal-use software (such as internal deployment tools and data analysis platforms) often does not directly generate revenue, and its future economic benefits are difficult to measure separately. The premise of capitalization is that the asset can bring identifiable future benefits, but internal tools typically serve as supporting assets for the overall business, and their benefits cannot be reliably allocated. Therefore, expensing is more consistent with the principle of prudence and also avoids the risk of asset impairment.

In summary, the choice of large technology companies to expense is not an arbitrary decision, but rather the result of cost-benefit analysis, applicability of standards, and communication with auditors. When reviewing, audit firms will focus on whether the company has consistently applied the policy and assess whether its disclosures are sufficient. For investors, understanding this accounting choice helps in more accurately interpreting financial statements and avoiding overestimation of assets or profits.

It is worth noting that this practice is not absolute. If a company develops a significant internal platform (such as Amazon's early AWS), it may meet the capitalization threshold. However, based on current public disclosures, these companies all believe that their internal-use software costs are not material, so expensing is reasonable and accepted by auditors.