Expand
If software is embedded in a product or integrated with other non-software components into the ultimate product marketed to customers, ASC 985-20 requires all R&D activities for other components be completed prior to capitalization of software costs, as described in ASC 985-20-25-4.

ASC 985-20-25-4

Software production costs for computer software that is to be used as an integral part of a product or process shall not be capitalized until both of the following conditions have been met:

  1. Technological feasibility has been established for the software.
  2. All research and development activities for the other components of the product or process have been completed.

For an integrated product, even if technological feasibility of the software has been established, software development costs should be expensed as incurred until all R&D activities for the integrated product are complete. Generally, software is an integral part of a product or process if the software could not be marketed separately from the ultimate product or process sold to customers. For example, software may be developed that will be embedded in a specific piece of hardware. If the software is not marketable as a stand-alone product, software development costs would be expensed when incurred until all R&D activities for the related hardware in which it will be embedded have been completed.
Question SW 2-2
When should costs be capitalized related to the development of software that will be embedded in a product to be ultimately marketed to customers if the product requires regulatory approval?
PwC response
In accordance with ASC 985-20-25-4, the reporting entity will need to assess whether all R&D activities for the product have been completed prior to capitalizing software development costs, regardless of whether technological feasibility has been established for the software. The reporting entity could have remaining R&D activities to complete leading up to or even after the regulatory approval event. Therefore, judgment may be required to assess when R&D activities are completed. To determine whether R&D activities are completed prior to regulatory approval, the reporting entity should consider whether the approval is a complex process that could require additional R&D or essentially a formality, resulting in no additional R&D.

Question SW 2-3
Does the guidance in ASC 985-20-25-4 also apply to software that has been purchased to be embedded in a product that will be sold to customers?
PwC response
Yes. As discussed in SW 2.5, the cost of purchased software to be externally marketed that has no alternative future use is accounted for in the same manner as costs incurred to develop such software internally. Therefore, if all R&D activities for the other components of the product in which the software will be embedded have not yet been completed, the cost to acquire the software would be expensed as R&D.
Expand Expand
Resize
Tools
Rcl

Welcome to Viewpoint, the new platform that replaces Inform. Once you have viewed this piece of content, to ensure you can access the content most relevant to you, please confirm your territory.

signin option menu option suggested option contentmouse option displaycontent option contentpage option relatedlink option prevandafter option trending option searchicon option search option feedback option end slide