Staff turnover is usually treated as a people issue: a signal of engagement, leadership quality or organisational culture. Those factors matter, but for the Office of the CFO, turnover creates a more immediate exposure.

It creates financial leakage risk.

When an experienced employee leaves, the organisation does not only lose capacity. It can lose the judgement that connects contracts, policies, transactions and approvals: why a reconciliation needs a particular adjustment, which exceptions deserve scrutiny, where a supplier charge falls outside scope and when an unusual payment should be escalated.

The role may be filled quickly. The control capability often is not.

Leakage happens in the gaps people used to manage

Financial leakage occurs in the gaps between what an organisation agreed, what it received, what it earned and what it paid.

Those gaps are often held together by experienced people. They know which contract version applies, where a rate card changed, which supplier credits remain outstanding and why a particular billing exception matters.

When that knowledge leaves, the process may continue while the underlying control weakens. Invoices are still approved. Accounts are still reconciled. Journals are still reviewed.

But the organisation may no longer be testing the right evidence, challenging the right anomalies or quantifying the dollars at risk.

That is how turnover becomes leakage: not necessarily through one dramatic failure, but through small exceptions, missed obligations and control gaps that compound across transactions.

A completed control is not always an effective control

Turnover rarely causes a control to disappear overnight. More often, it erodes control quality gradually.

A departing employee’s responsibilities may be reassigned to someone already carrying a full workload. Reviews become faster and less probing. Reconciliations are completed later. Supporting evidence becomes thinner. Exceptions are carried forward because investigating them takes time.

On paper, the control still operates. In practice, its ability to prevent or detect loss has declined.

A signed checklist proves that an activity occurred. It does not prove that the reviewer had the time, context or confidence to identify a duplicate payment, challenge an off-contract charge or recognise that delivered services did not match what was billed.

This creates a dangerous gap between apparent compliance and actual governance.

Where turnover creates financial leakage

1. Supplier leakage

A new or stretched team member may approve an invoice without checking every line against the current contract, purchase order, rate card, discount, rebate, delivery evidence or permitted scope.

That can allow contracted rates not applied, missed credits, incorrect quantities, short deliveries, duplicate invoices and services billed beyond scope to pass through unnoticed.

Most supplier leakage is not malicious. It lives in reconciliation gaps, billing drift and exceptions that nobody has the time or knowledge to investigate.

2. Revenue leakage

Turnover can also weaken the link between services delivered, supplier costs incurred and customer billing.

Knowledge of pass-through obligations, pricing changes, usage rules and customer-specific terms may sit with a small number of employees. When they leave, the organisation can miss price increases, underbill delivered work, fail to recover supplier costs or lose revenue between operational systems and customer invoices.

The work was completed. The value was earned. It was simply never billed.

3. Payment leakage

Vacancies and handovers increase the risk that duplicate, erroneous, off-policy or non-compliant payments reach approval.

The payment may pass because the workflow was followed, even though the right control did not. A reviewer might confirm that an approval exists without testing whether the amount, supplier, bank details, supporting evidence or delegated authority are valid.

By the time the issue appears in a reconciliation or audit, the money has already moved.

4. Manual workarounds and disconnected evidence

New employees are more likely to follow visible steps without understanding the control objective behind them. When systems or data do not align, they may inherit spreadsheets, manual adjustments and undocumented shortcuts.

These workarounds separate contracts, approvals, delivery evidence and transaction data across different files and workflows. That makes exceptions harder to identify, ownership harder to establish and the audit trail harder to reconstruct.

Treat departures as financial control events

The standard response to a resignation is operational: recruit a replacement, arrange a handover and redistribute urgent work.

That may restore capacity. It does not necessarily restore governance.

For every control-sensitive departure, management should establish:

  1. Which supplier, revenue and payment controls the employee performs, reviews or supports.
  2. Which contracts, policies, rate cards, reconciliations and exceptions depend on their knowledge.
  3. Where segregation of duties or approval independence will be compromised.
  4. Which permissions must be removed, reassigned or monitored.
  5. Which transactions require additional scrutiny during the transition.
  6. How temporary exceptions will be owned, evidenced and closed.
  7. When the replacement’s competence will be tested rather than assumed.

Higher-risk transitions may require tighter approval thresholds, independent review of key reconciliations, targeted checks of supplier and customer transactions, enhanced monitoring of unusual activity or temporary restrictions on access.

These measures should remain in place until the organisation has evidence—not simply confidence—that the control environment has stabilised.

Move from periodic checks to real-time governance

Traditional controls often identify problems after the transaction: at month-end, during a sample-based audit or when someone investigates an unexplained variance.

That is too late for many forms of leakage.

A more resilient model applies the right controls before money moves. It brings contracts, purchase orders, rate cards, supplier records, delivery evidence, policies and approval rules together at the point of decision.

Every in-scope transaction can then be checked for:

  • incorrect calculations, tax, dates and duplicates;
  • supplier identity and bank-detail changes;
  • mismatches against purchase orders and delivery evidence;
  • off-contract rates, missed discounts, rebates and credits;
  • scope, policy and delegated-authority breaches;
  • unusual patterns and incompatible access; and
  • the precise dollar value at risk.

The objective is not to remove people from financial decisions. It is to reduce dependence on individual memory and route only genuine exceptions to the right person, with the evidence needed to approve, reject or escalate them.

Human judgement remains essential. It becomes better focused and better supported.

Build controls that can survive a resignation

Identify key-person dependencies

Map critical controls to named owners, reviewers and tested backups. Where no capable backup exists, treat that dependency as a control weakness—not an informal staffing concern.

Test backup capability

Naming a backup is not the same as having one. Backup employees should periodically perform the control under supervision so their readiness is demonstrated before a transition.

Use the organisation’s own rules as the source of truth

Controls should be anchored to current contracts, policies, rate cards, approval limits and supplier records—not to what one employee remembers. This makes handovers more reliable and decisions more consistent.

Keep humans in the loop for exceptions

Automation should handle repeatable checks and bring together the supporting evidence. Sensitive decisions, ambiguous cases and material exceptions should remain with accountable people.

Monitor control quality in dollars

Track more than completion rates. Monitor overdue reconciliations, unreconciled differences, late journals, approval overrides, duplicate invoices, off-contract charges, access exceptions and the value of leakage detected or prevented.

This gives finance a clearer view of working capital protected, margin retained and governance improved.

Build the audit trail as work happens

A board-ready audit trail should show what was checked, which rule or term applied, what evidence supported the decision, who approved the exception and how the issue was resolved.

That is stronger than reconstructing the story months later.

The broader lesson

A strong control environment is not defined by whether every role remains continuously occupied. It is defined by whether reliable governance continues when people change.

Staff turnover exposes the difference between controls that are genuinely embedded and controls held together by individual knowledge.

The financial risk is not simply that an employee leaves. It is that value begins to leak through the gaps they used to manage—and the organisation discovers it only after the money has moved.

Businesses already monitor turnover as an indicator of organisational health. They should also treat it as an early warning signal for supplier, revenue and payment leakage.

The goal is not merely to recover losses later. It is to apply the right control, to every transaction, at the point of decision—protecting working capital, margin and confidence in the numbers.