About Bank Statement Validation
The AutoReconciliation program validates the information you load into the bank statement open interface tables. If the data passes validation, AutoReconciliation imports it into the main Cash Management tables. If any records in a statement fail validation, Automatic Reconciliation does not import the statement and assigns it an Error status.
You can use the AutoReconciliation Execution Report or the View Reconciliation Errors window to review any import validation errors. You can use the Bank Statement Interface window to correct any import validation errors.
Bank Statement Header Validation
Import validation requires that the imported bank statement header information pass the following checks:
- The bank account must be a currently defined internal bank account.
- If the bank account number is not unique within the system, you must provide a bank and branch name, in the interface table.
- If you provide a currency code in the header, it must be the same as the currency code defined for the bank account in Oracle Payables or Oracle Receivables.
Control Total Validation
Many bank statements provide control totals in the statement or account header for error-checking purposes. The bank statement header interface table has seven control total columns. If you enter values into any of these, AutoReconciliation uses those values for validation, except for CONTROL_BEGIN_BALANCE.
The control totals are as follows:
CONTROL_BEGIN_BALANCE: The statement opening balance. No validation is done for this entry.
CONTROL_END_BALANCE: The statement closing balance.
CONTROL_TOTAL_DR: Payment control total in the statement header must match the total payment amount on the statement lines. Payments are statement lines that have a bank transaction code with a type of Payment, Misc. Payment, NSF or Rejected.
CONTROL_TOTAL_CR: Receipt control total in the statement header must match the total receipt amount on the statement lines. Receipts are statement lines that have a bank transaction code with a type of Receipt, Misc Receipt, or Stop.
CONTROL_DR_LINE_COUNT: Number of payment lines in the statement must match the payment line control total in the statement header. Payments are statement lines that have a bank transaction code with a type of Payment, Misc. Payment, NSF or Rejected.
CONTROL_CR_LINE_COUNT: Number of receipt lines in the statement must match the receipt line control total in the statement header. Credits are statement lines that have a bank transaction code with a type of Receipt, Misc. Receipt, or Stop.
CONTROL_LINE_COUNT: Number of lines in the statement must match the line control total in the statement header.
Statement Line Validation
Currency Code: If you enter a currency code on the statement line, it must be a currency that is defined in the system. The currency code does not affect the matching or calculations.
Bank Transactions Codes: Bank Transaction Codes, if entered, must be defined in Cash Management.
Exchange Rate Type: The Exchange Rate Type must be a valid type as defined in Oracle General Ledger.
Amount: An amount must be entered for the statement line.
Multi-Currency Validation
AutoReconciliation checks each bank statement line for a valid currency and exchange rate type. During reconciliation, the program checks the following once a matching transaction is found:
- Bank statement line currency must be the same as the transaction currency. (Your bank statement currency may be different.)
- All transactions in the batch must use the same currency.
- Statement line currency is the same as the batch currency.
- For both transactions and batches:
- For user exchange rates, each transaction must include the Exchange Rate, and the Rate Type must be User.
- For predefined rates (such as Corporate or Spot), each transaction must include the Rate Type and Exchange Rate Date.
See Also
System Parameters
Bank Statement Open Interface
Loading Bank Statement Open Interface
Importing Bank Statements
Reviewing Bank Statement Interface Errors
Correcting Bank Statement Interface Errors
Reconciling Bank Statements Automatically
Multi-Currency Handling
Archiving and Purging Imported Bank Statements