Managing Bank Statements

About Bank Statement Validation

See: To Submit the Intra-Day Bank Statement Loader Program

Importing Bank Statements

If you load electronic bank statements into the Bank Statement Open Interface tables, you must import the bank statement information into the Cash Management Bank Statement tables before you can reconcile the statement detail lines.

Oracle Cash Management's Bank Statement Import program validates the information in the Bank Statement Open Interface tables and imports the validated bank statement information. If you import bank statements from bank accounts that are used by Oracle Treasury, the Bank Statement Import program also updates the bank account balances seen in Oracle Treasury. Additionally, the Bank Statement Import program can launch the AutoReconciliation program to perform an automatic reconciliation after the import process completes.

If you load intra-day bank statements, you must use the Intra-Day Bank Statement Import program to validate and import the information into the Cash Management Intra-Day Bank Statement tables.

After you have successfully imported the intra-day bank statements, you can include the information in your cash positioning in Oracle Treasury. Since intra-day information is not used for reconciliation, you cannot view the imported intra-day bank statements in Cash Management windows or reports. However, you can archive or purge the bank statements. When you import multiple intra-day bank statements within the same day, the Intra-Day Bank Statement Import program deletes the existing bank statement before importing the new bank statement.

You can use one of several ways to import data from the Bank Statement Open Interface tables into the Bank Statement tables.

To load and import a bank statement in the same request:

Navigate to the Submit Request window.
Select the Bank Statement Loader program.
Choose the option of Load and Import.
Specify the other parameters as appropriate.
Submit your request.

See: To Run the Bank Statement Loader Program.

To load, import, and reconcile a bank statement in the same request:

Navigate to the Submit Request window.
Select the Bank Statement Loader program.
Choose the option of Load, Import and AutoReconciliation.
Specify the other parameters as appropriate.
Submit your request.

See: To Run the Bank Statement Loader Program.

To import a bank statement only, without AutoReconciliation:

Navigate to the Submit Request window. Alternatively, you may submit the request directly from the Bank Statement Interface window by selecting AutoReconciliation from the Oracle Applications Tools menu.
Select the Bank Statement Import program.
Enter the Bank Account Number for the statement you want to import.
Specify the range of statement numbers in the Statement Number From and Statement Number To fields.
Specify dates for the Statement Date From, Statement Date To, and GL Date fields.

The GL Date is the default date for all General Ledger journal entries generated by AutoReconciliation. The date must be in an open or future-enterable Payables or Receivables period.
Submit your request. The Bank Statement Import program validates the data in the Bank Statement Interface tables, imports the validated information, and prints an AutoReconciliation Execution Report.
Review and correct any import validation errors, then repeat the steps above.

To import and reconcile a bank statement in the same request:

Navigate to the Submit Request window.
Select the Bank Statement Import and AutoReconciliation program.

Note: Alternatively, you may submit the request directly from the Reconcile Bank Statements window or Bank Statement Interface window by selecting AutoReconciliation from the Oracle Applications Tools menu.
Enter the Bank Account Number for the statement you want to import.
Specify the range of statement numbers in the Statement Number From and Statement Number To fields.
Specify dates for the Statement Date From, Statement Date To, and GL Date fields.
Select a Receivable Activity and a Payment Method to create Miscellaneous Receipts for differences that AutoReconciliation encounters when matching remittance batches or NSF transactions within tolerances.
Specify how to handle any NSF transactions that are in your bank statement. Choose:
- No Action: to handle manually
- Reverse: to reverse receipt and reopen the invoices
- Debit Memo Reverse: to create a debit memo that replaces the item closed by the original receipt
Submit your request. The AutoReconciliation program validates the data in the Bank Statement Open Interface tables, imports the validated information, reconciles the bank statement, and prints an AutoReconciliation Execution Report.

Note: You can get an AutoReconciliation Execution Report at any time by submitting a request using the Submit Request window.
Review and correct any import validation errors, then repeat steps above. Once any import validation errors have been corrected, the AutoReconciliation program submits a request to reconcile the bank statement.

