PocketCPA

BAR, Business Analysis and Reporting

Sources for Internally Developed Software

Last reviewed

The standards and authorities behind PocketCPA's BAR lessons on Internally Developed Software. The topic rests on ASC 350-40 / ASC 985-20.

About this topic

Software costs are the one asset class where the same programmer, writing the same code, produces an asset at one company and an expense at another. What separates the two is not the work. It is who will use the software once it is finished.

That single question splits the Topic, and the split is the thing to hold on to. Software the entity will run itself falls under ASC 350-40, internal-use software. Software the entity will sell, lease, or otherwise market falls under ASC 985-20. Which of those two models applies is what most items in this group actually turn on.

Key points

What the lessons cover

  1. Two regimes hinge on who uses the software
  2. Internal-use software: capitalize the application-development stage
  3. Software to be sold: technological feasibility is the trigger
  4. Amortization and impairment
  5. The two models side by side
  6. Hosting arrangements: the customer's implementation costs (ASC 350-40-25-18)
  7. Website development costs, and the ASU 2025-06 rewrite

Authoritative references

Which model applies:

Internal-use software: recognition and measurement:

Software to be sold: ASC 985-20:

Website development and related Topics:

How PocketCPA uses these sources

Every lesson is written in original words and cites the paragraph each rule comes from. No standard's text is reproduced. How lessons and questions are written and checked is set out in our methodology.

See also