Administration

Set up approval workflows: example and checklist

A complete example of three approval policies and the checklist to review before going live.

← Help center

Complete setup example

Priority Policy Conditions Steps Options
1 Urgent payments Urgent vendor batches 1: dynamic, from among the controllers Four-eyes, escalation after 4 h, in-app notification
5 Large amounts ≥ 100,000 Vendor batches and free payments ≥ 100,000, CHF or EUR 1: Treasury, any 1 member of the group — 2: Finance Department, all members Four-eyes, escalation after 48 h, email + in-app, action by email
10 Payments ≥ CHF 10,000 Vendor batches ≥ 10,000 1: Sophie Müller — 2: Marc Dupont Four-eyes, escalation after 24 h

An urgent CHF 250,000 batch is handled by the "Urgent payments" policy (priority 1), even though it exceeds 100,000: it is the first policy that matches. If you want large urgent amounts to go through the Finance Department as well, add a maximum amount to the urgent policy.

Checklist before going live

  • Every payment type in use is covered by at least one policy (or deliberately exempted).
  • Priorities run from the most specific to the most general.
  • Each group has enough members to absorb absences.
  • No single person is the only approver of two consecutive steps.
  • The four-eyes principle is enabled on every policy.
  • Automatic approval is left empty for large amounts. Escalation is still possible: it only moves the request on to the next step.
  • Each policy has been tested with a small batch.

Updated on October 17, 2026

Can’t find your answer? Our support team is here to help.
Contact support