BT REDCARE

What is held for this supplier

Canonical id

bt-redcare

Councils that published a payment

57

Payments published

948

Latest year held

2026/27

What each council published, by year

These councils are not comparable with one another. They hold different numbers of years, publish above different thresholds and buy different things, so a larger figure here means more was published and read, not that one council spent more freely than another. An empty cell is a year not held, never a year of nothing.

The largest payments published

A description is the council's own wording on the row. A large single payment is often a scheduled settlement of many smaller invoices, and this site does not know which of these are.

Which councils and years contributed

Covers 57 councils and 11 financial years in the AI DOGE corpus. Councils and years not listed have not been ingested and are not zero.

Financial years held: 2016/17, 2017/18, 2018/19, 2019/20, 2020/21, 2021/22, 2022/23, 2023/24, 2024/25, 2025/26, 2026/27.

Councils that contributed: Bassetlaw, Boston, Breckland, Buckinghamshire, Calderdale, Central Bedfordshire, Cheltenham, Chichester, Chorley, Dartford, Doncaster, Dorset, Ealing, East Lindsey, Eastleigh, Elmbridge, Enfield, Epsom & Ewell, Erewash, Fylde, Gloucester, Halton, Hart, High Peak, Hounslow, Hyndburn, Lambeth, Lancashire PCC, Leeds, Lewisham, Lincolnshire, Mansfield, Merton, North Northamptonshire, Oldham, Oxford, Plymouth, Preston, Rushmoor, Somerset, South Kesteven, South Oxfordshire, St Helens, Staffordshire Moorlands, Stockport, Stroud, Sunderland, Surrey, Swale, Tamworth, Vale of White Horse, Walsall, Wandsworth, West Lancashire, West Northamptonshire, West Oxfordshire, Wolverhampton.

A council that is not on this list has not been ingested for this supplier. That is a statement about this site's holdings and not about the council, and it is never a zero.

The council pages behind these figures

Every figure above was read off one council's own published payment file. Each council page carries what is held for it, when its files were last read, and its own publication threshold.

• Bassetlaw spending
• Boston spending
• Breckland spending
• Buckinghamshire spending
• Calderdale spending
• Central Bedfordshire spending
• Cheltenham spending
• Chichester spending
• Chorley spending
• Dartford spending
• Doncaster spending
• Dorset spending
• Ealing spending
• East Lindsey spending
• Eastleigh spending
• Elmbridge spending
• Enfield spending
• Epsom & Ewell spending
• Erewash spending
• Fylde spending
• Gloucester spending
• Halton spending
• Hart spending
• High Peak spending
• Hounslow spending
• Hyndburn spending
• Lambeth spending
• Lancashire PCC spending
• Leeds spending
• Lewisham spending
• Lincolnshire spending
• Mansfield spending
• Merton spending
• North Northamptonshire spending
• Oldham spending
• Oxford spending
• Plymouth spending
• Preston spending
• Rushmoor spending
• Somerset spending
• South Kesteven spending
• South Oxfordshire spending
• St Helens spending
• Staffordshire Moorlands spending
• Stockport spending
• Stroud spending
• Sunderland spending
• Surrey spending
• Swale spending
• Tamworth spending
• Vale of White Horse spending
• Walsall spending
• Wandsworth spending
• West Lancashire spending
• West Northamptonshire spending
• West Oxfordshire spending
• Wolverhampton spending
• Every public body on this site
• Money moving between public bodies

How this page was built

A supplier gets a page of its own when ten or more councils published a payment to it, or when at least £10m was published to it in a single financial year. That cut is a size, not a judgement, and it is applied the same way to every supplier.

Names are matched across councils by a canonical form of the supplier string each council published. Two councils spelling the same company differently are joined; a company and its subsidiary are not, unless the councils wrote the same name. Payments a council withheld are counted in that council's own totals and are on no page as a name. A Companies House number, where one is shown, comes from this site's own name match and plays no part in joining councils' payments together.

Index built 2026-09-27T11:39:42Z by burnley-council/scripts/build_supplier_index.py.