Trafford: every payment it published
A reading of the payment files Trafford Metropolitan Borough 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.
Trafford Metropolitan Borough Council, payments over £500 as published by the council. Covering April 2024 to March 2026.
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. Trafford published a payment file in 23 of the 24 months between April 2024 and March 2026. 1 months carry no file at all and 5 carry a file with far fewer rows than this council's normal month.
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2024 | outside the published range | outside the published range | outside the published range | April 2024: partial file, far fewer rows than this council's normal month, 25 payments | May 2024: partial file, far fewer rows than this council's normal month, 35 payments | June 2024: partial file, far fewer rows than this council's normal month, 39 payments | July 2024: partial file, far fewer rows than this council's normal month, 23 payments | August 2024: no file published | September 2024: file published, 417 payments | October 2024: file published, 1,089 payments | November 2024: file published, 1,213 payments | December 2024: file published, 1,162 payments | 8 of 9 |
| 2025 | January 2025: file published, 1,726 payments | February 2025: file published, 920 payments | March 2025: file published, 1,459 payments | April 2025: file published, 1,007 payments | May 2025: file published, 1,423 payments | June 2025: file published, 1,035 payments | July 2025: file published, 1,248 payments | August 2025: partial file, far fewer rows than this council's normal month, 107 payments | September 2025: file published, 1,376 payments | October 2025: file published, 1,407 payments | November 2025: file published, 1,290 payments | December 2025: file published, 1,151 payments | 12 of 12 |
| 2026 | January 2026: file published, 1,433 payments | February 2026: file published, 1,076 payments | March 2026: file published, 1,349 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 | outside the published range | outside the published range | 3 of 3 |
- File published
- Partial file
- No file published
Months with no file: August 2024.
Partial files: April 2024; May 2024; June 2024; July 2024; August 2025. These carry far fewer rows than this council's normal month. They are shown as published rather than dropped, because silently removing a file changes the published total.
Source: Trafford 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 Trafford 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
- 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 an amount we could not read against £275 for the largest named class, while the middle payment in each is not read against £203. 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 (24 months)
| Month | File | Total | Name matches a registered company | Small purchases, card merchants and names our registers do not match |
|---|---|---|---|---|
| Apr 2024 | partial | £16k | £15k | £1,214 |
| May 2024 | partial | £19k | £18k | £1,135 |
| Jun 2024 | partial | £17k | £16k | £1,170 |
| Jul 2024 | partial | £12k | £11k | £1,087 |
| Aug 2024 | none published | - | - | - |
| Sep 2024 | published | £119k | £109k | £10k |
| Oct 2024 | published | £273k | £258k | £15k |
| Nov 2024 | published | £359k | £342k | £18k |
| Dec 2024 | published | £299k | £288k | £11k |
| Jan 2025 | published | £384k | £361k | £23k |
| Feb 2025 | published | £228k | £213k | £14k |
| Mar 2025 | published | £416k | £404k | £12k |
| Apr 2025 | published | £204k | £192k | £12k |
| May 2025 | published | £355k | £343k | £12k |
| Jun 2025 | published | £287k | £271k | £16k |
| Jul 2025 | published | £278k | £265k | £13k |
| Aug 2025 | partial | £16k | £13k | £2,631 |
| Sep 2025 | published | £360k | £340k | £20k |
| Oct 2025 | published | £338k | £323k | £14k |
| Nov 2025 | published | £360k | £340k | £20k |
| Dec 2025 | published | £267k | £255k | £12k |
| Jan 2026 | published | £366k | £339k | £27k |
| Feb 2026 | published | £280k | £261k | £20k |
| Mar 2026 | published | £345k | £318k | £27k |
Source: Trafford 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 |
|---|---|---|---|---|---|---|---|---|
| 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 | £5.3m | 94.6% | 19,238 | 87.4% | 4 | £275 | £203 |
| 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 | £303k | 5.4% | 2,772 | 12.6% | 17 | £109 | £63 |
| All published payments | £5.6m | 100% | 22,010 | 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: Trafford published payments over £500. Figures as of 30 October 2026.
What the money was spent on, by year
Each column is one financial year, split by the label Trafford wrote on its own payments. The labels are free text from a spreadsheet, not a standard set of categories, so they describe this council's bookkeeping and nothing beyond it.
A taller column is not always more spending. How much a council published, and how much of it we have loaded, differs by year. This council's range runs 2024/25 to 2025/26, and an early year is often thin because only some of its files exist, not because less was spent.
Total across every label and year: £5.6m. These are payments over the £500 disclosure threshold, not the council's expenditure.
Source: council payment files published under the £500 local-transparency duty. 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.
Withheld-name totals are not shown here at the moment.
The recipient-class summary has not been built for this council yet.
This is an absence of data, not a finding. Nothing above or below should be read as evidence that there is nothing to report.
Which departments the withheld payments sit in
The departments the withheld payments sit in are not shown here at the moment.
No withheld-name rows are recorded against a department for this council.
Without it the withheld band cannot be explained, so nothing above should be read as saying what those payments are for.
This is an absence of data, not a finding. Nothing above or below should be read as evidence that there is nothing to report.
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: Trafford published payments over £500. Figures as of 30 October 2026.
The council-level count is readable even though the class breakdown is not: 0 of 22,010 published payments (0.0%) withhold the recipient's name, worth £0 of £5.6m (0.0% by value).
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 12 months of 2025/26 that fall inside its published range.
£3.5m of the £3.5m published in 2025/26 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. | £3.5m | 100.0% | 13,902 | 21 | 0 |
| All departments, 2025/26 | £3.5m | 100% | 13,902 | 0 |
Supplier names counts distinct published strings within the department, not distinct organisations.
What the money was forshown at expense type level
"What was this for" is read from the most specific field a row carries: the description, else the expense type, else the department. The per-supplier and per-department version of that cascade is not available for Trafford yet, so this is the expense-type level, which is what the loaded aggregate carries. These are the council's own labels, passed through unchanged. The top 7 are shown for 2025/26.
| Expense type, as published | Value | Share of the rows shown | Payments |
|---|---|---|---|
| 5199 | £3.0m | 88.3% | 11,435 |
| 5811 | £248k | 7.2% | 605 |
| 2842 | £123k | 3.6% | 1,186 |
| 5462 | £25k | 0.7% | 624 |
| 5300 | £9,043 | 0.3% | 39 |
| 5399 | £367 | 0.0% | 5 |
| 5999 | £326 | 0.0% | 8 |
Source: Trafford published payments over £500. Figures as of 30 October 2026.
The largest recipients
Every name below is the supplier name as Trafford 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 | Dunsters Farm Limitedmatched as DUNSTERS FARM LTD | Name matches a registered company | £3.5m | -£116,673 | 11,561 | 18 Apr 2024 | 27 Mar 2026 | 1 | - | register name match |
| 2 | Ralph Livesey Limitedmatched as RALPH LIVESEY LTD | Name matches a registered company | £1.2m | -£1,006 | 4,807 | 19 Apr 2024 | 27 Mar 2026 | 1 | - | register name match |
| 3 | James Burrows Ltdmatched as JAMES BURROWS LTD | Name matches a registered company | £332k | - | 2,404 | 5 Sep 2024 | 7 Sep 2025 | 1 | - | register name match |
| 4 | Chicken Joes Ltdmatched as CHICKEN JOES LTD | Name matches a registered company | £304k | -£4,966 | 466 | 1 Apr 2024 | 21 Mar 2026 | 1 | - | register name match |
| 5 | Alliance Disposables Limimatched as ALLIANCE DISPOSABLES LIMI | Small purchases, card merchants and names our registers do not match | £195k | -£1,912 | 1,886 | 8 May 2024 | 31 Mar 2026 | 1 | - | published name only |
| 6 | Smart Foodmatched as SMART FOOD | Small purchases, card merchants and names our registers do not match | £73k | -£10 | 207 | 15 Apr 2024 | 30 Mar 2026 | 1 | - | published name only |
| 7 | Morris Quality Bakers Limmatched as MORRIS QUALITY BAKERS LIM | Small purchases, card merchants and names our registers do not match | £25k | - | 624 | 17 Dec 2025 | 27 Mar 2026 | 1 | - | published name only |
| 8 | Hb Clark And Co Successormatched as HB CLARK AND CO SUCCESSOR | Small purchases, card merchants and names our registers do not match | £10k | - | 42 | 28 Jan 2025 | 17 Mar 2026 | 1 | - | published name only |
| 9 | Amazon* 296lx4075matched as AMAZON 296LX4075 | Small purchases, card merchants and names our registers do not match | £285 | - | 1 | 27 Jan 2026 | 27 Jan 2026 | 1 | - | published name only |
| 10 | Amznmktplace*bf72p0yr5matched as AMZNMKTPLACEBF72P0YR5 | Small purchases, card merchants and names our registers do not match | £121 | - | 1 | 19 Mar 2026 | 19 Mar 2026 | 1 | - | published name only |
| 11 | Amznmktplace*wk7m92sl5matched as AMZNMKTPLACEWK7M92SL5 | Small purchases, card merchants and names our registers do not match | £118 | - | 1 | 29 Jan 2026 | 29 Jan 2026 | 1 | - | published name only |
| 12 | Amazon* 8164f0305matched as AMAZON 8164F0305 | Small purchases, card merchants and names our registers do not match | £40 | - | 1 | 12 Mar 2026 | 12 Mar 2026 | 1 | - | published name only |
| 13 | Amznmktplace*zc4ao2g54matched as AMZNMKTPLACEZC4AO2G54 | Small purchases, card merchants and names our registers do not match | £33 | - | 1 | 7 Jan 2026 | 7 Jan 2026 | 1 | - | published name only |
| 14 | Amazon Uk* 0w7qt9a25matched as AMAZON UK 0W7QT9A25 | Small purchases, card merchants and names our registers do not match | £22 | - | 1 | 23 Oct 2025 | 23 Oct 2025 | 1 | - | published name only |
| 15 | Amznmktplace*zl6kt58u4matched as AMZNMKTPLACEZL6KT58U4 | Small purchases, card merchants and names our registers do not match | £19 | - | 1 | 24 Nov 2025 | 24 Nov 2025 | 1 | - | published name only |
| 16 | Amznmktplace*3b1qr6zq5matched as AMZNMKTPLACE3B1QR6ZQ5 | Small purchases, card merchants and names our registers do not match | £12 | - | 1 | 10 Mar 2026 | 10 Mar 2026 | 1 | - | published name only |
| 17 | Amazon* 5e2xw41w5matched as AMAZON 5E2XW41W5 | Small purchases, card merchants and names our registers do not match | £10 | - | 1 | 27 Jan 2026 | 27 Jan 2026 | 1 | - | published name only |
| 18 | Amazon Uk* Kt4xi0xl5matched as AMAZON UK KT4XI0XL5 | Small purchases, card merchants and names our registers do not match | £10 | - | 1 | 22 Oct 2025 | 22 Oct 2025 | 1 | - | published name only |
| 19 | Amznmktplace*f62pc2795matched as AMZNMKTPLACEF62PC2795 | Small purchases, card merchants and names our registers do not match | £10 | - | 1 | 18 Mar 2026 | 18 Mar 2026 | 1 | - | published name only |
| 20 | Amznmktplace*017sz7zw5matched as AMZNMKTPLACE017SZ7ZW5 | Small purchases, card merchants and names our registers do not match | £7 | - | 1 | 12 Mar 2026 | 12 Mar 2026 | 1 | - | published name only |
| 21 | Amznmktplace*uv6fu4gk5matched as AMZNMKTPLACEUV6FU4GK5 | Small purchases, card merchants and names our registers do not match | £7 | - | 1 | 27 Jan 2026 | 27 Jan 2026 | 1 | - | published name only |
| All recipients | £5.6m | |||||||||
Showing 21 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 20 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 |
|---|---|---|---|---|
| Dunsters Farm Limited | 23 | £289k | £3.5m | |
| Ralph Livesey Limited | 23 | £92k | £1.2m | |
| James Burrows Ltd | 13 | £62k | £332k | |
| Chicken Joes Ltd | 22 | £27k | £304k | |
| Alliance Disposables Limi | 22 | £17k | £195k | |
| Smart Food | 22 | £6,193 | £73k | |
| Morris Quality Bakers Lim | 4 | £8,840 | £25k | |
| Hb Clark And Co Successor | 9 | £2,237 | £10k | |
| Amazon* 296lx4075 | 1 | £285 | £285 | |
| Amznmktplace*bf72p0yr5 | 1 | £121 | £121 | |
| Amznmktplace*wk7m92sl5 | 1 | £118 | £118 | |
| Amazon* 8164f0305 | 1 | £40 | £40 | |
| Amznmktplace*zc4ao2g54 | 1 | £33 | £33 | |
| Amazon Uk* 0w7qt9a25 | 1 | £22 | £22 | |
| Amznmktplace*zl6kt58u4 | 1 | £19 | £19 | |
| Amznmktplace*3b1qr6zq5 | 1 | £12 | £12 | |
| Amazon* 5e2xw41w5 | 1 | £10 | £10 | |
| Amazon Uk* Kt4xi0xl5 | 1 | £10 | £10 | |
| Amznmktplace*f62pc2795 | 1 | £10 | £10 | |
| Amznmktplace*017sz7zw5 | 1 | £7 | £7 |
Source: Trafford 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: Trafford Metropolitan Borough 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/cmkpp5bx2009mfw8oyz91bhuh/spend-explorer (add ?fy=2025 for 2025/26).
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.