Sharing authentication between banks and companies
An authentication is a certificate or token used to authenticate direct communication with a bank. Instead of authenticating separately for every bank account, bank, or company, you can share an existing authentication so that it's reused. This article describes the scenarios in which sharing applies, and the requirements that must be met before an authentication can be shared. For the steps to share an authentication, see Managing tokens and certificates.
Sharing scenarios
Sharing an authentication can apply in different scenarios:
Between two banks in the same company - this typically applies when the same connection is used for two bank accounts registered under different bank codes in the same branch structure, for example Sydbank and Sydbank Flensburg.
Across companies, to the same bank code - the bank code set up in the target company matches the bank code where the authentication was originally set up. For some Danish banks, all bank accounts are coupled to one connection, so once the connection is set up, you can share the authentication across companies without selecting a bank code.
Across companies, to a different bank code - the target company uses a different bank code than the company where the authentication was originally set up. In this scenario, you must select the correct bank code that the shared authentication should be connected to in the target company.
If you don't have the option to share the authentication, this is most likely due to limitations in the bank setup.
Whether an authentication can be shared
Not every bank connection allows sharing. Whether sharing is possible depends on what the bank ties the authentication to:
- Connections that authenticate per organization number, such as TietoEvry, can't share a certificate. The certificate is bound to a single organization, so it can't be reused for another company or bank code.
- Connections that authenticate per division number, or that cover multiple companies under the same agreement, such as DNB, can share a certificate, because the agreement itself is designed to cover more than one company or division.
When you run the assisted Bank Account Setup guide and a matching connection already exists in another company, the guide only offers to share the authentication if the bank's connection type supports it. If sharing isn't supported, the guide proceeds with a new authentication for the bank account you're setting up.
Fields copied when sharing
When an authentication is shared, the following information is copied from the company where the connection is already set up to the company that uses it: relevant fields on the bank, the bank system active map, and the bank account communication setup.
After sharing, review these fields in the target company to confirm they match your setup, particularly if the target company uses a different bank code than the source company.
Important
You can only share certificates between companies within the same database. For multiple databases, each must have its own unique certificate. Sharing the same certificate across databases can lead to data conflicts, operational issues, and potential data loss.