A/P-A/R accounting >  Bank transactions >  Advanced bank statement import >  Bank transactions import  

Display all Hide all

Use this function to import statements from a file saved on your server or computer.

The import settings are defined in the Bank import settings function (BSIIMPPAR) and you cannot change them here. After you enter the code for the Bank import settings, the remaining fields populate based on these settings. These settings are also used for the matching process and for paying invoices.

Click OK to start the import and upload a file from your computer or a server location.

A log file displays when the import is complete. For each statement contained in the file, there is a dedicated statement entry.

A warning message displays if a file with the same name is imported again.

After importing the statement, use the Bank transaction management function (BSIIMP) to process the statements.

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).

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 or accounts 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. This 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.

When you select Process bank transactions, you can view details for all transactions in that statement. Transactions can have one of four initial matching levels:

A: An exact match to one or several open items (or a G/L account) was found.

AS: The transaction was automatically assigned to a G/L account or a BP according to search terms defined in the search term list function.

B: Some information was found, but not an exact match. Possible matching open items are displayed.

C: No matches were found and there are no possible matches displayed.


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 the payment. Before validating, you must distribute the complete transaction amount as paid, plus overpayment if applicable. You can distribute transactions in a statement to multiple open items or accounts. Once you have generated the payment, you can no longer modify the transaction. The validation is always performed for the entire current statement and depends on the matching status:

A/AM/AS: Payments are created for the matched open items or G/L accounts. Payment lines for discounts are created as needed.

B/C: 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

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

Entry screen

Fields

The following fields are present on this tab :

Bank statement import

Enter or select the Bank import setting code you defined in the Bank import settings function (BSIIMPPAR).

This field displays the company based on the Bank import setting.

If this field is blank, you can enter a value.

This field displays the bank based on the Bank import setting.

If this field is blank, you can enter a value.

This field displays the file format based on the Bank import setting.

If this field is blank, you must enter a value.

  • Flow type (field FLOTYP)

This field displays the flow type based on the Bank import settings. You cannot modify the type.

Reminder:

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).

File

  • Source (field TYPIMP)

This field indicates if the source file is located on your Client (computer) or on a Server.

  • Import volume (field IMPVOL)

This field displays the server volume or directory if Server is selected in the Source field.

If this field is blank, you can enter a value.

Close

 

Batch task

This function can be run in batch mode. The standard task BSIIMPORT is provided for that purpose.

Limitations

Please be aware of the following functional limitations of the bank statement import process.

  • Format
    Only MT940, CAMT.053/.054, BAI2, and CSV (for AR Lockbox) bank statement formats are supported.
  • Controls
    There are no controls on imported bank account balance, statement number, or company name. There is no check or control if the currently imported statement follows the data of the previous import, (i.e., next statement no.).
  • Currency handling
    Sage X3 bank account currency and bank statement currency must be the same. And you need to consider:
    • If the statement currency and company currency are the same, automatic and manual matching considers open items in company and in foreign currency. Open items matched to the same transaction must have the same currency.
    • If the statement currency and company currency are different, (i.e., USD bank account for a GBP company), then the statement currency and open item currency must be the same to be considered in the automatic or manual matching. You cannot match, for example, a USD payment to a GBP open item.
  • Single bank account import files
    One import file can contain (multiple) statements from the same bank account. You cannot mix statements from different bank accounts in one file.
  • Prepayment open items
    Prepayment open items are excluded from matching and are not displayed on the Process bank transactions screen.
  • Open items linked to a factor
    These are not considered in the automatic matching and are not displayed in the manual matching.
  • Netting a BP that is a supplier and customer
    A payment is matched to both supplier and customer invoices.
  • Late charges
    Neither automatic matching nor manual matching calculate or check on late charges (only on discounts).
  • Transactions marked Return debit (RD) and Return credit (RC)
    Transaction flagged with debit/credit marks RD and RC in segment :61: concern payment reversals. Currently, these transactions should be posted to the suspense account and not matched to open items. See the section Understanding electronic bank statement format basics.
  • SEPA Direct Debit returns (SDD)
    There is no automatic handling for SDD returns.
  • Access control
    Controls on access codes, validity of the time range, etc., are only performed before payment creation. If there are issues, the entry or the settings can be corrected accordingly.
  • Discount modes
    Automatic discount calculation in the bank statement import supports calculation modes Breakdown by VAT (invoice level), Breakdown by VAT (account level), and Discount on VAT (exempt)/Global in the (DEPMGTMOD Discount management mode parameter (TC chapter, INV group). For other cases, Breakdown by VAT (account level) is used as a fallback.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation