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.

(missing or bad snippet)

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