User setup (bank)¶
On Bank → User setup you decide what each user may do with each bank account. The page is for administrators.
The setup covers one account at a time¶
A user's bank access is set up per bank account, within one company. The same user can therefore approve freely from one account, only view a second, and not see a third at all. In another company the user starts again with no access.
Access, mandate and visibility¶
| Setup | What the user can do |
|---|---|
| No setup, or not enabled | The account is not shown at all. |
| Enabled, no mandate | The user can see the account but not approve. |
| Enabled, with a mandate | The user can approve payments from the account. |
A bank user without a mandate is a deliberate setup: it is how you give sight of an account without giving authority over it.
Mandate: A, B or C¶
The letter is not a level. It decides who the user may approve together with, when the company requires two approvers:
| Mandate | May approve together with |
|---|---|
| A | A, B or C |
| B | A or C — not another B |
| C | A or B — not another C |
The requirement for two approvers is switched on under Bank → Settings and applies per company.
Amount limits¶
You can set three limits per user and account:
- Transaction limit
- The largest single payment the user may approve.
- Batch limit
- The largest total in one batch.
- Daily limit
- The most in total in one day. The running count follows the user's own approvals in the company that same day.
An empty limit is unlimited. Exceeding even one limit refuses the approval outright — the batch is not split up.
The bank account itself may also carry a daily limit covering all users together. Each batch counts once towards it, however many people approved it.
Amounts in foreign currency are converted before the limits are checked.
Limits also govern notifications
When a batch is created, only the users who could actually approve it are notified — those with a mandate on the account whose limits cover the batch.
Changes must be confirmed with a one-time code¶
When you create or change a bank user — the mandate, a limit, or whether access is enabled — the change does not take effect immediately. You confirm it with a one-time code sent to your own phone number.
You therefore need a registered phone number for one-time codes yourself. Without one the change is refused and you have to contact an administrator or support.
The code is valid for two minutes and can be entered three times. After that the change is discarded and has to be made again.
Every change is recorded in the log, so it can be documented afterwards who could approve what, and from when.
The user's own signing details¶
To be able to approve, the user also needs a signing PIN and an OTP phone number in the company. If either is missing, the user cannot approve regardless of mandate.