Prerequisites
To send a payment to the bank from Catacloud:
The voucher must be attested and posted, if the Await voucher approval setting is on. If the setting is off, the payment can be sent even if the voucher has not been fully attested
You must have the correct access to the payment module
The bank integration must be set up and active
The bank consent (BankID authorisation) must be valid – you will receive a notification if it has expired
Overview of the payment list
Go to Bank → Payments in the left menu. The payment list is divided into five tabs:
For approval – payments that are ready or waiting for attestation
Bank processing – payments that have been sent and are being processed
Rejected – payments rejected by the bank
Paid – completed payments
All – full overview regardless of status
In the top right corner you will find the toggle Only ready for signing. When it is turned on, payments waiting for attestation of the payment itself, or whose attestation has been declined, are hidden. If the Await voucher approval setting is on, payments whose voucher has not been attested and posted yet are hidden too. You then only see those that can actually be sent to the bank right now.» Useful when you have many payments and want to work efficiently.
The screenshots show the app in Norwegian.
Payment statuses in «For approval»
A payment can have these states in this tab:
For approval (with checkmark ✓) – the voucher is attested and the payment is ready to be sent to the bank.
For approval – Awaiting approval of voucher attestation – – the payment has been sent for attestation but not yet approved. It cannot be sent to the bank until the attestation is approved, and it disappears from the view if you turn on «Only ready for signing».
For approval – The voucher must be posted before the payment can be signed – the voucher is still in the voucher inbox or saved as a draft, and the Await voucher approval setting is on. The payment cannot be selected until the voucher is posted. It also disappears from the view when «Only ready for signing» is on.
For approval – The voucher must be attested and posted before the payment can be signed – shown instead of «Awaiting approval of voucher attestation» when Await voucher approval is on.
For approval – with a green and grey bar underneath – the bank agreement requires more than one signature for the payment, and someone has already signed. Each part of the bar is one signature: green is signed, grey is still missing. Hover over the bar to see who has signed (Signed) and who it is waiting for (Pending). Once everyone has signed, the payment goes on to the bank. See also Two signatures – bank agreement or Catacloud attestation? further down.
How to send a payment to the bank
Go to Bank → Payments in the left menu.
Select the payments you want to send. Only payments with a checkmark ✓ can be selected – those without a checkmark are waiting for the voucher to be attested or posted.
Check the amount, account and payment date.
Click Confirm payments.
Confirm with BankID when prompted.
The payment has now been sent to the bank for processing. The status updates automatically.
The payment is past its due date
A payment that is past its due date can still be approved and sent to the bank. Catacloud then sends it with today's date as the payment date. So a passed due date is not the reason a payment cannot be approved.
If you want a different payment date, change the payment before you approve it. See Changing or deleting a payment – before and after it has been sent to the bank.
Note: Payroll payments must have a payment date that is today or later, and that is a business day.
Two signatures – bank agreement or Catacloud attestation?
Some companies require two people to approve a payment. It is important to distinguish between two things that are often confused: BankID signing and attestation.
BankID signing – bank agreement with 2 signatures
The bank's requirement for 2 signatures is set up in the bank agreement – not in Catacloud. Two authorised persons must sign with BankID for the payment to be processed. You do not need to activate anything extra in Catacloud for this.
With bank integration: Catacloud acts as the signing portal. The first signing is done in Catacloud. The second can be done in Catacloud or directly in the online bank – if it is signed in the online bank, the payment is updated in Catacloud at the next payment status sync. Exception: customers with Danske Bank via ZTL must currently complete the second approval in the online bank. See Second signature in the online bank – how it works with bank integration.
Note: Once all required signings have been completed in Catacloud and the payment has been forwarded to the bank for processing, further signings in Catacloud are not possible. Any further processing then takes place in the online bank.
Has your bank changed the number of signatures?
The number of signatures is set in your bank agreement, and Catacloud follows the bank's setup when a payment is sent. You do not need to change anything in Catacloud. The change applies to new payments.
Payments that have already been rejected cannot be changed or resent:
First check in your online bank that the payment did not go through, so you don't pay twice.
Delete the payment under Bank → Payments → Rejected.
Enter the payment again and send it to the bank.
Attestation of payments in Catacloud
Attestation is a separate internal approval control in Catacloud – completely independent of the bank's signing requirements. It takes place before the BankID signing and can be used whether the bank requires 1 or 2 signatures. It is activated under Administration → Module settings → Bank.
Note: BankID signing and attestation are two different things. Attestation is an internal pre-approval in Catacloud. BankID signing is the actual authorisation that sends the payment to the bank.
It is possible to combine both – then both internal attestation in Catacloud and BankID signing are required.
See the article Setting up attestation of vouchers and payments to activate and configure attestation in Catacloud.
«You must renew your consent with the bank»
The bank consent expires regularly and must be renewed. Here's how:
You will see a message that the consent must be renewed when you try to approve or send a payment.
Click the link in the message, or go to Administration → Module settings → Bank and scroll down to the Consents section.
Log in with BankID using the same login ID as when you log in to the company's online bank.
The consent is now renewed and the payment can be processed.
Note: If you have already tried to renew and still get the message, try starting a new payment – in some cases this triggers the renewal process again.
When should you contact us?
Contact support and provide:
Name of the company
Which voucher or amount it concerns
Which bank is connected
Exact error message (screenshot)