Oracle Revenue Management Cloud Services | what is ORMB? | revenue management and billing cloud

RMCS-Revenue Management Cloud Service​

FINANCIAL STANDARD OF REVENUE RECOGNITION​

• The core principle of ASC 606 and IRFS 15 is that an entity recognizes revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services.​
• ASC 606: Revenue from Contracts with Customers. In the US, this rule was issued by the Financial Accounting Standards Board​.
• Perhaps the biggest difference between the old regulation and the new is that you now review revenue at the inception of the sales order. You identify contracts and performance obligations without any dependencies on actual billing of the customer​

WHY RMCS ?​

• Deferred  Revenue Accounting replaced with performance obligation Accounting.​
• Issue with deferred Revenue Accounting is that-deferred revenue was classified as a liability, but it did not meet the definition of a liability​.
• You don’t owe it to anybody​
• You are just sitting on it until it is allowed to be recognized​

Revenue Management Features​

Revenue Management includes the following features:

• Allocates revenue according to published guidelines.
• Identifies and creates customer contracts and performance obligations based on user-defined rules.
• Provides user-defined rules from contract identification to revenue accounting generation.
• Books revenue when a performance obligation is satisfied.
• Processes revenue independently of billing.
• Simplifies and automates revenue accounting across product bundles.

What Has Changed: A Comparison

RMCS EXAMPLE​

Contract Structure​

What is a Performance Obligation​

A promise in a contract with a customer to transfer to the customer either:

• A good or service (or a bundle of goods or services) that is distinct or

• A series of distinct goods or services that are substantially the same and that have the same pattern of transfer to the customer

Item	Standalone Selling Price	Performance Obligation No.	PO Classification	Revenue Recognized
Smart Phone	490.68	1001	Point On Time	490.68
Voice Plan	588.82	1002	Over Time	50.01 1st mo.
Data Plan	392.50	1003	Over Time	33.34 1st mo.

Performance Obligation​

• When a contract is identified in Revenue Management, each line item in the contract is a performance obligation. When the performance obligation is satisfied, revenue is recognized.​
• In this example, one contract is created with three lines. Line 1 is for the smartphone and line 2 the voice plan and line 3 the data plan.​
• Revenue is recognized for the smartphone on the day the customer physically receives the phone. The revenue for the voice and data plans are recognized for $50.01 and $33.34 for the first month. Subsequent months amounts are calculated based on the number of days in each month.​

USER CASE​

What is our goal and how do we get there?

A telecom company make the following sale:

Item	Standalone Selling Price	Satisfaction Date Start	Satisfaction Date End	Revenue Recognized
Smart Phone	490.68	7/1/2016	7/1/2016	490.68
Voice Plan	588.82	7/1/2016	6/30/2017	50.01 1st mo.
Data Plan	392.50	7/1/2016	6/30/2017	33.34 1st mo.

USER CASE-SATISFACTION EVENT​

• Satisfaction Events Processed for 1 Month:​

USER CASE-Performance Obligation Billed​ Billing details loaded to RMCS​

• Billed for 1 month

USER CASE-RECEIVABLES PROCESSING​

Receivables Processing:

Over All Accounting in One Page​