Category Archives: recognition

New Revenue Recognition Guidelines: For Some, it’s New; for Oracle, it’s Déjà Vu

Part six of a 6-part series on new revenue recognition guidelines.

So now you’re faced with the challenge of introducing new revenue recognition guidelines to your organization. You realize that changes to your ERP systems are required, but you may not be quite sure what the final rules and procedures will look like. And, in any case, it’s going to take some time to make the required system changes. Are you at a standstill?


Good news! There is a way to get ahead of your ERP implementation of Oracle Revenue Management Cloud Service, while evaluating the impact of the new revenue guidelines. First, it’s important to validate the new accounting rules to prepare external stakeholders with new revenue comparisons as soon as possible. The trick, then, is to use a multidimensional consolidation tool during stage 2 of the implementation to prepare reports that illustrate and differentiate revenue under new and existing revenue reconciliation methods. 

Am I sure this will help? Yes. In fact, we’ve already helped many organizations successfully address a similar situation. In 2007, new revenue recognition rules set out by IFRS presented this exact challenge to many organizations (especially in Europe). Here’s what the head of Financial Reporting for a large book publisher said at the time about this transition, “…the group was able to quickly establish a unified chart of accounts in Oracle Hyperion Financial Management (HFM) covering UK GAAP, U.S. GAAP, and IFRS. It was then a simple matter to post the adjustments against these accounts as required.” 


The use of a multidimensional consolidation tool, like HFM, significantly simplified the ability to report the difference in revenue results between existing methods and the new IFRS rules. And it prepared external stakeholders to understand the impact of the new IFRS framework. But it also eased the transition required for ERP updates, since the many of accounting rules were defined early in the implementation of the new IFRS revenue recognition rules. 


Similarly, the task of updating your ERP systems to reflect the new FASB/IASB revenue recognition guidelines may appear daunting, but using multidimensional consolidation tools has been proven to be instrumental during the transitional stages. Once again, the impact studies created with HFM act as a control for the implementation of Oracle Revenue Management Cloud Service (RMCS) on your EBS, Fusion or other ERP.   RMCS uses rules engines to:



Identify accounting contracts, 


Identify distinct performance obligations, and classify them as over-time or point-in-time, 


Allocate the transaction price to the performance obligations in your Oracle or non-Oracle ordering, fulfillment, receivable, and other relevant systems. 



Also, RMCS serves as a customer liability and asset subledger to EBS and Cloud Service General Ledgers. 


Of course, as you deploy it, your detail rule setting will be subject to revision as you work on interpreting the standard.  You will be able to use its iterative modeling capabilities in conjunction with HFM to analyze the impact of the guidelines on your fiscal and management reporting.


Other articles in the New Revenue Recognition Guideline series can be reviewed by clicking the respective title: 



FAQs:



To learn more about Enterprise Performance Management, click here.

Disclaimer:
1)Oracle, Oracle Hyperion, Hyperion and Java are registered trademarks of Oracle and / or its Affiliates
2)Microsoft is a registered trademark of Microsoft and / or its affiliates
3)Any other trademark, name, logo, images, etc. are copyright and trademark of its respective owner which also includes Innov8 Infinite Technology Pvt.Ltd.

New Revenue Recognition Guidelines: What Should I be Doing?

Part 5 of a 6-part series on new revenue recognition guidelines.

When considering the introduction of the revenue recognition guidelines, begin as soon as possible. Don’t wait until the “mandatory” date to address the new guidelines; it will be too late. Here are the typical stages that we see organizations going through as they prepare for the new revenue recognition guidelines:

Stage 1: Study the impact and determine strategy
     •    Define the procedures for assigning value to a contract’s performance objectives
     •    Realistically analyze your accounting subsystems
          o    Can they easily be tweaked to accommodate the new revenue recognition guidelines?
          o    Will major systems need heavy modification or replacement? If so, what are the options?
          o    Do you have the resources to retrofit  on-premises systems? Will it require outsourcing?
          o    Would a cloud implementation provide a quicker and more financially prudent solution? 

Stage 2: Identify the reporting information required by external and internal stakeholders
     •    Determine the impact that the new guidance will have on existing contracts
     •    Consolidate the historic impact under new guidance
     •    Prepare reports to illustrate and differentiate revenue under new and prior revenue reconciliation methods

