Create a bank card

You must create a bank card for each of the banks you want to send payments through. For example, if you have active bank accounts in 2 different banks, you must create 2 bank cards.

Note

Before setting up the bank, make sure that you have imported the bank setup file for the given bank. You can read more about how to import the bank set up in the article Import Continia's bank setup. If you are unsure about under which bank your bank operates, please see Bank Information for more information.

How to create a bank account

Follow the guide below to create a bank account.

  1. Select the icon Søg efter side eller rapport, type in Banks, and select the related link.
  2. This opens the window Banks.
  3. To open a Bank Card, either select the action New if you want to create a new bank card, or open an existing bank card by selecting the Edit action.
  4. This opens the window Bank Card.
  5. Below you will find descriptions of the individual fields and functions in the window, and what consequences this has for the use of Continia Payment Management.
  6. When you have completed the setup, select OK.

Important

Note that certain fields of Bank card automatically is deactivated depending on the selection of Bank Bookkeeping Branch Code. This is because some fields are bank-specific and therefore only used at the individual bank.

General

FieldDescription
CodeIndicates the code Dynamics NAV uses to identify the bank. The code is used, among other things, under Create a bank account.
NameSpecifies the name of the bank.
File Name (Payment file)Specifies the file path to the payment file. File names are only required for banks that use manual file import and export. If your bank uses direct communication, you can leave the field blank.

Note that the path is always seen from the client.
Warn when replacing fileWhen you use manual communication, payment files will be exported to the location you specified in the field above. If you select the box Warn when replacing file, Payment Management will warn you if you are overwriting an existing file.

Many users want to store their payment files from time to time. When exporting the file, they correct the name in the dialog - eg. they add the date the file was exported. This creates a file archive containing all payment files sent to the bank.

If you do not want to be warned every time you export a payment file, you can clear the box.
Bank Bookkeeping Branch CodeIn order to Payment Management be able to validate your payments in the payment journal, as well as correctly format your import and export files, you need to associate a Bank Center code at your bank.

The code corresponds to the code from the setup file you imported under Import Continia's bank setup. The code must match the bank being created.

It is important that you choose the right bank, to ensure correct import and export of the payment files. If you are unsure about which Bank Bookkeeping Branch Code your should select, you can read more in the section Bank information.

Note that certain fields of Bank card automatically is deactivated depending on the selection of Bank Bookkeeping Branch Code. This is because some fields are bank-specific and therefore only used at the individual bank.
Enable LogSpecifies whether to save all xml files that Payment Management communicates with the bank.

The files are stored in an xml archive and can be accessed under the section How to use the XML archive on the bank card.
Request StatusIndicates how Payment Management requests the bank for status response when a payment file is created, and for which transactions a status response is requested.

The request is part of the header of the Pain001 payment file and cannot be changed afterwards, even though you change the setting and select the action Update status on the payment journal. You must create a new payment file before a change takes effect.

You can select "blank", Failed or All.

"blank"
If the field is left blank, no status response is requested. This setting is used, e.g. if you are using manual communication but don't want to manually import status files.

Failed
Should be specified if you only want to receive status replies to rejected payments.

All
With this option, a status reply is requested from the bank for all payments. This setting is used by most people who use direct communication or who want to manually import status files.
In UseAfter having finished the bank setup, make sure that this box is checked. If at some point you no longer use the bank, you simply uncheck In Use.

When you enable In Use, Payment Management updates all field validations on the payment methods available to the bank. The update may take some time.
Move Payment DateIf a Payment Date falls on a bank holiday Payment Management will move the Payment Date according to what has been selected in this field. Move Payment Date can have the following values:

"blank"
Back
Forward

Blank and Forward will move the payment date forward to the next non-bank holiday as is normal in i.e. Denmark. Selecting Back will move the Payment Date back to the first non-bank holiday.
Uses Shared CertificateIndicates whether Shared or Individual certificates are used. This field cannot be changed

You can specify that individual login is required from the general setup page of Payment Management. If individual login is required, the checkmark will be removed, and only users with Individual certificates can be used. See section Create bank certificates.
Certificate InstalledIndicates whether a certificate is installed.

Indicates whether a certificate is installed.

