{"id":2448,"date":"2018-11-19T10:50:36","date_gmt":"2018-11-19T18:50:36","guid":{"rendered":"http:\/\/www.projectp.com\/ppblog\/?p=2448"},"modified":"2023-02-01T16:36:52","modified_gmt":"2023-02-02T00:36:52","slug":"new-accounting-treatment-standard-for-cloud-computing-implementation","status":"publish","type":"post","link":"https:\/\/www.projectp.com\/ppblog\/2018\/11\/19\/new-accounting-treatment-standard-for-cloud-computing-implementation\/","title":{"rendered":"New Accounting Treatment Standard for Cloud Computing Implementation"},"content":{"rendered":"

\"\"<\/a>_________________________________________________________________________________________________________<\/p>\n

 Project Partners Blog Author: Donna Dignam | Principal Functional Consultant  <\/span><\/strong>
\n____________________________________________________________________________________________________________________<\/h5>\n

In April 2015, FASB (Financial Accounting Standards Board) issued ASU (Accounting Standards Update) 2015-05 to assist entities in determining when a customer in a cloud computing arrangement \u201cCCA\u201d (i.e., hosting arrangement) included a software license.<\/p>\n

If a CCA includes a license to internal use software, the software license is accounted for by the customer as an intangible asset.  The intangible asset is recognized for the software license, and the payments or said license made over time are recognized as a liability.  If no software license is included in the contract, the company should account for the arrangement as a service contract, and the fees associated with the hosting service of the arrangement are expensed as incurred.<\/p>\n

The update did not give guidance regarding the implementation costs for activities performed in a cloud computing arrangement as a service contract.  Since the FASB guidance in this area was not explicit, the Board decided to issue an Update to address the resulting diversity in practice.<\/p>\n

Who Is Affected by ASU 2018-154<\/sup>?<\/strong><\/span><\/p>\n

These Amendments on the accounting for implementation, setup, and other upfront costs (commonly referred to as implementation costs) apply to entities that are a customer in a hosting arrangement that is a service contract.  Oracle Cloud computing arrangements, where a license is sold to the customer and a hosting arrangement with Oracle Cloud, would be one such customer.<\/p>\n

Main Provisions of ASU 20184<\/sup><\/strong><\/span><\/p>\n

The Update intends to align the requirements for capitalizing implementation costs incurred in a hosting arrangement that is a service contract with the requirements for capitalizing implementation costs incurred to develop or obtain internal-use software and hosting arrangements that include an internal-use software license.  The current accounting for the service element of a hosting arrangement is not affected.<\/p>\n

It is up to the company to determine which implementation costs to capitalize as an asset related to the service contract and which to expense.  Costs to develop or obtain internal-use software that could not be capitalized under Subtopic 350-40, such as training costs and specific data conversion costs, also cannot be capitalized for a hosting arrangement that is a service contract.  The company in a hosting arrangement that is a service contract determines which project stage an implementation activity relates to.  Project stages include the preliminary project stage, application development stage or post-implementation stage.  Costs incurred for the application development stage are capitalized, while those costs related to the preliminary project stage or the post-implementation stage are expensed as the activities are performed.<\/p>\n

In addition, the company must amortize the capitalized implementation costs over the terms of the hosting arrangement.  The term of the hosting arrangement includes the noncancellable period of the arrangement plus periods covered by:<\/p>\n

    \n
  1. Option to Extend \u2013 customer must be reasonably expected to exercise this option<\/strong><\/li>\n
  2. Option to Terminate the Arrangement \u2013 where the customer is reasonably expected NOT to exercise this option<\/strong><\/li>\n
  3. Option to Extend or Not to Terminate \u2013 where the vendor can exercise the option.<\/strong><\/li>\n<\/ol>\n

    Impairment guidance, as if the costs were long-lived assets, and abandonment are to be applied based upon the existing guidance in SubTopics 350-40 and 360-10, respectively.<\/p>\n

    The income statement presentation by the entity should be the same line item as the fees associated with the hosting service of the arrangement.  Similarly, the classification of payments for capitalized implementation costs in the Statement of Cash Flows is done similarly to payments made for fees associated with the hosting arrangement.  In the Statement of Financial Position, capitalized implementation costs are presented in the same line item that a prepayment for fees associated with the hosting arrangement would be presented.<\/p>\n

    How is This Different, and Why is it an Improvement?<\/strong><\/span><\/p>\n

    GAAP does not explicitly address accounting for implementation costs associated with a HASC.  Therefore, the Update improves current GAAP as it clarifies accounting and aligns the accounting for implementation costs for hosting arrangements, regardless of whether a license is conveyed.<\/p>\n

    For consulting firms, the new standards present an improved selling point as costs previously required to be expensed can now be capitalized.  For capital-intensive industries, where cloud applications are being considered and dismissed due to financial considerations around increased expenses (and resulting decreased profitability metrics) due to cloud implementation, the new standard allows a way to capitalize the costs associated with both the license and the implementation and development costs around getting that application stood up.<\/p>\n

    When Does This New Update Take Affect?<\/strong><\/span><\/p>\n

    For public entities, the amendments are effective for fiscal years beginning after December 15, 2019, and interim periods within those fiscal years. For all other entities, annual reporting periods beginning after December 15, 2020, and interim periods within annual periods beginning after December 15, 2021, are required.  Early adoption is permitted at any time.<\/p>\n

    The amendments in this Update should be applied retrospectively or prospectively to all implementation costs incurred after the date of adoption.<\/p>\n

    Have Questions? <\/strong>
    \nSimply reach out to us, and our experts will immediately assist, provide additional information,
    \nand answer any of your questions.<\/p>\n

    P: #1.650.712.6203  |   Email: cfryc@projectp.com<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    The amendments provided by FASB and ASU for public and private project-driven organizations implementing the Cloud will be going into effect. From our Certified Public Accountant experts, learn how these changes will impact your organization and when these changes should be implemented: <\/p>\n","protected":false},"author":79,"featured_media":3234,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[15,181],"tags":[255],"class_list":["post-2448","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-industry-trends-standards","category-oracle-cloud","tag-implement-service"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.projectp.com\/ppblog\/wp-json\/wp\/v2\/posts\/2448","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.projectp.com\/ppblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.projectp.com\/ppblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.projectp.com\/ppblog\/wp-json\/wp\/v2\/users\/79"}],"replies":[{"embeddable":true,"href":"https:\/\/www.projectp.com\/ppblog\/wp-json\/wp\/v2\/comments?post=2448"}],"version-history":[{"count":0,"href":"https:\/\/www.projectp.com\/ppblog\/wp-json\/wp\/v2\/posts\/2448\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.projectp.com\/ppblog\/wp-json\/wp\/v2\/media\/3234"}],"wp:attachment":[{"href":"https:\/\/www.projectp.com\/ppblog\/wp-json\/wp\/v2\/media?parent=2448"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.projectp.com\/ppblog\/wp-json\/wp\/v2\/categories?post=2448"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.projectp.com\/ppblog\/wp-json\/wp\/v2\/tags?post=2448"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}