Use this function to view all imported bank statements and their status. By default only nonvalidated statements display.

The tasks you can perform for each statement vary depending on the flow type setting: Standard or Reconciliation only.

Note: Imports with a Reconcile Matching status only display if the filter is set to No filter.

Standard flow type:

  • Start the automatic matching for all unmatched statements.
  • Undo the matching or delete an imported statement if necessary.
  • Open a statement to review the transactions and to start the matching for this single statement. You can also do manual matches.

Reconciliation only flow type:

  • Access transactions in the Bank statement reconciliation function (RAPBAN) for matching and generating payments.
  • Display imported bank transactions.

These statements are imported using the Bank transactions import function (BSIIMPORT) or you can click Start import from the Action panel to access the this function.
 See How to Set up Bank statement imports guide on the How to tab to learn more.
After importing bank transactions, you need to match the transactions to open items or payments and validate to generate the payment.  For matches to payments, a new payment is not generated when you validate the statement. 

Matching transactions

Applies to Standard flow type only.

Click Start matching from the Actions panel. This runs the automatic matching process for all unmatched statements and searches for open items and posted payments based on search criteria in Bank import settings (BSIIMPPAR).

One bank statement transaction can only be matched to either an open item(s) or a payment(s). A transaction cannot be matched to both an open item and a payment.

Matching priority depends on the sign of the payment transaction:

  • Revenue: Open items are matched first.
  • Expense: Payments are matched first.

Note: You can start the matching for a single statement from the Process bank transactions option on the Actions icon menu on each line.

Processing transactions

Applies to Standard flow type only.

For each statement (line), the next step is to select Process the bank transactions from the Actions icon menu.

Bank statement reconciliation

Applies to Reconciliation only flow type only.

For each statement (line), click Bank statement reconciliation from the Actions icon menu at the beginning of a line to access that function.

Bank statement import overview

You must complete the setup process before importing bank statements, reviewing and processing matches, and generating payments through validation.

See Bank statement setup overview. The setup involves technical settings that should be done very carefully. If you are not certain, contact your administrator or business partner.

This is an overview of the bank statement import and matching process. See the relevant function help for specifics regarding each step.

The process varies based on the flow type selected in the Bank import settings function (BSIIMPPAR).

Standard: Importing, matching, and generating payments takes place within the full bank statement import workflow, including the Process bank transaction function (GESBSIMTC).

Reconciliation only: Importing takes place within the bank statement import workflow. Matching and generating payments takes place in the Bank statement reconciliation function (RAPBAN). This flow type is not available for CFONB file types.

1. Import transactions

This function imports bank transactions in various electronic formats from one or several bank statement files. These files have been obtained directly from your bank or exported from an online banking tool and saved to your workstation or server. The bank transaction import function (BSIIMPORT) imports these files from their saved location for matching and processing.

This step applies to Standard and Reconciliation only flow types.

See Bank transaction import

2. Managing imports and matching

Next, you need to manage how you import and match transactions.

An imported statement can have one of the following statuses:

  • Not matched: Initial status after import, no matching has been performed.
  • Matched: Matching or partial matching has been performed for the statement.
  • Validated: Payments have been generated and the statement is read-only.
  • Reconcile: The bank statement was imported with Reconciliation only as the flow type. The transaction data has been copied to the Bank statement reconciliation function (RAPBAN). The statement here is read-only.

Standard flow type:

Match transactions to open items, accounts, or existing payments using the Bank transaction management function (BSIIMP). You can perform an automatic match from this screen, but you cannot review or modify results and you cannot generate payments.

Reconciliation only flow type:

The transaction data for the statement has been copied to the Bank statement reconciliation function (RAPBAN) where you can perform a standard manual bank reconciliation. Import data is display-only. For each statement, you directly access the transaction data from the Action icon menu at the beginning of each line. You cannot process the statement through the Process bank transactions screen.

See Bank transaction management

3. Matching transactions to open items or accounts

This step only applies to the Standard flow type.

The imported transactions need to be reviewed and matched to open items or other accounts such as a G/L account, BP account, or a suspense account. Transactions can also be matched to existing payments.

Note: Existing payments refers to payments created through the standard payment processes like payment proposals and manual payment entry and have a status of Posted.

Matching is done in the Process bank transactions screen. You can match items automatically or manually.

  • Automatic matching: From the Bank transaction management screen, click Start matching to run the process on all unmatched statements in the grid.
  • Manual matching: From the Action icon menu at the beginning of a line, select Process bank transactions. This opens a new screen where you can review and edit results from automatic matching, perform manual matching and selection, and manual entry.

Processing transactions

This step only applies to the Standard flow type.

A: This represents an automatic exact match to one or several open items and/or existing payments. Matched open items display in the grid and are selected. The "A" status can also include:

Automatic matches:

A: to an open item or payment

AC: to open items in a different currency

AS: by search term list that automatically creates a manual entry

Manual matches:

AM: to an open item and/or an existing payment

AD: manual entry

B: Some information was found, but no exact matches. Possible matching open items or existing payments are displayed in the related grids and are not selected. If not processed manually before validating, payments are posted to the Suspense account unless you have selected to Suppress intermediation posing as defined in the Bank import settings function (BSIIMPPAR).

BC for possible matches involving open items in a different currency.

C: No information was found and no open items or existing payments display in the related grids. If not processed manually before validating, payments are posted to the Suspense account unless you have selected to Suppress intermediation posing as defined in the Bank import settings function (BSIIMPPAR).

