Financial controls are the foundation on which a reliable finance function is built, and yet they are one of the most misunderstood areas of the controlling role. Done well, controls protect the business from error and fraud, ensure the financial information is reliable, and do so without imposing a bureaucratic burden that slows the business down. Done badly, they become either a box-ticking exercise that provides the appearance of control without the substance, or an oppressive layer of process that frustrates everyone while still failing to prevent the things that matter. Designing controls that actually work — that genuinely manage risk without strangling the business — is one of the most valuable skills a Financial Controller can have, and the role takes its name from it.
This guide is written for Financial Controllers who want to design and run a control environment that is genuinely effective rather than merely present. It covers what financial controls are actually for, the difference between controls that work and controls that exist on paper, how to design controls proportionate to the risks they address, the practical balance between control and efficiency, and how to build a control environment that holds up as the business grows and changes. The aim is controls that a Financial Controller can stand behind because they genuinely do their job, not controls that exist to satisfy a checklist while the real risks go unaddressed.
The stakes have also risen. The corporate offence of failure to prevent fraud came into force on 1 September 2025 for large organisations, and the UK Corporate Governance Code now asks boards of companies that apply it to declare whether their material controls were effective, for financial years beginning on or after 1 January 2026. Both are covered later in this guide, along with a worked control matrix and a practical approach to segregation of duties in small teams. For the broader picture in smaller businesses, see our companion guide to internal controls for growing businesses.
What Financial Controls Are Actually For
The purpose of financial controls is to manage the risks to the integrity of the business’s finances — the risk of error, the risk of fraud, the risk of unreliable financial information, the risk of assets being lost or misused. Every control should exist to address a specific risk, and the test of whether a control is worth having is whether it genuinely reduces a risk that matters. This risk-based view is the foundation of good control design, because it focuses attention on the controls that matter and avoids the proliferation of controls that address trivial risks while consuming effort that could go to the significant ones.
The common failure is to design controls without reference to the risks they are supposed to address — to impose process for its own sake, or because a checklist or a template says it should be there, rather than because it manages a genuine risk. This produces control environments that are simultaneously over-controlled and under-controlled: heavy with procedures that address minor risks, light on the controls that would prevent the significant ones. The Financial Controller who designs from the risks — identifying what could actually go wrong, how badly, and how likely, then designing controls proportionate to those risks — produces a control environment that genuinely protects the business. This risk-first discipline is what separates real control design from the box-ticking that passes for it in many organisations.
A practical way to start is a simple risk register for the finance processes: list each process (purchase-to-pay, order-to-cash, payroll, treasury, the close, journals, system access), write down what could go wrong in each, and score each risk for likelihood and impact on a three- or five-point scale. The high-scoring risks are where control design effort goes first. Auditors think in terms of financial statement assertions — completeness, existence, accuracy, cut-off, valuation — and mapping each risk to the assertion it threatens makes later conversations with the audit team much easier.
Controls That Work Versus Controls on Paper
There is a profound difference between a control that exists on paper and a control that actually operates, and a great deal of apparent control is illusory. A control that is documented in a procedure but not actually performed, or performed mechanically without genuine attention, or easily circumvented when inconvenient, provides the appearance of control without the substance. The reconciliation that is signed off without being properly done, the authorisation that is given without genuine scrutiny, the segregation of duties that is bypassed when someone is on holiday — these are controls in name only, and they are dangerous precisely because they create false confidence.
Designing controls that actually work means designing controls that will genuinely be performed, properly, in the real conditions of the business. This requires controls that are practical enough to be followed consistently rather than so burdensome that they are skipped under pressure, clear enough that the people performing them understand what they are actually checking for, and embedded in the workflow rather than bolted on as an afterthought. It also requires the Financial Controller to verify that controls are operating as intended rather than assuming they are — to check that the reconciliations are genuinely done, that the authorisations are genuinely scrutinised, that the controls are real rather than nominal. A control environment is only as good as the controls that actually operate, and ensuring they operate is as important as designing them in the first place.
A useful test for any control is to ask four questions: what precisely is the reviewer looking for; what threshold triggers a follow-up; what evidence is left behind; and what happens when the reviewer is away. A control that cannot answer all four is likely to be a control on paper. “Bank reconciliation reviewed monthly” is weak; “Finance Manager reviews the bank reconciliation by working day 3, investigates any reconciling item over £1,000 or older than 30 days, and signs the reconciliation in the system; the Financial Controller covers absences” is a control that can be tested.
Proportionality: Matching Controls to Risks
The art of control design is proportionality — matching the strength of the control to the significance of the risk. A high-value, high-risk process warrants strong controls; a low-value, low-risk process does not, and imposing heavy controls on it wastes effort and frustrates the business for no real benefit. The Financial Controller who calibrates controls to risks — concentrating control effort where the risks are significant and keeping it light where they are not — produces a control environment that is both effective and efficient. This proportionality is what allows controls to manage risk without becoming the bureaucratic burden that gives controls a bad name.
Getting proportionality right requires genuine judgement about risk, which is exactly what a qualified, experienced Financial Controller brings. It means understanding which processes carry the real exposure — the payments process, the areas where assets could be misappropriated, the judgements that materially affect the numbers — and ensuring those are properly controlled, while not imposing the same intensity of control on areas where little can go wrong. The Financial Controller who applies this judgement avoids both of the failure modes: the over-controlled environment that frustrates the business and the under-controlled one that leaves the real risks exposed. The goal is controls that are exactly as strong as the risks require, no more and no less.
Tiered authority limits are the simplest expression of proportionality. A purchase order under a low threshold might need only a budget holder’s approval; above it, a second approver; above a higher threshold, the Finance Director or CEO. The same tiering applies to journals (a materiality threshold above which a second reviewer is required), credit notes and write-offs. Setting the thresholds is a judgement call: too low and the approvers rubber-stamp; too high and real exposure slips through.
The Balance Between Control and Efficiency
Controls and efficiency are often presented as being in tension, and badly-designed controls genuinely are — they slow the business down, add friction to every process, and frustrate the people subject to them. But well-designed controls need not impose this cost. The best controls manage risk while fitting naturally into the workflow, so that they protect the business without materially slowing it. The Financial Controller’s skill is in designing controls this way — finding the control that addresses the risk with the least friction, embedding it in the process rather than adding it as a separate step, automating it where automation is possible.
This matters because controls that impose too much friction tend to be circumvented, which defeats their purpose. A control that makes a process so cumbersome that people find ways around it is worse than no control, because it creates false confidence while not actually operating. The Financial Controller who designs controls that people can and will actually follow — because they are proportionate, practical and embedded — gets genuine control; the one who imposes heavy controls that people resist and circumvent gets the appearance of control and the reality of evasion. Automation increasingly helps here, allowing controls to operate within the system without manual friction, a theme explored further in our guide on how a Financial Controller uses AI and the controls considerations that come with it.
Examples of low-friction, automated controls include three-way matching of purchase order, goods received note and invoice in the purchase ledger; system-enforced approval workflows; duplicate invoice detection; automated bank matching; and role-based access that prevents the same user creating a supplier and approving a payment to it. Where AI tools are used in the close or reconciliations, the review step needs designing as carefully as the automation — see our guides to human-in-the-loop AI controls and AI for reconciliations.
Key Control Areas Every FC Should Get Right
While the specific controls depend on the business, certain areas warrant attention in almost every organisation. The payments process is the most obvious, because it is where money leaves the business and where the risk of both error and fraud is highest; proper authorisation, segregation of duties between those who set up payments and those who approve them, and verification of payment details are foundational. The reconciliation of key accounts is another, because reconciliations are the control that catches errors and discrepancies before they flow through to the numbers. The authorisation framework — who can commit the business to what, and how that is enforced — is a third.
Segregation of duties runs through all of these: the principle that no single person should control a process end to end in a way that would allow them to commit and conceal an error or fraud. In smaller businesses, where the finance team is too small for full segregation, the Financial Controller must find compensating controls — the review, the oversight, the verification that mitigates the risk that limited segregation creates. Getting these foundational areas right — payments, reconciliations, authorisation, segregation — addresses the risks that matter most in most businesses, and a Financial Controller who has these genuinely under control has the core of the control environment in place. The detail varies, but these fundamentals are close to universal.
Two further areas deserve a place on every list. Supplier master data: changes to supplier bank details are the route for most invoice-redirection fraud, so any change should be verified by calling the supplier on a number already held (not one on the request), approved by someone other than the person who keyed it, and reported weekly. Manual journals: journals are how numbers are adjusted outside the normal processes, so post-close and large journals should be reviewed by someone other than the preparer, and a periodic report of journals posted by senior staff, at unusual times or to unusual accounts is a cheap and effective detective control.
Segregation of duties in a small finance team
Most SMEs cannot fully segregate duties with two or three people in finance, so the design question is which incompatible duties to separate and how to compensate for the rest. The duties that matter most to keep apart are: setting up or amending suppliers and employees; processing invoices or payroll; releasing payments; and reconciling the bank. Practical approaches include:
- Making the managing director or owner the second authoriser on the banking platform for every payment run, with the supporting list attached — dual authorisation is often the single most valuable control in a small business.
- Having bank statements reviewed by someone who does not process payments, even if that is the owner looking at the statement monthly and initialling it.
- Restricting system permissions so that the person who amends supplier bank details cannot also approve payments, and reviewing the change log.
- Using an outsourced payroll bureau or an external accountant to provide independent review of payroll changes and month-end reconciliations.
- Requiring mandatory holiday, so that a process cannot be run continuously by one person without anyone else seeing it.
A part-time or fractional Financial Controller can provide exactly this independent oversight in a business that is not yet ready for a full-time hire; see our pages on fractional Financial Controllers and hiring a Financial Controller for an SME.
Controls That Scale With the Business
A control environment is not designed once and fixed; it must evolve as the business grows and changes. The controls appropriate to a small business are not the same as those appropriate to a larger one, and a control environment that was adequate at one stage can become inadequate as the business grows in size and complexity. The Financial Controller should periodically reassess whether the controls still match the business — whether new risks have emerged that are not controlled, whether the growth of the business has outstripped controls designed for a smaller operation, whether changes in how the business operates have created gaps.
This evolution is particularly important through periods of growth, where the business can outgrow its controls faster than anyone notices. A finance function that was small enough for informal oversight becomes too large for it; processes that were simple become complex; the volume of transactions outstrips manual controls. The Financial Controller who anticipates this — who strengthens the control environment ahead of the growth rather than after a problem reveals the gap — keeps the business protected as it scales. This forward-looking maintenance of the control environment is part of what distinguishes a Financial Controller who genuinely owns controls from one who treats them as a static checklist, and it is increasingly valued as businesses grow and the consequences of weak controls grow with them. A strong, scalable control environment is also exactly what stands a business in good stead when it faces external scrutiny, whether the annual audit or the due diligence of a transaction.
Common trigger points for a controls review are: crossing the audit threshold for the first time; private equity investment, which usually brings a lender covenant pack and an investor expectation of monthly reporting; an acquisition that adds entities and intercompany; a new ERP or finance system; and opening an overseas subsidiary. Each changes the risk profile, and each is a natural moment to re-run the risk register. Our guides on Financial Controllers for PE-backed companies and implementing a finance system as an FC cover two of the most common.
Preventive and Detective Controls
A useful distinction in control design is between preventive controls, which stop something going wrong before it happens, and detective controls, which catch it after it has happened. Both have their place, and a well-designed control environment uses each appropriately. Preventive controls — authorisation before a payment is made, segregation that prevents one person controlling a process end to end — are powerful because they stop the problem occurring at all, but they cannot catch everything. Detective controls — the reconciliation that finds the error, the review that spots the anomaly — provide the backstop that catches what the preventive controls miss.
The Financial Controller designing a control environment should think consciously about this balance, ensuring that significant risks are addressed by preventive controls where possible and backed by detective controls that would catch a failure. Relying entirely on detective controls means accepting that problems will occur and merely catching them afterward, which is weaker than preventing them; relying entirely on preventive controls means having no backstop when they fail, which is dangerous because no preventive control is perfect. The combination — prevent where you can, detect what gets through — provides the layered protection that a robust control environment requires. Understanding which type of control addresses which risk, and combining them deliberately, is part of the craft of control design.
| Risk | Preventive control | Detective control |
|---|---|---|
| Payment to a fraudulent bank account | Call-back verification of bank detail changes; dual authorisation of payment runs | Weekly report of supplier master data changes reviewed by FC |
| Duplicate supplier invoice paid | System duplicate check on supplier, reference and amount | Supplier statement reconciliations for key suppliers |
| Payroll ghost employee | New starters approved by HR and line manager before set-up | Monthly headcount and payroll variance review against HR records |
| Revenue recorded in the wrong period | Invoicing linked to dispatch or delivery evidence | Cut-off testing and margin analysis at month end |
| Inappropriate manual journal | Journals above a threshold require second approval | Review of journals by senior users, at weekends or to unusual accounts |
Fraud Risk and the Control Environment
Among the risks that controls address, fraud deserves particular attention, because it is deliberate, concealed, and often perpetrated by exactly the people the controls are supposed to rely on. Fraud controls differ from error controls in that they must withstand someone actively trying to circumvent them, which raises the bar for their design. Segregation of duties is the foundational fraud control, because it ensures that committing a fraud would require collusion rather than the action of a single person; where segregation is impossible, as in a small finance team, compensating controls such as independent review and oversight become essential.
The Financial Controller should think specifically about where the business is exposed to fraud — the payments process above all, but also areas like expenses, payroll, and anywhere assets could be diverted — and ensure those areas have controls designed to deter and detect deliberate wrongdoing. This is not about assuming bad faith in colleagues, but about recognising that a control environment which only protects against honest mistakes leaves the business exposed to the dishonest. A Financial Controller who has thought about fraud risk and built controls that would catch or prevent it is protecting the business against one of the most damaging things that can happen to it, and doing so is a core part of what genuine financial control means. The strongest control environments are those designed with both honest error and deliberate fraud in mind.
The failure to prevent fraud offence
The Economic Crime and Corporate Transparency Act 2023 (section 199) created a corporate offence of failure to prevent fraud, which came into force on 1 September 2025. It applies to large organisations — those meeting at least two of more than 250 employees, more than £36m turnover and more than £18m total assets in the financial year before the fraud, measured across the organisation including its subsidiaries. An organisation can be prosecuted where an employee, agent, subsidiary or other associated person commits a specified fraud intending to benefit the organisation (or its clients), and it is not necessary to show that senior managers knew about it.
The defence is to show that the organisation had reasonable fraud prevention procedures in place (or that it was reasonable not to have them). The Home Office’s statutory guidance sets out six principles: top-level commitment, risk assessment, proportionate risk-based prevention procedures, due diligence, communication and training, and monitoring and review. Note the different emphasis: this offence is aimed at fraud committed for the business — for example, false accounting to meet a covenant, mis-selling, or misleading investors — rather than fraud against it. For the Financial Controller, that puts the spotlight on revenue recognition, provisions, management overrides and the pressure points created by targets and bonuses. Smaller businesses are outside the offence, but the same principles are a sensible benchmark, and large customers increasingly ask suppliers about them.
Documenting and Testing the Control Environment
A control environment that exists only in the Financial Controller’s head is fragile, and documenting the controls — what they are, who performs them, what risk each addresses, how they operate — is part of building one that endures. Documentation matters not as bureaucracy for its own sake but because it makes the control environment explicit, allows it to be reviewed and tested, survives the departure of the people who designed it, and provides the evidence that auditors and others increasingly expect. A documented control environment can be assessed, improved and relied upon in a way that an informal, undocumented one cannot.
Equally important is testing that the controls actually operate as intended, rather than assuming they do. A Financial Controller who periodically checks that the reconciliations are genuinely performed, that the authorisations involve real scrutiny, that the segregation is actually maintained, knows whether the control environment is real or merely nominal. This testing — whether through the Financial Controller’s own review, internal audit where it exists, or the external auditor’s controls testing — is what distinguishes a control environment that is known to work from one that is merely assumed to. The Financial Controller who documents the controls and verifies that they operate has a control environment they can genuinely stand behind, which is the whole point: controls that work, that are known to work, and that can be shown to work, rather than controls that exist on paper and are hoped to be effective.
A simple control matrix example
The standard documentation tool is a risk and control matrix: one row per control, linking it to the risk it addresses and recording how it operates and how it is evidenced. The extract below is illustrative for a purchase-to-pay process in a mid-sized business; thresholds should be set for your own business.
| Ref | Risk | Control | Type / frequency | Owner | Evidence |
|---|---|---|---|---|---|
| P2P-01 | Unauthorised spend | Purchase orders approved in system per authority matrix before order | Preventive, automated, per transaction | Budget holders | System approval log |
| P2P-02 | Payment to fraudulent account | Bank detail changes verified by call-back to known number and approved by second person | Preventive, manual, per change | Purchase Ledger / Finance Manager | Change form with call-back record |
| P2P-03 | Incorrect or duplicate payment | Payment run reviewed against approved invoices and released by two authorisers | Preventive, manual, weekly | Financial Controller and Director | Bank platform dual-release log |
| P2P-04 | Liabilities misstated | Purchase ledger control account and key supplier statements reconciled; items over threshold investigated | Detective, manual, monthly | Financial Accountant; reviewed by FC | Signed reconciliation |
| P2P-05 | Unauthorised master data change | Supplier master data change report reviewed | Detective, manual, weekly | Financial Controller | Initialled report |
Testing follows the matrix: for each key control, select a sample of instances in the period and check that the control was performed, on time, by the right person, with evidence and with exceptions followed up. Record the results and any failures, agree remediation with owners, and retest. A matrix maintained this way gives the auditors something to rely on and makes it far easier to hand the control environment over; our guides to Financial Controller audit preparation and the internal audit job description explain how the work is shared as the business grows.
Board-Level Expectations: Provision 29 of the UK Corporate Governance Code
For companies that apply the UK Corporate Governance Code 2024 — principally those with shares in the London Stock Exchange’s commercial companies category, on a comply-or-explain basis — Provision 29 applies to financial years beginning on or after 1 January 2026. The board is expected to monitor the company’s risk management and internal control framework and review its effectiveness at least annually, and the annual report should include a description of how it did so, a declaration of effectiveness of the material controls as at the balance sheet date, and a description of any material controls that did not operate effectively, with the action taken or proposed.
The FRC leaves boards to decide which controls are “material”, and they cover operational, reporting and compliance controls, not only financial ones. In practice, much of the evidence comes from the finance function: a clear risk and control matrix, documented testing, a log of control failures and remediation, and an assurance map showing which controls are tested by management, internal audit and the external auditor. Unlisted businesses are not bound by Provision 29, but private equity owners, lenders and acquirers increasingly expect the same discipline, and a Financial Controller who can produce that evidence is well placed when the business heads towards investment or exit. For FCA-regulated firms, controls also need to satisfy the regulator’s systems and controls expectations; senior compliance appointments are handled by our sister firm SMF Capital.
Need a Financial Controller who owns controls? — 0204 553 8893
Accountancy Capital recruits Financial Controllers, Finance Managers and financial accountants on a permanent, interim and fractional basis. We respond the same working day; interim and fractional shortlists typically follow within days.
A Practical Checklist for Designing Financial Controls
- Map the finance processes and list what could go wrong in each; score likelihood and impact.
- For each significant risk, define at least one preventive and one detective control.
- Write each control precisely: who, what, when, threshold, evidence and cover for absence.
- Set and publish an authority matrix for spend, payments, journals, credit notes and write-offs.
- Separate supplier set-up, invoice processing, payment release and bank reconciliation as far as headcount allows; compensate for the rest.
- Restrict and review system access, including leavers and super-users.
- Automate controls in the system wherever practical, and design the human review of anything automated.
- Keep a risk and control matrix, test key controls periodically and log remediation.
- Assess fraud risk specifically, including fraud that could benefit the business, against the six principles in the failure to prevent fraud guidance.
- Re-run the review at each trigger point: audit, investment, acquisition, new system or new territory.
Many of these controls sit inside the month-end close; our guide to optimising the month-end close shows how reconciliations and review fit a fast close, and the FC’s role in fundraising and due diligence explains why control quality shapes how diligence goes.
Hiring a Financial Controller to Design Your Controls
Control design is one of the clearest tests of a Financial Controller’s judgement. In interview, ask candidates to describe a control environment they inherited, what they changed first and why, how they handled segregation in a small team, and a control failure they found and fixed. Strong candidates talk about risk, proportionality and evidence rather than listing procedures. As a guide, owner-managed businesses with £5m–£15m turnover typically pay £65k–£82k in London, £54k–£70k in the South East and £48k–£64k in the Midlands and North, and interim Financial Controllers in London typically command £400–£650 a day; see our Financial Controller salary guide for full ranges. Where a business needs controls fixed quickly — after a fraud, an audit finding or a senior departure — an interim Financial Controller is often the fastest route, and our Financial Controller recruitment page explains how permanent searches run. For Finance Director or CFO appointments we work with sister firm FD Capital.
Frequently Asked Questions
What is the difference between preventive and detective controls?
Preventive controls stop an error or fraud happening, such as dual authorisation of payments or system-enforced approval limits. Detective controls identify problems after the event, such as reconciliations, exception reports and variance reviews. A robust environment uses both for each significant risk.
How do you achieve segregation of duties with a two-person finance team?
Separate the most incompatible duties — supplier set-up, payment processing, payment release and bank reconciliation — and bring in someone outside finance, usually the managing director, as a second authoriser and reviewer of bank statements. Restrict system permissions and use compensating reviews, such as an external accountant or fractional FC, for what cannot be separated.
Does the failure to prevent fraud offence apply to my business?
It applies to large organisations meeting two of three tests — more than 250 employees, more than £36m turnover, more than £18m total assets — measured across the group, and has been in force since 1 September 2025. Smaller businesses are not in scope, but the guidance’s six principles are a useful benchmark. Take legal advice on your own position.
What is a risk and control matrix?
A document, usually a spreadsheet or GRC tool, listing each key control alongside the risk it addresses, its type and frequency, the owner and the evidence it leaves. It is the basis for testing controls and for showing auditors, investors or a board that the controls exist and operate.
Does Provision 29 apply to private companies?
No. Provision 29 forms part of the UK Corporate Governance Code, which applies on a comply-or-explain basis to companies in the London Stock Exchange’s commercial companies category, for financial years beginning on or after 1 January 2026. Private companies are not bound by it, although investors and lenders often expect similar discipline.
How often should financial controls be reviewed?
Test key controls at least annually, with higher-risk controls such as payments and master data reviewed more frequently. Re-run the overall risk assessment whenever the business changes materially — new system, acquisition, investment or expansion into a new country.
Adrian Lawrence FCA — Founder, Accountancy Capital
Fellow of the ICAEW | Chartered Accountant holding an ICAEW practising certificate | Part of FD Capital Group
Adrian is a former listed-company Finance Director and holds a BSc from Queen Mary College, University of London. He founded FD Capital in 2018 and later Accountancy Capital, which recruits the Financial Controllers and finance managers who build and run control environments in UK businesses.
Related Pages and Resources
Controls Guides
Building a control environment that works.
→ Internal controls for growing businesses
Pay and Role Guides
Benchmarks and role definitions.
→ Financial Controller salary guide
Hiring a Financial Controller? — 0204 553 8893
Our recruitment team places Financial Controllers who design control environments that manage real risk and scale with the business. Permanent shortlists typically follow within one to two weeks; fees are agreed in writing before a search starts. Email recruitment@accountancycapital.co.uk.