## Processing Bank Statements Manually

This chapter provides overviews of manual bank statement processing, transaction codes, and transit accounts, and discusses how to:

1. Enter bank statement transactions.

2. Refresh account reconciliation information.

3. Run the Bank Journal Statement Process program.

### Understanding Manual Bank Statement Processing

If banking practices in your country rely heavily on magnetic media processing, electronic fund transfers, and direct bank involvement for settling outstanding debts, you can use the bank statement process to reconcile your bank account by manually entering transaction information from your bank statement directly into EnterpriseOne software.

For each transaction, you enter a transaction code that specifies how the system reconciles the transaction. You can use the transaction codes that EnterpriseOne provides, or you can set up your own codes.

Depending on the types of transactions that you enter, you might need to perform additional tasks, such as posting receipts, payments, and journal entries, before you run the Refresh Reconciliation File program (R09130). You must post batches before running this program so that the WF - Account Ledger Reconciliation workfile (F0911R) contains all records.

If your banking process involves clearing all transactions through one bank account and then applying them to specific accounts during bank statement processing, you can use a transit account.

Note. You can process bank statement information by using electronic data interchange (EDI) media. You can receive information regarding specific bank accounts through EDI and reconcile the bank statements that are stored in EnterpriseOne.

See Also

Receiving EDI Standard Business Documents

#### Common Elements Used in This Chapter

Customer Bank Account Number | The number assigned by a bank to identify the account for a company. Note. For users in Nordic countries, this is the bank, Bankgiro, or Postgiro account number.
Bank Transit | The number assigned to a particular bank by the Federal Reserve to facilitate the clearing of funds.

### Understanding Transaction Codes

You must assign a transaction code to each item that appears on a bank statement. This code identifies the type of transaction, such as a journal entry or customer payment, and specifies the detail information that the system requires to reconcile the entry.

For the system to identify your transactions correctly, you must associate each transaction with a transaction code from UDC table 09/BJ. You can change the codes provided by EnterpriseOne to make them more suitable for your organization. Although you can change the code as well as the description for each code, you cannot change the function of a transaction type or the first two characters in the Description 02 field. For example, you can change the transaction code and the description of transaction type 02 (Cash Receipt - Batch). You cannot change the function to be a journal entry transaction and you cannot change the first two characters of the Description 02 field to, for example, 03.

The transactions that you enter are grouped into these two categories:

- Transactions that cleared your bank account and have been entered in the system.

- Transactions that cleared your bank account and have not been entered in the system.

Transactions That Cleared Your Bank Account and Have Been Entered in the System

This table shows setup information for transaction types that cleared your bank account and have been entered in the system:

Transaction Code | Description 01 | Description 02 | Description
CR | Cash Receipt Clear | 04 Cash Receipt Clear | This transaction code is used to record deposits or other receipts that you previously entered in the system.
CK | Payment Clear | 08 Payment Clear | This transaction code is used to record canceled checks or payments that you previously entered in the system.

Transactions That Cleared Your Bank Account and Have Not Been Entered in the System

This table shows setup information for transactions that cleared your bank account and have not been entered in the system:

Transaction Code | Description 01 | Description 02 | Description
JE | Journal Entry | 01 Journal Entry | This transaction code is used to record an adjustment that was made by the bank, such as a service charge or a wire transfer fee. These transactions might have an associated value-added tax (VAT).
CRE | Cash Receipt - Batch | 02 Cash Receipt - Batch | This transaction code is used to record payments that a customer made directly to your bank account, such as a wire transfer, that you have not previously entered in the JD Edwards EnterpriseOne Accounts Receivable system. When you run the Bank Journal Statement Process program (R09170), the system automatically applies the receipt to invoices by running the Update Receipts Header (R03B551) and Apply Receipts to Invoices (R03B50) programs.
CRI | Cash Receipt - Interactive | 03 Cash Receipt - Interactive | This transaction code is used to record payments that a customer made directly to your bank account, such as a wire transfer, that you have not previously entered in JD Edwards EnterpriseOne Accounts Receivable. When you enter a transaction with this code, the Bank Statement Entry program (P09160) launches the Standard Receipts Entry program (P03B102) so that you can apply the receipt manually to the correct invoices.
DP | Draft Paid to Supplier | 07 Draft Paid | This transaction code is used to record drafts that have been submitted by your suppliers to your bank for payment.
PWM | Manual Payments with Match | 10 Manual Payments with Match | This transaction code is used to record payments. When you enter transaction with this code, the system launches the Payment With Voucher Match program (P0413M).
PWO | Manual Payments without Match | 11 Manual Payments without Match | This transaction code is used to record payments. When you enter a transaction with this code, the system launches the Payment Without Voucher Match program (P0411).
BK | Self Reconciling | 09 Self Reconciling | This transaction code is used to record self-reconciling items. A self-reconciling item does not require reconciliation and does not launch a program.

