Skip to main content

Reconciling Bank Statements Manually


In Cash Management you can reconcile a bank statement manually as well as automatically. You can use the manual method to reconcile any bank statement, whether imported or entered manually. In addition, you can create new bank statement lines as you reconcile transactions, as well as update the reconciliation information for a previously manually-or automatically-reconciled statement.
When you use manual reconciliation, you reconcile each bank statement line with available transactions. You can search for Payroll payments, Receivables receipts, Payables payments, miscellaneous transactions, GL journal entries, open interface transactions, and statement lines that meet specific criteria, and reconcile the statement line against them. If the bank statement belongs to a bank account shared by Oracle Treasury and Oracle Cash Management, you can search for Treasury settlements using the Reconciliation Open Interface. You can search for transactions based on customer or supplier, batch name, or remittance number, as well as ranges for transaction numbers, transaction date, transaction amount, and maturity date. You can search for journal entries based on Period Name, Journal Entry Name, Document Number, or Line Number.
As you reconcile a statement manually, you may need to create transactions to account for differences between the sum of the reconciled transaction and the line amount. For example, you can create a miscellaneous transaction to account for bank charges or interest. You can also create Payables payments and Receivables receipts from Cash Management. To account for amount differences for Treasury settlements, you need to create exposure transactions in Oracle Treasury.
Recalculating Amount Differences
When manually reconciling, you can automatically default the amount difference between the statement line amount and the transaction amount to the Charges and Errors field based on how the system parameters are set.
For Payables payments or payment batches:
When the AP Tolerance Differences system parameter is set to Errors, the statement line charges amount defaults to the Charges field. The remaining amount difference between the statement line amount and the transaction amount defaults to the Errors field.
When the AP Tolerance Differences system parameter is set to Charges or is not defined, the amount difference between the statement line amount and the transaction amount defaults to the Charges field.
For Receivables receipts or remittance batches:
The amount differences between the statement line amount and the transaction amount defaults to the Charges field.


To manually reconcile a previously-entered bank statement:
1. Import or manually enter the statement information.
Note: If you don't use Oracle Receivables Automatic Lockbox, and your bank statement includes direct deposits or bank transfers, you must create the related receipts manually in Receivables before you can reconcile them in Cash Management. For more information on Automatic Lockbox, see your Oracle Receivables User's Guide.
2. Navigate to the Find Bank Statements window.
3. Enter the query criteria for the statement you want to reconcile, or leave the criteria blank to query all existing statements.
4. Choose Find to see the Reconcile Bank Statements window containing the statements that meet your query criteria.
Note: You can open custom folders that display statement information in a custom format if you or your organization has defined any. Refer to the Oracle Applications User's Guide for more information on modifying and saving folders.
5. Select the statement you want to reconcile, and choose Review. Cash Management displays the Bank Statement window, with the header information for the account you queried, including Bank Name, Bank Branch, statement Date, bank Currency, Document Number, and Statement Number. You can update any of the header information except for the bank information and the Currency. If you use automatic document sequence numbers, you cannot change the Document Number either.
The GL date defaults to the bank statement date. You can update it, or override it on the individual payment or receipt transaction.
6. Choose Lines to see the Bank Statement Lines window.
7. Select the statement line that you want to reconcile.
8. Choose Available to search for detail or batch transactions that are available for reconciliation.
9. Enter your search criteria in the Find Transactions window.
10. Select the available detail and batch transactions that apply to the current bank statement line.
11. (Optional) Choose the Recalculate button.
12. Reconcile the available detail or batch transactions.
13. Reconcile other statement lines.
14. (Optional) Create miscellaneous transactions for bank statement transactions with no matching Payables, Receivables, or General Ledger activity.
Note: Miscellaneous payments are actually handled as negative receipts by Cash Management. Therefore, to create miscellaneous payments you must have Receivables installed and set up.
15. (Optional) Create payments or receipts for bank statement transactions with no matching Payables or Receivables activity.
16. Reverse any NSF or rejected bank transactions.
17. Optionally, when you have reconciled all the bank statement lines, mark your bank statement as complete.
18. Save your work.
19. You can review the results of reconciliation in the following reports:
Bank Statement Detail Report
Bank Statement Summary Report
Bank Statement Document Number Report
20. Transfer the accounting transactions you created during reconciliation for Payables and Receivables to your General Ledger.
21. Review the GL Reconciliation Report.

Comments

Popular posts from this blog

Applying Prepayments to Invoices

You can apply the available amount of Item type distributions from a Temporary type prepayment to one or more invoices to offset the amount you pay on the invoice(s). If you entered the prepayment as a Permanent type and want to apply it, you can query the prepayment in the Invoices window and change the Prepayment Type to Temporary. If you use Automatic Offsets then your setting for the Prevent Prepayment Application Across Balancing Segments Payables option controls whether you can apply a prepayment to an invoice or expense report with a different balancing segment. Prerequisites The invoice type is Standard, Mixed, or Expense Report. Today's date is on or after the Settlement Date of the prepayment. The invoice date is on or after the date of the prepayment. The prepayment is type Temporary, fully paid, validated, not cancelled, has no active holds, and has not already been fully applied. The prepayment has the same supplier, invoice currency and payment currenc

Application Utilities Lookups and Application Object Library Lookups

Maintain existing and define additional Lookups for your shared Lookup types. You can define up to 250 Lookups for each Lookup type. Each Lookup has a code and a meaning. For example, Lookup type YES_NO has a code Y with meaning Yes, and a code N with a meaning No. Note: In Releases 11.0 and earlier, there were two Lookup features, Special Lookups and Common Lookups. These two features have been merged into one. The new consolidated Lookups feature has Lookups maintained in this form. If you make changes to a Lookup, users must log out then log back on before your changes take effect. Lookups Block Type Query the type of your Lookup. You can define a maximum of 250 Lookups for a single type. User Name The user name is used by loader programs. Application Query the application associated with your Lookup type. Description If you use windows specialized for a particular Lookup type, the window uses this description in the window title. Access Level The access level restricts changes that

Matching Prepayments to Purchase Orders

You can match a prepayment to a purchase order or receipt. The accounting entries for Item distributions on a matched prepayment typically debit a prepayment account that Payables provides. However, during prepayment entry you can override any account that Payables defaults or builds. Payables does not create an encumbrance entry for the prepaid amount when a prepayment is matched to a purchase order. The match is treated like a reservation of the quantity billed. Payables does not calculate the invoice price variance or exchange rate variance at this point. Furthermore, you cannot change the unit price during the prepayment match to purchase order. A final match to the purchase order is not allowed either. When the matched prepayment is applied to an invoice, Payables reverses the matched quantity on the prepayment to reflect the balance of the total quantity matched. The following example illustrates a prepayment application to a purchase order: You contract to attend a $5,000 trade