Master the Oracle Cash Management auto-reconciliation and clearing processes.
Oracle Cash Management (CE) is used to manage enterprise liquidity and control bank account balances. The core process is Bank Reconciliation: matching the transactions recorded in your subledgers (AP Payments, AR Receipts) against the actual bank statements provided by your financial institution.
Your company bank accounts must be defined in Cash Management (R12) or the Centralized Setup (Fusion).
Map the bank's transaction codes (e.g., 165 for Credit, 475 for Check Paid) to Oracle transaction types.
Rules that tell the system how to match a bank line to a system transaction (e.g., matching by Check Number and Amount).
Treasury Analyst
Treasury Analyst
Treasury Analyst
Treasury Analyst
Actor: Treasury Analyst | Module: Oracle Cash Management
The first step is bringing the bank's electronic statement file (often in BAI2, MT940, or CAMT.053 format) into Oracle. This is usually automated via an SFTP integration but can be loaded manually.
Example: The bank sends a daily BAI2 file. The "Bank Statement Loader" program reads the flat file and inserts the data into the CE statement interface tables.
Navigation Path:
Cash Management > Load and Import Bank Statement
Key Actions:
Usually handled by the "Process Electronic Bank Statement" scheduled process.
Actor: Treasury Analyst | Module: Oracle Cash Management
Once imported, you must verify that the statement loaded correctly. Sometimes a line might fail validation (e.g., an unrecognized transaction code).
Example: The analyst queries the bank statement for Dec 1st. One line has an error "Invalid Transaction Code". The analyst maps the new code to an Oracle type and re-saves the line.
Navigation Path:
Cash Management > Bank Statements
Key Actions:
Review the Bank Statement Lines UI for any validation errors.
Actor: Treasury Analyst | Module: Oracle Cash Management
AutoReconciliation is a concurrent program that automatically matches bank statement lines to AP Payments, AR Receipts, and Payroll checks based on the rules defined in the setup.
Example: The program matches a $5,000 withdrawal on the bank statement to AP Payment #10245 because the amounts and check numbers are identical.
Navigation Path:
Cash Management > Submit AutoReconciliation
Key Actions:
Fusion uses a very robust rules engine. Ensure Tolerance rules (for slight date or amount variances) are configured if needed.
Actor: Treasury Analyst | Module: Oracle Cash Management
AutoReconciliation rarely matches 100% of lines. Exceptions (like a combined wire transfer covering 5 invoices, or a slight bank fee deduction) must be reconciled manually by the user.
Example: The analyst sees an unreconciled $100 bank fee. They manually match it to a miscellaneous transaction or create a new GL journal directly from the reconciliation screen.
Navigation Path:
Cash Management > Manual Reconciliation
Key Actions:
Use the drag-and-drop or checkbox interface to match statement lines to system transactions.
Actor: General Ledger Accountant | Module: Subledger Accounting (SLA)
The act of clearing/reconciling transactions creates accounting events (e.g., clearing the AP Cash Clearing account). These events must be transferred to the GL.
Example: Run the Create Accounting program for AP and AR to push the cleared payment/receipt accounting to the General Ledger.
Navigation Path:
Handled via AP / AR Create Accounting programs.
Key Actions:
Same as R12. The clearing accounting belongs to the source subledger.
Understand how AP payments are generated before they hit the bank.
Read Guide