Bank import format definition

This function defines the overall structure for the segment format and order of events. You can use this function to control when new entries for statements or transactions are created during the bank transactions import.

The order in which you enter the segments determines the sequence within the statement.

You need to define at least one bank import format that can be used for several bank accounts. You can also define several bank formats definitions for banks using different electronic import formats.

Bank statement import setup overview

This provides an overview of the setup procedures necessary to perform advanced bank statement imports, which includes matching statements to open items and generating payments. You can also match to existing payments without generating a new payment. Note that you cannot match a single transaction to an open item and a payment combination. See Bank statement import overview.

This involves technical settings that should be done very carefully. If you are not certain, contact your Sage X3 administrator or business partner.

View the online help for each function for specifics on data entry and complete function help.

BSI - Bank statement import activity code
You need to activate this activity code to take advantage of the bank statement import process.

Understanding electronic bank formats
To set up the bank statement import successfully, at least a basic understanding about the structure and content of electronic bank statement files is required. This includes MT940, CAMT.053, BAI2, and AR Lockbox CSV file types.

Most banks provide CAMT messages in ZIP files. You need to unzip the files before importing into Sage X3.

Payment entry types for bank statement imports
It is strongly recommended to use dedicated payment entry types for the bank statement import (BSI) so that settings can be made independent from other entry types. A dedicated BSI entry type is available as part of the default setup that you can copy or adapt. A dedicated BAI2 entry type is also available.

Bank import segment definition
The segment definition describes the detailed structure of the information contained in a segment. This includes segments from the logical parts, like the header, data line, footer, and so on, of a bank import format. Based on this, the import extracts and interprets the information contained in the file. The sequence of the segments is controlled by the import format definition.

If you are importing BAI2 files, you need to define Bank import type codes (BSIIMPTC). This is an additional step dedicated to this format.

Bank import format
The format definition describes the overall structure of the format and the sequence or occurrence of the segments. It also controls when new entries for statements and transactions are created during the import.

At least one Bank import format must be defined; it can be used for several bank accounts. You can also have several formats, (i.e., for bank accounts from different banks using different MT940 or CAMT.053 variants).

BP number and Invoice number definitions
The BP number and the invoice number are the main criteria for automatic matching, but are typically given in the bank statement file in a non-structured way as part of the payment reason or information text.

For an efficient search, you need to provide information about the structure of these numbers so the search process can recognize parts of the payment reason text as a BP or invoice number.

Bank import settings
These settings control various aspects of the import and the matching processes. Settings are done at the company level at a minimum, but you can have different settings per company for different bank accounts and/or file formats.

These settings are applied in the context of an import, so if you import a bank statement file, you need to select a group of settings for this import. These settings are used for the import and the matching process later. For example, you can import and match transactions through the advanced bank statement import workflow or import files and then reconcile using the Bank statement reconciliation (RAPBAN) function.

If you want to included existing payments in the import and matching process, you need to select at least one option in the Payments block of the Search criteria section.

Excluded search terms
You can define common terms that are excluded from the business partner name search. Common search terms can include the abbreviations of legal forms that are used in BP names like Ltd, S.A., Inc., and GmbH AG. Salutations like Mister, Miss, Mrs., Herr, and Frau that are used in BP names can also be excluded.

Excluding these common terms that are found in many business partner records increases search performance because it reduces the number of possible BP accounts that need to be searched for open items.

Search term list
Search terms can be used if fixed identifications, like a BP name or specific text in the transaction, should be used to match the transaction to a certain general ledger or BP account.

Prerequisites

Refer to the documentation on Implementation.

Actions

Select Create to define a new bank import format or select the Edit to modify an existing bank import format.

Header

Format (field CODBFF)

Enter a code for the format. It can be alphanumeric and not longer than 10 characters.

Description (field DES)

Enter a description for the format (optional).

File type (field FILTYP)

Select a file type:

  • MT940
  • CSV (for AR Lockbox)
  • CAMT
  • BAI

ASCII (field FLDSEPTYP)

Select an option to determine how field separator characters are entered:

  • Character: like ; or ,
  • Ascii: a numeric ASCII code that represents a character used for non-printable characters like TAB

Field separator (field FLDSEP)

Enter a field separator that specifies the character used as the separator between two fields. The field separator must match the ASCII field selection.

This field is only active for CSV and CAMT file types.

Lines grid

Segment (field FILTYP)

Enter an existing segment defined using the Bank statement segment definition function (BSISCT).

Remember, the order in which you enter segments determines the sequence within the statement.

Start (field SCTSTR)

Select this check box if this is the start segment.

This setting only applies to MT940 formats.
  • End (field SCTEND)

Select this check box if this is the end segment.

This setting only applies to MT940 formats.

Destination table (field TABTYP)

Select an option to indicate the type of segment.

  • Header: Header data is stored once per statement.
  • Line: Line data is stored for each transaction in the bank statement.
  • Line detail: Line detail information is stored per subdetail (D level) of a CAMT.053/54 bank statement entry (transaction). In general, line detail information does not apply to MT940 statements or AR Lockbox CSV format.

Mandatory (field SEGOBY)

Select this check box if the segment is required for the import. An error occurs during import if a mandatory segment is missing.

Operation (field DBACT)

This field is typically not used for the bank statement import process.

You can use this field if you have segments with data relevant for later processing.

  • Unspecified: The segment is analyzed, but the data is not stored. It is stored on the next Create or Update operation.
  • Create: This operation creates a new data line in the database.
  • Update: This option updates an existing data line in the database.
  • Ignore:: This segment is ignored during the import process. Use this option if you have segments with data not relevant for later processing.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Format and segment definition have to be of the same file type

The file types defined in the bank import segment definition and the linked bank import format must be the same.

Tables used

The following tables are implemented by the function:

Table

Table description

BSIFILFMT [BSIFFM]

Bank import format definition