• Business

The four-eyes principle: definition, examples, limits

The four-eyes principle: definition, examples, limits

Two people instead of one: at first that sounds like twice the work. In fact the four-eyes principle is the simplest control there is — and in most loss cases the one that was missing.

What the principle requires

The rule is short: an important decision is not taken, released and carried out by one person alone. A second person looks at the same case and confirms it.

Behind it sit two risks that are often conflated:

  • Error: a mistyped figure, a service that was never delivered, an invoice that arrives twice.
  • Abuse: someone creates a fictitious supplier and transfers money to themselves.

The same measure helps against both. The second person finds the error. The abuse they prevent simply by existing.

Where it is mandatory — and where it is not

For most small and medium-sized companies there is no explicit duty. The principle becomes binding where supervisory law requires an internal control system: banks, insurers, fund managers.

That does not make it irrelevant for everyone else. Two things create pressure:

  • The auditor assesses the internal control system. Where material amounts pass without any separation, that is a finding.
  • Fidelity insurance asks after a loss which controls were in place. A payment one person could trigger alone is a poor start.

Four eyes and separation of duties are not the same thing

The two terms are often used interchangeably, but they work on different levels:

  • Four-eyes principle: the individual case. Two people look at the same decision.
  • Separation of duties: the organisation. Whoever captures invoices does not run the bank. Whoever maintains master data does not release payments.
  • Signing authority rule: the principle in numbers. Who signs alone up to which amount, and from where two signatures are needed.

The most dangerous gap is not a missing second signature. It is a person who may both change master data and pay. Then the second signature helps little — it is looking at a case that appears correct.

Three examples from mid-sized companies

Invoice approval. The classic case. One person brings the invoice into the system, a second checks the service, and above a set amount a third agreement is needed. How that works with thresholds and policies is on the page about invoice approval.

Payment release at the bank. Two authorised signatories release the payment run. Most companies already have a separation here — but it only bites at the very end, long after the check should have happened.

Changes to master data. The most often overlooked point. When a supplier’s bank details change, someone who did not make the change should confirm it. This is exactly where fraud by forged email takes aim.

From principle to a rule that holds.

In COMMITLY the separation does not live in a habit but in a policy: the label picks the approval route, the amount picks the step — and every sign-off is recorded with person and timestamp.

Try it free now! More on invoice approval >

Where it breaks down in practice

Agreeing the principle is quick. Whether it holds is decided in three places:

  • Holiday and illness. If the second signature is missing for two weeks, it gets bypassed — not out of bad faith, but because invoices fall due. Cover arrangements belong in the rule, not in a footnote.
  • Small teams. With three people there is no clean separation. The honest answer: bound the principle rather than claim it. Set thresholds so that only relevant amounts need two approvals — the second stays with management.
  • The quiet exception. Direct debits, PayPal, charges from advertising accounts: the money is gone before anyone could agree. Those documents still go through the check — after the fact, with the same record. With company cards that can be moved up front: the approval is the card itself, with a limit and an owner — the receipt reaches the system as a photo.

What belongs in writing

A principle that exists only in people’s heads is not there when it is examined. Three things belong in a written rule:

  1. Who approves what — alone up to which amount, jointly from where.
  2. Who covers for whom during absence, and for how long.
  3. Which exceptions exist and how they are checked afterwards.

Anyone who maps approvals in software gets the evidence along the way: every sign-off is recorded with person and timestamp and can be shown years later. A “fine by me” in passing cannot.

Frequently asked questions

What does the four-eyes principle mean?

An important decision is not taken and carried out by one person alone — a second person checks and confirms it. The name comes from the two pairs of eyes looking at the same case.

Is the four-eyes principle required by law?

For most small and medium-sized companies, no. It is mandatory in regulated sectors such as banks and insurers. Still, auditors and insurers expect a separation for larger amounts — and many companies adopt one voluntarily.

What is the difference between the four-eyes principle and separation of duties?

The four-eyes principle applies to the individual case: two people look at the same decision. Separation of duties applies to the organisation: whoever captures invoices does not run the bank; whoever maintains master data does not release payments.

How do you apply the four-eyes principle to invoices?

In three steps: capture, check, approve. Whoever brings the invoice into the system does not check it alone; whoever checks it does not release it alone. Add a threshold — small amounts pass through one person, larger ones through two.

Does the four-eyes principle work in small teams?

With limits. With three people there is no complete separation. The usual answer: set thresholds so that only relevant amounts need two approvals, and keep the second with management. What matters is writing it down — a deliberate exception is still a rule.

From principle to practice

The principle is quickly agreed — the question is where it sits in daily work. COMMITLY Bills turns approvals into a rule, with value thresholds and a documented sign-off.