Monday Jun 27, 2016

Part C. New Revenue Recognition – Disclosure, the Forgotten Implication

Tools

In a previous blog article (Series 1, part 6), I pointed out that the functionality of a multi-dimensional consolidation tool, like Oracle Hyperion Financial Management or Oracle Financial Consolidation and Close Cloud Service (FCCS), will assist in the transition phase adoption of the new revenue recognition guidelines. And, in concert with the capabilities built in to the ERP system, the consolidation tool is important to organization’s ability to measure and report revenue under the new recognition guidelines. But with the new revenue recognition rules, it is becoming increasingly important to report more than just the traditional consolidated financial statements.

In my discussion with Mike Malwitz, he mentioned that organizations are anxious for tools to help streamline the production of financial reports with supplemental details and narrative information.




Nigel Youell: “Mike, can you tell us about tools that will help with disclosure under the new revenue recognition guidelines? “

Mike Malwitz: “Sure, there are a few tools in the Oracle Hyperion Financial Close Management suite that should be considered for processing and reporting disclosure details under the new revenue recognition guidelines.

First, Supplemental Data Manager (SDM) is designed to collect, organize, update, edit, and manage supplemental data for financial analytical applications such as consolidation. SDM maintains the detailed multidimensional contract information and integrates it to the consolidation tool, where appropriate.

Most organizations want tools that provides intuitive and flexible authoring environment that provides easy access to Oracle and non-Oracle data from multiple on-premises and cloud sources. Ideally suited for these tasks, Enterprise Performance Reporting Cloud Services also offers a collaborative, workflow-driven environment for delivery of book-quality financial and management reports.

Finally, we’re also seeing that, under the new revenue recognition guidelines, organizations want to reduce risk of misstating revenue – automated reconciliation of revenue contract details would be advantageous. The Account Reconciliation Management module has helped companies reduce risk by introducing real-time visibility to the reconciliation process and it will prove to be an enabler for ensuring that the details of revenue contracts are properly qualified.”


To read Part A and Part B, click on the respective title.

Part A: New Revenue Recognition – Disclosure, the Forgotten Implication
Part B: New Revenue Recognition – Disclosure, the Forgotten Implication

To learn more about Enterprise Performance Management, click
here.

Monday May 16, 2016

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.

Monday May 09, 2016

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.

Monday May 02, 2016

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:

Monday Apr 25, 2016

New Revenue Recognition Guidelines: Who is Affected?

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

The new revenue recognition guidelines redefines “revenue” for every US GAAP and IFRS company.  But, its impact is more severe for companies who offer discounted goods and services alongside fully-priced goods or services, and for those who deliver to customers over extended time periods, or both simultaneously. 

There are exceptions; the guidelines do not apply to organizations covered by other standards (e.g., insurance or leasing contracts).


All companies need to review their revenue for hidden bundling and implicit performance obligations. These guidelines are likely to impact pharmaceutical companies, telecoms, construction contractors, real estate developers, auto companies, and other firms with multiple sources of revenue.

Organizations - Examples

1. A software company ships a new game, but some missions or episodes are missing: 


Under today’s GAAP, they would defer all the revenue until the missing episodes were published. 

Under the new guidelines, they recognize revenue that relates to the delivery they performed, and postpone recognizing the remainder of the revenue until the delayed missions are delivered. A key question is how to identify and value a performance obligation of this nature, especially since this company doesn’t sell missions separately.


2.

a. A cellular telephone sold under contract that includes automatic software upgrades for one year is considered a single performance obligation.
b. A phone with a list price of $600 is sold to a customer under a service contract for $200. The cell bandwidth revenue for that client must be recognized to include a “claw back” of the difference of the list and selling price of the device.

3. An auto dealer that includes maintenance services with the sale of a car can only recognize the service revenue once the owner of the car brings it in for maintenance.

4. Similarly, high-tech companies that include software licenses, consulting, and support services on sales contracts determined to be related will recognize service revenue once the services are delivered.

How will the new revenue recognition guidelines affect my organization? Look at part 4 of this series, “What are the challenges for affected organizations?” to answer this question. 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

Tuesday Apr 19, 2016

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

Monday Apr 11, 2016

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


Tuesday May 29, 2012

What's Going on With IFRS?

There hasn’t been much news lately about the adoption of IFRS in the United States, and I have received some questions from customers and partners on this topic.  So here’s a quick update.


Most of the world has moved to International Financial Reporting Standards (IFRS) with the last holdouts being Japan, India and the United States.  Japan has started the transition process and should be complete by 2015 and India will be in transition through 2018.  The Financial Accounting Standards Board (FASB) has been discussing and working with the International Accounting Standards Board (IASB) on the convergence of US GAAP and IFRS for many years.   The reality is that the United States Securities and Exchange Commission (SEC) is not going to force a switch entirely over to IFRS, but is proposing a slow convergence of US GAAP with IFRS principles over time.  In fact the latest word being used to describe this process is “condorsement”, as per a proposal issued by the SEC in May 2011. 


There are a number of convergence projects now being worked on between the two standards committees, but the four that are in focus currently relate to Financial Instruments, Revenue Recognition, Financial Statements and Leases.  Exposure drafts on these topics were released for public comment back in 2010 and SEC board reviews occurred in 2011.  The expected timeline for adoption of the revised US GAAP rules in these areas is highlighted below.


Revenue:  Exposure draft closed, comment period over, the boards are mulling the exact wording.   This is expected to be finalized in late 2012.  Effective date unknown – but not likely until 2015, with retroactive reporting back to 2013.


Leasing:  Principles established, exposure draft still being finalized.  Anything that meets the definition of a lease will be on the balance sheet as a right to use asset and a lease liability.  P&L expense will distinguish the interest element from the usage element.  Some issues still to be resolved.  This is expected to be finalized in 2013.


Financial Statement Reporting: Postponed indefinitely.


Financial Instruments:  Progress, dialogue this year between FASB & IASB.  Basel III, Dodd-Frank, JPMorgan Chase, Greek exposure all factors in getting this one done.  No final dates at this point.


The SEC has not made their announcement, but everyone is pretty certain that what they will do is ask the FASB to expose the IFRS statements, other than the 4 convergence ones listed above, as ASUs (Accounting Standards Updates) to US GAAP: that is, FASB will adopt IFRS, not companies.    Companies will then adopt the IFRS statements as US GAAP Updates as FASB rolls them out, but absolutely no details are available on that program currently.


Oracle has staff carefully tracking these developments and provides features and capabilities in our financial management applications designed to help customers migrate smoothly from their local GAAPs to IFRS.  For news and updates on US GAAP/IFRS convergence projects, please consult the following resources:


US SEC:  http://www.sec.gov/


FASB:  http://www.fasb.org/home


IASB:  http://www.ifrs.org/Home.htm


For information about how Oracle’s financial management solutions can help with the transition to IFRS:


http://www.oracle.com/us/solutions/corporate-governance/ifrs/061806.html


Please contact me if you have any questions or need more information:  john.orourke@oracle.com

About

This blog will highlight key EPM market trends, recent events and other news of interest to our field, customers and partners.

Search

Categories
Archives
« August 2016
SunMonTueWedThuFriSat
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
   
       
Today