Banking Services and Operations

An Agent Bank (or correspondent bank) acts as the custodian that holds the Nostro account on behalf of the customer bank. Therefore, the Nostro account is indeed held at the agent bank.

A Nostro account (derived from the Latin word for 'ours') is an account that a bank holds in a foreign currency at another, usually foreign, bank, allowing for international transactions.

In requirements engineering, functional requirements specify what a system must do while non-functional requirements specify how the system performs those functions. Security is a classic non-functional requirement at the architectural level because it defines quality attributes like confidentiality and integrity. A checking account rule represents a functional requirement at the design level because it specifies specific business logic the system must implement.

NFC (Near Field Communication) is the technology that enables mobile phones to function as credit cards through contactless payment. NFC allows short-range wireless communication between devices when brought close together. FFC, MFC, and CTMS are not related to contactless payment technology.

The bank account in the Payment Batches and Payments window defaults from the Payables Options (specifically the Payments region). While supplier or supplier site setups can store payment preferences, the primary default control for the batch bank account originates from the Payables Options level.

Auto Lockbox requires Auto Cash Rule Sets to automatically apply incoming customer payments to open invoices. When banks send payment files, Lockbox uses these rules to match receipts with the correct invoices based on criteria like invoice number, PO number, or other matching attributes.

In Oracle Receivables, a Lockbox is set up and defined for a specific bank account to automate the receipt entry process. Defining it at the bank account level ensures that incoming payments are correctly matched and processed.

Auto Lockbox is the banking service that automatically processes and applies customer receipts via electronic transmission. Banks send payment files containing remittance information, and the Auto Lockbox program automatically applies receipts to open invoices. Direct Debit (A) pulls funds from accounts, Automatic Clearing (B) is not a standard term for this service, and Electronic Fund Transfer (D) is the generic technology but not the specific Oracle Receivables feature name.

Oracle Payables is a source for cash OUTFLOW (making payments), not inflow. Oracle Receivables (customer payments) and Oracle Order Entry (sales orders) generate inflows. Therefore Payables is not a source for cash inflow.

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.

Subinventory transfers in Oracle EBS generally do not require formal approval workflows. These are routine inventory movements between subinventories that can be performed directly unless specific approval controls have been explicitly configured by the organization.

Before creating an alternate bill of materials or alternate routing, the primary bill or routing must already be defined for that item. The primary structure acts as the base template. Other options like copying or importing still require a primary reference to exist first.

The 'Mutually Exclusive' attribute applies to option class bills of material and controls whether a customer can select only one or multiple options within that option class during configuration.