CZ Banking Extension Setup

Update 30.05.2025

The CZ Banking Extension module needs to be activated, in the production environment the user will be asked to activate the subscription (see documentation on monetization).

Choose the icon, enter CZ Banking Extension Settings and then choose the related link.
Activate Enabled to enable the functionality.

Tip

Important: Before setting up, run the Assisted Setup for this module, which can be found in Assisted Setup -> Set up ARICOMA extensions. This will allow you to upload a configuration package and use it to add the sample settings, which are referenced in the scenarios in the following chapters, among others.

Bank statement and payment order formats

The Extended CZ Banking module is designed primarily to optimise work with statements and orders, but it also includes a universal import of bank statements in ABO format (*.gpc), which is supported in its basic form by most banks in the Czech Republic. It also allows you to export payment orders in ABO format (*.kpc).

Tip

Use one of the add-ons to this addon for API communication with your bank.

Processing Codeunit ID Processing Codeunit ID

Settings for manual batch import of statements

If your bank supports electronic statements that contain multiple transactions for multiple accounts, this can be used to create multiple statements at once (within a single company).

Choose the icon, enter CZ Banking Extension Settings and then choose the related link.
Go to the selected line (e.g. with the code "ABO_LOCAL").
Verify that the Processing Codeunit ID field contains the value 52057427 to allow you to import statements via the Import Bank Statements action.
Run the Extended Setup action.
Verify that the Batch Import Enabled flag is set to Yes.
Verify that the Processing Codeunit ID field contains the value 52057431 for processing ABO format files.

Tip

Enable the Support ZIP files field to allow importing multiple dump files at once within a single zip file.

Import encoding settings

In case of incorrect characters in the imported statement, you need to adjust the encoding used. Set the correct encoding in the Content Encoding field. To verify the functionality of the set encoding, we recommend using the Test Content Encoding action on the Statements Import Extended Setup page.

Settings for manual import of bank statements via API

If you have purchased an add-on from Aricoma for API communication with your bank and you do not want to use the automation processing support, then you need to adjust the settings. A detailed description of all the steps is in the documentation for each add-on, however the import itself is set up as follows in the case of ABO format:

Choose the icon, enter Bank Export/Import Settings and then choose the related link.
Navigate to the selected line (e.g. with the code "CZBE_ABO-IMP-LOCAL")
Select the line, press Ctrl+C, navigate to the new line and press Ctrl+V.
Rename the Code field to e.g "CZBE_ABO-IMP-API"
Check that the Processing Procedure ID field contains the value 52057427 to allow importing statements via the Import Bank Statements action.
Run the Advanced Settings action.
On the Statements Import Extended Setup, run the New action.
In the Description field, you can edit the pre-filled text.
Add parameters for the API connector - see the documentation for the specific API.

Important

If you use the bank import settings created in this way on the Bank Account card, then the user will start communicating with the bank's API every time the Import button is pressed on the Bank Statement card or when the Bank Statement Import function is started. This may not always be desirable, banks usually have set limits on the number of queries (e.g. per 10 minutes).

Setting up automation of import and processing of bank statements via the central stack

Automation can only be set up for methods where no user intervention is required. It is therefore not possible for importing from a local repository, but instead is typically suitable for API communication with the bank.

Setting the download to the Central Stack

The following procedure follows the result of the settings from the chapter Settings for manual import of bank statements via API.

Choose the icon, enter Bank Export/Import Settings and then choose the related link.
Navigate to the line with the code "CZBE_ABO-IMP-API".
Run the Advanced Settings action.
On the Statements Import Extended Setup, set the Enabled for the Central Stack field to Yes.

Automatic downloading of statements to the Central Stack

You only need to enable automatic downloading of statements to the Central Stack in one company. The function then goes through all the advanced settings for importing statements in this company, where the Enabled for Central Stack field is set to Yes. According to these settings, it will import the listings available on the interface that allows import without user intervention (typically the API).

Choose the icon, enter Extended CZ Banking Setup and then choose the related link.
Set the Automatically Download Statements To Central Stack flag.

Note

The created job queue entry is set to run at 6:00 AM on weekdays by default.

Tip

If you want to restrict the settings by which the automated import will be performed (see above), you can set the filter to a code in the Parameter String field on the Job Queue Items tab (for example, "CZBE_ABO*").

Setting up import from the central tray

The following procedure walks through the key settings included with the sample data.

Select the icon , enter Bank Export/Import Settings, and then select the associated link.
Navigate to the line with the code "CZBE_ABO-IMP-CENTRAL".
Make sure the Processing Procedure ID field has the value 52057427.
Run the Advanced Settings action.
In the Bank Statement Provider field, select the value "Central Stack".
Check that the Processing Procedure ID field contains the value 52057429 for processing ABO format files.

Setting up bank accounts for automation

For central processing and the resulting possibilities of automating processing, it is necessary to clearly define which companies own which bank accounts. The table Bank Statement Processing Setup is used for this purpose. All account numbers that contained files imported into the Central bank statement stack are automatically entered into this table. You then need to assign the account to one of the companies in BC.

Choose the icon, enter Bank Statement Processing Settings and then choose the related link.
Select the line with the account number you are setting up.
If the account is in a foreign currency, select the appropriate code in the Currency Code field.
At the bottom of the page in the Settings section, fill in the Statement Start Date field for the appropriate Company from which to process statements. This date refers to the Listing Date.

