Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Study: ASC 606 Might Slow IPOs in 2018 ??

Posted on October 13th, 2017 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

A new study by Deloitte reveals that initial public offerings (IPOs) may suffer as a result of New Accounting Standard (ASC606)

Here are excerpts from an article by Terry Sheridan in accountingWEB.com

Here’s a snapshot of the survey’s findings:

  • 60 percent of the respondents said they have not begun implementation of the standard or have only done an initial assessment.
  • But 53 percent said IPO activity will increase modestly (46 percent) or substantially (7 percent) in the next year.
  • 83 percent of respondents said it takes 12 months (40 percent) to 18 months (43 percent) prior to the IPO to put in place the structural and operations changes needed for a public offering.
  • 49 percent of respondents said media, technology and telecommunications industries would attempt the most IPOs.

Read the full article in accountingWEB.com

Posted in ASC606 | No Comments »

ASC 606 and IFRS 15 Revenue Recognition automation

Posted on September 1st, 2017 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Do you know , there have been multiple acquisitions and announcements in the revenue recognition space as IT vendors ensure that they can support the ASC 606 standard including:

  • Intacct’s May 2016 announcement as the first automated ASC 606 solution
  • Zuora’s May 10th, 2017 acquisition of Leeyo
  • CallidusCloud’s May 24th, 2017 acquisition of RevSym
  • Aptitude Software (Microgen plc) , On August 31st, 2017 Acquires RevStream

One wonders how long revenue recognition vendors Softrax will remain available on the market!

Moreover , EBS customer can think for exexistance possibility with Oracle Revenue Management Cloud , which is a centralized, automated revenue management product that enables you to address the ASC 606 and IFRS 15 accounting standard for Revenue from Contracts with Customers.

ERP vendor like SAP and Netsuites also have seprate module to support ASC 606 and IFRS 15.

Posted in ASC606 | No Comments »

ASC 606/IFRS 15 & Oracle’s Revenue Management Cloud Service (RMCS)

Posted on June 11th, 2017 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

As we know , the entire accounting approach to revenue recognition is undergoing a wholesale re-write. Rather than relying on using a deferred revenue account, you will need to identify and account for performance obligations.

WHAT CHANGES ARE BEING INTRODUCED?

Revenue recognition is taking a more scenario and rules based approach to what can be recognised and more importantly when.

as we know ASC606 , there is introduction of the following 5 Steps to Recognising Revenue:

  1. Identify the contracts with the customer
  2. Identify the separate performance obligations
  3. Determine the contract price
  4. Allocate the transaction price
  5. Recognise revenue when a performance obligation is satisf ed

Whatever ERP you run, whether it is Oracle or not, you need to consider the impact of this accounting regulation on your business.

IS THERE A SOLUTION/OPTIONS OUT THERE?

Oracle’s Revenue Management Cloud Service is the way forward.

This is a centralized, automated revenue management solution that enables you to address the ASC 606 and IFRS 15 accounting standard Revenue from Contracts with Customers.

Oracle’s Revenue Management Cloud service can be integrated with your existing ERP, whether it’s Oracle or not, to address the requirements of IFRS 15.

  • Comply - Adhere to the IFRS 15 core principles
  • Audit -Provide complete and accurate access to revenue
  • Automate -Automate revenue calculations based on the new accounting standard
  • Integrate -Integrate with your existing ERP and third party system

An application that enables you to manage customer contracts and performance obligations easily to help you address the mandates of the new accounting guidance.

Is part of Oracle Enterprise Resource Planning Cloud and has the capability to co-exist with any source application, say Oracle EBS.

Robust integration is available with third party applications, say Oracle EBS.

DISCLOSURE CONSIDERATIONS:

Once of the critical area in new Accounting standard is Disclosure Management .

You will need to either recalculate your fnancial statements for the last two years, or disclose in the year of go-live the impact of the new standard.
Oracle’s Revenue Management Cloud Service can help here too to Integrate with your BI or Hyprion .

