Significant development uncertainty
Under ASU 2025-06 the probable-to-complete threshold is not met while significant development uncertainty exists, so capitalization cannot start ASU 2025-06. For a novel or unproven model, this gate keeps the compute in expense even after funding is committed, because committing budget does not resolve technical feasibility.
What counts as significant uncertainty
The ASU names two factors, either of which is enough: the software has technological innovations or novel, unique or unproven functions or features whose uncertainty has not been resolved through coding and testing, or its significant performance requirements have not been identified or are still being substantially revised. An unproven model architecture, or a model whose target behaviour is still being redefined, fits that description. It is the US analogue of the IAS 38 technical-feasibility criterion under IFRS.
Why committed funding does not override it
Funding shows intent and resources; it does not show the model will work. Both the probable-to-complete threshold and this uncertainty gate must be cleared. A well-funded moonshot is still expensed until feasibility is demonstrable.
Posts to
Primary sources
- [S7] FASB: ASU 2025-06, Intangibles, Goodwill and Other, Internal-Use Software (Subtopic 350-40): Targeted Improvements (issued September 2025; reproduces the amended ASC 350-40 text) (US GAAP)
- [S3] BDO: New ASU on internal-use software costs guidance (ASU 2025-06) (US GAAP)
Ledger current as of 2026-10-23. A position and a citation, not accounting advice. See how we cite.