When generating revenue and invoices from Projects in Oracle Cloud PPM, revenue is transferred to the general ledger, but, the invoice information is sent to receivables. This might cause issues in accounting if not paying attention during configuration. We will look at how we got here.
In most cases, setup is a straight forward SLA rule to credit a revenue account. The Generate Revenue process will debit Unbilled Receivables and credit Revenue. Overlooking the accounting life-cycle of both the revenue and invoice in Oracle Cloud PPM is problematic.
Businesses leveraging the two technologies together would now be able to harness their data for critical insights and predictions, connect customer touchpoints across their business, and drive brand loyalty and growth.
An issue can present itself after the invoice transferred to receivables. If AR AutoAccounting Rules use the Transaction Type for Revenue you must complete the “Revenue” code combination on the Transaction Type. If you select the Revenue account value, then Revenue will double book, debit Receivables and credit Revenue.
The quick resolution is to enter the Unbilled Receivable account value in the Revenue code combination of the Transaction Type. This results in a debit to Receivables and a credit to Unbilled Receivables.
In summary the correct entry will be:
Revenue Generation (PPM to GL):
DR Unbilled Receivables
Invoice Generation (PPM to AR):
CR Unbilled Receivables
Developing more complex SLA rules in Oracle Cloud PPM is an option, too. Especially where segment values are dynamic, and/or, fewer Transaction Types are desired.