Deloitte
Accounting Research Tool
...
Chapter 9 — Contract Modifications

9.2 Types of Contract Modifications

9.2 Types of Contract Modifications

If a change in a contract qualifies as a contract modification under ASC 606-10-25-10 and 25-11, the entity must assess the goods and services and their selling prices. Depending on whether those goods and services are distinct or sold at their stand-alone selling prices, a modification can be accounted for as:
  • A separate contract (see ASC 606-10-25-12).
  • One of the following (if the modification is not accounted for as a separate contract):
    • A termination of the old contract and the creation of a new contract (see ASC 606-10-25-13(a)).
    • A cumulative catch-up adjustment to the original contract (see ASC 606-10-25-13(b)).
    • A combination of the items described in ASC 606-10-25-13(a) and (b), in a way that faithfully reflects the economics of the transaction (see ASC 606-10-25-13(c)).

Footnotes

1
If the answer is “Yes” for some goods or services and “No” for others, it may be appropriate to apply both models to a single contract, in the manner described in ASC 606-10-25-13(c), on the basis of an assessment at the performance obligation level. See Section 9.2.2.
2
For illustrative examples, see Example 9-3; ASC 606-10, Examples 8 and 9; and Example 9-7.
3
For illustrative examples, see Example 9-2; ASC 606-10, Example 5, Case B; ASC 606-10, Example 7; Example 9-6; Example 9-8; and ASC 606-10, Example 6
4
For an illustrative example, see ASC 606-10, Example 5, Case A.
5
Cumulative adjustments to revenue under ASC 606-10-25-13(b) are not common for these types of modifications of SaaS arrangements because the services provided after the modification are typically distinct from those transferred before the modification. Therefore, this discussion does not focus on modifications that would result in an adjustment to revenue.
6
Case A of Example 5 is reproduced in Section 9.2.1.
7
Quoted from Q&A 81 of the FASB staff’s Revenue Recognition Implementation Q&As (the “Implementation Q&As”).