ASC 605-985
Software
605 Revenue Recognition
Source downloaded: .Record version 4326346f5d1d. Effective date must be checked in the source.
After ASU 2014-09 gutted nearly all of its content, ASC 605-985 survives only to address recognizing a provision for losses on contracts to deliver software or a software system (alone or with other products and services) that require significant production, modification, or customization of software. It expressly provides no revenue recognition guidance; revenue for such arrangements is accounted for under Topic 606, with the loss provision guidance in Subtopic 605-35. If it becomes probable that the transaction price allocated to an unsatisfied or partially unsatisfied performance obligation will produce a loss, that loss is recognized under Topic 450.
Key points (6)
- The Subtopic's sole remaining purpose is guidance on recognizing a provision for losses on software contracts requiring significant production, modification, or customization of software (605-985-05-1).
- The Subtopic does not provide any revenue recognition guidance (605-985-05-2); the legacy software revenue model was superseded by ASU 2014-09.
- Scope is limited to arrangements to deliver software or a software system, alone or with other products or services, that require significant production, modification, or customization of software, and it applies to all entities (605-985-15-2; 605-985-15-3(e)).
- When such significant production, modification, or customization exists, the entire arrangement is accounted for under Topic 606 and Subtopic 605-35 on provision for losses on contracts (605-985-25-2).
- If it becomes probable that the transaction price allocated to an unsatisfied or partially unsatisfied performance obligation will result in a loss on that performance obligation, the loss is recognized pursuant to Topic 450 (605-985-25-7).
- Scope otherwise follows Section 985-10-15 of the Overall Software Subtopic, subject to the qualifications above (605-985-15-1).
For students. This is the hollowed-out shell of the old SOP 97-2 software revenue model (VSOE, multiple-element software arrangements) — nearly everything was superseded by ASU 2014-09. The common mistake is citing 605-985 for software revenue recognition; it now expressly gives none (605-985-05-2), and the only live rule is loss recognition on software contracts requiring significant production, modification, or customization.
Machine-generated study aid for ASC 605-985. Check the source paragraphs below.
605-985-00Status
Source downloaded: .Record version 7a13fc2ef0b5. Effective date must be checked in the source.
605-985-05Overview and Background
Source downloaded: .Record version 9f1f86c67f7a. Effective date must be checked in the source.
605-985-15Scope and Scope Exceptions
Source downloaded: .Record version 365eb99272aa. Effective date must be checked in the source.
Overall Guidance
Entities
Transactions
- a
- b
- c
- d
- eArrangements to deliver software or a software system, either alone or together with other products or services that require significant production, modification, or customization of software (see Topic 606 on revenue from contracts with customers and Subtopic 605-35 on provision for losses on contracts).
605-985-20Glossary
Source downloaded: .Record version bf80daccfc71. Effective date must be checked in the source.
605-985-25Recognition
Source downloaded: .Record version 5af93c5a7733. Effective date must be checked in the source.
Software Requiring Significant Production, Modification, or Customization
Determining the Need for a Provision for Loss on a Contract
605-985-50Disclosure
Source downloaded: .Record version 6a8434e1fca8. Effective date must be checked in the source.
605-985-55Implementation Guidance and Illustrations
Source downloaded: .Record version af04efc385e5. Effective date must be checked in the source.
605-985-65Transition and Open Effective Date Information
Source downloaded: .Record version 23ed0b50165c. Effective date must be checked in the source.