To load and import an intra-day bank statement in the same request:

Navigate to the Submit Request window.
Select the Intra-Day Bank Statement Loader program
Choose the option of Load and Import.
Specify the other parameters as appropriate.
Submit your request.

To import an intra-day bank statement only

Navigate to the Submit Request window. Alternatively, you may submit the request directly from the Bank Statement Interface window by selecting AutoReconciliation from the Tools menu.
Select the Intra-Day Bank Statement Import program.
Enter the Bank Account Number for the statement you want to import.
Specify the range of statement numbers in the Statement Number From and Statement Number To fields. The list of values displays only intra-day bank statements that are within the range.
Specify dates for the Statement Date From and Statement Date To fields.
Submit your request. The Intra-Day Bank Statement Import program validates the data in the Bank Statement Interface tables, imports the validated information, and prints an AutoReconciliation Execution Report.
Review and correct any import validation errors, then repeat the steps above.

Related Topics

About Bank Statement Validation

Loading Bank Statement Open Interface

About Bank Statement Open Interface

Multi-Currency Handling

Bank Statement Open Interface

About Bank Statement Validation

The Bank Statement Import program validates the information you load into the Bank Statement Open Interface tables. If the data passes validation, the program imports it into the Cash Management Bank Statement tables. If any records in a statement fail validation, the program does not import the statement and assigns the statement 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 defined.
If the bank account number is not unique within the system, you must provide a bank and branch name in the Bank Statement Headers Interface table.
The bank statement currency must be the currency defined for the bank account.
If the bank account is used by Oracle Treasury, you must have access to the company that owns the Treasury bank account.

Control Total Validation

Many bank statements provide control totals in the statement header for error-checking purposes. The Bank Statement Header Interface table has seven control total columns. The Bank Statement Import program verifies the values in these columns as follows. If the program encounters exceptions with the control totals, it generates warning messages but proceeds to import the statement.

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. The closing balance should satisfy the following equation:

CONTROL_END_BALANCE = CONTROL_BEGIN_BALANCE + CONTROL_TOTAL_CR - CONTROL_TOTAL_DR.

CONTROL_TOTAL_DR: Payment control total in the statement header should 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 should 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 should 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 should 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 should match the line control total in the statement header.

Statement Line Validation

Values populated in the CE_STATEMENT_LINES_INTERFACE table must not contain any trailing spaces.

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:

For transactions:
- Bank statement line currency must be the same as the transaction currency. (Your bank statement currency may be different.)
For batches:
- 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.

Related Topics

System Parameters

Loading Bank Statement Open Interface

Multi-Currency Handling

Country Specific Bank Account Validations

Reviewing Bank Statement Interface Errors

You can use the Bank Statement Interface window to review import validation errors that resulted when you imported bank statement information from the Bank Statement Open Interface tables. In addition, you can review the AutoReconciliation Execution Report that is printed automatically by the Bank Statement Import program.

You can review all import and validation errors for a statement, or you can review only those errors that occurred for a specific statement line.

Note: Only import validation errors are available from the Bank Statement Interface window. To review reconciliation-related errors, use the Reconcile Bank Statements window.

If you encounter import errors, you can correct the data one of three ways:

Use the Bank Statement Interface and Bank Statement Interface Lines window.
Repair the Bank Statement Open Interface tables manually.
Repair, reload, and re-import the original bank statement file.

Prerequisite

Import bank statement information from the Bank Statement Open Interface tables. See: Importing Bank Statements

To review bank statement interface errors online:

Navigate to the Bank Statement Interface window .
Query the statement whose interface errors you want to review.
Choose Errors. You see the Bank Statement Interface Errors window containing the list of interface errors.
Choose Done to exit.

Tip: If you prefer to review the errors in a printed report, the AutoReconciliation Execution Report is run automatically when you run either of the programs that include Bank Statement Import.

Related Topics

Statement Interface Window Reference

