When you set up bank integration for a client, the client often has to do one of the steps themselves – typically approving the bank consent with BankID. For that, the client needs the right permissions in Catacloud. The permissions are split across two modules: some under Administration and some under Bank. Here is how to set it up.
In short
As an accountant, your firm already has access to turn on the integration and add the bank accounts.
The client needs at least Create and update bank accounts under Administration to connect the accounts and approve the bank consent with BankID (ZTL).
The bank consent belongs to the person who approved it. Only that person can renew it later.
Recommended split between accounting firm and client
ZTL
The accounting firm turns on bank integration under Administration → Bank and adds the bank accounts with BIC/SWIFT.
The person with signing authority in the company signs the agreement with ZTL using the link in the email from ZTL.
The client clicks Actions → Set up integration on each bank account and approves the consent at the bank with BankID.
See the full procedure in Setting up bank integration via ZTL.
Aritma
With Aritma, the accounting firm can do the whole setup in Catacloud – both turning on the integration and connecting the accounts. The client completes the agreement in their online bank, outside Catacloud, so they need no extra permissions for the setup itself. See Setting up bank integration via Aritma.
Which permission is needed for what?
Connect a bank account and approve the bank consent (ZTL): under Administration, Create and update bank accounts. Without it, the Actions menu is not shown on the bank accounts.
Turn on the bank integration itself: under Administration, Add extra billable services. Bank integration is a paid service, so many accounting firms choose to do this step themselves.
Bank reconciliation: under Bank, Create and update bank reconciliations.
Approve payments: under Bank, Approve and process bank payments. See also Sending a payment to the bank.
When you tick a permission, Catacloud automatically turns on the permissions it depends on. For example, Add extra billable services also turns on Update organization data and settings, and Create and update bank reconciliations also turns on read access to bank statements and accounting.
How to give the client the permissions
Go to Administration → User access → Permissions on the client.
Click New access group and give the group a name, for example "Bank setup".
On the Access tab: click Show all … sub permissions under Administration and tick Create and update bank accounts. Do the same under Bank for the permissions the client should have there.
On the Members tab, tick the client's user.
Click Create group.
If the client is already in an access group, you can add the permissions to that group instead and click Save changes.
Note: A user with the Member role who is not in any access group cannot open Administration at all – and so cannot see the bank accounts there. The client must be in an access group with the permissions above, or have the Administrator role. Read more in Access control and user permissions in Catacloud.
The bank consent belongs to the person who approved it (ZTL)
A bank consent is tied to the person who approved it with BankID. Only that person sees the Renew consent button and can renew the consent. This means:
The client must renew the consent themselves when it expires – the accounting firm cannot do it on the client's behalf.
Do not remove the client's permissions after the setup. They will need them again to renew.
If the person who approved the consent leaves, someone else must reconnect the account: Actions → Disconnect on the bank account, then Actions → Set up integration with their own BankID.
See also Bank consent: create, delete and renew.
When should you contact us?
The client has the permissions above but still does not see Actions → Set up integration on the bank account.
You get an error message when the client tries to renew a consent.
Please include the client, the user's name and email, and what happens (a screenshot helps).