Stage 3: Implement the required accounting subsystems changes
     •    Configure accounting rules and set up ledgers
     •    Modify or install the accounting subsystems
     •    Process and report using dual accounting

Stage 4: Transform the business
     •    Communicate the impact of the changes to the business
     •    Train the organization to apply the new revenue recognition guidelines
     •    Report using new revenue recognition guidelines

But how are you going to manage these stages? How do you begin? Part 6 of this series, “How will Oracle’s experience help?” provides some advice. Other articles in the New Revenue Recognition Guideline series can be reviewed by clicking the respective title:

Part one: Like it or not, they’re on the way

FAQs:
Part two: What are the new guidelines? Can you provide a simple example?
Part three: Who is affected?
Part four: What are the challenges for affected organizations?
Part six: How will Oracle’s experience help?

To learn more about Enterprise Performance Management, click here.

Disclaimer:
1)Oracle, Oracle Hyperion, Hyperion and Java are registered trademarks of Oracle and / or its Affiliates
2)Microsoft is a registered trademark of Microsoft and / or its affiliates
3)Any other trademark, name, logo, images, etc. are copyright and trademark of its respective owner which also includes Innov8 Infinite Technology Pvt.Ltd.

New Revenue Recognition Guidelines: What Challenges Do the New Rules Present?

Part four of a 6-part series on new revenue recognition guidelines.

The new revenue recognition guidelines, proposed jointly by FASB and IASB, will impact multiple areas of affected organizations. They are likely to affect IT systems, internal processes and controls. For many organizations, changes in the way revenue is recognized and reported will generate questions from external stakeholders and concerns from the organization’s staff. 


With the new revenue recognition guidelines, expect IT systems to be impacted: 


Enterprise resource planning (ERP) systems may need to be upgraded or modified to capture additional data to support the necessary accounting and disclosures. How and when does your ERP system allocate prices for products and services? Does it have the capabilities to accrue for liabilities of goods and services to customers by performance obligation? Is it capable of recognizing transfers to customers of the performance obligations over time using the seven new tests of GAAP, rather than the old four? 


There will likely be a need to report revenue under new and existing guidelines. It will take some time for external stakeholders to get adjusted to the new results being reported and understand how the new reports map to the old way of doing things. In an effort to ease this transition, many organizations will want to report using both guidelines for a pre-determined period of time.  


Since the new guidelines often require judgment and use of estimates (both estimated selling prices and variable considerations) to value the performance obligations, internal controls and accounting procedures will need to be reviewed and, in many cases, revised. Do you have a pre-accrual estimation process in place?  Do you have post-accrual revision of estimation process in place?


Anticipate external questions. Key financial measures and ratios may change, which could affect analyst expectations. 


Expect internal concerns. The new rules may impact sales commissions, bonuses, budgeting, and compliance with contractual covenants. For example, the revenue recognition guidelines are likely to trigger reviews and changes to organizational sales and contracting processes. Additional thought will need to be given to contract language and sales compensation plans.

How do I go about introducing the new revenue recognition guidelines to my organization? See part 5 of this series, “What should I be doing?” for some guidance. Other articles in the New Revenue Recognition Guideline series can be reviewed by clicking the respective title: 



FAQs:


Disclaimer:
1)Oracle, Oracle Hyperion, Hyperion and Java are registered trademarks of Oracle and / or its Affiliates
2)Microsoft is a registered trademark of Microsoft and / or its affiliates
3)Any other trademark, name, logo, images, etc. are copyright and trademark of its respective owner which also includes Innov8 Infinite Technology Pvt.Ltd.

New Revenue Recognition Guidelines: What Are the Guidelines and Examples?

Part two of a 6-part series on new revenue recognition guidelines.

The core principle of the new guidelines is to recognize revenue to depict the transfer of promised goods or service to customers in an amount that reflects the consideration to which the entity expects to be entitled for those goods or services2. That is, the aim is to recognize revenue consistently as the customer assumes ownership of the various components of a contract, and values the revenue at that obligation’s appropriate share of the expected revenue.


Steps to achieve this core principle:



Establish the contract with the customer