Account Number: The bank account number as defined in Oracle Payables, Oracle Receivables, or Oracle Payroll.

Bank Name: The name of the bank.

Bank Branch: The name of the bank branch.

Currency: The currency of the bank account.

Intra-Day: Indicates whether or not the statement is an intra-day bank statement.

Statement Number: The number of the bank statement. If you do not use sequential numbering, the default statement number is the statement date.

Statement Date: The closing date of the bank statement. The date also includes the timestamp information provided by your bank. On intra-day bank statements, the timestamp indicates how recent the information is.

Status: The status of the bank statement:

Corrected: Errors corrected after input.
Error: Errors detected during input.
New: New statement, not imported.
Transferred: Successfully imported.

Check Digits: Field for bank account validation.

Creation Date: The creation date of the bank statement. This is the date that the bank statement was created in Oracle Cash Management, not the date that your bank created the bank statement. If the intra-day bank statement does not contain timestamp information, you can use this date to determine how recent the information is.

Opening Amount: The beginning balance for the statement, as provided by the bank.

Receipts Amount: The total amount of receipts on the statement.

Receipts Lines: The total number of receipt lines on the statement.

Payments Amount: The total amount of payments on the statement.

Payments Lines: The total number of payment lines on the statement.

Closing: The closing balance on the bank statement.

Lines: The total number of lines on the statement.

Available: The available balance on the statement.

Value Dated: The balance on the statement used to calculate interest.

One Day Float: The one day float balance on the statement. When you import bank statements from a shared bank account, this balance is used to update the One Day Float Balance in Oracle Treasury.

Two Day Float Balance: The two day float balance on the statement. When you import bank statements from a shared bank account, this balance is used to update the Two Day Float Balance in Oracle Treasury.

Reviewing Interface Errors Online for a Specific Statement Line

To review interface errors online for a specific statement line:

Navigate to the Bank Statement Interface window .
Query the statement whose interface errors you want to review.
Choose Lines to see the Bank Statement Line Interface window .
Select the line whose errors you want to review.
Choose Errors.

You see the Bank Statement Interface Line Errors window containing the list of interface errors for the selected line.
Choose Done to exit.

Bank Statement Line Interface Window Reference

Account: The bank account number, as defined in Oracle Receivables, Oracle Payables, or Oracle Payroll.

Date: The closing date of the bank statement.

Line Number: The line number provided by the bank. If the bank does not provide line numbers, you can enter line numbers in a sequence.

Code: The code that the bank uses to identify a transaction.

Number: The transaction number, such as the receipt number, check number, or payment batch name. Automatic Reconciliation uses this number to identify transactions when matching the bank statement line to a transaction or batch.

Date: The date that the transaction cleared the bank. The default is the statement date.

Amounts Tabbed Region

Amount: The amount of the transaction, in the bank account currency. This amount must be within tolerance for AutoReconciliation to succeed (even if the netted value of the Amount and Charges column equals the amount of the system transaction).

Charges: The amount of any bank charges associated with the transaction. This field is not required.

Original Amount: The statement line amount, in its original currency. This amount is used in foreign exchange transactions when the currency of the transaction is different from the currency of the bank account.

Exchange Tabbed Region

Curr: The currency of the transaction.

Date: The date associated with the exchange rate that was used.

Type: The exchange rate type (as defined in Oracle General Ledger) used for this transaction.

Rate: The exchange rate specified by the bank for this transaction.

Reference Tabbed Region

Agent: The customer or supplier associated with the transaction.

Agent Bank Account: The bank account number of the customer or supplier associated with the transaction.

Invoice: The invoice number associated with the transaction.

Description Tabbed Region

Effective Date: The value date for the transaction.

Description: Any other information provided by the bank.

Related Topics

About Bank Statement Open Interface

Loading Bank Statement Open Interface

Correcting Bank Statement Interface Errors

If any record in a statement fails validation, the Bank Statement Import program does not import the statement, and assigns it an Error status. You can review import validation errors from the Bank Statement Interface window, or by reviewing the AutoReconciliation Execution Report.

