Previous | Next | Contents | Index | Navigation | Glossary | Library |
Note: All options, except for Set of Books, are updatable.
If Payables is fully installed but Receivables is only a shared installation, then the list of values is limited to the sets of books chosen in Payables. If Receivables is fully installed but Payables is only a shared installation, then the list of values is limited to the sets of books chosen in Receivables. If neither Payables nor Receivables is fully installed, then all sets of books defined in General Ledger (the GL_SETS_OF_BOOKS table) are included in the list of values.
Cash Management supports multiple sets of books. Each responsibility is tied to a set of books and an operating unit. In a multiple organization environment, you set up System Parameters for each operating unit. You assign bank statements to your current operating unit, and reconcile payments and receipts in that operating unit.
Begin Date: Cash Management will not display payment, receipts, journals, and open interface transactions dated earlier than the Begin Date.
Show Cleared Transactions: If you check this check box, cleared transactions remain available for reconciliation. Otherwise, only uncleared transactions will appear for reconciliation.
Add Lines to Automatic Statements: If you do not check this check box, you cannot add lines to automatically loaded bank statements.
Use Reconciliation Open Interface: You must check this check box if you want to use the Reconciliation Open Interface to reconcile bank statement lines to receipts and payments created outside Oracle Receivables and Oracle Payables.
Matching Order: Setting these options for Payables and Receivables controls how the AutoReconciliation program searches for transactions to match bank statement lines. You can choose to have Cash Management match Transactions or Batches first.
Note: Carefully choosing these options can lead to better performance during the AutoReconciliation process.
Tax Codes: AutoReconciliation uses these codes when creating miscellaneous transactions. There are two Tax Codes fields:
Float Handling: This parameter specifies how to handle reconciliation of bank statement lines where the effective date is later than the current date. The effective date may have been user-entered, or it may have been derived. Cash Management derives an effective date by adding the value in the Float Days field in the Bank Transaction Codes window to the statement date.
There are two choices on how to handle this float:
Tolerances: Reconciliation Tolerances include a variance Amount and a variance Percent. (See: Reconciliation Tolerances).
Tolerance Differences: There are two Tolerance Differences you can set:
Note: This option applies only to Oracle Payables transactions and batches. Oracle Receivables transaction differences are booked only to the bank Charges account.
Note: Oracle Receivables transaction differences are booked only to the bank Charges account.
Note: You cannot archive transactions without also purging them. However, you can purge transactions without archiving. Also note, the purge and archive check boxes on the System Parameters window only affect the bank statement interface tables. To purge or archive/purge bank statement tables, you must run the Archive/Purge program.
Lines per Commit: This is the number of lines that AutoReconciliation will save at a time, and controls the number of Payment and Receipt rows that AutoReconciliation locks at any given time. The greater the number of lines, the faster AutoReconciliation processes. However, the number of lines you can specify is limited by the amount of memory your system has available.
Previous | Next | Contents | Index | Navigation | Glossary | Library |