Previous	Next		Contents	Index	Navigation	Glossary	Library

• Matching: Match a bank statement line against Receivables and Payables transactions using a transaction number (such as the check or deposit number), bank account, amount, and currency. You can also match a statement line against a General Ledger journal entry.

For automatic reconciliation, the transaction amount must be equal to the bank statement line amount, or the difference between the amounts must fall within a specified tolerance. If the matching criteria are not met, the statement line remains unmatched.

For manual reconciliation, there are no restrictions for matching statement lines and transactions.

• Clearing: After matching a bank statement line and a transaction, they can be cleared. Cash Management assigns a cleared date and amount for all receipts and payments that your bank reports as cleared, and initializes the accounting transactions.

Matching Criteria for Oracle Payables Transactions

• The transaction currency is the same as the bank statement line currency.

• For payment batches (such as EFT batches), the Reference or Payment Batch Name matches the statement line Transaction Number, and the transaction amount is within the reconciliation tolerance.

• For the detail payment transactions and stopped transactions, the matching sequence is the same: first the program tries to match against the invoice number and supplier bank account, then just the invoice number, and finally the payment number. Also, the transaction amount is within the reconciliation tolerance.

Note: For payments with no check number, such as electronic payments, matching to the invoice number and supplier bank account number is particularly useful.

• For stopped transactions the payment must first be stopped or voided in Oracle Payables.

Matching Criteria for Oracle Receivables Transactions

• The transaction currency is the same as the bank statement line currency.

• For remittance batches (such as Direct Debit batches), the Remittance Batch Deposit Number or Receipt Batch Name matches the statement line Transaction Number and the transaction amount is within the reconciliation tolerance.

• For detail remittance transactions, NSF (Non-Sufficient Funds), and Rejected transactions, the matching sequence is the same: first the program tries to match against the invoice number and customer bank account, then just the invoice number, and finally the receipt number. Also, the transaction amount is within the reconciliation tolerance.

• For NSF (Non-Sufficient Funds) or Rejected transactions the receipt must first be reversed in Oracle Receivables.

Note: For receipts with no check number, such as electronic payments, matching to the invoice number and customer bank account number is particularly useful.

Matching Criteria for Miscellaneous Transactions

• If the transaction type matches to regular miscellaneous transactions:

• The transaction amount is within the reconciliation tolerance.

• The Receipt Number matches the statement line Transaction Number.

• If the transaction type matches to correction statement lines:

• For reversal corrections, the statement line has the same transaction number, same amount, and opposite transaction type (for example, Miscellaneous Receipt and Miscellaneous Payment).

• For adjustment corrections, the statement line has the same transaction number, and has a transaction type of payment, receipt, miscellaneous payment, or miscellaneous receipt, and the net amount is within the reconciliation tolerance.

Matching Criteria for General Ledger Journals

• The journal line is posted.

• The journal line Accounting Flexfield matches the bank account's asset Accounting Flexfield.

• The journal line Description matches the statement line Transaction Number.

See Also