Oracle Payables Fundamentals

Invoices can be validated by using the validate checkbox or validate related invoices checkbox in the Invoice Actions window. This provides a direct, manual validation method from the workbench. The other options describe incorrect methods (batch programs are not used for individual invoice validation, and there is no 'submit request' option for validation).

Payables and Purchasing can close independently of each other. These are separate modules with their own period close processes. While there may be business dependencies, the system does not enforce any technical requirement that one must close before the other.

Entering invoices and matching them to purchase orders in Payables generates the accounting entries for period-end accruals. The accrual process creates liabilities for goods received but not yet invoiced, which happens when you enter and match invoices to corresponding receipts/POs.

The special calendar in Payables is used for recurring invoices - it defines the schedule for invoices that occur at regular intervals. Option B refers to the Payables calendar (not special calendar), and Option C refers to the future periods setting (not calendar-based).

During PO matching, the system updates the quantity billed on the purchase order and copies PO distributions to create invoice distributions. Tolerances are checked (not 'enforced' in a way that blocks matching outright without settings), and quantity received is updated during receiving, not matching.

Oracle Payables' Recurring Invoices feature is specifically designed for automatically generating invoices at regular intervals, such as monthly rent payments. You define the invoice template once, and the system creates new invoices automatically based on the schedule you set. RTS Invoices are for return-to-supplier transactions, while Retroactive Price Adjustment Invoices handle price changes, not periodic billing.

The Mass Additions Create Program transfers capital invoice line distributions from Oracle Payables to Oracle Assets when lines are marked as 'Track as Asset.' This program populates the Mass Additions interface table in Oracle Assets for processing into fixed asset records. The other programs handle different functions: purging open interface data, sweeping unaccounted transactions, and validating invoices.

In Oracle EBS, once an invoice is validated it cannot be deleted - only cancelled. Prepayments can be applied to one or more invoices sharing the same supplier and site as the prepayment. Payables invoices integrate with Oracle Assets by sending lines marked 'Track as Asset' to the Mass Additions interface for asset creation. Since all three statements are true, 'All of the above' is correct.

Oracle Payables has three main open interfaces: Payables Open Interface (for invoices), Payables P-Card Open Interface (for procurement card transactions), and Payables Credit Card Open Interface (for credit card transactions). 'Payables payment interface' is not one of the standard interfaces - payments are created through payment processes and formats, not through an interface table.

An Expense Report in Oracle Payables represents the amount due to an employee for business-related expenses incurred. Employees submit expense reports for reimbursement of costs like travel, meals, or supplies. Mixed invoices are PO-related, PO Default references purchase orders, and Credit Memos represent supplier credits, not employee reimbursements.

Oracle Payables can automatically create all three invoice types with proper setup: Recurring Invoices (scheduled periodic invoices), RTS Invoices (Return to Supplier for return material authorization), and Retroactive Price Adjustment Invoices (when supplier price changes affect previously purchased goods). Each requires specific configuration but can be generated automatically.

Oracle Payables supports multiple payment methods including Check, Wire, and Clearing (for electronic payments). DD (Direct Debit) is not a standard payment method in Oracle Payables - it's a banking term but not a Payables payment method type. The system uses Electronic Funds Transfer (EFT) for automated debits, not labeled as 'DD'.

To interface Payables invoice lines with Oracle Assets, two prerequisites exist: the invoice must be transferred to General Ledger (accounting created), and the distribution account must be either an Asset Clearing account or a CIP (Construction in Progress) account. These conditions ensure only asset-related capital costs flow to Assets. Since both A and B are required, 'All the above' is correct.

The manual payment method in Oracle Payables is used to record a payment that was made outside the Payables system, such as a handwritten check or a wire payment initiated directly at the bank. You're simply recording the payment transaction for accounting purposes, not creating or printing it. This differs from Quick Payment, which generates the payment within Payables.

Quick Payment in Oracle Payables creates and prints a computer-generated payment to pay a supplier for one or more selected invoices. You select the invoices, and the system generates the payment (check or electronic) immediately. This differs from manual payment (recording external payments) and payment batches (processing multiple suppliers at once).

A Prepayment in Oracle Payables is an invoice used to pay an advance payment to a supplier or employee before goods or services are received. Prepayments are later applied to regular invoices when they arrive. Standard invoices are for regular purchases, Expense Reports reimburse employees, and Quick Match is a matching method, not an invoice type.

A Credit Memo in Oracle Payables represents a credit for goods or services, typically issued when goods are returned to a supplier or when a supplier owes the customer money. It reduces the amount owed to the supplier. Debit Memos increase liability (not credits), Expense Reports reimburse employees, and QuickMatch is an invoice creation method.

Quick Match is the feature in Oracle Accounts Payable that automatically matches all purchase order shipment lines to an invoice in a single step. When you use Quick Match, the system automatically finds and matches all applicable PO shipments to the invoice lines based on the PO number, eliminating manual line-by-line matching. This is different from regular PO Default invoice matching where you match lines individually.

All the listed types are valid invoice types in Oracle Accounts Payable: QuickMatch invoices (matched to POs), Prepayment invoices (advance payments), and Mixed invoices (combining multiple types). Therefore 'All of the above' is the correct answer. Each type serves different business needs in the procure-to-pay process.

The Payables Open Interface is the standard mechanism for importing supplier invoices into Oracle E-Business Suite. While GL Open Interface handles journal entries and Receivables Open Interface processes customer receipts, Payables Open Interface specifically handles supplier invoice imports, making it the most common interface for getting invoices into the system.