Interface errors may occur for a variety of reasons. The following is a list of the most common causes of bank statement interface errors:

Incorrect setup information in Oracle Cash Management, such as bank transaction codes, currencies, or bank account information.

Solution: Update the Cash Management setup information and reload the bank statement file.
Errors in the bank statement file.

Solution: Obtain a corrected transmission file from your bank and reload it.
Exceptions from the Bank Statement Loader program or the Intra-Day Bank Statement Loader program.

Solution: Review the Bank Statement Loader Execution Report and resolve the exceptions by correcting the SQL*Loader script, the mapping template, or the bank statement file. Reload the file.
Problem in your custom loader program.

Solution: Modify the custom loader program and reload the bank statement file. After you have reloaded the file, import the bank statement file again.

Instead of reloading the bank statement file, you may want to directly modify the information in the Bank Statement Interface tables by using the Bank Statement Interface and the Bank Statement Interface Lines window. You can update all bank statement header and line information as well as any optional descriptive flexfield content.

To correct the bank statement interface header information:

Navigate to the Bank Statement Interface window.
Query the Statement you want to correct.
Edit the bank statement header information as necessary, including the Control Balances.
Save your work.
Run the Bank Statement Import program to import the corrected bank statement information from the open interface tables. If this is an intra-day bank statement, run the Intra-Day Bank Statement Import program.

Note: You can submit the Bank Statement Import program or the Intra-Day Bank Statement Import program directly from the Bank Statement Interface window. Choose AutoReconciliation from the Tools menu.

To correct the bank statement interface lines:

Navigate to the Bank Statement Interface window.
Query the Statement you want to correct.
Choose the Lines button.
Edit the bank statement transaction information. You can edit the Line Number, transaction Code, transaction Number, and Date.
In the Amounts tabbed region, edit the transaction Amount, bank Charges, and Original Amount.
In the Exchange tabbed region, edit exchange rate information, including Currency code, Exchange Date, Exchange rate Type, and Exchange Rate.
In the Reference tabbed region, edit the Agent (customer or supplier), Invoice number, and Agent Bank Account associated with each line.
In the Description tabbed region, edit the Value Date and Description for each line.
Save your work.
Run the Bank Statement Import program to import the corrected bank statement information from the open interface tables.

Related Topics

About Bank Statement Validation

Sequential Document Numbering

Entering Bank Statements Manually

In addition to loading bank statement information automatically with the Bank Statement Open Interface, you can enter bank statement information manually. You can enable users to update information on a statement that was previously entered manually or loaded automatically, even if the statement is already reconciled.

When you enter a bank statement manually, you enter the bank statement header and the transaction lines. You can reconcile transaction lines as you enter them, or you can reconcile the bank statement (manually or automatically) after you enter all the transaction lines and save your work.

Note: Cash Management assumes that you enter statements in chronological order, and uses this order to calculate cumulative bank account balances.

Prerequisites

Define your banks.
If you plan to use the Bank Statement Import program, you need to define bank transaction codes for the bank account.
Set up Receivables activities and payment methods for miscellaneous transactions.
If you want to use document sequences, you or your System Administrator must set up sequential document numbering for Cash Management.

Note: For document sequencing, the effective date is the statement date.
If you have enabled the Allow Adding Lines to Imported Statements feature in the System Parameters window, you can add lines to automatically-loaded statements.

To enter a bank statement manually:

Navigate to the Find Bank Statements window. Choose New.
Choose the New button to display the Bank Statement window.
Enter the following bank header information: Account Number, Account Name, Bank Name, Bank Branch, and Currency.
Enter the Statement Date.
If you use manual document sequence numbers, enter the Statement Document Number.

Note: If you use automatic document sequence numbers, Cash Management creates the Document Number for the statement automatically. You cannot edit an automatically assigned Document Number.
Enter the Statement Number.
Enter the GL Date - the default is the Statement Date. The GL Date must be in an open or a future-enterable period in Receivables or Payables.
Optionally, enter Bank Statement Control Totals:

