PUBLIC SECTOR SOFTWARE LTD

What is held for this supplier

Canonical id

public-sector-software

Councils that published a payment

40

Payments published

137

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 40 councils and 14 financial years in the AI DOGE corpus. Councils and years not listed have not been ingested and are not zero.

Financial years held: 2013/14, 2014/15, 2015/16, 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: Bath & North East Somerset, Bolsover, Bournemouth, Christchurch and Poole, Broadland, Cherwell, Coventry City Council, Derby City, Durham, Epsom & Ewell, Guildford, Halton, Horsham, Hounslow, Ipswich, Islington, Leicester City, Lewes, Mansfield, North Somerset, Nottingham City, Portsmouth, Preston, Rochdale, Rushmoor, Sandwell, Somerset, South Gloucestershire, South Kesteven, South Norfolk, St Helens, Stoke-on-Trent, Stratford-on-Avon, Test Valley, Tewkesbury, Vale of White Horse, Wakefield, Walsall, Wolverhampton, Worcester, York.

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.

• Bath & North East Somerset spending
• Bolsover spending
• Bournemouth, Christchurch and Poole spending
• Broadland spending
• Cherwell spending
• Coventry City Council spending
• Derby City spending
• Durham spending
• Epsom & Ewell spending
• Guildford spending
• Halton spending
• Horsham spending
• Hounslow spending
• Ipswich spending
• Islington spending
• Leicester City spending
• Lewes spending
• Mansfield spending
• North Somerset spending
• Nottingham City spending
• Portsmouth spending
• Preston spending
• Rochdale spending
• Rushmoor spending
• Sandwell spending
• Somerset spending
• South Gloucestershire spending
• South Kesteven spending
• South Norfolk spending
• St Helens spending
• Stoke-on-Trent spending
• Stratford-on-Avon spending
• Test Valley spending
• Tewkesbury spending
• Vale of White Horse spending
• Wakefield spending
• Walsall spending
• Wolverhampton spending
• Worcester spending
• York 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.