Clean-down requirements in revolving credit facilities: why an overdraft-style balance may need to fall

A clean-down requirement obliges a borrower to reduce drawings under a revolving or working-capital facility to a specified level for a specified period. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.

What clean-down requirements means in practice

A clean-down requirement obliges a borrower to reduce drawings under a revolving or working-capital facility to a specified level for a specified period. The commercial effect often appears before accounting catches up, so treasury should identify the exact event that changes the position.

The purpose is often to show that the facility supports working-capital timing rather than permanent structural borrowing, but the exact test is contractual. A practical procedure should say exactly who checks the condition, when it is tested and where the supporting record is retained.

How clean-down requirements works from start to finish

The operating file should contain the required balance, number of clean days, testing window, currencies, permitted netting, other debt included and the cash forecast around the test period. Bringing those facts together prevents legal, treasury and accounting teams from reaching different conclusions about the same event.

Operational ownership should follow the transaction through to its final state. The person who initiates an action does not need to perform every later step, but the business must know who owns unresolved exceptions.

The data and evidence that matter

Evidence also needs a retention location that survives staff turnover. A material clean-down requirements decision should be understandable from the treasury or finance record without depending on a private mailbox or one employee's memory.

An effective record should also make the exception path visible. If the normal rule cannot be met, the team should capture who approved the deviation, how long it applies and what evidence will close it. For clean-down requirements, that distinction prevents a temporary workaround from becoming an undocumented permanent practice. For clean-down requirements, the specific checkpoint is this: Forecast the clean-down date months ahead and reserve enough free cash or alternative liquidity to meet the contractual balance for the full required period.

Where the process can fail

A business can technically have enough liquidity yet fail the clean-down because customer receipts arrive after the testing window or another draw keeps the balance above the required level. The financial exposure can grow quickly when the issue is discovered close to settlement, drawdown or payment day.

Deadline pressure can also weaken controls. If the process depends on an emergency override every month, the underlying timetable is wrong and should be redesigned rather than normalising exceptions.

Worked example: test the mechanics

A £8 million revolving facility must fall below £1 million for five consecutive business days each financial year. The borrower repays to £800,000 on Monday but draws £600,000 on Thursday for payroll. The balance no longer stays below £1 million for five consecutive business days, so the test may fail.

This example is a method rather than a universal rule. The business should replace every illustrative figure with its own contractual terms, bank data and dates, then test the result before assuming that cash or authority is available.

Governance and controls for clean-down requirements

Forecast the clean-down date months ahead and reserve enough free cash or alternative liquidity to meet the contractual balance for the full required period. A reviewer should be able to see the rule, the data used and the final status in one case file without rebuilding the chronology from emails.

Monitoring should focus on unresolved items and ageing. For clean-down requirements, management gains more from seeing exceptions that are approaching a deadline than from a report showing only how many transactions completed successfully.

Senior review is most valuable where judgement remains. Automated controls can check limits and formats, but unusual legal, liquidity or counterparty issues still need an accountable person to decide whether the business should proceed.

Decision records should separate three layers: what the governing document or payment scheme allows, what the bank or counterparty operationally supports, and what internal policy permits. Those layers can produce different answers, and clean-down requirements is safest when the difference is explicit before the transaction proceeds. In this workflow, the supporting record should cover the required balance, number of clean days, testing window, currencies, permitted netting, other debt included and the cash forecast around the test period.

The review should use the required balance, number of clean days, testing window, currencies, permitted netting, other debt included and the cash forecast around the test period and should identify which item would force the team to pause, obtain consent or change the planned date. A useful challenge question is whether the transaction would still be safe if a business can technically have enough liquidity yet fail the clean-down because customer receipts arrive after the testing window or another draw keeps the balance above the required level.