Multi Period Accounting (MPA) 2 – Revenue Recognition

From Oracle official concept, revenue recognition is renue recognition. It belongs to AR. Multi Period Accounting is the concept of SLA. But in fact, they are the similar thing. One of  initial purpose of MPA is for revenue recognition, but it is not flexible enough for revenue recognition. So revenue recognition is still handled in Receivables itself.

Let’s have a look at revenue recognition first then compare it with multi period accounting feature in SLA.

1. Create AR transaction and assign Invoice Rule in AR transaction header. There are two options for Invoice Rule:

  • In Advance: Receiving money at first before revenue recogonition
  • In Arrears: Receiving money at last after revenue recogonition

2. Assign accounting rules in AR transaction line. Accounting Rule means the revenue recogonition schedule. The revenue recognition program/API calcualte the recogonition schedule against accounting rule. Only if invoice rule is assigned in header, accounting rule can be

image

3. Once AR transaction is assigned with invoice rule and accounting rule, the original revenue account distribution will be changed to defered revenue account. It can be set up in AutoAccounting functionality. And receivable account distribution will be changed agasint invoice rule. If “In Arrears” is selected, the recevable account will be defaulted against the autoaccouting setup for Unbilled Receivable.

4. Complete the AR invoice.

5. Create Accounting with Final option.

6. Revenue Recognition: You have two options to recogonize revenue.

  • by concurrent program “Revenue Recognition Master Program”
  • by Revenue Accounting form. In the form, you can manage revenue and sales credits more flexible than concurrent program. You can schedule or unschedule the revenue recogonition and you can also partailly recogonize the revenue.

image

7. Whatever you select to recogonize the revenue by concurrent program or form, the functionality will create series of AR transaction distributions with multiple period. And for each period, it create accounting event with type of “Invocie Update”. So by revenue recogonition, multiple events will be created. It’s one of the difference between MPA and Revenue Recogonition.

image

Please note that, for normal transaction entry, you can’t key in unopened GL date. But for program inserting, it can.

8. Create Accounting againt for the new created events and distribution lines. The SLA journal entries are created for all of the periods even though the period is not opened.

  • For the opened GL period and future entry statsu GL period, the journal entry status is “Final”and can be transfered to GL.
  • For un-opened GL period, the journal entry status is “Invalid”and event status is unprocessed.
  • It is very strange that it depends on GL period but not Receivable period.
EVENT_ID APPLICATION_ID EVENT_TYPE_CODE EVENT_DATE ENTITY_ID EVENT_STATUS_CODE PROCESS_STATUS_CODE
3362490 222 INV_UPDATE 23-2月 -13 3295913 U I
3362489 222 INV_CREATE 23-1月 -13 3295913 P P

 

AE_HEADER_ID APPLICATION_ID LEDGER_ID ENTITY_ID EVENT_ID EVENT_TYPE_CODE ACCOUNTING_DATE GL_TRANSFER_STATUS_CODE GL_TRANSFER_DATE JE_CATEGORY_NAME ACCOUNTING_ENTRY_STATUS_CODE ACCOUNTING_ENTRY_TYPE_CODE AMB_CONTEXT_CODE PRODUCT_RULE_TYPE_CODE
5003040 222 1 3295913 3362489 INV_CREATE 23-1月 -13 N   Sales Invoices F STANDARD DEFAULT S
5002952 222 1 3295913 3362490 INV_UPDATE 23-2月 -13 N   Sales Invoices R STANDARD DEFAULT S

 

image

 

image

 

image

 

image

9. When you open the next period and run create accounting again, the journal entry status will changed from Invalid to Final and transferred to GL module.

By summery, in revenue recogonition solution, Oracle insert the transaction ditribution line with multiple periods, create events for each period and create journal entries for each period. For unopened period, Oracle make its journal entries as “Invalid” until the period opened.

Leave a Reply