Essex: every payment it published
A reading of the payment files Essex County Council published under the duty to disclose spending over £500. It is a record of what was published, not a budget, not total expenditure, and not a judgement about the council.
Essex County Council, payments over £500 as published by the council. Covering April 2022 to May 2023.
Totals leave out treasury management flows: deposits with the Debt Management Office (DMADF), Public Works Loan Board borrowing and repayments, money market and liquidity funds, and temporary loans between public authorities. That cash is moved or lent, not spent.
the council's own published payment dataas of 30 Oct 2026. Every figure on this page inherits this as-of date: 30 October 2026.
Need every supplier as a spreadsheet? Download this council's region or all England as CSV.
Important: These are published payment records. A payment to a named supplier is a record that money moved; it is not evidence of any wrongdoing by the council or by the supplier, and most entries have entirely ordinary explanations.
What was published
Each figure is a direct count of the published rows. A figure we could not read says so rather than showing a zero.
There is no score and no ranking on this page. A council that publishes more rows is not spending more than one that publishes fewer, and the totals are payments over the disclosure threshold rather than the council's expenditure.
Source: council payment files published under the £500 local-transparency duty. Figures as of 30 October 2026.
What the council published, month by month
This comes before the charts on purpose. Essex published a payment file in 12 of the 14 months between April 2022 and May 2023. 2 months carry no file at all and 0 carry a file with far fewer rows than this council's normal month. The longest unbroken gap runs from February 2023 to March 2023, 2 months.
A month with no file is not a month with no spending. Nothing on this page treats it as one, and any change from one year to the next that straddles a gap cannot be interpreted.
| Year | J | F | M | A | M | J | J | A | S | O | N | D | Months published |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2022 | outside the published range | outside the published range | outside the published range | April 2022: file published, 2 payments | May 2022: file published, 3 payments | June 2022: file published, 2 payments | July 2022: file published, 2 payments | August 2022: file published, 1 payments | September 2022: file published, 2 payments | October 2022: file published, 1 payments | November 2022: file published, 3 payments | December 2022: file published, 1 payments | 9 of 9 |
| 2023 | January 2023: file published, 1 payments | February 2023: no file published | March 2023: no file published | April 2023: file published, 1 payments | May 2023: file published, 1 payments | outside the published range | outside the published range | outside the published range | outside the published range | outside the published range | outside the published range | outside the published range | 3 of 5 |
- File published
- Partial file
- No file published
Months with no file: February 2023 to March 2023.
Source: Essex published payments over £500, as republished by Civic Core Institute. Figures as of 30 October 2026.
Every published month, by what kind of recipient was paid
Each bar is one month. Its height is the value of the payments Essex published that month, split by the kind of recipient. Months with no published file are drawn as a hatched gap that runs the full height of the plot, so they can never be read as a month of no spending.
- Name matches a registered company
- Small purchases, card merchants and names our registers do not match
- Name withheld (payment to or for an individual)
- No payment file published
- Partial file
About the withheld band. The band labelled "name withheld" is payments to or for individuals. The council is legally obliged to withhold those names, so this is a legal duty rather than concealment, and it is not a sign that anything is hidden: the department, the expense type, the amount and the date are all still published.
A withheld payment averages £600 against £888 for the largest named class, while the middle payment in each is £600 against £625. Both are published because a mean and a median answer different questions and neither on its own describes a class well. The department composition below is what shows what kind of payment they are; it could not be read this time, so nothing here should be taken as saying what these payments are for.
The same figures as a table (14 months)
| Month | File | Total | Name matches a registered company | Small purchases, card merchants and names our registers do not match | Name withheld (payment to or for an individual) |
|---|---|---|---|---|---|
| Apr 2022 | published | £8,500 | - | £8,500 | - |
| May 2022 | published | £3,000 | - | £1,500 | £1,500 |
| Jun 2022 | published | £1,800 | - | £1,500 | £300 |
| Jul 2022 | published | £2,000 | £500 | £1,500 | - |
| Aug 2022 | published | £1,500 | - | £1,500 | - |
| Sep 2022 | published | £3,500 | £2,000 | £1,500 | - |
| Oct 2022 | published | £1,500 | - | £1,500 | - |
| Nov 2022 | published | £2,800 | £300 | £2,500 | - |
| Dec 2022 | published | £1,500 | - | £1,500 | - |
| Jan 2023 | published | £1,500 | - | £1,500 | - |
| Feb 2023 | none published | - | - | - | - |
| Mar 2023 | none published | - | - | - | - |
| Apr 2023 | published | £1,500 | - | £1,500 | - |
| May 2023 | published | £750 | £750 | - | - |
Source: Essex published payments over £500; recipient class assigned by name pattern and exact register-name match. Figures as of 30 October 2026.
What kind of recipient the money went to
Every published supplier name is put through one cascade of rules and takes the first class that matches. The basis column says which rule decided it. A class is a statement about the name as published, not about which legal entity was paid: exact register-name equality is not identity, and this page never asserts a company number for a council supplier.
| Kind of recipient | How it was decided | Value | Share of value | Payments | Share of payments | Names | Mean | Median |
|---|---|---|---|---|---|---|---|---|
| Small purchases, card merchants and names our registers do not matchNo rule matched the published string. It is overwhelmingly small purchases and purchase-card merchant descriptors: most of its rows come from suppliers whose average payment is a few hundred pounds. It is not a suspicious category. | no rule matched the published name | £25k | 82.1% | 13 | 65.0% | 3 | £1,885 | £1,500 |
| Name matches a registered companyThe published supplier name is exactly a name on the Companies House register after normalisation. At least one registered company carries this name; which one is not answerable from the name alone. | the published name exactly matches a name on the Companies House register | £3,550 | 11.9% | 4 | 20.0% | 1 | £888 | £625 |
| Name withheld (payment to or for an individual)The council published the payment but withheld the recipient's name because the recipient is an individual. That is a legal obligation under data-protection law, not concealment. The department, expense type, amount and date are all still published, so these rows remain fully analysable. | the published name is a redaction marker | £1,800 | 6.0% | 3 | 15.0% | - | £600 | £600 |
| All published payments | £30k | 100% | 20 | 100% |
The mean and the median are both shown because they say different things. Where a class has a low mean and an ordinary median, the class does not contain the large payments, rather than containing individually small ones. Names counts distinct published supplier strings, so one organisation spelled two ways counts twice, and it is not shown for withheld names because every withheld payment carries the same marker.
Source: Essex published payments over £500. Figures as of 30 October 2026.
Payments where the recipient's name is withheld
Some rows in a council payment file carry no supplier name. The recipient is an individual, and the council is legally obliged to withhold the name under data-protection law. This is a legal duty, not concealment, and it is not a measure of how transparent a council is.
A withheld row still carries its department, its expense type, its amount and its date. It is a fully analysable class that is missing one field, and it is presented that way here: the department composition below shows what kind of payment it is.
A withheld payment averages £600 against £888 for the largest named class, but the medians are £600 and £625. Both figures are published because a mean and a median answer different questions, and a mean on its own can mislead about a class with an unusual spread.
The share is broadly flat over time
Withheld names were 16.7% of published payments in 2022/23 and 16.7% in 2022/23. The department composition below is what says which services these rows sit in. A change in the share is a question about where the money goes, not a finding about the council, which is why the composition is published beside the trend rather than the share on its own.
| Financial year | Withheld payments | Share of payments | Value | Share of value | Median |
|---|---|---|---|---|---|
| 2022/23 | 3 | 16.7% | £1,800 | 6.5% | £600 |
Which departments the withheld payments sit in
This is the evidence for the paragraph above. Each row also carries that department's own totals, so the withheld share is readable in context rather than asserted.
| Department, as published | Withheld payments | Withheld value | All payments in this department | Withheld share of the department |
|---|---|---|---|---|
| Department not stated | 3 | £1,800 | 18 | 16.7% |
Councils spell the withholding marker several different ways and change the spelling over time. All spellings are merged on the marker rather than on the string, so a change of wording does not split one class into two entries in the tables above.
Source: Essex published payments over £500. Figures as of 30 October 2026.
Departments, one year at a time
Department names are free text chosen by each council and they churn with every restructure. This council has used more than one name for the same service in different years, so a ten-year trend by department would show departments appearing and vanishing because of renaming. Departments are therefore shown one year at a time and never as a trend, and are never compared with another council's departments.
The council published a file in all 2 months of 2023/24 that fall inside its published range.
£2,250 of the £2,250 published in 2023/24 sits on an accrual or control code rather than an operating department. Those rows are marked in the table and stay in the total, because they are real payments to real suppliers: what is missing is the department attribution, not the money. Removing them would understate the council.
| Department, as published | Value | Share | Payments | Supplier names | Name withheld |
|---|---|---|---|---|---|
| Department not statednot statedno department stated on these rows. | £2,250 | 100.0% | 2 | 2 | 0 |
| All departments, 2023/24 | £2,250 | 100% | 2 | 0 |
Supplier names counts distinct published strings within the department, not distinct organisations.
Source: Essex published payments over £500. Figures as of 30 October 2026.
The largest recipients
Every name below is the supplier name as Essex published it. It has not been resolved to a company. Where a name exactly matches a name on the Companies House register that is shown as a name match and nothing more: common trading names match dozens of registered companies, so which one was paid is not answerable from the name.
Credits and refunds are published as negative rows. They are held in their own column rather than netted into the total, because netting them is right for a total and wrong for "largest payments".
| # | Supplier name, as published | Kind of recipient | Total paid | Credits | Payments | First | Last | Departments | Most common purpose | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Millie-Bea Pantrymatched as MILLIEBEA PANTRY | Small purchases, card merchants and names our registers do not match | £17k | - | 11 | 2 Apr 2022 | 18 Apr 2023 | 1 | - | published name only |
| 2 | Anna Harrismatched as ANNA HARRIS | Small purchases, card merchants and names our registers do not match | £7,000 | - | 1 | 16 Apr 2022 | 16 Apr 2022 | 1 | - | published name only |
| 3 | Pixelin Ltdmatched as PIXELIN LTD | Name matches a registered company | £3,550 | - | 4 | 21 Jul 2022 | 17 May 2023 | 1 | - | register name match |
| 4 | redactedmatched as REDACTED | Name withheld (payment to or for an individual) | £1,800 | - | 3 | 11 May 2022 | 6 Jun 2022 | 1 | - | published name only |
| 5 | Paddy Lennoxmatched as PADDY LENNOX | Small purchases, card merchants and names our registers do not match | £1,000 | - | 1 | 12 Nov 2022 | 12 Nov 2022 | 1 | - | published name only |
| All recipients | £30k | |||||||||
Showing 5 names. Value is concentrated: on this council a few hundred names carry most of it, which is why the list is capped and the remainder is kept as one visible row rather than dropped.
The largest 5 recipients, month by month
Each strip runs across the same month grid as the coverage table above. A hatched column is a month in which the council published no file, not a month in which this supplier was paid nothing. The figures beside each strip are the ones to quote.
| Supplier name, as published | Month by month | Months paid | Largest month | Total |
|---|---|---|---|---|
| Millie-Bea Pantry | 11 | £1,500 | £17k | |
| Anna Harris | 1 | £7,000 | £7,000 | |
| Pixelin Ltd | 4 | £2,000 | £3,550 | |
| redacted | 2 | £1,500 | £1,800 | |
| Paddy Lennox | 1 | £1,000 | £1,000 |
Source: Essex published payments over £500. Figures as of 30 October 2026.
Methodology and limitations
Every figure comes from the council's own published payment files, republished under the local government transparency code duty to disclose spending over £500. Rows are summed exactly as published; nothing is estimated, modelled or filled in. Months come from a coverage table built from the council's first to its last published payment, so a month with no file exists as a slot and is drawn as an absence rather than as zero. Each published supplier name is normalised (upper case, punctuation stripped, legal forms canonicalised) and put through one cascade of rules, taking the first that matches: a redaction marker; then public-body, school, NHS and local-authority word patterns; then an exact match against a copy of the Companies House register; then a company-suffix pattern; and anything left is unclassified. The class describes how the NAME was matched and never asserts which legal entity was paid. Departments and expense types are the council's own labels, passed through unchanged and never mapped to a shared vocabulary, because no shared vocabulary exists. Rows posted to a year-end accrual code or a control account are marked as such and kept in every total. Totals leave out treasury management flows: deposits with the Debt Management Office (DMADF), Public Works Loan Board borrowing and repayments, money market and liquidity funds, and temporary loans between public authorities. That cash is moved or lent, not spent. Credits and refunds are published as negative rows and are held in a separate column. The page reads precomputed aggregates in the serving database rather than the raw transaction table, which is held separately; where an aggregate has not been built the section says so instead of showing a zero.
- These are payments over the £500 disclosure threshold, plus credits and refunds published as negative rows. They are not the council's budget and not its total expenditure. Anything below the threshold, and anything the council did not publish, is not here.
- Councils do not publish every month. The coverage table above lists the months with no file by name. A year-on-year change that straddles a gap cannot be interpreted and is not shown as one.
- Some published files carry far fewer rows than the council's normal month. They are marked as partial and kept in the totals rather than dropped, because silently removing a file changes the published total. A partial month should not be read as a quiet month.
- Supplier names are the strings the council published. They are not resolved to companies. A name that exactly matches a name on the Companies House register is reported as a name match only: common trading names match dozens of registered companies, so which one was paid is not answerable from a name, and no company number is asserted anywhere on this page.
- Supplier strings are dirty in ways that break exact matching. Several councils truncate the name at a fixed width, and some carry trailing ledger text. A name that does not match a register is not evidence that no such company exists.
- The charity class is a word pattern in the published name, not a lookup in the charity register. The register copy we hold carries a usable identifier on a minority of its rows and matches almost nothing here, so a charity lookup is not offered.
- Redaction is a legal obligation, not concealment. Where the recipient is an individual the council must withhold the name under data-protection law. No council is ranked by its redaction rate on this site: a high rate tracks how much a council pays direct to or for individuals, so ranking on it would penalise councils doing more direct payment to vulnerable people.
- The redaction detector matches a word pattern on the supplier name, so a real organisation whose name contains that word can be caught by it. The effect is a handful of rows and a negligible share of value, but it is a known false positive rather than a clean rule.
- Department names are per-council free text with no shared vocabulary, so they cannot be compared between councils. They also change with restructures inside one council, which is why departments are shown one year at a time rather than as a trend.
- Rows posted to a year-end accrual code or a control account are marked in the department table and kept in the totals. They are real payments to real suppliers whose operating department is not stated; excluding them would understate the council.
- Several columns exist in the source schema but are empty in practice, including cost-centre name, VAT amount and payment method. Nothing on this page is built on them.
- "What was this for" is read from the most specific field a row carries: the description, else the expense type, else the department. Every purpose shown is labelled with which of those levels it came from. No prose is generated.
- Credits and refunds are published as negative rows. They are held in their own column rather than netted into the largest-payment figures, because netting is right for a total and wrong for a ranking.
- The figures on this page come from precomputed aggregates that are refreshed on a schedule, not continuously. The as-of date is published beside every section.
Source: Essex County Council published payment dataas of 30 Oct 2026
Company-name matching uses a copy of the Companies House register. A match means a registered company carries that exact name after normalisation. It does not identify which company was paid.
Machine-readable version of this page: /api/councils/cmkpp54zd003cfw8oe6jv9nit/spend-explorer (add ?fy=2023 for 2023/24).
Something wrong on this page? Write to corrections@civiccoreinstitute.com and we will correct it.
Get new data by email
A short email when we publish new data or analysis on UK public money, about once a month. Unsubscribe at any time.
We use your email only to send this newsletter and you must confirm it first. See our privacy policy.