If an individual certificate is selected, only whether a certificate is installed for the user logged in. All installed individual certificates can be seen under the action Individual Certificates.
User NameBank specific field
User name that you have created with the bank, also called User number or Function ID. For more information, see the section Create bank certificates.
PasswordBank specific field
Type in the password that you have received from the bank. Also called Security Code or Password. For more information, see the section Create bank certificates.
Main Bank Branch No.Bank specific field, Bank Connect and BEC.
For some banks, this field refers to the bank for which an agreement has been signed. The bank's main registration number must be entered. For more information, see the section Create bank certificates.
Vendor No.Bank-specific field, Handelsbanken.
Must be filled in with an SHB number, which is an agreement no. at Handelsbanken. For more information, see the article Create bank certificates.
Bank IdentificationBank specific field, Nordea.
Typically, the field is filled with Signer Id from the Corporate Access File Transfer screen. For more information, see the article Create bank certificates.
Web Service FolderBank specific field, Nordea.
Typically, the field is filled with Signer Id from the Corporate Access File Transfer screen. Thus, the same information as is filled in the field Bank identification. For more information, see the article Create bank certificates.
Web Service Country CodeBank specific field, Bank Connect.
In connection with the creation of a certificate for banks in the Bank Connect collaboration, Payment Management uses the country code registered in Business Centrals Company Information to indicate from which country the customer comes.

For example, if you create a certificate for a Bank Connect bank, and a country code is registered in Company Information which is not supported by the bank, e.g. Greenland, then you can override the country code in the Company Information with another country code, e.g. Denmark.

If the field is empty, the country code from the Company Information is used.
G/L Acc. Payment DifferencesSpecifies which general ledger account to post amount differences, found in account reconciliation, for this bank.
Bank File CounterBank specific field, US Nacha banks.
The US Nacha format accepts a maximum of 26 payment files per day and requires that the files be named the same, however, that the files be versioned from A-Z in the file name. The field shows which version of the payment file (letter) was exported last. The field is automatically reset to "A" when the date changes. If an attempt is made to export more than 26 payment files, an error message is displayed.

SFTP

FieldDescription
SFTP User NameSpecifies the user name for logging in on the server.
SFTP PasswordSpecifies the password for the server.
SFTP Ingoing filesSpecifies the directory of where files from the bank are located on the SFTP server.
SFTP Outgoing FilesSpecifies the directory of where files to the bank are located on the SFTP server.
SFTP Port No.Specifies the SFTP port number used for communication. Normally port 21.
SFTP AddressSpecifies the IP address or DNS name of the SFTP server.

DNB

FieldDescription
Own E-mailE-mail used when registering for Direct Communication between DNB Corporate Internet Bank for DNB Connect and Payment Management.

Continia and DNB use this email to inform you of the status of the registration. Both DNB and Continia send you e-mails when the Direct Communication is approved and activated. The field is mandatory.
DNB Division NumberThe division number is found in the email received from DNB.
DNB Division NameThe division name is found in the email received from DNB.
DNB Client NumberThe client number is found in the email received from DNB.
The client number must be 11 digits.
DNB Registration ReferenceContains an internal reference to DNB, which is used in connection with registration for Direct Communication between DNB Corporate Internet Bank for DNB Connect and Payment Management.

To ensure that others can not create a subscription on your behalf, DNB and Continia have developed a shared API, where Payment Management creates a unique ID and then starts DNB's registration. This ensures an absolutely secure and unique registration of your integration with DNB Corporate Internet Bank for DNB Connect and Payment Management.
DNB Signup LinkLink to DNB registration page for establishing Direct Communication between DNB Corporate Internet Bank for DNB Connect and Payment Management.

When you click on the small globe to the right of the field, a new tab opens in your browser, from where you can start signing up for DNB Direct Communication. You must log in with your DNB Connect credentials to run the registration process.

Actions on the window

At the top of the window, under Navigate, you'll find the following features specific to Payment Management:

ActionDescription
Create Shared CertificateOpens the window Login, where you can enter Username and Password. When selecting OK a shared certificate will be created for the bank.

Also used for creating the DNB Signup Link for DNB.
Individual CertificatesOpens the window Certificate Handling from where you can create individual certificates.
XML ArchiveOpens the window File archive, where you can access all the xml files that Payment Management has communicated with the bank.
Recon. SetupOpens the window Bank Recon. Setup where you can configure the Statement Intelligence module.
Pmt. Ref. Search RulesSearch rules allow Statement Intelligence to match a payment reference to a customer record.

See also

Bank information

Import Continia's bank setup

Create a bank account

Create bank certificates

Using the Xml archive on the debit card

Set up reconciliation

Pmt. Ref. Search Rules