This function defines the business partner (BP) number that is used with the Invoice number as the main criteria for matching imported bank statements to invoices.

Typically, these non-structured numbers are in the bank statement file as part of the reason for the payment. Therefore, for an efficient search during import and matching, you need to define the structure of these numbers so that the process can recognize parts of the payment reason as a BP number.

Bank statement 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, CFONB, and AR Lockbox CSV file types.

Note: 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. Dedicated BAI2 and CFONB entry types are 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, etc., 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.

Note: 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. For CFONB file formats, a specific bank is not entered.

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.

Note: For CFONB file formats, you cannot reconcile using the Bank statement reconciliation function for matching.

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 a certain text given in the transaction) should be used to match the transaction to a certain G/L or BP account.

Prerequisites

SEEREFERTTO  Refer to documentation Implementation.

Actions

 Click Create to define a new BP number or click the Edit to modify an existing number.

Presentation

Click Create to define a new BP number or click the Edit icon to modify an existing number.

Close

Fields presentation

Header

  • Company (field CPY)

Enter a company for this definition.

  • Site (field FCY)

Enter the site if this definition applies to a single site for this company.

  • File format (field FILFMT)

Enter or select an existing file format defined in the Bank import format function (BSIFILFMT).

  • Description (field DES)

Enter a description (optional).

Grid

  • Prefix (field PFX)

Enter the BP number prefix for this BP.

You can create several lines for different prefixes if needed.

Examples:

If all customer numbers start with “D,” (i.e., D001001, D001002, etc.) and all supplier numbers start with “C,” (i.e., C00302”), create two lines, one for each prefix.

If all BP numbers are numeric with different ranges for customers, suppliers, etc., create one line for the starting number of each number range: Consider a customer range of 100000-299999 and supplier ranges of 700000-799999 and 900000-999999. This results in 3 different lines with the following prefixes: 1, 7, and 9.

  • From number length (field LENINVSTR)

Enter a range for the possible total length of the number including the prefix.

Examples:

If BP numbers have a constant length of 7, (i.e., D001001), enter 7 for the number range.

If the length varies between 7 and 8, enter 7 to 8 as the number range.

A search key is created for each possible length and used during the searching and matching process. Large ranges can increase the time required for the automatic matching process.

  • To number length (field LENINVENT)

Enter a range for the possible total length of the number including the prefix.

A search key is created for each possible length and used during the searching and matching process.

Close

Error messages

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

The only error messages are the generic ones.

Tables used

The following tables are implemented by the function :

Table

Table description

BSIBPRNUM [BSIBPN]

BP number definition

BSIBPRNUMD [BSIBPND]

BP number definition detail

SEEREFERTTO  Refer to documentation Implementation.