Oracle Financials: Purchasing and Cash Management

When payments are reconciled in Oracle Cash Management, their status updates to 'reconciled' to indicate they've matched with bank statement lines. This status change prevents duplicate reconciliation and provides audit trail visibility. The workflow ensures payment records reflect their true bank-cleared state for accurate financial reporting.

The bank reconciliation sequence follows logical workflow: first receive the physical/electronic statement from bank, then load and verify it into system (validation step), perform reconciliation to match transactions, and finally post to General Ledger. Loading before verification is impossible, and reconciliation requires loaded data. This sequence ensures data integrity before accounting impact.

Bank Reconciliation is the process that verifies internal bank balances in Oracle Financials match the actual bank statement balance. This control detects discrepancies, errors, or timing differences between company records and bank records. Cash Forecasting projects future positions, Auto Reconciliation automates matching, and Remittance handles payment transmissions.

The 'Bank Statement Import and Auto Reconciliation' program combines both operations in a single execution for efficiency. It first loads the bank statement data into Oracle, then immediately runs auto-reconciliation to match transactions. Running separate programs requires two manual steps and scheduling coordination.

Oracle Receivables handles incoming customer payments (cash inflows), not outflows. Payroll processes employee salary payments, Payables manages vendor payments, and Purchasing handles procurement-related disbursements - all representing cash outflow sources. Receivables is the only module focused on cash collection.

Manual bank statement entry requires complete system configuration: Define Banks establishes the bank entity, Define bank transaction codes maps statement codes to Oracle actions, and Set up Receivables activities handles miscellaneous transaction classification. All three must exist before manual entry can function properly.

The Cleared Transactions Report displays all transactions that have been cleared through bank statement matching, whether manually entered or auto-reconciled. This report provides visibility into reconciliation activity and audit trail. Bank Statement Detail shows line-level detail, Transaction Detail is generic, and Reconciled Transactions is not the standard report name.

The 'Payables transfer to General Ledger' program moves accounted subledger entries from Payables to GL interface tables for posting. This creates the accounting linkage between Payables transactions and the General Ledger. Other options are generic names or incorrect - AP Reconciliation is different functionality.

The Bank Statement Detail Report shows individual statement line items with their reconciliation status, including unreconciled lines. This granular view helps identify remaining reconciliation work. GL Reconciliation is different, Cleared Transactions shows only matched items, and Auto Reconciliation Execution Report shows program run results.

Option C is false because Oracle prevents updates to reconciled bank statements to maintain data integrity and audit trails. Once reconciled, statements are locked from modification. Option B correctly states you CANNOT update reconciled statements. This is a control feature preventing accidental changes to matched data.

The Invoice Exceptions Report specifically identifies transactions that are missing from the Aging report, often due to data inconsistencies or timing issues. This helps close process discrepancies. It does not identify workflow-stuck orders, Transaction Register missing items, or unposted transactions.

The Transactions Available for Reconciliation report displays all transactions that are ready for reconciliation for a specific bank account. This report is used to identify which transactions have been processed by the bank and are available to be matched against the general ledger. Options A, B, and C refer to different reports - cash in transit, cleared transactions, and batch reports - but do not show all transactions available for reconciliation.

Cash forecasting is a planning tool that helps businesses anticipate cash inflows and outflows, allowing them to project future cash needs and assess liquidity. Unlike cash inflow (A) and cash outflow (B) which are individual components, cash forecasting encompasses the complete planning process. Cash prediction (D) is not the standard terminology used in financial management.

The Batches Available for Reconciliation report lists both payment batches and remittance batches that are ready for reconciliation. This report groups transactions into batches for easier processing. Option B refers to individual transactions, while options C and D describe only partial aspects of the report's functionality.

GL Reconciliation report is used to reconcile the general ledger cash account to the bank statement balance. This process ensures that the company's internal records match the bank's records. AR (Accounts Receivable) and AP (Accounts Payable) reconciliation focus on those specific modules, while Auto Reconciliation is a process, not a report type.

The Auto Reconciliation execution report is used to review the results of the auto reconciliation program run. This report shows which transactions were automatically matched and any exceptions that need manual review. Execution report (A) is too generic, Output report (B) is not the correct terminology, and Statement report (D) refers to bank statements.

In Purchasing, a Requisition status of 'Returned' indicates that the buyer has rejected the requisition, typically due to issues with the request. This is different from approver rejection (A), which would show a different status, or preparer cancellation (C) and supplier cancellation (D), which have different workflows.

The 'Use Approval hierarchies' flag in Financial Option Setup enables Position Hierarchy-based approvals, where document routing follows the organizational position structure rather than employee-supervisor relationships. Employee/Supervisor Hierarchy (A) is a separate approval method, while Direct and Indirect forward methods (C, D) are document routing options, not approval hierarchy types.

Receiving transactions in Purchasing encompasses tracking material from receipt through final delivery, including recording movements during receiving and inspection processes. Option A only describes initial receipt, while Option C focuses on quality control. Option D refers to a later accounts payable process. The complete definition includes the full traceability aspect.

A PO shows Pre-Approved status when the final authority approves it but forwards it for additional approval, or when using encumbrance budgeting where the PO is approval-eligible but funds aren't yet reserved. This status indicates the PO has passed initial approval stages but requires additional steps before full approval.