Enter the opening and closing balances as needed. Enter control totals for Receipts and Payments, as well as the number of statement lines for each.

Note: You can compare the Control Total amounts to those displayed by Cash Management in the Line Totals tabbed region of the Statements window, to ensure the completeness and correctness of your entered bank statement.
Choose Lines to begin entering your statement lines. Optionally, you can save the header information now and enter the statement lines later.
Save your work.

Bank Statement Window Reference

Account Number: The bank account number. Note that you can update this value but if you have already reconciled bank statement lines, it will not update them.

Account Name: The bank account name.

Bank Name: The name of the bank.

Bank Branch: The name of the bank branch.

Date: The closing date of the statement.

Currency: The currency of the bank account.

Document Number: The document number that appears on the bank statement. If you use automatic document sequence numbers, Cash Management creates the document number for the statement automatically. You cannot edit a document number that is assigned automatically.

Statement Number: The statement number. The default statement number is the statement date.

GL Date: The date that the transaction posts to the General Ledger. The default is the statement date. The GL Date must be in an open or future-enterable period in Oracle Receivables or Oracle Payables.

Check Digits: Enter Check Digits for bank account validation.

Control Totals and Line Totals: The Control Totals and Line Totals tabbed regions of the window contain the same fields. You can compare these fields to ensure that the bank statement that you entered is complete and correct.

Opening Balance: The beginning balance for the statement, as provided by the bank. The default is the closing balance of the previous statement.

Receipts Amount: The total amount of receipts on the statement.

Receipts Lines: The total number of receipt lines on the statement.

Payments Amount: The total amount of payments on the statement.

Payments Lines: The total number of payment lines on the statement.

Closing Balance: The closing balance on the statement.

Available Balance: The available balance on the statement.

Value Dated Balance: The value dated balance on the statement. This balance is used to calculate your interest.

One Day Float: The one day float balance on the statement.

Two Day Float: The two day float balance on the statement.

Complete: Check this field to indicate that the bank statement is complete and to prevent any changes to it. You may want to freeze a bank statement after completing the reconciliation process. However, you can mark or unmark the statement as complete at any time.

Unreconciled Amount: The total amount on the statement that is unreconciled. This amount is the net of unreconciled receipts and unreconciled payments.

Unreconciled Lines: The number of unreconciled lines on the statement.

Related Topics

Bank Statements

Entering Bank Statement Lines

Reconciling Bank Statements Manually

Creating Reconciled Bank Statement Lines

Country Specific Bank Account Validations

Entering Bank Statement Lines

To enter bank statement lines:

Navigate to the Find Bank Statements window.
Choose Find to see a list of all statements you have already entered.
Select the statement whose header information you've already entered, then choose Review to see the Bank Statement window.

Note: If you have not already entered the bank statement header information, see Entering Bank Statements Manually.
Choose Lines to enter the bank statement lines.
Enter the Line Number.
Enter the transaction Type for the line, or select a type from the poplist.
Optionally, if you plan to automatically reconcile the bank statement once you finish entering it, for each transaction line enter the Bank Transaction Code and:
- Transaction Number, or
- Invoice Number (see step 11 below) and Agent Bank Account
Note: For Payroll EFT payments, the transaction number should be entered in the order specified by the Payroll matching order for the transaction code and separated by "/".
In the Amounts tabbed region, enter transaction amount details.
- Enter the Transaction Date. The default is the statement date.
- Enter the Value Date.
- Enter the transaction Amount. The transaction type determines whether the amount is a payment or receipt.
In the Exchange tabbed region, enter exchange information for foreign currency transactions.
- Enter the Original Currency Code and Exchange Date.
- Enter an exchange rate Type or select one from the available list of values.
- If you select exchange rate type of User, enter the exchange Rate. If you use a predefined rate type, Cash Management picks up the exchange rate automatically if you do not enter one.
In the Reference tabbed region, enter the Agent (customer or supplier), Invoice number, and Agent Bank Account associated with the transaction.
In the Description tabbed region, enter a description of the transaction and any Bank Charges related to the transaction.
Enter each additional transaction line.
Save your work.

