The recommendation from the banks is to use the ISO20022 XML format. This is a global standard format that supports all future changes and new features.
By using ISO20022 XML, a higher degree of standardization is achieved, making it easier to exchange information between different systems and parties. This creates a more efficient and consistent way of working, both now and in the future.
Uniconta supports this format for all banks in Denmark and a number of other countries in Europe. Here is a list of the countries where we support the format.
- Denmark
- Sweden
- Norway
- Germany
- The Netherlands
- England
- Switzerland
- Lithuania
- Estonia
Note: Not all banks within each country are supported. During setup, you can select the bank and here it is typically the largest banks that can be selected.
Setup
The format is set up under Vendors/Maintenance/file formats for methods of payment.
This is also where all the other file formats we have for the banks are created.
If an XML format is selected, press the Options button and choose the bank or banking center to be used.
In Denmark, select Danske Bank, Nordea, SEB or one of the three banking centers Bankdata, BEC or SDC.
Denmark - Banking centers
Here you select Payment format = ISO20022 (DK) under the Options button you select the banking center that your bank is affiliated with. It is either Bankdata, BEC or SDC.
In this article you can see which banking center your bank is affiliated with. Read more here.
It is a requirement from the banking centers that you fill in the field 'identification of agreement' under bank reconciliation for the current bank account. Read more about bank reconciliation here.
The recommendations for each banking center are:
- Bankdata - they recommend that you enter your CVR number in the field
- BEC - they recommend that you enter your CVR number in the field
- SDC - they recommend that you enter your CVR number in the field
Denmark - Nordea
It is a requirement from Nordea that you fill in the following two fields under bank reconciliation:
- Identification of agreement - the field is filled in with Nordea SignerId. It is stated on the appointment made with Nordea, otherwise please contact Nordea
- Customer id - the field is filled in with the Nordea CCM agreement number. It is stated on the appointment made with Nordea, otherwise please contact Nordea
Nordea recommends that you fill in ID with Nordea SignerId. It is a requirement that ID is between 10 and 18 digits. Read more about bank reconciliation here.
Note: It is a requirement that ID is between 10 and 18 digits
Read more about bank reconciliation here.
Denmark - Danske Bank
There are no special requirements from Danske Bank.
Denmark - SEB
Version-95With SEB in Denmark, you can, among other things, make FIK71 payments.
Foreign customer with Danish bank account
In the ISO20022 payment files, the country code for the receiving bank must be specified. With the module 'Approval of vendor bank details', it is possible to specify a country code for the vendor bank.
In most situations, the bank's country code will be the same as the vendor's. However, there are situations where they differ. This could be a Swedish vendor with a Danish bank account, where an account-to-account payment is made via BBAN.
This has previously resulted in an extra fee, as the bank saw it as a cross border payment, as the vendor and receiving bank had two different country codes.
With correct setup, this can be avoided going forward. In the above example, this is solved by specifying the country code Denmark under bank details.
Sweden
Uniconta supports the following payment types for Sweden with the payment format ISO20022_SE.
- Account transfer
- IBAN
- SEPA
- Bank Giro
- Bank Giro with OCR
- Plus Giro
- Plus Giro with OCR
If you use Nordea, the two fields below must be filled in with an ID under bank reconciliation for the current bank account. Read more under bank reconciliation or the section Denmark - Nordea.
Below is a review of BankGiro and PlusGiro. Regular bank transfer and SEPA work as usual.
BankGiro
On the vendor, payment information is specified.
Select payment method 'BankGirot'. If you select Swedish language, the Danish text FIK71 will be replaced with the text BankGirot. That is, FIK71 = BankGirot.
In the field Betalningsidentifikation (payment identification), the BankGiro number is specified.
BankGiro can also have an OCR id specified. It must be specified in the field payment identification (the posting journal) in connection with registration of a vendor invoice.
It can also be specified in the payment proposal, as shown below in the field Betalningsidentifikation (payment identification)![]()
The number of digits for the BankGiro number is validated. It can be 7 or 8 digits.
The OCR number is validated if it is filled in. It can be between 4 and 25 digits and must comply with a Modulus 10 check.
PlusGiro
On the vendor, payment information is specified.
Select payment method 'PlusGirot'. If you select Swedish language, the Danish text FIK75 will be replaced with the text PlusGirot. That is, FIK75 = PlusGirot.
In the field Betalningsidentifikation (payment identification), the PlusGiro bank account number is specified.
Here is an example of two payments to a vendor that uses PlusGiro. One payment is with OCR. ![]()
The number of digits for the PlusGiro number is validated. It can be between 2 and 8 digits.
The OCR number is validated if it is filled in. It can be between 2 and 25 digits and must comply with a Modulus 10 check.
Norway
Uniconta supports the following payment types for Norway with the payment format ISO20022_NO.
- Account transfer
- Account transfer (KID number)
- IBAN
- SEPA
Account transfer with KID number
Note: In general, for a Norwegian company, bank account details are always retrieved from the vendor, as the field payment identification on the payment proposal is reserved for a possible KID number.
The screenshot below is an example from the payment proposal.
KID number is specified in the field 'payment identification'. The vendor bank account (BBAN) is retrieved from vendor base data in connection with the file being generated. Validation will be performed to ensure that the vendor bank account is filled in on the vendor. Validation will also be performed to ensure that the KID number complies with a Modulus 10 check.