Important

The number of records in this table with the Statement Start Date filled in is the determinant for controlling the number of accounts in the subscription. If a number greater than the number valid in the subscription is defined, the Central Stack cannot be opened and the number of valid records in this setting must first be reduced. Disabling the import is possible by setting the Processing disabled flag.

Tip

If you have a new bank account but no statement has been imported yet, you can also make the setting in advance by manually entering the account number.

Automatic processing of the extract from the central stack

You only need to enable automatic processing of statements from the Central Stack in one company.

Choose the icon, enter Extended CZ Banking Setup and then choose the related link.
Set the Automatically Create Bank Statements flag.

Note

The created job queue entry is set to run at 6:00 AM on weekdays by default.

Cleaning processed statements from the Central Bank Statement Stack

We recommend that you continuously delete the already processed records in the Central Bank Statement Stack table, preferably with an automated task in one company:

Choose the icon, enter Extended CZ Banking Setup and then choose the related link.
Set the Automatically Clean Central Stack flag.

Note

The created job queue entry is set to run at 6:00 AM on weekdays by default. The automatic batch by default deletes statements older than 14 days, but can be overridden in the report dialog (the "Date formula" field).

Support settings for importing statements

Automatic account number formatting (optional)

Enabling this feature will automatically format bank account numbers in BC, eliminating problems with importing bank statements

Choose the icon, enter Company Information and then choose the related link.
Activate the Format Account Number field.

Bank account number on bank statement (optional)

This is used to specify the exact format of the bank account number that is in the statement files if it differs from the value entered by default in the Bank Account Number field.

Choose the icon, enter Bank Accounts and then choose the related link.
Complete the Bank account number on bank statement field.

Support settings for automatic processing of statements

Last level of batch processing (mandatory)

Specifies the last level of automatic processing of bank statements. The actual processing of the bank statement is carried out using the standard process.

Choose the icon, enter Bank Accounts and then choose the related link.
Select the desired value in the "Last Bank Statement Level" field:
- Bank Statement (default value)
- Issued bank statement
- Journal

Note

Usually the value Journal is set. The Bank Statement value is set when a payment advice needs to be manually imported for the imported bank statement.

Number Series (required)

You must set the same number series for unissued and issued bank statements on the Bank Account Card. This number series must have Manual Numbering activated and the Mask filled in. The Mask must contain a minimum of 2 characters for the year (yr) and the free number (ccc).
The bank statement processing functionality automatically numbers bank statements in BC by entering the year and the statement serial number assigned by the bank according to the mask.

Check bank statement turnover (optional)

When "Issuing" a bank statement, the function checks if the statement turnover matches the difference between the Starting and Ending balance of the statement as shown on the bank statement header. The Starting and Ending balance of the statement is imported from the Bank Statement file.

Choose the icon, enter Bank Accounts and then choose the related link.
Activate the Check Bank Statement Turnover field.

Custom modifications

Custom format for import

If you download statements in a different format or if you need a specifically customized import, your partner must create a custom process codeunit to import bank statements into the bank statement stack. The stack should be populated with unformatted data as it is directly in the bank statement file of the appropriate format (the formatting and validation of the data is handled by the bank statement creation function).

codeunit xxx "Bank Stmt.Imp.-MyFormat"

TableNo = "Bank Stmt. Import Request Acb";

trigger OnRun()
var
    DotNetStreamReader: Codeunit DotNet_StreamReader;
    InStream: InStream;
   TempCentralBankStmtBufferAcb: Record "Central Bank Stmt. Buffer Acb" temporary;
    TempBankStmtLineBufferAcb: Record "Bank Stmt. Line Buffer Acb" temporary;

begin
    //StreamReader initialization to read the contents of the dump file:
    Rec.CreateStreamReader(InStream, DotNetStreamReader); 

    //Where to populate the contents of the StreamReader dump into temporary tables - see examples below

    //Example of header filling:
    NextBufferNo += 1;
    TempCentralBankStmtBufferAcb.Init();
    TempCentralBankStmtBufferAcb."No." := NextBufferNo;
    TempCentralBankStmtBufferAcb."Account No." :=  ;	//our account no.
    TempCentralBankStmtBufferAcb."Statement No." := ;
    TempCentralBankStmtBufferAcb."Statement Date" := ;
    TempCentralBankStmtBufferAcb."Starting Balance" := ;
    TempCentralBankStmtBufferAcb."Ending Balance" := ;
    TempCentralBankStmtBufferAcb.Insert();

    //Example of filling rows:
    TempBankStmtLineBufferAcb.Init();
    TempBankStmtLineBufferAcb."Buffer No." := NextBufferNo;
    TempBankStmtLineBufferAcb."Line No." := NextLineNo;
    TempBankStmtLineBufferAcb."Variable Symbol" := ;
    TempBankStmtLineBufferAcb."Constant Symbol" := ;
    TempBankStmtLineBufferAcb."Specific Symbol" := ;
    TempBankStmtLineBufferAcb."Account No." := ;   //account no. in 16+4 format
    TempBankStmtLineBufferAcb.Description := ;
    TempBankStmtLineBufferAcb.Amount := ;	
    TempBankStmtLineBufferAcb.Insert();
    NextLineNo += 1;

    //Save the result of processing:
    Rec.SetData(TempCentralBankStmtBufferAcb, TempBankStmtLineBufferAcb); 
end;