A generally accepted accounting principle (GAAP), ASC 606 revenue recognition identifies the specific conditions in which revenue can be recognized and provides a framework for how companies need to account for revenue received. Essentially, the revenue recognition principle states that revenue can only be recognized once it has been earned – not necessarily when payment is received.
To illustrate, let’s look at a couple of examples. Say your landscaping business completes the tree trimming of a housing development and sends the client an invoice for $4,000. With the contractual obligation met, you can recognize the $4,000 immediately – even though payment won’t be received until the following month.
Using the same landscaping example, we’ll add a twist to the scenario. At the start of each quarter, the client pays $1,000 in advance. Can the company recognize the $1,000 as soon as it’s received? The short answer is no. However, since the client is paying $1,000 in advance of services being rendered, the company can recognize $1,000 per quarter – but only once the quarterly services are complete.
Across all industries and business models, knowing when to recognize revenue can (and is) challenging. To establish best practices, eliminate confusion and standardize the recognition of revenue, the Financial Accounting Standards Board (FASB) and International Accounting Standards Board (IASB) developed a framework – Accounting Standards Codification (ASC 606) – for more consistent revenue recognition.
The Four W’s of ASC 606 Revenue Recognition
While revenue recognition is complicated and has its fair share of nuances, it can be explained using the four W’s – who, what, when, and why – of ASC 606 revenue recognition.
Who:
ASC 606 revenue recognition affects virtually all companies or entities – public, private, and non-profit – that enter into contracts with customers for the transfer of goods or services, or enter into contracts for the transfer of specific nonfinancial assets.
What:
ASC 606 provides businesses and entities with a universal framework for recognizing revenue from the sale of goods and services. It focuses on the promises documented in the contract to ensure that revenue is only recognized when contractual obligations have been met. To help organizations adhere to the principles, the standard provides a five-step process for revenue recognition.
1) Identify the contract
This is the agreement between the company and the client and contains obligations and rights that can be enforced by either party if/when necessary. The essential components of the contract are:
- All parties have approved the contract
- All parties are committed to fulfilling their obligations
- Each party’s rights are identifiable
- Payment terms are identified
- The contract has commercial substance
- Collectibility is probable
2) Identify the performance obligation
This is the promise to transfer goods to the customer or complete contractual services. According to IFRS 15.27, a good or a service is distinct if both of the following are met: The good or service is capable of being distinct. This means that the customer can benefit from it either on its own or together with other available resources. The good or service is distinct within the context of the contract.
3) Determine the transaction price
This step refers to the cash and non-cash a company expects to receive in exchange for the transferring of the promised goods or services. The amount can be fixed, variable, or a combination of both and may include other considerations such as upgrades, downgrades, price concessions, volume discounts, rebates, etc. The allocated amounts are recognized as revenue when (or as) performance obligations are met.
4) Allocate the transaction price
When a contract contains more than one performance obligation, the company needs to allocate the total consideration to each performance obligation based on its relative standalone selling price. We should note that ASC 606 doesn’t prohibit any methods used for estimating the standalone selling price, as long as the estimate is an accurate representation of what the price would be if it were a separate transaction. This step is a bit more complicated for software-as-a-service (SaaS) companies since their products or services are delivered on a recurring basis.
5) Revenue recognition
The final step, revenue is recognized when or as the performance obligations stated in the contract are fulfilled. Satisfying performance obligations can happen either at a specific moment or over a period of time.
When:
In May 2014, the FASB and IASB jointly issued Accounting Standards Update (ASU) 2014-09, which introduced ASC 606. It highlights how revenue received from contracts is treated and provides a uniformed framework for recognizing revenue.
Why:
ASC 606 revenue recognition was developed for a variety of reasons, including to:
- Remove inconsistencies and weaknesses in revenue requirements.
- Provide a robust framework for addressing revenue issues.
- Improve comparability of revenue recognition practices across entities, industries, jurisdictions, and capital markets.
- Provide useful information to financial statement users through improved disclosure requirements.
- Simplify the preparation of financial statements by reducing the number of publications.
- Eliminate differences between GAAP and IFRS.
- Add transparency to financial reporting.
Adhering to ASC 606 has many nuances and amendments continue to be made. However, the fact remains – ASC 606 compliance is mandatory. To overcome pitfalls and comply with this revenue recognition standard, companies need a way to streamline their financial processes and ensure accuracy.
Transform Your Revenue Recognition Processes
At its very core, ASC 606 revenue recognition governs how revenue generated is recorded on a business’s financial statements. Getting it right requires intelligent revenue recognition software that delivers automation, accuracy, and auditability.
Obtaining the right revenue recognition solution shouldn’t be left to chance. To help you select the solution that will best meet your revenue recognition needs, here are four key characteristics the software should provide.
- Contract management: Ensure the billing solution enables you to easily manage contract rates and payment terms, as well as provides the ability to set specific pricing, define rules, and create account hierarchies.
- Flexible data models: An extensible data model enables you to add objects, fields, and relationships, as well as apply business rules to support any monetization model. A flexible data model allows you to quickly modify the application and data structure to respond to market or regulatory changes.
- Seamless integration: By integrating your billing, revenue recognition, customer relationship management (CRM), enterprise resource planning (ERP), general ledger, etc. systems, data is seamlessly shared between applications – eliminating the need for manual data entry, reducing or eliminating duplicate entries, and lessening manual, error-prone financial tasks. A fully integrated financial ecosystem provides a single source of the truth, helping to ensure accurate revenue recognition.
- Global compliance: A billing solution that ensures regulatory compliance ensures your company remains in sync across all accounting standards and ensures revenue recognition complies with ASC 606 mandates.
The right revenue recognition platform helps you simplify revenue recognition complexities – even for the most complex billing scenarios. BillingPlatform delivers a rules-based revenue recognition engine that enables you to define rules specific to your company. You can then make assignments in real time, while providing the agility needed to speed the financial close process with real-time subledger transactions that integrate into downstream ERP and accounting systems.
Are you ready to transform your revenue recognition processes? Our team of experts are just a click away.