Revenue Management Cloud Services Coexistence with Oracle E-Business Suite

Oracle Revenue Management Cloud is an automated and a centralized, revenue management product that addresses ASC 606 and IFRS 15.

Oracle Revenue Management Cloud Service lets you to apply the five steps of core principle of ASC 606 and IFRS 15 requirements:

clasical steps ASC 606

The product provides a framework to automate the creation of customer contracts and performance obligations as per IFRS 15, their valuations and resulting accounting entries, and enables to recognize the revenue over time or at a point in time with these key Features.

  • Contracts and Performance Obligations
    • Rules based Automation
    • Flexible Configurations
  • Revenue Allocations
    • Simplified Revenue Accounting
    • Compliant Allocations as per Standards
  • Satisfaction Schedules
    • Point in time and over time
    • Independent Billing
  • Recognition
    • Liabilities Accrual and Assets recognition
    • Income Statement on transfer to customer on performance obligation met

Most of companies must comply with the new ASC 606 and IFRS 15 accounting standard for fiscal years that begin on or after January 1, 2018.

In its last and greatest release of Oracle Revenue Management Cloud R12 includes a coexistence solution with Oracle EBS.

Oracle E-Business Suite (EBS) products use the coexistence solution for integration with Revenue Management to bring in source document revenue lines from upstream sales cycle systems. Beacuse of these co-existance model , Reference data, such as customers and inventory items, are synchronized between EBS and Revenue Management seemlessly .

ORCA

 

The coexistence feature enables you to deploy a uniform, centralized and comprehensive view of contracts with customers, unifying the details tracked in a variety of order management, retail point of sales, and billing systems.

The Revenue Management Cloud Service (ORMCS) is a Software-as-a-Service (Saas)-based too, sold on a per user per month basis

As per Documentation , following 6 steps will ensure automated, efficient compliance with ASC 606 and IFRS 15 without impacting your existing sales processes in EBS:

  1. Extract Data from EBS : Extract data related to the sales cycle.
    • For example, orders, contracts, receivable data, point of sale data, projects, shipping, traffic, and other fulfillment data.
  2. Import Revenue Basis Data and Billing Data: Import revenue and billing data into Revenue Management using predefined File-Based Data Import (FBDI) templates for Revenue Basis and Billing data.
  3. Validate and Correct Customer Contract Source Data: Integrated programs in RMCS validates the imported lines, transforms master data, and assigns the transaction period to the imported lines.
  4. Ensure compliance with the new accounting standards ASC 606 and IFRS 15: Revenue Management analyzes the data in centralized repository that stores imported and processed sales cycle data, and provides user-configurable contract identification and performance identification rule engines for the system to automatically run the 5 steps of the core principle of ASC 606 and IFRS 15 requirements illustrated above.
  5. Compare sales cycle data: Perform what-if iterative studies of how you might implement the new rules, such as the impact of different definitions of contracts and performance obligations, different pricing paradigms, different satisfaction criteria, and so forth.
    • Oracle recommends that you compare the results of your current accounting (ASC 605 and IAS 18) to each accounting iteration generated in Revenue Management (based on ASC 606 and IFRS 15) in an enterprise performance tool,
  6. Create Accounting in EBS GL: The Subledger Accounting rules engine in RMCS provides out-of-the-box seeded accounting events to address the need for creating contract assets and contract liabilities at initial performance, as well as reflecting the appropriate accounting once a performance obligation is billed.

This is how best we can undersood Revenue Process with Oracle Revenue Management Cloud.

Revenue Process

Untill , next post , bye.

Posted in ASC606 | No Comments »

Revenue recognition transition adoption Options- Full or modified retrospective?

Posted on May 10th, 2017 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

The deadline for adoption of the new revenue recognition standards under ASC606 is fast approaching.

Public companies need to adopt for fiscal years beginning in 2018 while private companies have until 2019.

The changes in how to account for software and services can be significant, often requiring the break out of underlying performance elements that were bundled together under current reporting standards.

