Bank import type codes

Use this function to define type codes in BAI2 bank import files as credit or debit so that files can be imported and automatically matched to open items. This function is one of several that are required to complete the advanced bank statement import setup process.

When importing bank transactions using the BAI2 file format, the import process cannot identify whether a transaction code is a credit or a debit. The type codes are included in the Account identifier record (Record type 03) and Transaction detail (Record type 16) of the BAI2 file. If a code is not defined with the appropriate sign, the bank statement file is not imported and is listed as an error in the import log file. Note that only type codes related to a transaction detail record are blocked while importing the file, if not defined.

You can create multiple sets of Bank type codes, either one for all banks or one per bank. The list below shows which type codes can be defined for the advanced bank statement import process. However, always check with the bank to ensure you are using the correct type codes.

101-399: Credit summary and detail type codes

401-699: Debit summary and detail type codes

700-799: Loan summary and detail type codes

See Understanding the BAI2 file format for more information.

(missing or bad snippet)

Understanding the BAI2 file format

The BAI2 file is a standard bank statement format developed by the Bank Administration Institute (BAI) and used for electronic cash management balance reporting. It is mostly used in the United Kingdom and the United States.

A BAI2 file contains multiple record types in a specific structure. Each file contains one File header (type 01) and one File trailer (type 99), but can contain multiple groups. Each group has a Group header (type 02) and a Group trailer (type 98). Within each group pair, there can be multiple Accounts (types 03 and 49) that contain the Transaction detail (type 16) followed by single or multiple Continuation lines (type 88).

The image below highlights the nesting structure of a BAI2 file that contains one group and two accounts.

The first two digits of each line followed by a comma identify the Record type.

On the lines for Transaction detail (highlighted in purple), the type code follows the Record type 16, separated by a comma. In this example, one Transaction detail line has a 195 type code and the second Transaction detail line has a 495 type code.

Example how how the XML file is structured for BAI2 file types

File header

  • Group header
    • Account identifier
      • Transaction detail
    • Account trailer
    • Account identifier
      • Transaction detail
    • Account trailer
  • Group trailer

File trailer

Prerequisites

Refer to the documentation on Implementation.

Actions

Select Create to define bank type codes when importing BAI2 bank transaction files or click the Edit icon to modify an existing bank type code.

Header

Bank type code (field BSICODSCT)

Enter a unique identifier for the list of type codes.

Bank (field BAN)

Enter a bank to apply these type code definitions to imports from this bank.

Leave this field blank to apply these settings to BAI2 imports from banks with no specific list of type codes defined. A list defined specifically for a bank will always take precedence.

Description (field DESAXX)

Enter a description for the type code.

Short description (field SHO)

Enter a short description.

Lines grid

Code (field COD)

Enter a specific type code for a transaction.

The following codes can be defined for advanced bank statement import:

  • 101-399: Credit summary and detail type codes
  • 401-699: Debit summary and detail type codes
  • 700-799: Loan summary and detail type codes

    • Description (field DES)

    Enter the description for the type code according to information provided by your bank.

    Level (field LEV)

    Select the transaction type:

  • Status
  • Summary
  • Detail

    • Note: Only Detail transaction types are taken into account for the advanced bank statement import process.

    Sign (field SIG)

    Select Credit or Debit to define the appropriate sign for the transaction.

    Summary code (field SUMCOD)

    This field is optional and is used for codes that summarize account credit or debit activity. Example: 100 for credit or 400 for debit.

    This field is not used for Detail transaction types.

    Record (field REC)

    Enter 16 to indicate that this type code is in the Transaction detail (Record 16) in the BAI2 file.

    Note: Only Record type 16 is used by the advanced bank statement import process.

    Destination (field DESFLD)

    Enter the database field to store the defined type codes. For example, [BSIIMPD]SNS.

    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.

    Mandatory field '$1$' in segment '$2$' does not exist. Please check the according format and segment definition.

    Review and update the segment definition.

    Tables used

    The following tables are implemented by the function :

    Table

    Table description

    BSIIMPTC [BSITC]

    Bank import type codes