Transaction Limits
Transaction Limits let you set a maximum transaction value per role. A user on a capped role cannot approve, reject or confirm a transaction above that value; someone with a higher limit (or no limit) must handle it.
Key points:
Each role can have one limit, in one currency, converted with one FX rate template.
A limit is enforced only when its status is Active. Activation always needs a second person (four-eyes rule).
Roles without an Active limit work exactly as before. The feature is additive.
A limit controls whether a user can complete a step, not how many approvals the step needs. Maker-checker counts are unchanged.
Deal setup and deal approvals are not affected.
Before you start
Anyone can view limits; only users with the Transaction Limits Maker or Checker capability can change them. No existing role has either capability after release, so an administrator must grant them first.
Where to find it:
My Organisation → Transaction Limits (below User Management).
Every Portal Admin, Funder and Customer user sees the page and their own company's limits.
Permissions
Permission | What it allows |
|---|---|
None | View limits (eye icon) |
Transaction Limits – Maker | Add, edit and delete Inactive limits; request activation; withdraw a pending request; deactivate an Active limit |
Transaction Limits – Checker | Activate (approve) or reject a pending request; deactivate an Active limit |
Nobody can act on a limit for their own role. So, to cap a role and activate the limit, you need:
The capped role – the users who perform the stage actions.
A Transaction Limit Maker permission in a second role – creates the limit and requests activation.
A Transaction Limit Checker permission in a third role – activates it. The Checker must be a different person from the requester.