After reviewing an incomplete invoice, the Billing Manager clicks the Complete button in the Transactions window.
What are three results of this action?
When the Billing Manager clicks the Complete button in the Transactions window, the following results occur:
The invoice can now be printed or delivered to the customer by the preferred delivery method.
The invoice is eligible for transfer to the General Ledger and posting to the customer account.
The payment schedules are created using the payment terms specified on the transaction or customer profile. The other options are not correct because:
The invoice is not sent for a dunning follow-up until it becomes overdue.
The invoice is included in the standard aging and collection process if the transaction type has the Open Receivables option set to Yes, not No. Verified Reference: https://docs.oracle.com/en/cloud/saas/financials/23b/faofc/manage-customer-billing.html#FAOFC-GUID-9E7F8B0A-5F6E-4B6E-AF0B-9C1E5D7D2A8A
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 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]
Your organization is looking to adopt a flexible approach to control the creation of claims investigation when the lockbox files contain invalid positive remittance references. This feature helps manage lockbox files that encounter invalid transaction numbers for receipts with customer assignment.
When this option is enabled in the Manage Receivables System Options task, which process must be run in Scheduled Processes to process Lockbox Receipts with invalid transaction referenced?
This process is used to process lockbox receipts with invalid transaction references when you enable the Create Claims Investigation option in Receivables System Options. Reference: [How You Process Lockbox Receipts - Oracle]
When entering the Customer import upload spreadsheet, which two columns, if populated with *NULL will remove the existing values on loading?
These are the two columns that, if populated with *NULL, will remove the existing values on loading. They are part of the customer profile class attributes that can be updated using customer import. Verified Reference: [How You Manage Customer Data Uploads - Oracle]
