Setting up direct communication to SDC's Netbank Erhverv solution, via Bank Connect
This article describes how to set up direct communication between Continia Payment Management and SDC's Netbank Erhverv solution, via Bank Connect.
Prerequisites
Before starting the setup, you should make sure that the following prerequisites are met:
| Text | Description |
|---|---|
| Form of communication | You want to set up direct communication between Continia Payment Management and SDC's Netbank Erhverv solution, via Bank Connect. |
| Create Netbank Erhverv Agreement | You must subscribe to SDC's Netbank Erhverv solution. Please note that some banks have named their online banking solution with different names. See the list here, or contact your bank adviser to hear how you will be registered, prices etc. |
| Do you have the necessary permits in your online bank? | You must be an administrator in the Netbank Erhverv solution so that you can order the integration, order files, and retrieve certificates. Pay attention to who you give access to Payment Management. Anyone with permission to send payments can potentially misuse your funds in the bank. Read more about setting up rights here. |
| Create Bank Connect agreement | In addition to your subscription to SDC's Netbank Erhverv solution, you must also subscribe to the Bank Connect solution. At the individual banks, there is a big difference between how you order Bank Connect and what the information you need for setup is called. To make it all clearer, we have in the table here added the name of the integration solution you have to subscribe to, depending on which bank you have, and thus in addition to your Netbank Erhverv solution. The registration typically takes place on the bank's website, where you must select Continia Software as the ERP supplier and enter a number of information about your current commitment with the bank. At the same time, you must decide whether you still want to approve payments in the online bank in the future or whether you want payments sent from Payment Management to be considered pre-approved and thus sent for payment without further approval in the online bank. You must also decide which payment methods you want to use and which files must be ordered for delivery every day (bank statement, deposit, and status files). If necessary, see the next section. Once you have created your Bank Connect subscription, you will receive a Function ID and an Activation Code by post. The codes must be used when you are asked to create your Bank Connect certificate and activate the direct communication in Payment Management, described below. Contact your bank adviser to find out how to sign up for Bank Connect, prices etc. |
| Order files at the bank | A prerequisite for you to be able to import status files, deposit files, and account statements into Payment Management is that your bank creates and delivers the right files for you. Use the Order files at the bank list below as inspiration for which files to order. Contact your bank adviser if you need assistance. |
| Does your Business Central use the right "Environment"? | You can not use direct communication in a test company, sandbox, or in our demo environment. Only production environments are supported. |
| Minimum version of Continia Payment Management | In order for you to enable direct communication, Payment Management must be updated to the latest version or at least version 2.75. |
1. Order files at the bank
When you order your online banking subscription, you will be asked which files you want to order. Use the table below to help identify which files you need:
| If you want to | Description | Order the following from the bank* | Continias recommendation |
|---|---|---|---|
| Import status files in connection with. sending payments in ISO Pain.001 format. | Status file for outgoing payments. The ISO Pain.002 file is sent by the bank immediately upon receipt of the ISO Pain.001 file. Payment Management automatically searches for the file immediately after a payment file is successfully transferred to the bank. | ISO Pain.002 |  |
| Update status on payments in the payment journal. | This is your intraday information. This report provides you with a nearly real-time view of your account(s). ISO CAMT.052 is mostly used by banks not sending updated ISO PAIN.002 second edition, but instead offering this file. When you press Update status in the payment journal, Payment Management automatically searches for the file, and if available, imports the file. You can, of course, also import the file manually from a file. | ISO CAMT.052 | |
| Import detailed information about completed customer payments, incl. KID payments. | Final confirmation that payments (credits) have been made. The file contains the day's completed incoming payments, both account transfers to the account, and KID payments. When you select Import payments in the cash receipt journal, Payment Management automatically searches for the file and imports it if available. Of course, you can also import the file manually from a file. The file is also called "CREMUL". | ISO CAMT.054C | |
| Import FIK / GIK inpayments only. | A detailed confirmation of yesterday's payments from NETS. The NETS PBS file is sent in the morning. | NETS PBS-sector format | |
| Reconcile bank statements and import payments. | Account statement with a detailed description of all yesterday's transactions as well as extended information on all deposits and withdrawals, including notifications associated with a deposit or withdrawal. | ISO CAMT.053 | |
*Applicable to all file orders is that one file is ordered per. account per day.
2. Create or edit your bank accounts
An important prerequisite for you to complete the setup of Payment Management is that you have set up your bank accounts correctly before running the assistant guide for setting up Payment Management. The guide ensures that the correct bank card is created and that you get the correct bank setup imported.
Before running the wizard in the next section, you must create or edit your bank accounts and ensure that the fields shown in the table below are filled in correctly on the bank account card. You are welcome to fill in more than the mentioned fields on the bank account card, but these are a minimum. You can find our guide to creating a new bank account here, where there is also a description of all the fields on the bank account card that are Payment Management specific.
| Fast tab | Field on the Bank Account Card | Description |
|---|---|---|
| General | Bank Branch Code. | Can be filled in, otherwise, the registration number must be part of Bank Account No. |
| Bank Account No. | Must be filled in. | |
| Communication | Country/Region Code | Must be filled in. |
| Posting | Currency Code | Must only be filled in if the account is held in a currency that is different from LCY. |
| Transfer | BIC/SWIFT Code | Must be filled in. |
| IBAN | Must be filled in if you make international payments. |
3. Run the Assisted setup guide for Payment Management Basis
The next step is now to run the Assisted setup guide for Payment Management Basis.
Select the icon
or press Ctrl-F3, enter Assisted setup guide for Payment Management Basis, then select the related link.Select your bank account on the first screen.
If you are prompted to overwrite the base Payment Management setup, answer No. This saves only changes in connection with the setup of your bank. If you answer Yes, be sure to review the base setup of Payment Management again, otherwise all selections and values will be set to standard values.
When you are subsequently prompted to import the bank setup, open the XML Bank Setup folder in the product package that you have downloaded from Continia PartnerZone, and select the following file:
Type Bank Code Filename SDC SDC20022 Sparekassernes Data Central - Webservice Communication x.xx.xx.xml* *Note that x.xx.xx replaces the version number of the file.
The bank setup is now imported and a new bank card is automatically created with code SDC20022.
The last screen is a summary of your setup.
Finish the wizard.
If you have several bank accounts, you must run the guide for each bank account.
4. Create your Bank Connect certificate on your bank card
To ensure that others cannot decode the communication between your Payment Management and the bank, create and exchange a certificate with the bank. To create the certificate in Payment Management, follow the wizard Create certificates at a bank. Remember to open the bank card with the code "SDC20022".
When you, in the wizard, are prompted to create the certificate, whether it is a shared or individual certificate, fill in the fields on the screen as described in the table below.
| Field on Bank Card | Informed from the bank | Note |
|---|---|---|
| User Name | Function ID | Must be filled in. Contains 26 characters. Received from your bank once you have created your Bank Connect agreement. |
| Password | Activation Code | Must be filled in. Contains 16 characters. Received from your bank once you have created your Bank Connect agreement. |
| Main Bank Branch No. | Must be filled in. See Bank Connects' list of banks here. The numbers in parentheses are the banks' main registration numbers, which you must enter to activate an agreement. | |
| Vendor No. | Not to be filled. | |
| Bank Identification | Not to be filled. | |
| Web Service Folder | Not to be filled. |
Your Payment Management solution is now set up to use direct communication with SDC's Netbank Erhverv solution, via Bank Connect.
Recommended articles
Once you have completed the setup, we recommend that you read the following articles:
- To set up vendor payment information, read the article Assisted setup of vendor payment information.
- To create a payment suggestion, read the article How to create a payment suggestion in the payment journal.
- To send the payments to the bank, read the article How to use the payment journal and send payments to the bank.
- To import bank account statements, read the article How to reconcile your bank account.
- To import customer payments in the cash receipt journal, read the article Import customer payments.
See also
System requirements for communication components (dll files).