Identify the performance obligations (promises / deliverables) in the contract

Determine the (overall) transaction price

Assign the transaction price to the contract’s performance obligations

Recognize revenue as the reporting organization satisfies a performance obligation

A Simple Example

Your organization sells a computer system and printer to a customer for $1,000. The computer and software are delivered to the customer in June but, due to manufacturing delays, the printer is delivered in July. Under the new Performance Obligation guidelines, when is the revenue for the various components of the contract to be recognized?

1. A contract is established for a computer system

2. Consisting of three performance obligations:



a. Laptop computer
b. Software
c. Printer

3. The overall transaction price is $1,000
4. The company’s standalone selling prices are:



a. Laptop: $800

b. Printer: $200

c. Software: $200

(Total: $1,200) 


Under the contract, then, the performance obligations are assigned transaction prices of: 


a. Laptop: $1,000 / 1200 * 800 = $666.67
b. Printer: $1,000 / 1200 * 200 = $166.67
c. Software: $1,000 / 1200 * 200 = $166.67
(Total: $1,000)

Once either party has acted on the contract (i.e., at the earlier of the customer accepting an invoice or the vendor commencing shipping), the vendor accrues the liability to the customer for each performance obligation at the assigned revenue valuations.

5. Upon delivery of the laptop and software, the vendor recognizes $833.33 in June. At the end of June, the balance sheet shows an accrued liability to the customer of $166.67 for the printer. In July, when the client takes ownership of the printer, the vendor recognizes $166.67.

Do the new revenue recognition guidelines affect you? Part 3 of this series, “Who is Affected?” may help you answer that question. 

Other articles in the New Revenue Recognition Guideline series can be reviewed by clicking the respective title:

Part one: Like it or not, they’re on the way 

FAQs:
Part three: Who is affected?
Part four: What are the challenges for affected organizations?
Part five: What should I be doing?
Part six: How will Oracle’s experience help?

To learn more about Enterprise Performance Management, click here.



2
Retrieved on March 9, 2016 from FASB web page: http://www.fasb.org/jsp/FASB/Page/BridgePage%26cid=1351027207987

Disclaimer:
1)Oracle, Oracle Hyperion, Hyperion and Java are registered trademarks of Oracle and / or its Affiliates
2)Microsoft is a registered trademark of Microsoft and / or its affiliates
3)Any other trademark, name, logo, images, etc. are copyright and trademark of its respective owner which also includes Innov8 Infinite Technology Pvt.Ltd.

New Revenue Recognition Guidelines: What Are the Guidelines and Examples?

Part two of a 6-part series on new revenue recognition guidelines.

The core principle of the new guidelines is to recognize revenue to depict the transfer of promised goods or service to customers in an amount that reflects the consideration to which the entity expects to be entitled for those goods or services2. That is, the aim is to recognize revenue consistently as the customer assumes ownership of the various components of a contract, and values the revenue at that obligation’s appropriate share of the expected revenue.


Steps to achieve this core principle:



Establish the contract with the customer

Identify the performance obligations (promises / deliverables) in the contract

Determine the (overall) transaction price

Assign the transaction price to the contract’s performance obligations

Recognize revenue as the reporting organization satisfies a performance obligation

A Simple Example

Your organization sells a computer system and printer to a customer for $1,000. The computer and software are delivered to the customer in June but, due to manufacturing delays, the printer is delivered in July. Under the new Performance Obligation guidelines, when is the revenue for the various components of the contract to be recognized?

1. A contract is established for a computer system

2. Consisting of three performance obligations:



a. Laptop computer
b. Software
c. Printer

3. The overall transaction price is $1,000
4. The company’s standalone selling prices are:



a. Laptop: $800

b. Printer: $200

c. Software: $200

(Total: $1,200) 


Under the contract, then, the performance obligations are assigned transaction prices of: 


a. Laptop: $1,000 / 1200 * 800 = $666.67
b. Printer: $1,000 / 1200 * 200 = $166.67
c. Software: $1,000 / 1200 * 200 = $166.67
(Total: $1,000)

Once either party has acted on the contract (i.e., at the earlier of the customer accepting an invoice or the vendor commencing shipping), the vendor accrues the liability to the customer for each performance obligation at the assigned revenue valuations.

