FHDC Public Money: 46 Contract Red Flags Raise Questions Over Council Spending

There’s no point dressing this up in committee-room cotton wool. Folkestone & Hythe District Council’s public data shows 46 confirmed 2025/26 contract red flags and irregularities. Together, those entries had a recorded award value of £1,002,043.97, but matched confirmed spend of £20,720,797.37, producing a public-data variance of £19,718,753.40 above the recorded award values. Each one has been checked against both the council’s contract register, Kent business Portal Register, FHDC’s purchase-order data and its payment-to-suppliers data.

That doesn’t prove fraud, illegality or that every contract was overspent. It does show there are serious public-money questions sitting inside the very accounts residents are now meant to be able to inspect the accounts — and FHDC gives you the residents of the district 256 characters to ask about it.

That’s the story. Forty-six contract red flags and irregularities. One inspection year. A 256-character box that turns public inspection into a grim little game show: how much public-money detail can you cram into a space smaller than a social-media post? That’s not transparency. It’s accountability through a keyhole.

What the 46 actually mean

The 46 are confirmed public-data red flags and irregularities. They’re “confirmed” because each one passed the quadruple ledger test: KCC Contract Register, The Counci’s Contract Register lthe purchase-order total exceeded the recorded contract award value, and the payment-to-suppliers total also exceeded the recorded award value when matched by supplier and contract window. The analysis uses the lower of the two ledger totals as “confirmed spend”, so it doesn’t just grab the biggest number and leg it down Sandgate Road.

They’re not findings of unlawful expenditure. To prove that, you’d need the missing paperwork: signed contracts, invoices, VAT treatment, waiver forms, variation reports, extension approvals, procurement comments, S151 sign-offs, Monitoring Officer sign-offs, project codes and budget codes. That’s exactly what the inspection period should help residents test.

Why the 256-character limit belongs at the top of the story

The 46 red flags and the inspection form shouldn’t be treated as separate issues. The problem isn’t only that the figures look odd. The problem is that the year containing these 46 red flags is the year residents are now allowed to use their public inspection rights to look at the 2025/26 accounts, FHDC’s form doesn’t give them enough room to ask for the records properly.

Try fitting this into 256 characters: “Please provide the signed contract, current approved contract value, all variations, extension approvals, waiver forms, purchase orders, invoices, VAT treatment, S151 sign-off, Monitoring Officer sign-off, budget code and payment records for contract X.” You can’t. Not properly. Not without butchering the request like a badly carved Sunday roast.

FHDC may say residents can submit more than one form. That’s a fig leaf, not a solution. Public inspection shouldn’t require people to chop one proper request into scraps and hope the council tapes them back together in the right order.

The money trail doesn’t join up

Across 1 April 2016 to 31 March 2026, the FHDC public money trail points in different directions. The combined contract-register reconciliation gives £299.42m of recorded award value. Over the same period, purchase orders total £296.69m excluding VAT, while supplier payments total £495.18m including VAT.

The VAT point matters. FHDC publishes purchase orders of £5,000 and above excluding VAT, while its supplier-payment data covers payments of £250 and above including VAT. So the two ledgers aren’t like-for-like, and nobody serious should pretend they are.

Still, the gap doesn’t vanish. If every published purchase order is given a simple 20% VAT uplift, the purchase-order total rises to £356.03m. Supplier payments still sit £139.15m higher. That doesn’t prove wrongdoing, but it does show residents can’t follow the money properly from the public data alone.

The missing plank is obvious: a clean public bridge from contract to purchase order to invoice to payment. FHDC publishes updated tender and contract information, and says ITQ and ITT processes are managed through the Kent Business Portal, but the public datasets don’t carry one simple thread through the whole spending chain.

Extensions and waivers may explain some irregularities

Here’s the fair bit. Some of these red flags may have ordinary explanations. An extension means a contract carried on beyond its original period. A variation means the contract changed, often in value, scope, timing or work. A waiver means permission to step outside the usual procurement route. A direct award means a contract was awarded without a fresh open competition, often through a framework or other permitted route.

Those things can be lawful. They can also be messy. If FHDC says the figures are explained by extensions, variations, waivers, framework call-offs or VAT treatment, the answer is simple: show the paper trail.

FHDC’s own rules say the paperwork should exist

FHDC’s Financial Procedure Rules say council resources must be used legally, properly authorised, with value for money and best value in mind. They also place the Chief Finance Officer, or S151 Officer, at the centre of proper financial administration and financial controls.

