1. Home
  2. /
  3. Setup Guides
  4. /
  5. Financials
  6. /
  7. Imported bank statements
  8. /
  9. Setting up the Imported...

Setting up the Imported bank statement functionality

Related topics

The process starts from Integrator by receiving and interpreting the XML files from financial institutions according to the guidelines:

  • UNIFI ISO 20022 Payments Messages for the business area Bank-to-Customer Cash Management, found in the ISO MDR 2009 (Message Definition Report);

    * BankToCustomerV02 (Msg ID pain.053.001.02)
    * BankToCustomerDebitCreditNotificationV02 (Msg ID camt.054.001.02)
  • Teller Merchant Settlement Report (MSR) guideline.

The reported payments within the bank statement are automatically imported and processed in the Work with imported bank statements routine and, depending on the setup, automatically transferred to be further processed in the Work with open batches routine.

Preparation

  • Set up the communication between Integrator and the bank.
  • Install the applicable Integrator script(s).
  • See the Setting up the basic data section in this document.
  • The reference handling is unique for each company. It needs to be verified and tested according to the set up for the selected Internal reference rules. A good hit percentage saves time and money. See the Reference handling section in About the Imported bank statement functionality for more information.
  • The banks load the XML file in different ways. The interpretation should be considered as a frame and needs to be verified in the company’s environment. Modifications might be needed.

Setting up the basic data

The following outlines the complete setup procedure in the basic tables and files.

Tables/Files To do Additional information Pre-load in application
Set up the communication between the Integrator and the bank
Install the applicable Integrator script(s).		 See the Schemes section in About the Imported bank statement functionality
Communicate with the bank regarding the applicable bank transaction codes (Domain/Family/Sub family) for A/R payments. The codes are defined in Work with Cash Management schemes/Bank account details.
Work with banks Enter bank accounts.
Work with voucher number series Enter voucher number series. Handling code = 1
Work with voucher types Enter voucher types. Check voucher amount = Y

Activate the ARP and ARS routines.
Work with document types Enter payment document types. Data type = 2

Liquid panel must be left blank.
Work with open batches, Templates The pre-loaded templates require that voucher type is defined with Check voucher amount = Y in Work with voucher types. FIN
Work with batch import options FIN
Work with Cash Management schemes Cash Management schemes define the format in which transaction information has been interpreted and imported from Integrator to DC1 to be further processed in the Work with imported bank statements routine, and subsequently in the Work with open batches routine.

The schemes *STDCM053 (Base standard scheme camt.053), *STDCM054 (Base standard scheme camt.054) and *STDTELSTR (Base standard scheme Teller) are system-defined as the base standard schemes. The Integrator script passes a hard coded Scheme ID, (i.e. one of our pre-defined Scheme ID’s) to identify the Message file.

If you manually enter a scheme, you need to change/create an Integrator script and pass the accepted Scheme ID.

Activate the applicable scheme.

Drill down to Work with Cash Management scheme, Bank accounts.

 FIN
Work with Cash Management schemes, Bank accounts Set up applicable bank accounts.

Drill down to Work with Cash Management schemes/Bank account details.

 Some data is possible to override in Work with Cash Management scheme/Bank account details.
Work with Cash Management schemes, Bank account details The bank transaction code (Domain/Family/Sub family) identifies the transaction entry. Set up applicable transaction data.

Some data overrides data in Work with Cash Management schemes, Bank accounts.

Example:
PMNT/RCDT/ESCT = Received SEPA CT
PMNT/RCDT/XBCT = Received cross-border CT
PMNT/RCDT/*ALL = Received payment for all undefined sub-families

Drill down to the Work with Cash Management schemes/Bank account details /Internal text rules.

Drill down to the Work with Cash Management schemes/Bank account details /Internal reference rules.

 Discuss applicable codes with the creditor’s bank. The codes exist in Work with ISO 20022 external code lists. Applicable elements:
*BKTXDOMN
*BKTXFMLY
*BKTXSUBFM

Sub family *ALL = Internal DC1 code to pick up all undefined sub-families.
Work with Cash Management scheme/Bank account details/Internal text rules Set up text handling for selected internal text rules.

All pre-defined Rule ID’s are displayed.

 See the Text handling section in About the Imported bank statement functionality. FIN
Work with Cash Management scheme/Bank account details/Internal reference rules Set up reference handling for selected internal reference rules.

All pre-defined Rule ID’s are displayed.

The reference handling controls:

  • rules for separating references in a text string.
  • rules for interpreting the reference to make a search in A/R for the referred A/R document to settle.

A good hit percentage saves time and money and creates goodwill.

 See the Reference handling section in About the Imported bank statement functionality. FIN
Work with DI documents For technical consultants:
Activate the DI document subtype files for the DI document IMPBSTMTOE if you would like to print the database documentation for the OE-files from menu item Build DI interface definitions.

Related topics