Manage Aging Methods
Scenario
Your organization needs to create their own a-bucket aging method for reporting purposes.
Task
Create a new 4-bucket Aging Method in the Collections application, where:
Name Of the aging method is XXAging Method (Replace XX with 03, which is your allocated User ID.)
Aging method is accessible to all business units
Aging buckets are 45 days apart
Last bucket is 91 days
Log in to Oracle Financials Cloud.
Click on theAging Methodsicon in theReceivableswork area.
Click on theCreatebutton.
In theAging Methodwindow, enter the following information:
Name:XXAging Method (Replace XX with your allocated user ID.)
Description:Custom aging method for reporting purposes.
Aging Buckets:
1:0 to 45 days
2:46 to 90 days
3:91 to 135 days
4:136 to 180 days
Last Bucket:181 days
Available to All Business Units:Yes
Click on theSavebutton.
The new aging method will be created.
Which flexfields does Autolnvoice require to identify transactions and transaction lines, if you load the interface using a customized form?
These are the two flexfields that AutoInvoice requires to identify transactions and transaction lines, if you load the interface using a customized form. They are used to group transaction lines into transactions and assign transaction attributes. Verified Reference: [How You Define AutoInvoice Grouping Rules - Oracle]
The AutoAc counting rule for the Revenue account is defined as follows:
When entering a manual invoice, the revenue account code combination is incomplete with the Department segment left blank. Which are the three reasons for this?
These are the three reasons for the revenue account code combination being incomplete with the Department segment left blank. The salesperson is not required on the transaction and is left blank, so the system cannot derive the Department segment from the salesperson reference accounts. The revenue reference accounts were entered for all salespersons, so the system cannot use the default revenue account from the transaction type. The no sales credit salesperson has no reference accounts, so the system cannot use the default revenue account from the no sales credit salesperson. Verified Reference: [How You Define AutoAccounting - Oracle]
You are reviewing an invoice on the Review Transaction page. After clicking the Sales Credit subtab. you notice the following breakdown: Revenue Allocation and Nonrevenue Allocation.
What is Nonrevenue Allocation?
Nonrevenue Allocation is the amount of sales credits that are associated to deferred revenue. It represents the portion of sales credits that are not yet recognized as revenue and are allocated to future periods. Verified Reference: [How You Manage Sales Credits - Oracle]
You defined a Payment Terms Threshold Policy to defer revenue recognition of 120 days. An invoice is imported with split Payment Terms, consisting of the following five installments:
What revenue amount would be deferred on this Imported Invoice?
This is the revenue amount that would be deferred on this imported invoice. The Payment Terms Threshold Policy defers revenue recognition of 120 days, which means that only the first two installments (1000 and 4000) are within the threshold and can be recognized as revenue. The remaining three installments (1000, 2000, and 2000) are beyond the threshold and must be deferred until they are due. Verified Reference: [How You Manage Revenue Recognition - Oracle]
Leila
4 months agoLeslie
5 months agoEmilio
6 months agoShawna
6 months agoMalinda
6 months agoAlita
6 months agoReynalda
7 months agoLashon
7 months agoGaston
7 months ago