The four eyes principle is an internal control mechanism requiring that high-risk financial transactions, data changes, or strategic decisions be reviewed and authorised by at least two independent people before execution. By mandating a second pair of eyes, businesses prevent unilateral actions that could lead to financial loss, operational disruption, or compliance breaches.
In daily financial operations, this concept is commonly known as dual control or a maker-checker workflow. In operational finance, the objective of the four eyes principle is to involve several people in the life of a single transaction, from initiation to settlement and reporting, to minimise the risk of fraud across accounts teams, treasuries, and leadership.
What is the four eyes principle?
The German phrase Vier-Augen-Prinzip literally translates into English as four eyes principle, operating as a control rule where an action or transaction takes effect only once a second person has independently checked and approved it. In corporate environments, the principle establishes that no single employee should hold unchecked power over sensitive operational or strategic decisions.
In the UK, the four eyes principle informs both corporate governance arrangements and operational financial controls. At the governance level, FCA guidance in SYSC 4.2.4 G clarifies that at least two independent minds should be applied to the formulation and implementation of the policies of a common platform firm. Furthermore, under FCA guidance in SYSC 4.2, where a single individual is particularly dominant in a firm, this will raise doubts about whether SYSC 4.2.2 R is met.
At the operational level, the principle governs everyday transactions within finance teams. Rather than allowing one employee to initiate and disburse funds unilaterally, authority is distributed between a maker who prepares the entry and a checker who verifies it.
How the four eyes principle works
In operational finance, the four eyes principle functions through a structured maker-checker sequence. One team member, the maker, prepares the transaction, compiles documentation, and inputs the entry into the accounting or enterprise resource planning (ERP) system. A second qualified employee, the checker, reviews the underlying details against supporting records before granting final authorisation.
Modern finance software enforces this sequence through system permissions. Role-based access controls physically prevent the person who initiates a transaction from approving it. If a finance assistant inputs a payment, the system removes their ability to execute the release, routing the file to a designated finance manager instead.
For dual control to remain effective, the checker must conduct an authentic review rather than a procedural sign-off. When approvers face heavy workloads, they can succumb to approval fatigue or diffusion of responsibility, assuming the maker has already validated every detail. Effective organisations counteract this by setting explicit verification requirements for reviewers before sign-off is permitted.
Four eyes principle vs segregation of duties
Finance professionals often compare the four eyes principle with segregation of duties, but they address risk from complementary angles. Segregation of duties is a broad organisational framework that separates incompatible responsibilities across different roles, such as separating the creation of vendor records from the execution of disbursements.
By contrast, the four eyes principle focuses on joint participation in a single sensitive task, requiring two distinct individuals to examine and authorise the specific action before it is executed.
A historic example of control failure occurred in the 1995 collapse of Barings Bank. Trader Nick Leeson held dual authority over front-office trading and back-office settlement in Singapore, allowing him to conceal unauthorised trades and £827 million in losses inside error account 88888 without independent verification. This breakdown highlighted the danger of failing to implement independent oversight and dual authorisation.
Key benefits of dual control in financial operations
Mandatory dual sign-offs introduce necessary friction at critical decision points, protecting business capital and strengthening operational integrity.
Preventing corporate fraud and human error
Unchecked authority creates an environment susceptible to internal misconduct and external deception. The ACFE estimates that typical organisations lose roughly 5% of their annual revenue to occupational fraud globally, but organisations with effective anti-fraud controls in place consistently experienced lower losses and faster fraud detection.
Dual verification also protects businesses against external attacks, such as invoice scams and impersonation fraud where criminals spoof payment communications. When a four eyes policy requires checkers to verify bank account amendments via independent communication channels, spoofed payment instructions can be caught before funds leave the company account. Beyond deliberate fraud, secondary review catches routine human errors, such as transposed numbers, incorrect currency selections, and duplicate entries.
Maintaining compliance and robust audit trails
Dual approvals provide indispensable evidence for statutory auditors and regulatory bodies, demonstrating that appropriate checks and balances govern key operations.
When enforced through digital approval software, every decision produces an indelible audit trail. Automated audit logs capture the identity of the maker, the identity of the checker, timestamps for submission and release, and attached invoice evidence. This transparent record simplifies both internal audit evaluations and year-end external reviews.
Common use cases across business and banking
Finance teams deploy maker-checker controls across areas where unilateral errors or tampering carry severe consequences:
- Supplier disbursements: In accounts payable supplier disbursements, internal controls require segregating approval from payment execution so authorising and releasing stay in two different hands, with dual authorisation enforced for batches above a defined threshold during a payment run.
- Vendor master data changes: Modifying supplier bank details presents significant fraud risks. Finance teams often apply dual verification so that proposed alterations to payee sort codes or account numbers require independent validation before records are updated.
- General ledger adjustments: Posting manual journal entries to the general ledger frequently incorporates dual sign-off to ensure significant accounting adjustments are reviewed before entry.
- Credit limit modifications: Adjusting credit facilities or approving spending overrides often involves secondary approval to manage commercial credit exposure.
- Treasury and foreign exchange: Booking large currency hedges or shifting liquid cash reserves between corporate banking entities typically requires dual execution.
Best practices for implementing a four eyes policy
Applying dual control successfully requires balancing risk management against operational speed:
- Define tiered financial thresholds: Requiring dual sign-off on trivial purchases causes administrative gridlock. Apply four-eyes checks based on materiality, such as transactions exceeding £5,000, unbudgeted expenses, or sensitive actions like bank detail amendments.
- Enforce technical boundaries: Never rely on verbal agreements or email threads. Use spend management systems and banking platforms that enforce permissions programmatically, preventing users from approving their own entries.
- Fight approval fatigue: Train approvers on specific inspection criteria so review does not degenerate into a passive rubber stamp. Checkers should confirm that delivery receipts match invoices and that pricing aligns with agreed contracts.
- Require out-of-band validation for bank changes: Never approve supplier payment detail alterations based solely on email attachments. Mandate that staff verify changes by telephoning the vendor on an established, trusted number.
- Monitor audit trails regularly: Review approval records periodically to identify signs of control overrides or suspicious approval pairings between colleagues.