The guidance lays out two alternatives for disclosing the revenue recognition transition , both of which require dual accounting to support the disclosure requirements.

  • Full retrospective
    • Under the full retrospective approach, the full prior two years of financials are restated to the new standards to provide an apples to apples comparison between the years under the new standards.
  • Modified retrospective
    • The modified retrospective approach does not require restatement of prior years but requires disclosure of the year of adoption financials under the old standards to provide the apples to apples comparison under the old standard

Full retrospective

Under the full retrospective approach, the sooner that a multi-book solution can be implemented, the better.

A multi-book approach accounts for new contracts under both standards.

In a perfect world, implementing this type of dual accounting at the beginning of the retrospective period would be ideal, but most companies will need to perform recast calculations on some period of contracts.

The full retrospective also requires two points to calculate a cumulative adjustment.

First, a cumulative adjustment will need to be performed at the beginning of the retrospective period and then again at the date of adoption to adjust the company’s primary books to the new standards as per below diagram.

606 Full Retrospective

Modified retrospective

The modified retrospective is a bit simpler in that it only requires one cumulative adjustment of open contracts as of the date of adoption and only requires the cumulative impact calculation of open contracts vs the period by period recast required to support a full retrospective.

Usually it recommend establishing a multi-book strategy two purposes as below :

modified approach

  • First, the establishment of a legacy GAAP standard book will provide the accounting for the comparative disclosure during the year of adoption.
  • Secondly, the establishment of an ASC606 book reflecting the new standards. This book will assist with calculating the cumulative adjustment as well as providing visibility to accounting differences between the old and new standards leading up to the year of adoption.

High Points and Low points in two Options

Let’s take a quick look for highpoints and low points for each approach, and offer a few reasons why a company might choose one over the other.

 

Full Retrospective Modified Retrospective
  • Sstakeholders and/or shareholders may demand it
  • Useful trend information can be had across all the period presented on your financials
  • This must recast previous financial statements as if the new guidance had always existed for a comparative two-year period prior to the adoption year
  • It’s likely to require significant time and effort
  • If contract volume exceeds even a handful, then finance and accounting automation beyond that provided by Excel spreadsheets will be a necessity
  • Reduced effort in restating prior year amounts
  • No recasting of past revenue can speed implementation
  • Potential for “lost revenue” if the new guidance recognizes less revenue than the previous method would have in a particular period
  • Requires you to keep two sets of accounting records in the year of adoption in order to comply with the requirement to disclose all line items in the financial statements as if they were prepared under today’s guidance
  • Here too, even a modest number of contracts will demand more accounting and finance automation than Excel spreadsheets can reasonably provide

Therefore , regardless of the which method is choosen to disclose revenue recognition transition, there will be a significant effort which need to assess properly .These options include considerations for historical data restating requirements and overall data volume requirements. Discuss and engage your Implemenation partner to plan for this transition and deploy technologies to support these new requirements.

Posted in ASC606 | No Comments »

ASC 606 ) Step5 :Recognize revenue as performance obligations are satisfied

Posted on May 4th, 2017 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

The underlying principle of the new standard is that an entity will recognize revenue to depict the transfer of goods or services to customers at an amount that the entity expects to be entitled to in exchange for those goods or services.

The standard consists of a five-step approach as follows:

clasical steps 606

Fig : 5 steps Framework

Last post we have seen step 1 and step 2

Lets take a quick look on Step 5 which is Recognize revenue as performance obligations are satisfied

RECOGNIZE REVENUE AS PERFORMANCE OBLIGATIONS ARE SATISFIED

Finally, the business can recognize revenue when they meet the performance obligations.

If that fulfillment happens at a distinct point in time, revenue can be recognized right then.

If the obligation is satisfied over time—for example, a technical support contract—the business needs to decide how to measure the progress and completion of that obligation.

More details herewith:

Performance Obligations Satisfied Over Time – An entity will recognize revenue over time if any of the following criteria are met:

