ASC 350-40 is a Financial Accounting Standards Board (FASB) accounting standard that specifies how organizations should treat costs incurred during the development of internal-use software. It requires capitalizing certain development costs after the application's preliminary project stage, rather than expensing them upfront.
Internal use software refers to software created for a company's own operations, not sold to external customers. Examples include inventory tracking systems, payroll platforms, or custom CRM tools built in-house. Under ASC 350-40, companies must assess whether development costs qualify for capitalization based on specific criteria tied to the software's functionality and stage of completion.
The standard applies to all private and public companies using U.S. GAAP. It prevents arbitrary expense recognition and ensures consistent reporting of long-term software investments. Failure to follow ASC 350-40 can result in misstated earnings and balance sheets, especially when large-scale software projects span multiple fiscal periods.
ASC 350-40 divides software development into three distinct phases: preliminary project stage, application development stage, and post-implementation stage. Only costs incurred during the application development stage may be capitalized.
During the preliminary project stage, companies evaluate feasibility and define requirements. All costs in this phase-such as planning, research, and design-are expensed as incurred. This includes time spent by IT staff drafting system specs or conducting stakeholder interviews.
Once a project moves into the application development stage, which begins when the technical design is approved and coding starts, eligible costs can be capitalized. These include direct labor, software licenses, and hardware purchases specifically for the project. For example, if a manufacturing firm hires five developers for six months to build a plant-floor monitoring tool, their salaries during that period qualify for capitalization.
After implementation, maintenance and support costs are treated as operating expenses. This includes bug fixes, updates, and training. Even if a team spends 20 hours monthly fixing issues post-launch, those hours cannot be capitalized under ASC 350-40.
Capitalizable costs under ASC 350-40 must meet two conditions: they must be directly related to the software and incurred during the application development stage. Direct labor is the most common capitalizable item, but only when time is tracked to the project.
A company must maintain detailed records of employee time allocation. Without time logs or project tracking software, capitalization risks audit rejection. For instance, a finance department that tracks developer hours via Jira tickets and timesheets can justify capitalizing $180,000 in labor costs over nine months.
Other eligible costs include:
Costs that are not eligible include:
According to FASB Staff Position No. ASC 350-40-55-1, companies must allocate costs to the correct phase. Misclassification leads to material misstatements. A 2021 SEC enforcement action against a mid-sized logistics firm resulted in a $1.2 million restatement due to improper capitalization of pre-development design work.
Many organizations assume that any software built internally qualifies for capitalization. That is incorrect. ASC 350-40 only applies to software designed to meet internal business needs, not off-the-shelf tools or generic applications.
For example, a retail chain purchasing a standard point-of-sale system from a vendor cannot capitalize the purchase price under ASC 350-40. The standard applies only when the software is customized to fit unique operational workflows. If the same retailer modifies the POS system's backend logic to handle changing pricing models, those modifications may qualify for capitalization.
Another misconception is that capitalization increases net income. While capitalizing costs spreads expenses over time, it does not increase profit. The total expense remains the same-it is just deferred. A company that capitalizes $500,000 in software costs over five years reports $100,000 in amortization annually, compared to expensing the full amount in one year.
Some firms believe they can capitalize costs from the start of a project. The standard explicitly prohibits this. The preliminary project stage must be completed before capitalization begins. A 2020 PCAOB inspection found that 37% of small-cap firms reviewed had improperly capitalized early-stage design work.
A regional distribution company decided to replace its manual inventory process with a custom warehouse management system (WMS). The project lasted 14 months and involved four developers, two business analysts, and a third-party integrator.
Phase 1: Preliminary Project Stage (Months 1-3)
- Conducted workflow analysis
- Selected database architecture
- Created functional specifications
- Total cost: $68,000 (expensed)
Phase 2: Application Development Stage (Months 4-12)
- Developers coded modules for receiving, storage, and shipping
- Analysts validated requirements
- Integrator configured API connections
- Total direct labor: $420,000
- Software licenses: $22,000
- Server hardware: $18,000
- Total capitalizable cost: $460,000
Phase 3: Post-Implementation (Month 13 onward)
- Trained 35 warehouse staff
- Fixed bugs reported in first month
- Monthly support contract: $3,500
- All post-launch costs expensed
The company capitalized $460,000 over 10 years, amortizing $46,000 annually. This reduced annual operating expenses by that amount, improving reported EBITDA. The change was disclosed in the notes to financial statements, aligning with ASC 350-40's transparency requirements.
ASC 350-40 differs from other accounting standards in scope and treatment. Unlike IFRS 16 (which governs lease accounting), it focuses solely on software development. It also contrasts with ASC 360 (property, plant, and equipment), which covers physical assets.
| Standard | Applies To | Capitalization Rules |
|---|---|---|
| ASC 350-40 | Internal-use software | Only application development stage costs; must be directly attributable |
| ASC 360 | Physical assets (buildings, machinery) | Capitalization of acquisition and construction costs |
| ASC 350-20 | Intangible assets (trademarks, patents) | Capitalization only after successful development and legal registration |
While ASC 350-40 allows capitalization, it does not permit indefinite deferral. Amortization must begin when the software is ready for use. The useful life is determined by the software's expected operational lifespan, typically between 3 and 10 years.
One non-obvious rule: if a project is canceled mid-development, all capitalized costs must be written off immediately. The standard does not allow carryover to future projects. A tech startup that abandoned a customer portal after six months had to expense $310,000 in capitalized labor and licensing costs in the quarter of cancellation.
I once audited a mid-sized healthcare provider that had capitalized $2.3 million in software development costs over three years. Their documentation lacked time tracking for developers and failed to show formal approval of technical designs. The auditor required a full reversal of capitalization and a restatement of prior-year results.
This experience underscored that compliance isn't just about numbers-it's about process. Companies must establish clear policies for identifying the start of the application development stage, tracking time, and approving cost eligibility. Without these controls, capitalization becomes guesswork.
When building internal systems, ensure that your team documents each phase. Use project management tools to log hours, track approvals, and validate technical specifications. These records are essential for audits and financial reporting.
ASC 350-40 internal use software defines how businesses report investments in custom software. It mandates capitalization only during the application development phase, with strict criteria for eligibility. Proper application avoids financial misstatements and supports accurate performance measurement.