Software Capitalization: CFO Guide to ASC 350-40 & ASU 2025-06

Software Capitalization: CFO Guide to ASC 350-40 & ASU 2025-06

Woosung Chun

Woosung Chun

Woosung Chun is the CFO of DualEntry with experience in corporate finance, accounting, strategy, and acquisitions. He previously grew from scratch and led the M&A and Finance teams at Benitago, where he completed more than 12 acquisitions in 2 years. He graduated with a BS from NYU Stern. At DualEntry, Woosung writes about AI in accounting, revenue recognition, foreign currency accounting, hedge accounting, and ERP modernization for finance teams navigating complex, multi-entity environments.

Learn about our editorial policies.

Last updated

November 5, 2026

Reviewed by

Do San (Justin) Myung

Do San (Justin) Myung

Expert Accountant & Former Consulting CFO

Justin (Do San Myung) is Expert Accountant at DualEntry with 20+ years of hands-on experience managing general ledgers, financial close processes, and ERP implementations for mid-market and enterprise companies. As a former Consulting CFO and Controller, he has personally overseen month-end closes, SOX compliance programs, and multi-entity consolidations across technology, manufacturing, and services industries. Justin specializes in transforming manual accounting workflows into automated, AI-driven processes.

Contents

What is software capitalization?

What costs can you capitalize?

ASC 350-40: the rules for internal-use software

What's changing: FASB ASU 2025-06

Journal entries and amortization

Why capitalization gets scrutinized

Tracking and controls: how to build the evidence that auditors want

How an AI-native ERP handles software capitalization

Capitalizing software is a policy you defend, not a loophole

Software Capitalization FAQs

What is software capitalization?

Software capitalization records qualifying software costs as an asset, not an expense. Build and implementation costs go onto the balance sheet as an intangible asset and amortize over the software’s useful life, instead of reducing the profit in the period you spend the money. You spend the same amount either way. Capitalizing moves the earnings impact into later years.

Two situations put software capitalization front of mind for a finance team. The first is building software you run yourself – it could be your internal systems, or a platform you sell to customers. The second is implementing purchased cloud software, where the SaaS license is a service contract but the implementation work may not be.

Both situations fall under ASC 350-40, the standard we’ll cover in detail later.

What costs can you capitalize?

Capitalization depends on the activity and its stage. Coding, configuration, testing, and installation costs capitalize. Planning, evaluating alternatives, data conversion, training, and maintenance costs expense.

Capitalize vs. expense: which treatment to use and why

Activity / cost Stage Treatment Why
Evaluating alternatives; feasibility Preliminary / planning Expense Too uncertain to be an asset
Coding, configuration, installation Application development Capitalize Directly builds the asset
Testing, interfaces, direct payroll Application development Capitalize Directly attributable cost
Data conversion Any Expense Not part of the asset (generally)
Training Any (expensed whatever the stage) Expense Benefits people, not the asset
Maintenance; bug fixes Post-implementation Expense Sustains, doesn’t add value
Upgrades adding functionality New development Capitalize Creates new/expanded value
Cloud/SaaS implementation (config, integration) Application development (per ASU 2018-15) Capitalize Amortize over the hosting term

Four things to keep in mind when deciding:

  1. Direct payroll: Salary, benefits, and contractor fees capitalize for people doing the work that builds the software.
  2. Data conversion: The costs of cleaning and migrating old data are expensed unless software is written specifically for that purpose.
  3. Upgrades vs maintenance: New functionality capitalizes; keeping existing functionality working expenses.
  4. Cloud implementation: Subscription itself is a service contract (operating expense), while configuration and integration work can capitalize under ASU 2018-15.

ASC 350-40: the rules for internal-use software

ASC 350-40 governs accounting for internal-use software costs. That includes software you build to run your own operations and the SaaS platform you deliver by hosting.

Stage Examples Capitalize?
Preliminary project Concept, evaluate alternatives No, expense
Application development Design, code, configure, test, install Yes, capitalize qualifying costs
Post-implementation Train, maintain, operate No, expense

What's changing: FASB ASU 2025-06

.avif)

ASU 2025-06 removes the project-stage framework from ASC 350-40. Capitalization begins when management authorizes funding and completion is probable with no significant development uncertainty.

ASC 350-40 today vs. ASU 2025-06: a comparison

Current ASC 350-40 ASU 2025-06
When capitalization starts Application development stage begins Management authorizes/funds + completion probable
Framework Three project stages Stages removed; principle-based threshold
Development method Assumes sequential/waterfall Neutral; built for agile/iterative
Effective date In effect now Annual periods beginning after Dec 15, 2027 (early adoption OK)

Journal entries and amortization

A capitalized software journal entry debits an intangible asset and credits cash, payroll, or accounts payable as qualifying costs accumulate. Nothing amortizes during the build. Capitalized software is amortized over its estimated useful life.

Capitalization, amortization, and impairment entries (illustrative)

Event Debit Credit
Capitalize qualifying dev costs Capitalized software (intangible) 300,000 Cash / payroll / AP 300,000
Amortize (ready for use; 3‑year life) Amortization expense 100,000 Accumulated amortization 100,000
Impair (abandoned/obsolete) Impairment loss X Capitalized software X

Why capitalization gets scrutinized

.avif)

Capitalizing development costs increases current-period EBITDA and net income. The spend moves off the income statement and onto the balance sheet.

Tracking and controls: how to build the evidence that auditors want

A defensible capitalization policy comes down to 5 things:

  1. A written policy.
  2. Time capture by project.
  3. The authorization file.
  4. Preparer and reviewer split.
  5. A roll-forward every close.

How an AI-native ERP handles software capitalization

DualEntry is an AI-native ERP built for SaaS finance teams scaling past QuickBooks and spreadsheets through to IPO readiness.

Capitalizing software is a policy you defend, not a loophole

If you want your policy running in the ledger instead of a spreadsheet, talk to us about automating software capitalization.

Software Capitalization FAQs

What is software capitalization?

Software capitalization records qualifying software costs as an intangible asset and amortizes them over the software’s useful life, rather than expensing them as incurred.

What software costs can be capitalized?

You can capitalize costs in the application-development phase (coding, configuration, testing, installation, and directly attributable payroll).

What is ASC 350-40?

ASC 350-40 is the US GAAP standard for internal-use software costs, including SaaS delivered by hosting.

What changed under FASB ASU 2025-06?

ASU 2025-06 removes ASC 350-40’s project stages. Capitalization now starts when management authorizes and funds the project and completion is probable.

Does capitalizing software increase profit?

In the short term, yes. Capitalizing moves development spend off the income statement into an amortizing asset.