### Understanding Transit Accounts

To clear all payments and receipts through one bank account and then apply them to a specific bank account during bank statement processing, you can use a transit account. To use a transit account, you specify the transit account in the processing options for the Bank Statement Entry program. When you run the Bank Journal Statement Process program, the system creates a journal entry to reallocate the amounts from the transit account to the bank account. You can use a transit account with these transaction codes only:

- CR

- CRE

- CRI

- CK

When you use transit accounts, you do not need to run the Refresh Reconciliation File program (R09130) to update the F0911R table. However, because you do not update the F0911R table, the Bank Journal Statement Process program cannot compare information between the F0911R and F0917 tables to determine whether an item should be reconciled. The system assumes that the information that you entered in the F0917 table is correct. Therefore, you must reconcile the transit account to ensure the accuracy of the information entered for the bank statement.

When the system reconciles the transaction, it marks the bank account as reconciled but does not mark the transit account.

### Entering Bank Statement Transactions

This section provides an overview of bank statement transactions and discusses how to:

- Set processing options for Bank Statement Entry (P09160).

- Enter bank statement transactions.

#### Understanding Bank Statement Transactions

Entering bank statement information involves entering header information, such as the statement date and the beginning balance, and then entering information that is specific to each transaction on your statement, such as the transaction code and the amount. Depending on the transaction code, you also need to enter detailed information about the transaction, such as an account number or a payment number.

When you enter each transaction into the system using the Bank Statement Entry program, the system creates records in the Bank Statement Header (F0916) and Bank Statement Detail (F0917) tables. The F0917 table contains a record for each transaction that you enter for the bank statement. The F0916 table usually contains one header record for each bank statement. This header record includes information such as the bank statement number, bank account number, and beginning balance. Depending on how your bank creates statements, you might have more than one header record in the F0916 table for each statement. For example, if your bank issues one statement for multiple bank accounts, the F0916 table would contain a header record for each account.

When you enter a transaction code and amount, the system displays the corresponding detail form for the transaction if you set the Editing Mode processing option for the Bank Statement Entry program accordingly.

As you enter transactions, the system updates the Remaining Amount field on the Enter Statement form. When the remaining amount is zero, the statement is in balance. The system also updates the total number of transactions (lines), the number of incomplete transactions, the total withdrawal amount, and the total deposit amount as you enter transactions. If a statement is out of balance, you can display only the incomplete lines to correct the missing information.

The system displays the word Processed next to transactions that have been processed in the system.

#### Forms Used to Enter Bank Statement Transactions

