Banking Link Application – Installation Instructions

Preface:

The Banking Interface extensions by Micro Apps currently only support Dutch banks, trying to configure any other bank will result in error message and transactions not being processed. This means that for now the following bank are support: ABN AMRO, Rabobank, ING, ASN Bank, RegioBank, SNS Bank, Knab, Bunq and Triodos.

Installation:

To install the banking interface app you simply navigate to the Microsoft Marketplace for Business Central apps (AppSource) via your own Business Central environment. From here you can automatically install the extension and make it available within every company in your Business Central environment.

For the correct working of the app, make sure that the setting for the Micro Apps Base App is set to “allowing HttpClient Request”.

Prerequisite:

Before the banking interface extension can be used to its full potential, a couple of settings need to be set up. In this chapter we will discuss these settings.

Bank accounts

The bank accounts that are going to be used via the banking interface need to have the following configuration.

IBAN: Used for matching the Business Central bank account with the bank accounts at the financial service provider.

 

General journal template

The banking interface extension uses as much of the standard Business Central functionality as possible. This means that Business Central need to be configured in such a way that the base functionality can be used.

This also means that for each of the bank accounts that will be used via the banking interface extension a general journal template is needed. Refer to the table below for the information that is required:

Field Value
Type Bank
Bal. account type Bank account
Bal. account Bank account that will be used as balance account when the gen. journal is used.
No. series No. series that will be used for the numbering of the journals.
Force Doc. Balance True / Active
Copy VAT setup to line True / Active

The general journal template must be setup in Business Central. In the picture below an example is shown for a ‘ABN AMRO’ bank account:

This needs to be configured for every bank account that will be used via the banking interface extension. In case this is not configured correctly transactions cannot be imported using this app.

Financial service provider

The banking interface extension uses the services of a third-party to enable functionality for transactions to be imported. The financial service provided chosen by Micro-Apps is Bizcuit. Bizcuit is a fully licensed financial service provider that connects with any Dutch bank via PSD2.

This means that Micro-Apps has no direct access to your bank account as Bizcuit is handling all the financials transactions.

With the use of the PSD2 act the financial service provider only has access to the bank account for a limited time. This means that after a period of 3 months (90-days) the mandate needs to be renewed with Bizcuit.

Banking Interface Setup

Once the installation is complete, the app needs to be set up. This can be done via the banking interface setup page. This page contains all the necessary information to completely set up the extension.

Account registration

The actions on the setup page are divided into two areas, the first is the general page it set. Here you will be able to enable or disable the entire extension and you are also able to authenticate the extension with the financial service provider Bizcuit. To authenticate with Bizcuit an account is needed first, an account can be created via the ‘Create account’ button in the ribbon of the setup page, or by going to their website and following the setup steps as described by Bizcuit: Create Bizcuit account

After an account is created, you have to authenticate the app by using the ‘Authenticate’ button on the setup page. This will link your Business Central company to Bizcuit and you are able to use the extension. When this is done, the app will automatically be set to ‘Active’.

Bank account registration

After registering a Bizcuit account and authenticating, the bank accounts need to be registered with Bizcuit too. This can be done from the Banking interface setup page, by clicking the ‘Register bank account to Bizcuit’ button in the ribbon.

The newly shown page will show all the bank accounts that are eligible to be registered with Bizcuit. The banking interface app checks if the bank accounts is already known in Bizcuit, if this is the case the bank account will not be shown.

To register a bank account, you select the bank account you would like to register and click on ‘OK’. This will register the bank account within Bizcuit. To register multiple bank accounts at once, hold shift and click on the bank accounts that you would like to register, after selecting the desired bank accounts click ‘OK’. After clicking OK, you will be asked to give consent to Bizcuit and you will be directed to the Bizcuit website to do so.

If you would login into the Bizcuit portal you would see the registered bank accounts listed as in the image below. The banking interface app will also create a company in the Bizcuit portal that is named after the company from which the bank account is registered.

Job queues

The banking interface app does have functionality to import the latest transactions automatically into the Bank/Giro Journal. This is done via a job queue that is created at the time the extension is installed.

To start the automatic processing of the transactions, the job queue needs to be started because these are inserted with status ‘On Hold’ by default. To start the job queue you click on ‘Job queues entries’ in the ribbon of the banking interface setup page. This will open all the job queues that are currently configured. To start the job queue you simply select the banking interface job queue and click ‘Restart’ in the ribbon.

A job queue will be created for each of the banks that are currently supported by the Banking Interface extension. Below you will see an example of each of the job queues that will be created when the ABN AMRO, ING and Rabobank interface extension is installed.

General use

After the installation and registration of the bank accounts with Bizcuit, you can import the transaction(s) that are ready for import. Importing transaction(s) can be done via one of the following ways:

When transactions are being imported, a call will be made to Bizcuit to determine which transactions need to be processed. Therefor only transactions that are not yet imported will be downloaded from Bizcuit. It is therefore important not to import transactions via the standard Business Central functionality, when the banking interface is being used to process bank transactions.

Manually importing transactions

To manually import transactions, the following actions need to be performed.

Via bank-/giro Journal:

The imported transaction will be placed in a bank journal. These journals will need to be checked and posted before the transaction will be visible in the General Ledger of Business Central.

Via Bank Account card:

To manually import transaction the following actions need to be performed.

The imported transaction will be placed in a bank journal. These journals will need to be checked and posted before the transaction will be visible in the General Ledger of Business Central.

 


 

Import of SEPA definitions:

Before you can start using the banking interface extension developed by Micro Apps there are several settings and setups that need to be performed. Most of the setup is done during the initial installation of the application. Sometimes however it can occur that the definitions for data exchange for SEPA CAMT are not present. Please refer to the remainder of this instruction to learn how to import and setup the definition for yourself.

 

Definition data exchange

Business Central needs to know the structural layout of the files before you can correctly import the SEPA files. This is determined through Date Exchange definitions.

  1. Navigate to Date Exchange definitions.
  2. Click on Import/Export in the top ribbon.
  3. Now, click on the button for Import Date Exchange definition
  4. A new window will be shown, select Choose and navigate to the file that contains the definitions. (The file can be downloaded by clicking here)
  5. You will notice the definition has been imported, it is called MABI SEPA CAMT.

 

Linking of the definition code

  1. Navigate to Bank Export/Import setup.
  2. Here you will find the bank export/import setup which will be used by the banking interface extension. The ones used by the banking apps will be marked with MA (Micro-Apps).
  3. Select the value MABI SEPA CAMT in the column Data Exch. Def. Code
  4. Repeat this for all rules that start with the code.