Oracle Accounts Receivable

The Revenue Recognition program is the concurrent program that generates GL distributions for revenue when transactions use accounting rules combined with invoicing rules. It creates the appropriate accounting entries to recognize revenue across periods. Options B (Create Accounting), C (Auto Reconciliation), and D (AR to GL Reconciliation) are different Oracle programs for other purposes - general ledger posting, bank reconciliation, and account reconciliation respectively.

Manual invoices in Oracle Receivables cannot be created with a GL date in a closed period (A is false), for an inactive customer (B is false), or without specifying the Bill To customer (C is false - Bill To is mandatory). The only valid option is D - invoices must have a GL date in an open period that hasn't been closed yet. This is a fundamental period-close control.

The Invoice Print New Invoices Program prints only transactions that have NOT been printed previously AND have a print status set to 'Print'. It specifically targets new, unprinted invoices. Option A is incorrect - it doesn't reprint already-printed transactions. Option B is wrong - it ignores 'Do not print' status. Option D is incorrect - it doesn't reprint already-printed transactions.

Valid receipt statuses in Oracle Receivables include Approved (remittance approval), Remitted (sent to bank), Cleared (bank reconciliation), and others like Unidentified, Confirmed, etc. 'Pending for Approval' is NOT a valid system status name - the correct term would be simply 'Pending' or a specific workflow status. The question asks for the invalid status, making C the correct answer.

The 'Include in Dunning' customer profile setting determines whether a customer is included in the current dunning cycle. If set, they receive dunning letters for overdue accounts. Options A (Exclude from dunning) and B (Remove from dunning) would have the opposite effect. Option D (Add in Dunning) is not a standard Oracle setting name.

Adjustment transactions in Oracle Receivables require Approval Limits to be set up because they represent balance adjustments that need approval workflow. Refunds (A), Debit Memos (B), and On-Account Credits (D) can be created without approval limits being configured. The question asks which method MAY NOT work without approval limits - Adjustments require this setup to function properly in the approval workflow.

The AR: Enter Transactions form is used to create standard transaction types including Debit Memos (B), Deposits (C), and Invoices (D). However, Chargebacks (A) cannot be created through this form - they are created through the AR: Chargebacks form or generated automatically during receipt application. Chargebacks are a specialized transaction type for disputed invoice portions.

Transaction Sources control the sequential numbering of transactions in Oracle Receivables. Each transaction source can have its own numbering scheme, and this is where you define whether automatic numbering is used and what the starting number should be. Auto Accounting is for creating accounting distributions, Transaction Types define default transaction class and printing options, and System Options control global AR settings - none of these handle transaction numbering.

Dunning letters are collection correspondence letters sent to customers as reminders of overdue balances or invoices. They do not serve as cover letters for statements or invoices, nor are they receipts.

Profile classes in Oracle Receivables store default values that are inherited by customers. When you change a profile class value, the system prompts you to choose whether to update all existing customers assigned to that profile class or only apply the new value to new customers going forward. This design prevents unintended bulk changes to customer records while allowing for deliberate updates when needed.

An unidentified receipt in Oracle Accounts Receivable is used when a payment is received without enough information to match it to a specific customer or invoice. This differs from unapplied receipts (customer known but not applied to specific invoices), on-account receipts (payments applied to customer's account balance), and miscellaneous receipts (non-invoice payments like interest or donations). The unidentified receipt type is specifically designed for this scenario.

For adjustments and discounts in Oracle Receivables, the balancing segment value is derived from the Receivables account associated with the transaction. This ensures that accounting entries for these transaction-related activities maintain proper segment balancing. The Revenue account is for recording income, Unapplied Cash handles unapplied receipts, and Unbilled Receivables is for recognized revenue not yet billed - none of these are used for adjustments and discounts.

Oracle Collections is a module that allows collectors to manage customer accounts, including placing invoices in dispute when customers contest charges. Option A describes the iReceivables self-service application (customer-facing), Option C also describes iReceivables, and Option D is incorrect because Collections is for collecting on existing transactions, not creating new ones. Placing invoices in dispute is a core Collections functionality.

AutoInvoice is Oracle's import tool for loading transaction data from external systems. It validates the data and creates invoices, debit memos, credit memos, and on-account credits in Receivables. Auto Lockbox is for processing bank receipts, Revenue Recognition handles revenue accounting rules, and Create Accounting is the subledger accounting process - none are for importing transaction data.

Payment terms with multiple payment schedules allow invoices to be due in stages. By assigning payment terms that have four payment schedules defined, the invoice will automatically split into four due dates. Invoicing rules determine revenue recognition timing over multiple schedules, not payment due dates. Creating multiple lines with different payment terms would fragment the invoice logically rather than creating staged payment terms for a single invoice.

Before entering transactions in Oracle Receivables with no seeded values, you need: B) Transaction type (defines transaction class, printing options, accounting), E) Transaction batch source (controls numbering, validation, and grouping), and F) Customer with Bill To business purpose (required to identify who is billed). Sales tax location is optional unless you charge tax, receivable activities are for adjustments/credits, grouping rules are optional, and Ship To is only needed if you ship goods.

If a receipt's value exceeds the invoice amount and there is no remittance guidance, the entire receipt's status is 'unapplied' or 'partially applied' (with $1500 applied and $500 unapplied). According to Oracle Receivables standards, since the receipt has been partially applied to the invoice, the general state of the leftover amount or the receipt status changes, but if the receipt is partially applied, the correct state in the application process is 'unapplied' for the remaining $500. However, standard training questions list 'unapplied' as the stored answer because the unapplied portion is not yet allocated to 'on-account' or a specific refund.

Standard reversal is the correct method to reverse a miscellaneous receipt. Debit memo reversals apply to standard invoice-applied receipts when the customer's balance must be reinstated, and GL adjustments or manual adjustments bypass subledger integrity and fail to properly correct the receipt's subledger state.

Profile options in Oracle E-Business Suite control system behavior and user preferences. Cross-currency receipts are enabled through the AR: Enable Multi-Currency Receipts profile option or similar profile settings. Quick codes are for predefined lists, system options are module-wide settings (not typically for currency features), and 'None of the above' would be incorrect because this is definitely a profile option.

Credit memos in Oracle Accounts Receivable represent amounts owed to customers. When these are paid (refunded), the payment processing happens through Accounts Payable, which handles outgoing payments. Accounts Receivable manages incoming payments, Cash Management handles bank reconciliation and cash positioning, and Fixed Assets manages capital assets - none of these handle credit memo payments.