Q20. Manage Balance Forward Billing Cycles and Payment Terms
Scenario
You are a consultant for a client who is implementing the Balance Forward Billing feature in Oracle Financials Cloud. You have been asked to define Balance Forward Billing Cycle as well as Balance Forward Billing Payment Terms so that your client can generate consolidated bills.
Task:
Create Balance Forward Billing Cycle, where:
* Name of the cycle is XXCycle (Replace XX with 03. which is your allocated user ID.)
* Bills are generated every day
* Cycle is effective as Of January 1,2023
See the explanation below for solution.
Explanation
* Log in to Oracle Financials Cloud.
* Click on the Balance Forward Billing icon in the Receivables work area.
* Click on the Cycles tab.
* Click on the Create button.
* In the Balance Forward Billing Cycle window, enter the following information:
* Name: XXCycle (Replace XX with your allocated user ID.)
* Billing Frequency: Daily
* Effective Date: January 1, 2023
* Click on the Save button.
The new balance forward billing cycle will be created.
To create a Balance Forward Billing Payment Term:
* Click on the Payment Terms tab.
* Click on the Create button.
* In the Balance Forward Billing Payment Term window, enter the following information:
* Name: XXPaymentTerm (Replace XX with your allocated user ID.)
* Billing Cycle: XXCycle (The cycle that you created in the previous step.)
* Due Date: Next Business Day
* Overdue Days: 30
* Click on the Save button.
The new balance forward billing payment term will be created.
Q21. Manage Receipt Classes and Methods
Scenario
Supremo US Business unit needs to capture customer payments that will be reconciled in the Cash Management application. You need to define a receipt class and receipt method, and assign the appropriate bank account to meet this requirement.
Task:
Create Receipt Method. where:
* Name of the new receipt method is XXCheck (Replace XX with 03. which is your allocated User ID.)
* Receipt method must be effective as of January 1. 2023
See the explanation below for solution.
Explanation
* Log in to Oracle Financials Cloud.
* Click on the Receipt Methods icon in the Receivables work area.
* Click on the Create button.
* In the Receipt Method window, enter the following information:
* Name: XXCheck (Replace XX with your allocated user ID.)
* Effective Date: January 1, 2023
* Receipt Class: XXReceipt Class (The receipt class that you created in the previous step.)
* Bank Account: The bank account that will be used to clear receipts for this receipt method.
* Click on the Save button.
The new receipt method will be created.
Q26. When deciding how to set up the system to recognize revenue, it is important to understand the extent of revenue deferral and the subsequent timing of revenue recognition.
Which two statements are true when you consider that recognition depends on the nature of the contingency?
Explanation
When you consider that recognition depends on the nature of the contingency, these two statements are true:
* Payment-based contingencies do not always require payment before the contingency can be removed and revenue recognized. For example, if a customer pays a deposit or an advance payment, the contingency is removed and revenue is recognized at that point.
* Post-billing customer acceptance clauses must expire (implicit acceptance), or be manually accepted (explicit acceptance), before the contingency can be removed and revenue recognized. For example, if a customer has 30 days to accept or reject a product after receiving an invoice, the contingency is removedafter 30 days or when the customer accepts the product, whichever comes first. The other statements are not true because:
* Pre-billing customer acceptance clauses require the recording of customer acceptance in the feeder system, and its expiration, before importing into Receivables for invoicing. Customer acceptance or its expiration must occur before invoicing, not before revenue recognition.
* Time-based contingencies can expire, but the contingency will have to be removed manually before the revenue is recognized if payment is not due yet. For example, if a customer has a one-year warranty period, the contingency is removed after one year, but revenue is recognized when payment is due or received, whichever comes later.
* Time-based contingencies must expire before the contingency can be removed and revenue recognized, not must not expire. Verified References:
https://docs.oracle.com/en/cloud/saas/financials/23b/faofc/manage-revenue-for-receivables.html#FAOFC-
Leave a Reply