Form Name | FormID | Navigation | Usage
Work With Bank Statements | W09160B | Manual Bank Statement Processing (G09211), Bank Statement Entry | Review a list of bank statements for a specific bank account. You can delete an entire bank statement on this form only if all transactions are unprocessed.
Enter Statement | W09160A | On the Work With Bank Statements form, click Add to enter transactions. Or select the statement to access transactions for an existing statement. | Enter bank statement transactions. You can add transactions to and revise transactions for unprocessed bank statements only.
Clear Receipts | W09160J | On the Enter Statement form, enter CR in the TR CDe field and click OK. | Add detailed information for a cleared cash receipt.
Journal Entry | W09160E | On the Enter Statement form, enter JE in the TR CD field and click OK. | Add detailed information for a journal entry.
Clear Payment | W09160G | On the Enter Statement form, enter CK in the TR CD field and click OK. | Add detailed information for a cleared payment.
Automatic Receipts Entry | W09160I | On the Enter Statement form, enter CRE in the TR CD field and click OK. | Add detailed information for a batch cash receipt.
Receipt Entry | W03B102E | On the Enter Statement form, enter CRI in the TR CD field and click OK. | Add detailed information for an interactive cash receipt.
Clear Draft Payment | W09160H | On the Enter Statement form, enter DP in the TR CD field and click OK. | Add detailed information for a draft that is paid to a supplier.
Enter Voucher - Payment Information | W0411A | On the Enter Statement form, enter PWO in the TR CD field and click OK. | Add detailed information for a manual payment without a matching voucher.
Manual Payment Entry | W0413MA | On the Enter Statement form, enter PWM in the TR CD field and click OK. | Add detailed information for a manual payment with a matching voucher.
Options | W09160D | On the Enter Statement form, select Options from the Form menu. | Specify search criteria for the transactions that you want to review or revise.

#### Setting Processing Options for Bank Statement Entry (P09160)

Use these processing options to set default values for the Bank Statement Entry program.

Criteria

1. Short account ID for the default bank account | Specify whether the system should preload a bank account in the query-by-example (QBE) row. You must enter the short account ID of the bank account. If you leave this processing option blank, the system does not preload a bank account.
2. User ID preload | Specify whether the system should preload a user ID in the QBE row. Values are: Blank: Do not preload a user ID. 1: Preload a user ID.
3. Posted Code | Specify whether the system should preload a specific posted code in the QBE row. Values are: A: Preload a posted code of A (approved). D: Preload a posted code of D (processed).
4. Pre-load records | Specify whether the system should preload all records. Values are: Blank: Do not preload all records. If the system does not preload all records, you must click Find on the Work With Bank Statements form to load the records. 1: Preload all records.

Defaults

1. Default Deposit Transaction Type and 2. Default Withdrawal Transaction Type | Specify a default transaction type from UDC table 09/BJ for deposit amounts and withdrawal amounts.
3. Default Transit Accounts (Short account ID) | Enter the short account ID for the types of transactions specified in the previous processing options.
Automatic Receipts Entry, Receipts Clear, Manual Receipts Entry, and Payment Clear | Enter the short account ID of the default transit account for each processing option.

Journal Entry

1. Default short account ID for Journal Entry transactions | Enter the short account ID of the default account for journal entries.

Dates Tab

1. Value Date (GDVLDT) and, 2. G/L Date (GDDGJ) | Specify the default date to use for the value date and the GL date. The value date is the date that the payment amount was debited or credited to the bank account. The GL date identifies the financial period to which a transaction is posted. Values are: 0: Use the GL date. 1: Use the statement date.

Document Type

1. Default Document Types for Transaction Codes BK - Self-Reconciling, CK - Payment - Clear, CR - Cash Receipt - Clear, CRE - Cash Receipt - Batch, CRI - Cash Receipt - Interactive, DP - Draft Paid to Supplier, JE - Journal Entry, PWM - Manual Payments w/Match, and PWO - Manual Payments w/o Match | Enter the default document type from UDC table 00/DT for each processing option and corresponding transaction code.

Display 1

Gross Amount (GDAG), Remark (GDRMK), Bank Transit (GDTNST), Cleared/Value Date (GDVLDT), Reference (GDR1), and Explanation (GDEXA) | Specify whether to restrict access to the field associated with each processing option. Values are: Blank: Do not restrict access. 1: Restrict access.

Display 2