5. Upon delivery of the laptop and software, the vendor recognizes $833.33 in June. At the end of June, the balance sheet shows an accrued liability to the customer of $166.67 for the printer. In July, when the client takes ownership of the printer, the vendor recognizes $166.67.

Do the new revenue recognition guidelines affect you? Part 3 of this series, “Who is Affected?” may help you answer that question. 

Other articles in the New Revenue Recognition Guideline series can be reviewed by clicking the respective title:

Part one: Like it or not, they’re on the way 

FAQs:
Part three: Who is affected?
Part four: What are the challenges for affected organizations?
Part five: What should I be doing?
Part six: How will Oracle’s experience help?

To learn more about Enterprise Performance Management, click here.



2
Retrieved on March 9, 2016 from FASB web page: http://www.fasb.org/jsp/FASB/Page/BridgePage%26cid=1351027207987

Disclaimer:
1)Oracle, Oracle Hyperion, Hyperion and Java are registered trademarks of Oracle and / or its Affiliates
2)Microsoft is a registered trademark of Microsoft and / or its affiliates
3)Any other trademark, name, logo, images, etc. are copyright and trademark of its respective owner which also includes Innov8 Infinite Technology Pvt.Ltd.

New Revenue Recognition Guidelines: Like it or Not, They’re on the Way

Part one of a 6-part series on new revenue recognition guidelines.

In May, 2014, the Financial Accounting Standards Board and the International Accounting Standards Board issued a joint revenue recognition standard related to customer contracts. The new guidelines impact most organizations that deliver goods and/or services on a contract basis, especially when delivered over extended periods of time.

Using the new guidelines for revenue recognition, companies align revenue to the delivery of “performance obligations.” They must account for these obligations – items that are owed to the customer under the terms of the contract – as accrued contract liabilities, and extinguish them by transferring those items to customers and recognizing revenue on the successful transfer. No longer will companies apply the variety of current practices for recognizing revenue (for example, deferring revenue on early invoicing) or apply current, by-industry US revenue guidance. Application of the guidelines will require some companies to recognize that a contract exists where they previously may not have thought they had one.


The aim of the joint guidelines is to establish a common set of global standards for all companies to recognize and report revenue. But, it’s not really about accounting as much as it’s about capital markets. By uniformly applying these guidelines, it becomes easier for external stakeholders (such as shareholders or financial analysts) to compare revenue performance between organizations. It’s also interesting to note that in a September 2013 speech, SEC Enforcement Director, Andrew Ceresney stated that “Revenue recognition issues will remain a staple of our financial fraud caseload.[1]”

There isn’t a great deal of time remaining to implement these new guidelines. Public organizations should apply the new revenue standard to annual reporting periods beginning after December 15, 2017. Nonpublic organizations should apply the new revenue standard to annual reporting periods beginning after December 15, 2018.

These guidelines represent a major shift in revenue recognition for affected companies. For some, it represents the first time that they’ve had to rethink how they “count” revenue, and they may not be sure of what’s involved in this switch from a procedural or systems perspective. Others, especially for those who went through the adoption of IFRS standards in 2007, have experienced this type of transformation before. And many organizations, with Oracle’s help, made that IFRS transition smoothly.

With the tight timeline, and some very serious decisions to be made, many will have questions. Other articles in the New Revenue Recognition Guideline series can be reviewed by clicking the respective title (as they become available):

Part two: What are the new guidelines? Can you provide a simple example?
Part three: Who is affected?
Part four: What are the challenges for affected organizations?
Part five: What should I be doing?
Part six: How will Oracle’s experience help?

To learn more about Enterprise Performance Management, click here.
__________________



[1]

Retrieved on April 5, 2016 from SEC web page: https://www.sec.gov/News/Speech/Detail/Speech/1370539845772


Disclaimer:
1)Oracle, Oracle Hyperion, Hyperion and Java are registered trademarks of Oracle and / or its Affiliates
2)Microsoft is a registered trademark of Microsoft and / or its affiliates
3)Any other trademark, name, logo, images, etc. are copyright and trademark of its respective owner which also includes Innov8 Infinite Technology Pvt.Ltd.