The customer concurrently receives and consumes the benefits provided by the entity’s performance as the entity performs.

  • The entity’s performance creates or enhances a customer-controlled asset.
  • The entity’s performance does not create an asset with an alternative use and the entity has a right to payment for performance completed to date.

Regarding the last bullet, a right to payment exists if an entity is entitled to payment for performance completed to date if the customer terminates the contract for reasons other than the entity’s nonperformance.

Performance Obligations Satisfied at a Point in Time – An entity will recognize revenue at a point in time (when control transfers) for performance obligations that do not meet the criteria for recognition of revenue over time.

To determine when a customer obtains control, the entity should consider the following indicators (not all indicators have to be met in order to recognize revenue):

  1. The entity has a present right to payment for the asset.
  2. The entity transferred legal title to the asset.
  3. The entity transferred physical possession of the asset.
  4. The entity transferred the significant risk and rewards of ownership to the customer.
  5. The customer accepted the asset.

Measuring Progress Toward Satisfying a Performance Obligations Satisfied Over Time

  • Output Methods – Units produced or delivered, contract milestones, or surveys of work performed.
  • Input Methods – Costs incurred, labor hours expended, time lapsed, or machine hours used.

Posted in ASC606 | No Comments »

( ASC 606 ) Step 4 : ALLOCATE THE TRANSACTION PRICE

Posted on May 3rd, 2017 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

The underlying principle of the new standard is that an entity will recognize revenue to depict the transfer of goods or services to customers at an amount that the entity expects to be entitled to in exchange for those goods or services.

The standard consists of a five-step approach as follows:

clasical steps 606

Fig : 5 steps Framework

Last post we have seen step 1 and step 2

Lets take a quick look on Step 4 which is Allocation of Transaction Price

ALLOCATE THE TRANSACTION PRICE

Step 4 allocates the transaction price to the distinct POBs in a contract. An entity typically allocates the transaction price to each POB based on the relative standalone selling prices of each distinct good or service promised in the contract.

If a contract has more than one performance obligation, the business needs to provide an accurate estimation as to that obligation’s standalone selling price versus the total agreed upon amount.

ASC 606 allows for includes three methods of figuring this amount—adjustment market assessment, expected cost plus margin, and residual.

To be continued

Posted in ASC606 | No Comments »

( ASC 606 ) Step3 : Determine the transaction price

Posted on May 2nd, 2017 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

The underlying principle of the new standard is that an entity will recognize revenue to depict the transfer of goods or services to customers at an amount that the entity expects to be entitled to in exchange for those goods or services.

The standard consists of a five-step approach as follows:

clasical steps 606

Fig : 5 steps Framework

Last post we have seen step 1 and step 2

( ASC 606 ) Step1 : Identify the contract with a customer

( ASC 606 ) Step2 : Identify the performance obligations in the contract

Lets take a quick look on Step 3:

DETERMINE THE TRANSACTION PRICE

The next step is to determine the transaction price, the amount of consideration that the seller expects to be entitled to in exchange for transferring the control of goods or services promised in the contract.

The transaction price is the amount of consideration that an entity expects to be entitled to in exchange for transferring promised goods or services to a customer, excluding amounts collected on behalf of a third party (i.e. sales taxes).

The transaction price is the amount the business expects to receive in return for transferring the goods or services outlined in Step 1. The amount can be fixed, variable, or a combination, but is allocated specifically to the performance obligations outlined in Step 2.

Therefore , once these performance obligations are fulfilled, the business can recognize this as revenue.

When a certain amount of cash is transferred to the business simultaneously with the promised goods or services, this is quite easy. But, more complex payment arrangements require additional thought.

Variable Consideration and the Constraint on Revenue Recognition:

  • The transaction price may be variable or contingent upon future events, including discounts, refunds, rebates, credits, incentives, performance bonuses, etc.
  • Variable consideration should be estimated based on either the expected value or the most likely amount, defined as follows:
    • Expected Value – Sum of the probability weighted amounts for various possible outcomes.
    • Most Likely Amount – The most likely amount in a range of possible amounts.