Notes: If you review a statement before matching or if you unmatched a transaction, the status code is blank.

For a manual match, you must distribute the complete transaction amount as paid, plus overpayment if applicable. Otherwise you can't save your changes. You can distribute transactions in a statement to either multiple open items or accounts or existing payments.

For A level matches

To open items: This generates the payment and no more changes can be made.

              

To existing payments: This simply creates the match to the bank transaction with no new posting or payments.*

              

To an existing payment linked also to manual entry: This matches the existing payment and creates a new payment posting for the manual entry amount only.

*For A level matches to existing payments, validation creates the following data:

PAYMENTH: a reference to the linked transaction in BSIIMPD

GACCENTRY: set the matching flag entry  (BSI) for those journal entries related to the entry in PAYMENTH

For B and C level matches

Payments are created for the suspense account unless you have selected to Suppress intermediate posting. In that case, you need to manually generate payments and journal entries for those transactions. This option and suspense account settings are defined in the Bank import settings.

See Process bank transactions

4. Validating a statement

This step only applies to the Standard flow type.

Validating is the final step in the bank import process and generates a payment for transactions matched to open items or BP/GL accounts. After you have validated the statement, you can no longer modify the transactions. The validation is always performed for the entire current statement and depends on the matching status:

See Process bank transactions

5. Manually completing a transaction

This step only applies to the Standard flow type.

In certain cases, open items associated with a bank statement transaction might have been settled outside the bank statement import process. In other words, a payment transaction included in the bank statement already exists as a payment.

Complete transaction is active when the transaction status is Not validated but has already been matched or when the transaction status is Partially validated.

This option is inactive when the transaction status is Not validated but has not yet been matched, or when the transaction status is Validated or Manually completed.

Note: Use this action with care. Completing a transaction cannot be undone.

Prerequisites

SEEREFERTTO  Refer to documentation Implementation

Screen management

Grid

Presentation

By default, only nonvalidated statements are shown, but you can change the display using options available from the Menu bar. The fields in this grid are read-only.

Possible status of a statement:

Not matched: initial status after import (Standard flow type)

Matched: matching for some or all transactions performed (Standard flow type)

Validated: payments generated, read-only (Standard flow type)

Reconcile: statements imported with the Reconciliation only flow type to be processed through the Bank statements reconciliation function (RAPBAN)

Close

Fields presentation

Possible status of a statement:

  • Not matched: initial status after import (Standard flow type)
  • Matched: matching for some or all transactions performed (Standard flow type)
  • Validated: payments generated, read-only (Standard flow type)
  • Reconcile: statements imported with the Reconciliation only flow type to be processed through the Bank statements reconciliation function (RAPBAN)
    • Statement Code (field STMCOD)

    This field displays the statement code, which represents the chronological number of the import. It is automatically assigned when importing a statement. It cannot be modified.

    • Bank account identification (field REFBAN)

    This field displays the Bank account identifier defined in the Management section of the Bank account function (GESBAN). The bank account identifier represents an additional control that warns you when the bank account defined for the bank statement is different from the bank account selected for the import in the Bank transactions import screen.

    • Bank (field BAN)

    This field displays the bank code for the bank defined for the bank statement import.

    • Company (field CPY)

    This field displays the code and short description for the company in the bank statement.

    • Site (field FCY)

    This field displays the code and short description for the site, if defined for the bank statement import.

    • Statement currency (field CUR)

    This field displays the currency defined in the bank statement.

    Note: The statement currency is mandatory for importing bank statement files. If this information is not available in the file provided by the bank, you can define a currency code as a constant in the Bank import segment definition function for the bank statement format to import. This usually applies to AR Lockbox files.

    • Start date (field DATSRT)

    This field displays the start date for the statement period, if available in the imported file. It is usually the date for the bank account starting balance.

    • End date (field DATEND)

    This field displays the statement period ending date, if available, in the imported file. It is usually the date for the bank statement ending balance.

    • File name (field FILNAM)

    This field displays the imported file name. It is limited to 250 characters.

    Close

    Delete

    This actions deletes the current statement. You can only delete statements that have not been validated. Matched statements must be unmatched before you can delete them. Statements with a Reconcile Matching status cannot be deleted.

    Undo matching

    This action unmatches the current bank statement. This does not apply to statements with a Reconcile Matching status.

    Process bank transactions

    Use this function to review and manage matching results and to generate payments through validation. This only applies to Standard flow type imports.

    You can perform the following actions:

    • Check and edit automatic matching results
    • Undo and redo matching
    • Manual matching
    • Manual selections (search for open items)
    • Manual entries
    • Start the validation and generate the payment

    See the documentation for Process bank transaction.

    Bank statement reconciliation

    For statements with a Reconcile Matching status only, click this option to go directly to the Bank statement reconciliation function to match items and generate payments.

    Action panel

    Start import

    This action opens the Bank transactions import function where you can import bank transactions.

    This applies to both flow types: Standard and Reconciliation only.

    Start matching

    This action starts the automatic matching process for all unmatched statements at once. The matching searches for possible open items to match against imported statements.

    Error messages

    [<<<

    Use the options below to filter import results in the grid.

    Click this action to undo previous filters by new statements or validated statements.

    Click this action to display only new statements.

    Click this action to display only validated statements.
    [>>>>MENU_FLOTTANT_DIV]

    The only error messages are the generic ones.

    Tables used

    The following tables are implemented by the function :

    Table

    Table description

    BSIIMP [BSIIMP]

    Bank statement import

    SEEREFERTTO  Refer to documentation Implementation