Where the scope boundary sits between hosted SaaS and on-premise licenses, probable-to-complete vs. technological feasibility, greater-of amortization, and annual Net Realizable Value testing.
Under US GAAP, hosted SaaS platforms follow ASC 350-40 (amended by ASU 2025-06), whereas software sold, leased, or licensed on-premise follows ASC 985-20, which ASU 2025-06 did not amend. ASC 985-20 delays capitalization until technological feasibility, requires greater-of revenue-ratio or straight-line amortization, and enforces an annual Net Realizable Value write-down ($20,429 in Year 2 of Kestrelway's worked case).
Worked in full in The Software Costs Accounting Handbook by Julian R. Sterling, with every figure reproduced in live Excel workbooks.Get the DRM-free PDF, $19.99 →
One of the sharpest traps in US GAAP software accounting is applying internal-use rules to a commercial software product, or vice versa. As read in November 2026, ASC 350-40 governs software acquired, internally developed, or modified solely to meet internal needs with no substantive plan to market the software externally as a standalone product. Crucially, software used to deliver a cloud-hosted SaaS subscription is within ASC 350-40 whenever customers only receive hosted access and do not take possession of a software license under ASC 350-40-15-4A.
By contrast, ASC 985-20 governs computer software developed to be sold, leased, or otherwise marketed externally as a separate product, including perpetual and term on-premise software licenses installed on customers' own servers. When FASB issued ASU 2025-06 on September 18, 2025, it modernized ASC 350-40 and folded in ASC 350-50 website costs, but left ASC 985-20 completely untouched. Hybrid technology companies that sell both a cloud SaaS platform and an on-premise licensed version must therefore maintain two distinct accounting policies simultaneously.
| Feature | ASC 350-40 (After ASU 2025-06) | ASC 985-20 (External-Use) | Controller Impact |
|---|---|---|---|
| Primary scope | Internal use & hosted SaaS (no license) | Software sold, leased, or licensed | Scope decides subtopic |
| Amended by ASU 2025-06? | Yes (probable-to-complete gate) | No (unchanged) | Different gates |
| Capitalization start | Funded + no significant uncertainty | Technological feasibility | Narrower window in 985-20 |
| Amortization method | Straight-line (typical) | Greater of revenue ratio or SL | Faster runoff in 985-20 |
| Impairment model | ASC 360-10 recoverability / abandon | Annual NRV lower-of-cost test | No restoration in 985-20 |
Under ASC 985-20-25-1 through 25-3, every dollar spent before technological feasibility is established must be expensed as research and development under ASC 730. Technological feasibility is reached only when the entity completes either a detail program design (confirming the product can be built to specifications with all high-risk development issues resolved) or, in the absence of a detail program design, a working model whose completeness and consistency with design specifications have been confirmed by testing.
Capitalization then runs only during the narrow window between technological feasibility and the date the product is available for general release to customers. In modern continuous-delivery engineering teams, the working model is often finished only weeks before general release, leaving a thin slice of capitalizable coding and production-master costs compared with ASC 350-40. Once general release occurs, capitalization stops immediately.
Post-release accounting under ASC 985-20 is equally demanding. Under ASC 985-20-35-1, annual amortization is calculated on a product-by-product basis as the greater of two methods: (a) the ratio of current gross product revenues to the total of current and anticipated future gross revenues for that product, or (b) straight-line amortization over the remaining estimated economic life of the product, including the current period. Because the greater-of formula picks the larger expense each year, front-loaded license sales accelerate amortization automatically.
At every balance sheet date, ASC 985-20-35-4 requires comparing unamortized capitalized cost to the product's Net Realizable Value (NRV), defined as estimated future gross revenues minus estimated future costs of completing and disposing of the product, explicitly including ongoing maintenance and customer support required to fulfill obligations established at the time of sale. Any excess of carrying amount over NRV is written off immediately and can never be restored, even if demand later rebounds.
In The Software Costs Accounting Handbook, Kestrelway Systems develops Kestrelway Freight Engine v5 as an on-premise licensed product. In 2025, Kestrelway expenses $640,000 of pre-technological-feasibility R&D and capitalizes $360,000 between working-model confirmation and general release on January 1, 2026, over an estimated 3-year economic life.
In Year 1 (2026), actual gross revenue hits $1,080,000 with $1,320,000 of anticipated future gross revenue (total $2,400,000, ratio 45.0%). Revenue-ratio amortization ($162,000) exceeds straight-line ($120,000), so Kestrelway records $162,000, leaving $198,000. Year-end NRV ($900,000) comfortably clears carrying value, so no write-down occurs.
In Year 2 (2027), customers migrate faster than expected to cloud SaaS. Actual 2027 revenue drops to $520,000 and revised 2028 revenue falls to $320,000 (denominator $840,000, ratio 61.9%). Revenue-ratio amortization ($122,571) again beats straight-line ($99,000), bringing pre-NRV carrying cost to $75,429. However, estimated 2028 maintenance and customer support costs are $265,000, leaving NRV of only $55,000 ($320,000 minus $265,000). Kestrelway must record an immediate $20,429 NRV write-down, reducing ending NBV to $55,000, which amortizes cleanly in 2028.
| Freight Engine v5 Schedule | 2026 Actual | 2027 Forecast | 2028 Forecast |
|---|---|---|---|
| Opening unamortized cost | $360,000 | $198,000 | $55,000 |
| Current gross revenue / Total anticipated | $1,080,000 / $2,400,000 | $520,000 / $840,000 | $320,000 / $320,000 |
| Revenue-ratio vs. Straight-line | $162,000 vs. $120,000 | $122,571 vs. $99,000 | $55,000 final |
| Recorded amortization (greater of) | $162,000 | $122,571 | $55,000 |
| Year-end NRV write-down | $0 | $20,429 | $0 |
| Ending Net Book Value | $198,000 | $55,000 | $0 |
On the External Software 985-20 tab of the free Software Cost Capitalization Model, a product starting the year with $240,000 capitalized over a 3-year life generates $900,000 of Year 1 revenue against $2,000,000 total anticipated revenue (45.0%). Revenue-ratio amortization ($108,000) beats straight-line ($80,000), leaving $132,000 at year-end with an automated NRV check underneath.
Under IFRS, IAS 38 does not split internal-use and external-use software into separate standards: both follow the same research-versus-development split and the six criteria of IAS 38 paragraph 57. For US GAAP teams comparing internal-use abandonment against ASC 985-20 NRV write-downs, see our ASC 360 impairment test example.
The trap: Running straight-line amortization on an ASC 985-20 license product without testing the revenue ratio or deducting future customer support costs from Net Realizable Value. Both omissions understate expense in a declining product cycle.
A SaaS company whose customers only access hosted software without a contractual right to take possession of a license follows ASC 350-40 (internal-use software), not ASC 985-20.
No. ASU 2025-06 amended ASC 350-40 (internal-use software) and superseded ASC 350-50 (website costs), leaving ASC 985-20 external-use software guidance unchanged.
Product by product, at the greater of (a) current gross revenues divided by total current and anticipated future gross revenues, or (b) straight-line over the remaining estimated economic life.
No. Once unamortized capitalized software cost is written down to Net Realizable Value under ASC 985-20-35-4, the reduced carrying amount becomes the new cost basis and cannot be restored.
This guide is one chapter arc of The Software Costs Accounting Handbook. The book tracks one US GAAP company through Legacy ASC 350-40 vs. ASU 2025-06, agile sprint evidence, stock-based compensation, abandonment write-offs, cloud ERP implementation vs. IFRIC 2021, ASC 985-20 NRV testing, EBITDA covenants, transition methods and deferred taxes.
Paperback PDF edition, $19.99 Book page and companion workbooks
Free download: Software Cost Capitalization Model (Excel).
Illustrative figures computed by the book's model; every company, project and dollar figure is fictional. Rules checked as read in November 2026; education only, not accounting, audit or tax advice.