Managing Bank Statements 346166667.doc Effective Mm/dd/yy Page 1 of 18 Rev 1

Managing Bank Statements
Overview
Copyright 2007, Oracle. All rights reserved.
Managing Bank Statements 346166667.doc

Effective mm/dd/yy Page 1 of 18 Rev 1
System References
Distribution
Job Title*
Ownership
The Job Title [list@YourCompany.com?Subject=EDUxxxxx] is responsible for ensuring that this
document is necessary and that it reflects actual practice.


Objectives

Agenda

Overview

Entering Bank Information
Entering Bank Information

Prior to reconciliation, you must enter the bank statement data into Oracle Cash Management
manually or using a Bank Statement Loader program, custom loader program, or automatic
bank transmission feature.

Loading the Bank Statement Open Interface
Loading the Bank Statement Open Interface

Using the Bank Statement Open Interface
Before you can reconcile transactions with a bank statement, you need to enter the bank
statement information into Oracle Cash Management.
If your bank provides bank statements in a flat file, you can use the bank statement open
interface to load this information into Oracle Cash Management.
The Bank Statement Open Interface consists of two bank statement open interface tables:
Bank Statement Headers Interface Table CE_STATEMENT_HEADERS_INT_ALL
Bank Statement Lines Interface Table CE_STATEMENT_LINES_INTERFACE

Loading Bank Statement Open Interface: Using the Bank
Statement Loader Program
Loading Bank Statement Open Interface: Using the Bank Statement Loader
Program
Use the Bank Statement Loader program to map and transfer bank statement data from an
electronic bank statement into the open interface tables in Oracle Cash Management.
You can execute the Bank Statement Loader program in one of the following modes:
Load
Load and Import: Bank Statement Import program starts after the Bank Statement
Loader program completes successfully.
Load, Import, and AutoReconciliation: Bank Statement Import and AutoReconciliation
programs launch after successful completion of the Bank Statement Loader program.
In either case, if the Bank Statement Loader program completes with errors or warnings, the
concurrent request terminates. You can review the exceptions encountered by the Bank
Statement Loader program using the Bank Statement Loader Execution Report.

Loading Bank Statement Open Interface: Using a Custom Loader
Program
Loading Bank Statement Open Interface: Using a Custom Loader Program

First, define own bank statement mapping rule if necessary. Then, run the custom loader
program against the bank statement file to populate the Bank Statement Open Interface tables.
Verify that the bank statement data was loaded into the open interface tables correctly.
You can use the Bank Statement Interface window to ensure that bank statement header
information is correctly inserted into the CE_STATEMENT_HEADERS_INT_ALL table.
You can use the Bank Statement Lines Interface window to ensure that bank statement
transaction lines are correctly inserted into the CE_STATEMENT_LINES_INTERFACE table.
The Bank Statement Interface and Bank Statement Lines Interface windows show you the
statement header and lines information in the open interface tables. You can correct the data
using these windows or you can correct the original bank statement file and reload it using
your custom loader program.

Loading Bank Statement Open Interface: Intra-Day Bank
Statement Loader Program
Loading Bank Statement Open Interface: Intra-Day Bank Statement Loader

Program
Use the Intra-Day Bank Statement Loader program to load updated bank statements.
The Load option loads the bank statement data into the Bank Statement Open Interface
tables, where you can make corrections prior to import.
The Load and Import option automatically starts the Intra-Day Bank Statement Import
program after the Intra-Day Bank Statement Loader program completes.
When submitting the intra-day bank statement loader program, you must:
Use the Bank Statement Loader Execution Report to review any exceptions.
Set up Oracle Treasury for integration with Oracle Cash Management.
Create a SQL*Loader script for the format of your bank statement, if it is neither BAI2
nor SWIFT940.
Define a mapping template for the format of your bank statement file.

Loading Bank Statement Open Interface: XML Bank Statements
Loading Bank Statement Open Interface: XML Bank Statements

You can set up the XML Gateway to receive XML bank statements automatically from your
bank. The bank delivers the prescheduled bank statements to the XML Gateway, which
validates the message, populates the Bank Statement Open Interface tables, and launches the
Bank Statement Import program to transfer bank statement data to Cash Management. If the
validation fails, the XML Gateway sends email notifications to the administrator and bank
contact.
When setting up your system to receive XML bank statements, ensure that Oracle XML
Gateway, Oracle Advanced Queuing, and Oracle Workflow Business Event System are
installed and both the bank and your system should use Oracle Transport Agent. If the bank is
not using Oracle Transport Agent, the bank needs to integrate its communication software to
conform to the Oracle Transport Agent message protocol.

Importing Bank Statements
Importing Bank Statements

You must import the bank statement data into the Cash Management Bank Statement tables if
you load them into the Bank Statement Open Interface tables and if you are to reconcile.

Importing Bank Statements: Bank Statement Validation
Importing Bank Statements: Bank Statement Validation

Use the AutoReconciliation Execution Report or the View Reconciliation Errors window to
review any import validation errors.
Use the concurrent request log file to review any errors or warnings related to Treasury.
Use the Bank Statement Interface window to correct any import validation errors.

Reviewing and Correcting Bank Statement Interface Errors
Reviewing and Correcting Bank Statement Interface Errors

Bank Statement Interface Errors
Use the Bank Statement Interface window to review import validation errors from the Bank
Statement Open Interface tables.
Review the AutoReconciliation Execution Report.
Review all import and validation errors for a statement.

Entering Bank Statements Manually
Entering Bank Statements Manually

Prerequisites in Entering Bank Statements
Define your banks.
Define bank transaction codes for the bank account.
Set up receivables activities and payment methods for miscellaneous transactions.
Set up sequential document numbering for Cash Management.

Entering Bank Statements Manually (continued)
Entering Bank Statements Manually (continued)

Refer to Practice Enter a Cash Journal [LAB3F70Y]
Refer to Practice Pay Invoices in Payables [LAB3F71Y]
Refer to Practice Enter Receipts [LAB3F72Y]
Refer to Practice Enter a Bank Statement [LAB3F73Y]

Summary


Managing Bank Statements 346166667.doc Effective Mm/dd/yy Page 1 of 18 Rev 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Managing Bank Statements 346166667.doc Effective Mm/dd/yy Page 1 of 18 Rev 1

Uploaded by

Copyright:

Available Formats

Managing Bank Statements

Copyright 2007, Oracle. All rights reserved.