There is some suggestion that companies that implement ASC 606 rules early might be able to recognize more upfront revenue on sales, but that shouldn't be taken as a guarantee

To be continued.

Posted in ASC606 | No Comments »

( ASC 606 ) Step2 : Identify the performance obligations in the contract

Posted on May 2nd, 2017 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

The underlying principle of the new standard is that an entity will recognize revenue to depict the transfer of goods or services to customers at an amount that the entity expects to be entitled to in exchange for those goods or services.

The standard consists of a five-step approach as follows:

clasical steps 606

Fig : 5 steps Framework

Last post we have seen step 1

  • ( ASC 606 ) Step1 : Identify the contract with a customer

Lets take a quick look on Step 2:

IDENTIFY THE PERFORMANCE OBLIGATIONS IN THE CONTRACT

A performance obligation is the basically promise to transfer goods or services to a customer.

In this step, the business needs to identify all the distinct performance obligations in an arrangement.

A good or service is defined as distinct if

  1. the customer can benefit from it on their own, or with resources they already have, and
  2. can be transferred independent of other performance obligations.

Any goods or services that can't be deemed distinct should be bundled together until they can be.
Performance obligations can also cover an obligations the customer might expect because of their history, which can make this step more complex.

Posted in ASC606, Oracle Application | No Comments »

( ASC 606 ) Step1 : Identify the contract with a customer

Posted on May 1st, 2017 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Revenue is one of the most important key performance indicators (KPIs) used by investors when assessing a company’s performance and prospects.

Revenue recognition represents one of the highest risks on financial statements, and it is one of the leading causes of restatements. Every publicly traded company has to follow the
guidelines set by the Securities and Exchange Commission (SEC) to communicate their financials effectively to investors. Based on the operations in different countries, businesses sometimes need to comply with more than one set of standards.

Most of the companies located in North America or Europe comply with generally accepted accounting principles (GAAP) and International Financial Reporting Standards (IFRS). Recently, the standards-setters developed new revenue-related standards (IFRS 15 and Accounting Standards Codification [ASC] 606), which ensure clarity and transparency in reporting revenue. These new guidelines require a substantial change in the way currently revenue is being reported compared to the new revenue recognition standards.

The underlying principle of the new standard is that an entity will recognize revenue to depict the transfer of goods or services to customers at an amount that the entity expects to be entitled to in exchange for those goods or services.

The standard consists of a five-step approach as follows:

clasical steps 606

Fig : 5 steps Framework

Lets take a quick look on Step 1:

1.IDENTIFY THE CONTRACT WITH A CUSTOMER

ASC 606 dictates that a business can account for a contract when all these criteria are met.

  • Both parties should approve the contract (in writing, orally, or via some other agreed-upon practice)
  • Both parties can identify what goods or services are to be transferred to the customer
  • Accounting for the contract will need to be applied when all of the following occur:
    • The parties have approved the contract and intend to perform their respective obligations.
    • Each party's rights regarding the goods or services to be transferred can be identified.
    • The payment terms can be identified.
    • The risk, timing, or amount of the entity's future cash flows are expected to change (contract has commercial substance).
    • It is probable that the entity will collect the consideration to which it will be entitled in exchange for the goods or services transferred

Regarding the collectability criteria, the entity will assess at the inception of the contract whether it is probable it will collect the transaction price.

Credit losses arising from a contract that was probable of collection at inception will be recognized as an expense in the income statement.

For Contract Modifications - Accounted for as a separate contract if the modification adds one or more distinct performance obligations and the price increases accordingly. Otherwise, a modification is accounted for as an adjustment to the original contract, either prospectively or through a cumulative catch-up adjustment depending on whether the remaining goods or services in the contract are distinct

to be continued :

Posted in ASC606, Oracle Application | No Comments »

Page 1 of 11