Transit Account (GDANI) and G/L Date (GDDGJ) | Specify whether to restrict access to the field associated with the processing options. Values are: Blank: Do not restrict access. 1: Restrict access.
2. Home Business Unit | Specify whether to restrict access to the Home Business Unit field or to remove the field from the form. Values are: Blank: Allow regular access. 1: Restrict access. 2: Remove this field from the form.
3. Default Bank Account (specified in the Criteria tab) | Specify whether to allow users to change the default bank account. Values are: Blank: Allow. 1: Do not allow.

Versions

1. Override Manual Receipts Entry processing, 2. Override Manual Payments with Voucher Match processing, and 3. Override Manual Payments without Voucher Match processing | Specify which version to use of the Standard Receipts Entry (P03B102), Payment With Voucher Match (P0413M), and Payment Without Voucher Match (P0411) programs. If you leave a processing option blank, the system uses version ZJDE0001.

Entry Mode

1. Editing Mode | Specify the type of editing that the system performs on the Enter Statements form. Values are: 0: The system does not display the detail form and, therefore, does not perform any editing. 1: The system displays the detail form, but does not perform any editing if you enter incorrect information or leave required fields blank on the form. 2: The system displays the detail form and performs editing if you enter incorrect information or leave required fields blank on the form.
2. Exit Out of Balance | Specify whether a user can exit the Enter Statement form out of balance. Values are: Blank: Allow the user to exit out of balance. 1: Set an error that does not allow the user to exit out of balance. 2: Set a warning if the user attempts to exit out of balance, but still allow the user to exit out of balance.

Prev Balance

1. Bank Statement Beginning Balance | Specify the mode for populating the beginning balance of the bank statement. Values are: Blank: Allow the user to manually enter the beginning balance. 1: Load the beginning balance using the ending balance from the previous bank statement. This processing option requires that bank statements be entered in sequential order and that the previous statement be completely reconciled before entering the next one. 2: Load the beginning balance using the account balance as of the bank statement date. Include posted transactions only. 3: Load the beginning balance using the account balance as of the bank statement date. Include both posted and unposted transactions. Note. Entering a 1, 2, or 3 in this processing option disables the Beginning Balance field on the Enter Statement form.

Transaction Codes

BK - Self-Reconciling, CK - Payment -Clear, CR - Cash Receipt - Clear, CRE - Cash Receipt - Batch, CRI - Cash Receipt - Interactive, DP - Draft Paid to Supplier, JE - Journal Entry, PWM - Manual Payments w/Match, and PWO - Manual Payments w/o Match | Specify whether to allow the transaction code associated with the processing option. Values are: Blank: Allow the code. 1: Do not allow the code.

#### Entering Bank Statement Transactions

Access the Enter Statement form.

Header Area Fields

Statement Date | Enter the date of the bank statement. This date is used as the general ledger date when you process bank statements.
Statement Number | Enter the statement number assigned by the bank.

Detail Area Fields

TR CD (transaction code) | Enter a valid code from UDC table 09/BJ to identify the type of transaction on a bank statement.
Value Date | Enter the date that the payment amount was debited or credited to the bank account. The value date is not the date that the bank reconciled the payment. Automatic payments populate this field automatically. If the Value Date processing option is 0, the system uses the default GL date from the header area for this field. If it is1, the system uses the statement date.
G/L Date | Enter the GL date or the bank statement date. If the G/L Date processing option is 0, the system uses the default GL date from the header area in this field. If it is 1, the system uses the statement date.
Pmt/Rcpt Number (payment/receipt number) | Based on the transaction code in the TR CD field, do one of the following: CR: Enter the batch number of the receipt. The system validates this number to verify whether the receipt batch number exists. CK: Enter the number of the payment. The Bank Journal Statement Process program uses this number to locate the payment record in the F0911 table when reconciling the transaction. JE: Leave this field blank. CRE or CRI: Enter the number of the receipt from the bank statement. The system does not validate either number against any other tables in JD Edwards EnterpriseOne. DP: Enter the payment number of the draft paid to the supplier. PWM or PWO: Leave this field blank. The system uses the number that you enter for the payment.
Ty (type) | Enter the code from UDC table 00/DT that specifies the kind of document that is used to match the original document. If you entered a default document type for the transaction code in a processing option, the system uses it as the default.
G/L Posted Code | A code that designates the processed and reconciled status of a bank statement transaction. This code represents the G/L posted code status of F0917 records as well as the reconciliation status of F0917 and F0911 records. For unprocessed or unreconciled records, the G/L Posted Code field in the F0917 table is A and the Reconciled field is blank. For processed or reconciled records, valid codes are specified in the processing options for the Bank Journal Statement Process program (R09170). These codes are edited against UDC table 09/RC. For reconciled records, the code in the G/L Posted Code field is the same as the code in the Reconciled field for both the F0917 and F0911 tables.