Bank Statement Interface Lines Window Reference

Account: The number of the bank account associated with the transaction.

Date: The closing date of the bank statement.

Line: The line number provided by the bank. If the bank does not provide line numbers, you can enter line numbers in a sequence.

Type: The transaction type:

Payment: Payments, such as generated or recorded checks, wire transfers, and electronic funds transfers.
Receipt: Receipts, such as received checks, direct debits, and bills of exchange.
Miscellaneous Payment: Payments not associated with supplier invoices, such as petty cash transactions posted directly to cash accounts.
Miscellaneous Receipt: Receipts not associated with customer invoices, such as petty cash transactions posted directly to revenue accounts.
Stopped: Stopped payments previously entered, generated, or cleared, such as callback of a check. A stopped transaction type matches only to voided or stopped payments in Oracle Payables and Oracle Payroll.
Rejected: Receipts rejected for reasons other than non-sufficient funds, such as an invalid bank account. A rejected transaction type matches only to reversed receipts in Oracle Receivables.
NSF: Receipts rejected by the bank because the accounts on which they were drawn had non-sufficient funds.
Sweep In: Incoming funds transfer from an internal bank account. This bank transaction type identifies the originating bank account.
Sweep Out: Outgoing funds transfer from an internal bank account. This bank transaction type identifies the receiving bank account.

Code: The code that the bank uses to identify a transaction.

Number: The transaction number.

Amounts Tabbed Region

Transaction Date: The date the bank cleared the transaction. The default is the statement date.

Value Date (formerly Effective Date): The date when cash activity (payments or receipts) is recognized in a bank account. This date is important for interest calculations on a bank account. The statement line Value Date can be provided by the bank or entered manually. It is used to populate the Actual Value Date in Oracle Payables and Oracle Receivables.

Amount: The amount of the transaction, in the bank account currency. This amount must be within tolerance for autoreconciliation to occur (even if the netted value of the Amount and Charges column equals the subledger transaction amount).

Amount Reconciled: The amount of the transaction that was reconciled.

Charges: The amount of any bank charges associated with the transaction. This field is not required. Cash Management derives the amount reconciled by adding the Charges and Amount columns.

Exchange Tabbed Region

Currency: The currency of the transaction.

Date: The date associated with the exchange rate that was used.

Type: The exchange rate type (as defined in Oracle General Ledger) used for this transaction.

Rate: The exchange rate specified by the bank for this transaction.

Reference Region

Agent: The name of the customer or supplier associated with the transaction.

Agent Bank Account: The bank account of the customer or supplier associated with this transaction.

Invoice: The invoice number associated with the transaction.

Description Tabbed Region

Status: The status of the transaction, reconciled or unreconciled.

Description: The customer-related text provided by the bank.

Related Topics

Bank Statements

Entering Bank Statements Manually

Reconciling Bank Statements Manually

Creating Reconciled Bank Statement Lines

Entering Bank Statements Manually

Updating Bank Statements

You can update any bank statement, whether imported or entered manually in Cash Management.

Prerequisites

Import or enter a bank statement.
Make sure the bank statement is not marked as Complete. See: Marking a Bank Statement as Complete.

To update a bank statement:

Navigate to the Find Bank Statements window .
Enter the query criteria for the statement you want to update, or leave the criteria blank to query all existing statements.
Choose Find to see the Reconcile Bank Statements folder window containing the statements that meet your query criteria.

Note: You can modify the Reconcile Bank Statements folder window to customize your query capabilities on statements you have entered. Refer to the Oracle Applications User's Guide for more information on modifying and saving folders.
Select the statement you want to update, and choose Review.
Update bank statement header and line information as necessary. You can change any bank statement information. You can also add information, such as transaction lines.
Save your work.

Related Topics