One cloud accounting dilemma will soon be fixed

“);});try{$(“div.lazyload_blox_ad”).lazyLoadAd({threshold:0,forceLoad:false,onLoad:false,onComplete:false,timeout:1500,debug:false,xray:false});}catch(exception){console.log(“error loading lazyload_ad “+exception);}});

You know cloud computing is here to stay when the accountants take notice. The Financial Accounting Standards Board’s Emerging Issues Task Force plans to propose .

The updated guidance means that a customer under contract with a cloud computing provider would consider the current processes of leveraging internal-use software to determine how to recognize implementation costs as an asset. Moreover, the new guidance recognizes that implementation costs are an asset that may be expensed over the terms of the contract with the cloud computing provider, as long as the arrangement is not terminated at the time of the contract.

This is good news for both the enterprises that use cloud computing whose accountants need to figure out how to treat these costs, and for the cloud computing providers that now have a way to explain to enterprises how the costs should be treated. Enterprises have struggled to find best practices, as well as define legal issues, to determine how to treat cloud computing costs that are significant for many enterprises.

The reality is that, no matter if you use internal systems or public cloud systems, you’re getting the advantage of using systems. So the treatment of those costs should be aligned. Thanks to the FASB, they soon will be more aligned.