After you enter a transaction on the Enter Statement form and click OK or select Detail from the Row menu, the system displays one of the following, based on a processing option setting:

- If the Editing Mode processing option is 1 or 2, the system displays the detail form that corresponds to the transaction code that you entered. If you entered CR, the system displays the Clear Receipts form. If you entered CK, the system displays the Clear Payment form and so on.

  If the Editing Mode processing option is 2, the system also performs editing if you enter an invalid value or leave required fields blank on the detail form.

  Default values for some fields on the detail form are specified in processing options for the Bank Statement Entry program.

- If the Editing Mode processing option is 0, the system does not display a detail form. Instead, it displays the warning message Incomplete Transactions Exist. Click OK and then Cancel. You must remember to enter the detail at another time.

### Refreshing Account Reconciliation Information

This section provides an overview of the Refresh Reconciliation File program, lists a prerequisite, and discusses how to:

- Run the Refresh Reconciliation File program.

- Set data selection for Refresh Reconciliation File.

- Set processing options for Refresh Reconciliation File (R09130).

#### Understanding the Refresh Reconciliation File Program

After you enter bank statement transactions, you must run the Refresh Reconciliation File program (R09130). This program updates the F0911R table with the transactions that you recorded prior to receiving your bank statement. When you run the Bank Journal Statement Process program, the system compares the transaction information in the F0911R table with the information that you entered in the F0917 table using the Bank Statement Entry program. If the information for the transaction in the tables matches, the system reconciles the transaction.

Note. Run this program only for transactions that do not use a transit account. If all transactions on your bank statement use a transit account, do not run this program.

The Refresh Reconciliation File program is also used to reconcile bank account transactions manually.

See Refreshing Account Reconciliation Information.

#### Prerequisite

Post any unposted batches.

#### Running the Refresh Reconciliation File Program

Select Manual Bank Statement Processing (G09211), Refresh Reconciliation File.

This program updates the F0911R table with posted batches only.

#### Setting Data Selection for Refresh Reconciliation File

For faster processing, use data selection to specify the accounts to be reconciled.

To create the F0911R table for only one account, enter the short account ID number in the data selection. If you subsequently refresh the F0911R table using a specific account number in the data selection, the system adds the new records to the previous records and does not clear the F0911R table.

#### Setting Processing Options for Refresh Reconciliation File (R09130)

Use these processing options to specify the records that you want to include in the F0911R table.

Select

1. Beginning Date and 2. Ending Date | Specify the beginning and ending date to refresh the F0911R table.
3. Reconciled Status | Select the transactions to include in the F0911R table. Values are: Blank: Reconciled transactions only. 1: Both reconciled and unreconciled transactions. The F0911R table can become unmanageable and impact processing time if you choose to include both reconciled and unreconciled transactions on a regular basis. Include both reconciled and unreconciled records only when you need to correct a previous reconciliation.

Default

1. Ledger Type | Specify the ledger type that the system uses to select records from the F0911 table. If you leave this processing option blank, all ledger types are selected.

Display

1. Document Type Filter | Specify whether the system includes adjusting entry (AE) transactions when selecting records from the F0911 table. Values are: Blank: Do not include AE transactions. 1: Include AE transactions.

Print

1. Messages | Specify whether the system prints messages on the Refresh Reconciliation File report (R09130) for all accounts or only for accounts that are refreshed. Values are: Blank: Print messages only for accounts that are refreshed. 1: Print all messages.

