CZ Banking Extension
Update 30.05.2025
The module extends the functionality "Banking documents for Czech Republic (extension)", which is part of the Czech local functionality of D365 Business Central (hereinafter referred to as BC).
The main benefit of the Extended Banking module is to simplify the import and subsequent processing of bank statements, thereby reducing routine user activities.
The advantage is the variability in the setting of the import of bank statements into BC and their subsequent processing, where you can individually set the mode for each bank account separately.
The module allows to support users in processing statements in 2 levels: basic and advanced.
Basic variant
Bank statements
You gain access to the functionality by purchasing a subscription for your first bank account. This option does not determine the number of accounts for which you will use it. However, the work is manual within the company and for a specific bank, and in the case of multiple accounts with one bank, it supports importing multiple statements at once. Also for this variant it is possible to purchase one of the offered add-ons for API communications with the bank.
Payment orders
In the basic version, the standard Export function on the Issued Payment Order page is used. In the case of a configured API, the statement is sent without downloading the file to the client computer.
Advanced variant
Bank statements
You can access the full automation functionality (except for the final posting of the Payment Journal) by purchasing a subscription for multiple bank accounts. The advanced option provides the ability to automate all steps:
- Uploading bank statements (using methods without manual input, typically API or other custom developed methods)
- triggering bank statement imports across companies
- automating the processing of statements through to the creation of Payment Journal entries, including the suggestion of matching
Payment orders
As part of the development of the module, support for automating the sending of Issued Payment Orders across companies and bank accounts will be completed during 2026.
Use cases
The following chapters describe the most common scenarios for using the functionality to import statements and export payment orders. The example scenarios describe the import of statements in .gpc format, see the section Bank statement and payment order formats.
Basic - Import and processing of one statement
In this case, this is standard BC functionality. The user opens a new Bank Statement tab and starts the "Import Bank Statement" action. After importing, the user uses the Issue and Post function to post it.
Note
For a detailed description of the functionality and settings see CZ Bank Statements and Payment Orders.
Basic - Import and processing of bulk statement
This is a situation where one bank statement file contains multiple bank statements for one or more bank accounts. For functionality settings, see. Settings for batch import - bulk statement and .zip, Supporting settings for BV import, Supporting settings for BV processing
- Choose the
icon, enter Import Bank Statements and then choose the related link.
- Start the Import... action.
- Drag the file or click to browse and select the file
- When you press OK, the Bank Statement Stack automatically opens. This is a temporary table for viewing imported statements and processing them immediately. Therefore, it is necessary to continue with the next step.
- Run the Processing action to create the bank statement up to the set processing level.
Note
When importing after selecting a file, you may receive the message "Nothing to import. Do you want to view a report with bank statements?" Clicking YES will display the files with error details.
Tip
Most common errors:
- The imported file already exists in BC --> in this case the status field shows the processing status in BC.
- Bank account number was not recognized --> in this case the field "Bank account number" is shown in red.
- Either the imported file does not belong to the imported company
- or the bank statement file contains an account number in a different format, usually a prefix and an account number without a hyphen. In this case, make the settings according to Bank account number on the bank statement (optional)
Basic - Import and processing of multiple statement files
This is typically a situation where files containing only one bank statement are used and multiple files need to be imported at once. The files need to be compressed into a single .zip file to be imported, with automatic extraction taking place. The procedure for importing a bank statement is the same as described in Importing and Processing a Bulk Bank Statement into a Single Company.
Note
Multiple files can be passed at once directly in the file selection dialog (from BC26 version).
Basic - Export Payment Order
Exporting payment orders is performed on the Issued Payment Order tab by running the Export action.
Note
If you purchase one of the API extensions, you can export the order directly to your bank's system.
Advanced - manual import to multiple companies
The scenario describes a situation where there are multiple companies in the BC environment and the import of bank statements will be done centrally for multiple companies at once from a local repository. It is imported into the Central bank statement stack table. The table records are common to all companies. Imported statements are stored here for further processing. After processing, it is advisable to delete them on an ongoing basis.
Tip
In the Advanced CZ Banking Settings, turn on automatic purging.
- Choose the
icon, enter Central Bank Statement Stack and then choose the related link.
- Start the Import... action.
- Drag the file or click to browse and select the file
- When you press OK, the statements will automatically import into the Central Bank Statement Stack rows. Each statement will be filed on a separate line.
Note
If you import a .zip file, the functionality will only import supported formats from compressed files. If there are unsupported formats in the .zip, the import ignores them. Multiple files can be passed at once directly in the file selection dialog (from BC26 version).
Advanced - automated import to multiple companies
This is a situation where there are multiple companies in the BC environment and the import of bank statements will be done centrally for all companies automatically without user intervention. An example would be direct communication with the bank via API, where BC directly downloads statements or executed transactions and stores them in the Central Bank Statement Stack for further processing.
Tip
See SettingsXXX for instructions on how to create your own import automation.
Advanced - manual processing of statements
Using the example of manual processing, we will show the steps that need to be performed after the statement has been loaded in order to reach the posting of the journal.
This method of processing may be useful in a situation with a large number of accountants, where each person is responsible for one or a few companies with multiple bank accounts. In this case, each user creates statements from one place in the companies or for the banks they are in charge of:
- Choose the
icon, enter Central Bank Statement Stack and then choose the related link.
- Choose the company name in the Company name field.
- Enable the Company Bank Statements Only flag to display statements belonging to the selected company.
- Select the Process function and confirm the execution by selecting Yes. This will create Bank Statements in the respective company for the rows for which they have not yet been created - you can see the result in the Status and Bank Statement Number columns.
- Clicking on the value in the Status field (or directly on the Bank Statement Number*) in the row will open either a Bank Statement, Payment Journal or Issued Bank Statement depending on the value of the Status field. Perform the next steps to post the statement in the Payment Journal.
- Return to the Central Bank Statement Stack and continue with additional statements or another company.
Tip
If a bank statement has not been created, or you are importing a new bank account, check the settings see Bank Statement Processing Settings
Advanced - automated processing of statements
Automated processing of imported statements is increasingly used not only in companies with a smaller number of accountants serving multiple companies with many bank accounts. The time saving consists in processing centrally imported statements according to set parameters, i.e. transferring them to individual companies including processing to a defined level (e.g. up to the draft lines in the Payment Journal).
The functionality knows which statements have already been imported and only fills in the missing ones (if the input file is not yet available or if the operator deletes the record in the central stack) at an interval of 14 days.
Through the Central Bank Statement Stack page, the user has an overview of the processing status of individual companies and can use it as a so-called dispatcher's counter (from the line, he can open a record in another company and change the status, e.g. post the statement):
- Choose the
icon, enter Central Bank Statement Stack and then choose the related link.
- Choose the company name in the Company name field.
- Sort the Statement Date column in descending order.
- Scroll to the row where the Status is not Posted. Click on the value in the Status field to open the record and perform the next steps to post the statement in the Payment Journal.
- Return to the Central Bank Statement Stack and continue through the other rows until all are in the Posted status.
Note
Verify settings for automation see Supporting settings for automatic processing.
Important
To work with the Central Bank Statement Stack, the user must have a standard set of permissions to create and process bank statements in the companies where the statements are to be served by this tool.
Advanced - automated export of Payment Orders
The functionality will be added during 2026.
See also
CZ Banking Extension Setup
CZ Banking Extension APIs Setup
Financial Pack