The rules apply to councillors, officers, council-related bodies and anyone acting on the council’s behalf. Chief officers are responsible for complying with Contract Standing Orders, controlling and monitoring spending, highlighting budget variances early and consulting the S151 Officer before commitments are made on matters liable to affect council finances.

So if one of the 46 is explained by an extension, variation, waiver, framework call-off or VAT treatment, FHDC shouldn’t need to reach for a fog machine. The records should show it.

The waiver issue wasn’t imaginary

FHDC’s own waiver strategy says the review was initiated after the new Director of Finance looked at the waiver process. It says the purpose was to strengthen financial discipline, transparency and accountability, and that the volume and nature of waiver use had prompted the need for a refreshed strategy.

That matters because the article isn’t making a wild leap from odd numbers to dark conclusions. It’s saying the public data shows 2025/26 red flags, and FHDC’s own governance papers had already pointed to weaknesses in the machinery that should explain them.

The waiver report identified high waiver volumes, thin or inconsistent justifications, retrospective waiver requests after a supplier had already been chosen or work had started, reliance on known suppliers, and limited challenge in the approval process. For 2024/25, it recorded 33 waivers with a combined value of £1.741m, including a £475,000 temporary-accommodation waiver.

Grant Thornton pointed to the same stretch of road

Grant Thornton’s 2024/25 Auditor’s Annual Report also pointed to weaknesses in FHDC’s waiver process and contract management, including late engagement from budget managers, minimal justification, contractual risk, incomplete register data, inconsistent compliance, manual processes, poor visibility and weak central supplier-performance monitoring.

That isn’t background noise. It puts an audit frame around the spreadsheet findings, the waiver strategy, the financial rules and the 256-character inspection box. The same problem keeps bobbing up: FHDC’s public contract trail isn’t clear enough for residents to follow the money without forcing their way through a hedge backwards.

The 46 need records, not reassurance

The KCC entries need particular caution. They pass the quadruple-ledger test, but several sit in overlapping supplier and date windows, so some supplier spend may be caught across more than one contract entry unless FHDC supplies the missing contract IDs, invoice coding and PO links.

That doesn’t kill the story. It proves the point. If the public data can’t tell whether spend belongs to one contract, another contract, a framework call-off or a wider service arrangement, the public data isn’t good enough for proper inspection.

Download the full FHDC contract red flags spreadsheet

The retention rules make “we can’t find it” harder to swallow

The Council’s 2019 and 2025 retention schedules say ordinary contract records should generally be kept for six years after the contract terms expire, while contracts under seal or deeds should generally be kept for twelve years after expiry. Contract-management records, changes, variation forms, extensions, complaints and payment disputes aren’t loose scraps down the back of a cabinet; they’re exactly the records needed here.

That makes the 2025/26 inspection issue sharper. These aren’t dusty files from another age. They’re current-year or recent-year records sitting inside the accounts now open to public inspection.

The line FHDC should now answer

For each of the 46, residents should be able to inspect the signed contract, original award value, current approved value, extension approvals, variation reports, waiver forms, procurement comments, S151 sign-offs, Monitoring Officer sign-offs, purchase orders, invoices, payment records, VAT treatment, project code and budget code.

That’s not a fishing trip. It isn’t vague. It isn’t “send me everything about contracts”. It’s a targeted inspection request about named 2025/26 public-data irregularities.

If FHDC’s answer is that the records exist and explain the figures, all well and good. Publish the trail. If the records don’t exist, aren’t linked, can’t be found, weren’t approved, or don’t match the public data, that’s a different story altogether.

Ending

Some of the 46 may have vering boring explanations. Boring explanations are welcome, because they’re the bread and butter of proper transparency and accountability.

Right now, residents have fragments: contract values in one place, purchase orders in another, payments somewhere else, waiver concerns in a governance report, auditor warnings in another document, and an inspection form that barely gives enough room to ask the question.

That isn’t open government. It’s a paper chase.

FHDC’s problem isn’t that every flagged contract is automatically rotten. It’s that its own rules say the cure should exist — waiver forms, variation reports, extension approvals, procurement comments and finance/legal sign-offs — while the public data still sends residents down a rabbit hole with a torch running out of batteries.

Forty-six red flags and irregularities. One inspection year. A 256-character doorway. If the explanations are there, open the files to proper inspection requests. If they’re not, that’s the story.

The Shepway Vox Team

Delightfully Delicious Dissent