Reviewing Reconciliation Errors

After you run the AutoReconciliation program, you can review any reconciliation errors online from the Bank Statement or Bank Statement Line window. You can review all reconciliation errors for a statement, or just those errors that occurred for a specific statement line.

Note: The Bank Statement window shows errors for both statements and individual lines. To review import validation errors, use the Bank Statement Interface window.

Prerequisite

To review reconciliation and validation errors:

  1. Navigate to the Find Bank Statements window.

  2. Enter your query criteria, or leave the criteria blank to query all existing statements.

  3. Choose Find to see the Reconcile Bank Statements folder window containing the statements that meet your query criteria.

  4. Select the statement whose errors you want to review, and choose Review.

  5. If you want to review statement line errors, choose Lines.

  6. Choose Errors. You see the Reconciliation Errors window, showing a list of all reconciliation errors for all statement lines, or the selected statement line if you are reviewing statement line errors. See the following chart for further explanation of any error.

You can correct any reconciliation errors in the bank statement and rerun AutoReconciliation, or reconcile the statement lines manually.

Bank Reconciliation Errors

The following table contains bank reconciliation error codes and explanations of those error codes.

Error Code Explanation
AP period not open or future The GL date is not in an open or future period in Oracle Payables.
AR period not open or future The GL date is not in an open or future period in Oracle Receivables.
Cannot find transactions to lock  
Charge amount exceeds tolerance The charge amount cannot be greater than the tolerance amount.
Currencies don't match The statement line currency is not the same as the Foreign currency bank account. Reconciliation is not allowed.
Duplicate BACS payment batches Duplicate BACS payment batches
Duplicate journal entries Oracle General Ledger has more than one matching journal entry line.
Duplicate NACHA payment batches Duplicate NACHA payment batches
Duplicate Open Interface transactions More than one Open Interface transaction number matches the bank statement transaction number.
Duplicate payment batches Oracle Payables has more than one matching payment batch.
Duplicate payments There is more than one matching payment in Oracle Payables. Please reconcile manually.
Duplicate payroll payments There is more than one matching payroll payment in Oracle Payroll.
Duplicate receipts Oracle Receivables has more than one matching receipt.
Duplicate remittance batches Oracle Receivables has more than one matching remittance batch in.
Duplicate statement lines There is more than one matching statement line.
EFT payment amount does not match The payment amount does not match the amount on the line.
Exchange rate date missing The statement line does not have an exchange rate date.
Exchange rate type missing The statement line does not have an exchange rate type.
Future payment not yet negotiable This future dated payment's status is "Issued". You can reconcile future dated payments only if the payment status is "Negotiable". The payment status can be updated to "Negotiable" in Payables after the maturity date.
Future value date You cannot reconcile a statement line that has a future value date.
Inconsistent currencies The statement line and the transaction currency are different.
Inconsistent exchange rates The statement line exchange rate and the GL daily rate for the exchange type and exchange rate date do not match.
Inconsistent transaction currencies within batch All transactions within a batch must be in same currency.
Line amount ledger currency not within the tolerance range The statement line amount in the ledger currency is not within the tolerance range.
Miscellaneous receipt currency doesn't match bank currency Miscellaneous receipts must have the same currency as the foreign bank account currency.
Missing exchange rate information This message appears for one of the following reasons: 1) The exchange type is User, and you have not provided both the exchange rate and the exchange rate date; 2) The bank currency differs from your ledger currency and you are creating a miscellaneous receipt; 3) You are creating a foreign currency miscellaneous receipt.
Missing matching criteria The statement line needs at least one of the following criteria to match, and all are missing: 1) transaction number; 2) invoice number and agent name; 3) invoice number and agent bank account.
No document sequence defined Document sequence is not set up for the receipt/payment method.
No matching BACS payment batches No matching BACS payment batches
No matching journal entries Oracle General Ledger has no journal entry line that matches the bank statement transaction number.
No matching NACHA payment batches No matching NACHA payment batches
No matching Open Interface transactions The Open Interface has no transaction number that matches the bank statement transaction number.
No matching payment Oracle Payables has no payment number that matches the bank transaction number.
No matching payment batch Oracle Payables has no payment batch number that matches the bank statement transaction number.
No matching payment for the invoice number and the agent bank account Oracle Payables has no matching payment for the invoice number and the agent bank account.
No matching payment for the invoice number and the agent name Oracle Payables has no matching payment for the invoice number and the agent name.
No matching payroll payments Oracle payroll has no payroll payment number that matches the bank statement transaction number and amount.
No matching receipt Oracle Receivables has no receipt number that matches the bank transaction number.
No matching receipt for the invoice number and the agent bank account Oracle Receivables has no receipts that match the invoice number and the agent bank account number.
No matching receipt for the invoice number and the agent name Oracles Receivables has no receipts that match the invoice number and the agent name.
No matching remittance batch Oracle Receivables has no remittance batch number that matches the bank statement transaction number.
No matching statement line A matching statement line cannot be found.
No partial reconciliation for EFT payments. You must unreconcile all Payroll transactions that are reconciled to the statement line.
No receivables activity or payment method for tolerance receipt Autoreconciliation could not create a miscellaneous receipt for the tolerance amount for this NSF line because at least one of the following parameters were not entered at program submission: receivables activity, payment method.
Note: AP reconciliation accounting not enabled You can reconcile this payment, and Payables will update the payment status to Reconciled but Unaccounted. However, note that the Oracle Payables option "Account for Payment When Payment Clears" is not enabled. Therefore Payables accounts for the payments and gain/loss only at payment issue time, and does not account for bank charges, bank errors, or gain/loss at payment clearing time.
Payment method for the bank account is invalid The payment method for the bank account is invalid.
Receipt already reconciled The receipt has already been reconciled to statement line.
Receipt is not reversed The receipt history shows that this receipt has not been reversed. The statement line has a transaction code identifying it as NSF.
Receipt not remitted The receipt history shows that this receipt has not been remitted to the bank.
Receipt reversed The receipt history shows that this receipt has been reversed. The statement line has a transaction code identifying it as a receipt.
Reconciliation Open Interface not enabled Please enable "Use Reconciliation Open Interface" in the Bank Account Controls region of the Bank Account.
Statement line amount is not within the tolerance range The statement line amount is not within the tolerance range.
Stop initiated You have initiated a stop on the payment in Oracle Payables. You can match to a stop initiated payment only if the transaction code is "Stopped". However, this transaction line code is "Payment".
Stopped statement line The payment has not been voided or stop initiated. However, the statement line is "Stopped". The statement line can be matched to a payment only if the payment has been voided or stop initiated.
The statement line is currently in use. Please try again later. The statement line is currently in use. Please try again later.
The Cleared Date for this payment is earlier than the Transaction Date. This is a warning to let you know the Cleared Date for this payment is earlier than the Transaction Date.
The transaction is currently in use. Please try again later. The transaction is currently in use. Please try again later.
Undefined exchange rate No exchange rate is defined in General Ledger for this combination of exchange date and exchange type.
Voided The payment is voided in Oracle Payables. You can match to a voided payment only if the transaction code is "Stopped". However, this transaction line code is "Payment".
Voided (Payroll) The payroll payment is voided in Oracle Payroll. You can match a statement line to this payment only if the transactions code is "Stopped". However, the transaction code is "Payment".