### Running the Bank Journal Statement Process Program

This section provides an overview of the Bank Journal Statement Process program and discusses how to:

- Run the Bank Journal Statement Process program.

- Set data sequence for Bank Journal Statement Process.

- Set processing options for Bank Journal Statement Process (R09170).

- Review the bank statement processing reports.

- Process batch cash receipt transactions.

#### Understanding the Bank Journal Statement Process Program

The Bank Journal Statement Process program (R09170):

- Compares transaction information.

  The program compares each transaction in the F0911R table with the corresponding transaction in the F0917 table to verify that information such as the amount and the date are the same in each table.

  If you used a transit account, the program does not compare the two tables; the system assumes that the information that you entered in the F0917 table is correct. You must reconcile the transit account to ensure the accuracy of the information.

- Runs the Update Receipts Header (R03B551) and Apply Receipts to Invoices (R03B50) programs.

  If you entered CRE transactions, the Bank Journal Statement Process program runs these two programs to create receipts and apply them to invoices.

- Creates journal entries.

  If you used a transit account, the program creates a journal entry to reallocate the amount from the transit account to the bank account.

  Note. You must post the journal entry batches that the system creates after you run the Bank Journal Statement Process program.

- Generates reconciliation reports.

  The program generates these reports, which show the results of the comparison between the F0911R and F0917 tables:

  - Bank Journal Statement Processing

  - Bank Reconciliation Report

  - Cleared Not Issued

  - Cleared Before Issued

  - Amounts Not Equal

  - Unreconciled Items

- Reconciles transactions.

You specify in the processing options whether to run the program in proof or final mode. In proof mode, the system prints reconciliation reports but does not reconcile transactions.

In final mode, for each transaction with matching information in the F0911R and F0917 tables, the system updates the GLRCND (Reconciled Code) field in the F0911 table with R..To use a reconciliation code other than R, enter a different code in the processing options for the Bank Journal Statement Process program. If you used a transit account, the system updates the GLRCND field without comparing the two tables.

You also specify in the processing options whether you want the system to update the Reference 3 field for the transaction in the F0911 table with the bank statement number. These programs display or print the information in the Reference 3 field:

- Account Ledger Inquiry (P09200)

- Account Inquiry by Category Code (P09202)

- Transaction Journal (R09321)

#### Prerequisite

Run the Refresh Reconciliation File program to refresh the F0911R table with updated information.

See Also

Processing Bank Statements Manually in Multiple Currencies

#### Running the Bank Journal Statement Process Program

Select Manual Bank Statement Processing (G09211), Bank Journal Statement Process.

#### Setting Data Sequence for Bank Journal Statement Process

The data sequence for bank statements must be in this order:

1. Statement number

2. Statement date

3. Bank account number

#### Setting Processing Options for Bank Journal Statement Process (R09170)

Use these processing options to specify the records that you want to include when you process bank statements.

Proof/Final

1. Process Mode | Specify the mode in which to process bank statements. Values are: Blank: Proof mode. Do not update the F0911 table. 1: Final mode. Update the F0911 table.

Document Type

1. Document Type | Enter a code from UDC table 00/DT that begins with U. (U1–U9 and UA–UZ and are reserved for clients.) If you leave this processing option blank, the system uses JE as the default document type. For document type JE, the system uses the next number for journal entries to assign a document number to the transaction. If a document type other than JE, the system uses the next number for bank journals.

Variance

1. Variance Tolerance Limit | Enter an amount for the tolerance limit for automatic write-offs. You can also enter an amount with a percent sign to indicate that the number should be used as a percentage. If you leave this processing option blank, tolerance limits are not used.
2. Journal Entry Creation | Specify whether to automatically create journal entries to write off variances that are equal to or less than the tolerance limit. Values are: Blank: Do not automatically create journal entries. Variance amounts are listed separately. 1: Automatically create journal entries.
3. Enter the date mode for the Journal Entry. | Specify the date to use for the journal entry. Values are: 0: System date. 1: General ledger date. 2: Value (cleared) date.
Business Unit | Enter the business unit of the GL account for the journal entry. If you leave this processing option blank, the system uses the business unit of the bank account that appears on the bank statement.
Object Account and Subsidiary | Enter the object account and the subsidiary of the GL account for the journal entry.

