four-eyes

Four-eyes principle for payments: a checklist for Swiss finance teams

AA
Aurum Avis Labs Author
7 min read

Four-eyes principle for payments: what finance should enforce

The four-eyes principle for payments means no outbound transfer or master-data change is released by one person alone. In a Swiss SME with 20 to 250 staff, finance is often two or three people; the rule still applies through written thresholds, role separation, and a second signature in the bank tool or ERP. BACS lists clear payment processes among the controls against business email compromise, alongside phone verification and staff awareness. It does not replace calling a supplier when the IBAN changes; that playbook sits in our article on invoice fraud with a changed IBAN. Here the focus is who may prepare, who may approve, and what you log when someone tries to skip the second pair of eyes.

If you are tightening controls after a near-miss, pair this checklist with how staff report phishing in Switzerland so odd payment requests reach IT early.

  • Define amount thresholds that always need a second approver
  • Separate “prepare payment” from “release payment” in the bank or ERP
  • Block master-data IBAN changes without a second role
  • Keep an out-of-band callback rule for any new beneficiary
  • Log exceptions with name, time, and reason

What “four eyes” means in practice

Preparation and approval must be two different people for payments above your threshold. The preparer uploads invoices, matches PO numbers, and schedules the batch. The approver sees the same totals and beneficiary list but did not build the batch alone. In e-banking, that may mean four-eyes signing, dual authorisation, or a second login. In ERP, it may mean workflow states. The names differ; the idea is unchanged.

A made-up example: a services firm with 45 staff sets CHF 5’000 as the line where a second approver is mandatory. The accountant prepares a CHF 12’000 run every Friday. The managing director approves in the bank app after scanning beneficiaries, not only the total. When a “new supplier” line appears, both pause and use the verification path in the IBAN article before releasing.

Thresholds and what belongs inside four-eyes

Set thresholds in writing. Common choices: all payments above a fixed franc amount, all first-time beneficiaries, all changes to supplier bank details, and all payroll files above a headcount cutoff. Below the threshold, some firms allow one person for petty cash or small recurring rent, but document that exception so auditors know it is intentional, not a gap.

Usually inside four-eyes

  • Supplier payments above your CHF limit
  • New IBAN or new beneficiary
  • Manual overrides of duplicate warnings

Often outside, if documented

  • Small recurring items with fixed beneficiaries
  • Petty cash replenishment under a low cap
  • Card payments with separate merchant controls

Who can be the second pair of eyes

The approver should not report to the preparer on the same payment line without oversight. In tiny teams, the owner approves what the bookkeeper prepared; that is acceptable if the owner actually reads beneficiaries. Avoid “I approve my own batch” by sharing one e-banking user. Shared logins destroy four-eyes and complicate incident response.

When the usual approver travels, name a deputy in advance. “Anyone with access” is not a policy. HR and the management assistant need to know that urgent CEO messages do not replace the approver role, which overlaps with CEO fraud training.

Write the rule on one page

Finance, the owner, and IT should share a single page, not a thread in someone’s inbox. State the franc threshold, name the roles (preparer and approver), list what always needs both people, and point to where master data is changed. Add the date the bank or ERP settings were last checked. When a new hire gets e-banking rights, they read that page before their first payment run.

If invoice capture is already structured in ERP, a separate invoice approval workflow can reduce retyping on the process side. Security still needs a human approver who compares beneficiaries to master data before release.

Turn on dual control in the bank and ERP

Product names differ; the pattern is the same. One identity prepares, another releases, and the tool refuses a single step for amounts above your limit.

  1. Map current rights

    List who can create payments, who can sign, and who can edit supplier bank details today.

  2. Enable dual signing

    In e-banking, switch on four-eyes or dual authorisation for outbound payments above your threshold.

  3. Lock master data

    Require a second role for IBAN and beneficiary changes in ERP or master-data screens.

  4. Test with a small payment

    Run a low-franc batch through prepare and release before you raise limits on live suppliers.

  5. Remove combined rights

    After role changes, check that no one still holds both preparer and releaser on the same account.

Master-data changes use the same second person

A changed IBAN in master data is as sensitive as a large payment. If one person can edit the account number and release the next run, four-eyes on the payment alone is hollow. Pair master-data edits with the same approver role you use for high-value batches, or block edits until a second login confirms.

When master data and the invoice disagree, stop the batch and follow verification in the IBAN fraud article. Four-eyes catches “two people signed”; it does not replace the callback to the supplier.

What four-eyes is not

It is not a full segregation-of-duties audit for a listed group. It is not a substitute for verifying bank details by phone. It is not automatic in every Swiss bank product; you must enable dual signing or workflow. It also does not stop an insider who controls both roles unless someone else reviews logs.

When someone tries to bypass the rule

Treat urgency as a stop signal. If a message says “skip approver today”, hold the payment and use your internal incident reporting path. Document the attempt even when no money moved. Insurance and later audits ask whether controls were live or only on paper.

  • CEO mail asks to pay today

    Hold the batch. The approver calls the CEO on a known number. No release from the email alone.

  • Supplier thread says new IBAN

    Do not release until master data matches a verified account. Four-eyes does not skip the callback.

  • ”Only this once” on a Friday run

    Log the exception with amount, beneficiary, and who gave verbal OK. “Only once” without a log becomes the new normal.

  • Logging exceptions without eroding the rule

    When the owner approves an urgent run while the deputy is away, record amount, beneficiary, reason, and who performed the out-of-band check. Store the log where finance and audit can find it, not in a private chat. Review exceptions each quarter. If the same name appears every month, the threshold or the deputy rule needs a fix, not another verbal waiver.

    Rolling the rule out without blocking payroll

    Start with the bank: enable dual authorisation, test a small payment, then raise thresholds gradually. Train approvers to open beneficiary lists, not only totals. Review once a quarter whether anyone still has both preparer and releaser rights after role changes. Run payroll on the new rule only after a dry run with a test file, so a signing error does not stop salaries on the live date.

    Does Swiss law require four-eyes for every company?

    There is no single federal rule that every SME must use dual signing. Contract, insurance, and sector expectations push many firms to adopt it. BACS guidance treats clear payment processes as a core BEC control.

    Can the same person prepare and approve small amounts?

    Many firms allow that below a written threshold for recurring rent or petty cash. Document the exception. Everything above the line stays two people.

    Where awareness training fits

    Finance, assistants, and owners often sit in the same live session on payment fraud, phishing, and stop rules. The Aurum format includes a prep look at your situation, a one to two hour session, and a follow-up conversation a few weeks later, remote or on site in Switzerland. Details are on the security awareness training page.

    four-eyes payments finance controls switzerland
    AA

    Written by

    Aurum Avis Labs

    Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

    Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

    Essential Cookies

    Required for basic website functionality, security, user authentication, and error tracking.

    Always active

    Analytics Cookies

    Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

    Marketing Cookies

    Used to track visitors across websites to display relevant and engaging advertisements.