Realized Gain/Loss

1. Realized Gain/Loss Processing | Specify whether to create realized gain and loss journal entries. Values are: Blank: Do not create entries. 1: Create entries.
2. Date Mode | Specify the date to use for realized gain and loss journal entries. Values are: 0: System date. 1: General ledger date from the F0911R table. 2: Value (cleared) date from the F0917 table.

Date

1. Transaction Mode for Value (Cleared) Date | Specify how to manage transactions if the value (cleared) date is earlier than the general ledger date in the F0911 table. Values are: Blank: Do not reconcile the transactions, but print them on the report. 1: Reconcile the transactions and print them on the report. 2: Reconcile the transactions, but do not print them on the report.

Reconciliation

If you leave any of these processing options blank, the system uses the value from the first condition. Enter a code from UDC table 09/RC for each processing option.

Exact One for One Match without Consolidation or Use of Tolerance Rule (Default 'R') | Enter a code for an exact one-for-one match.
Consolidated Items Where the G/L Transactions Balance to Zero and There is No Bank Record. | Enter a code for consolidated items with a balance of zero and no bank record.
Consolidated Items Where the Bank Transactions Balance to Zero and There is No G/L Amount. | Enter a code for consolidated items with a balance of zero and no amount.
The Consolidation Process was Used to Achieve the Match of the Transactions. (There are G/L and Bank Statement Transactions.) | Enter a code for the consolidation process.
The Transactions Were for Different Values But Fell Within the Tolerance Allowed. | Enter a code for transactions with different values that are within the tolerance allowed.
This Transaction Only Exists in the Bank Statement File and is a Self Reconciling Item. | Enter a code for self-reconciling items.

Statement

1. Enter the Mode for Populating the GLR3 Reference Field in the F0911 with the F0917 Bank Statement Number. | Specify whether to update the GLR3 (Reference 3) field in the F0911 table with the bank statement number in the F0917 table for corresponding records. Values are: Blank: Do not update the GLR3 field. 1: Update the GLR3 field. If you specify final mode for processing, the system overwrites any previous value in the GLR3 field.

#### Reviewing the Bank Statement Processing Reports

The Bank Journal Statement Process program generates these reports, which provide information about the reconciliation status of bank statement transactions:

Report | Description
Bank Journal Statement Processing | Lists summary information about each batch. If the program reconciled the transaction, the report prints the message No Errors Found. If the program was unable to reconcile the transaction, the report prints the message **See Reconciliation Reports **.
Bank Reconciliation | Lists detail information about each transaction on the bank statement. The report has separate columns for issued amount and date, and cleared amount and date. The issued amount and date column uses information from the F0911R table. The cleared amount and date column uses information from the F0917 table. The report also includes the status of each transaction after the reconciliation process.
Cleared Not Issued | Lists transactions that are in the F0917 table but are not in the F0911R table.
Cleared Before Issued | Lists transactions that are in the F0917 table with a cleared date that is prior to the GL date in the F0911R table.
Amounts Not Equal | Lists transactions that have different amounts in the F0917 and F0911R tables.
Unreconciled Items | Lists all unreconciled items in the F0917 table.

Note. If column C (consolidated) on a report contains an asterisk, that particular line on the report consists of multiple transactions that are consolidated together.

#### Processing Batch Cash Receipt Transactions

CRE transactions are not created until you run the Bank Journal Statement Process program. You must complete these additional steps to reconcile the transactions after you run the program:

1. Post the receipt batch.

2. Run the Refresh Reconciliation File program.

3. Manually reconcile the transactions using the Bank Account Reconciliation form, which you access from the Manual Reconciliation program (P09131).