Westmorland and Furness: every payment it published
A reading of the payment files Westmorland and Furness 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.
Westmorland and Furness Council, payments over £500 as published by the council. Covering April 2025 to July 2025.
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. Westmorland and Furness published a payment file in 4 of the 4 months between April 2025 and July 2025. 0 months carry no file at all and 0 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2025 | outside the published range | outside the published range | outside the published range | April 2025: file published, 10 payments | May 2025: file published, 14 payments | June 2025: file published, 6 payments | July 2025: file published, 3 payments | outside the published range | outside the published range | outside the published range | outside the published range | outside the published range | 4 of 4 |
- File published
- Partial file
- No file published
Source: Westmorland and Furness 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 Westmorland and Furness 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
- Company-shaped name, no register match
- Other public body
- 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 £10,888 for the largest named class, while the middle payment in each is not read against £1,801. 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 (4 months)
| Month | File | Total | Name matches a registered company | Company-shaped name, no register match | Other public body |
|---|---|---|---|---|---|
| Apr 2025 | published | £375k | - | £187k | £188k |
| May 2025 | published | £48k | £10k | £38k | - |
| Jun 2025 | published | £46k | - | £46k | - |
| Jul 2025 | published | £788 | - | £788 | - |
Source: Westmorland and Furness 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 |
|---|---|---|---|---|---|---|---|---|
| Company-shaped name, no register matchThe name carries a company suffix such as LTD or PLC but does not match a register name exactly. Council supplier strings are often truncated or carry trailing ledger text, so a miss is not evidence the company does not exist. | a word pattern in the published name | £272k | 57.9% | 25 | 75.8% | 4 | £10,888 | £1,801 |
| Other public bodyCentral government departments, agencies, police, fire and other public bodies. | a word pattern in the published name | £188k | 40.0% | 4 | 12.1% | 1 | £47,029 | £41,690 |
| 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 | £10k | 2.1% | 4 | 12.1% | 1 | £2,510 | £2,451 |
| All published payments | £470k | 100% | 33 | 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: Westmorland and Furness 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 Westmorland and Furness 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 2025/26 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: £470k. 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: Westmorland and Furness 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 33 published payments (0.0%) withhold the recipient's name, worth £0 of £470k (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 4 months of 2025/26 that fall inside its published range.
| Department, as published | Value | Share | Payments | Supplier names | Name withheld |
|---|---|---|---|---|---|
| Payroll Deductions | £351k | 74.6% | 5 | 2 | 0 |
| Kerbside Coll Recycling Client | £71k | 15.2% | 4 | 1 | 0 |
| Street Cleansing | £18k | 3.8% | 4 | 1 | 0 |
| District Special Expenses | £8,980 | 1.9% | 2 | 1 | 0 |
| Car Parks | £8,431 | 1.8% | 3 | 1 | 0 |
| Parish Lighting | £5,729 | 1.2% | 5 | 1 | 0 |
| Bank Charges | £3,725 | 0.8% | 6 | 3 | 0 |
| Human Resources | £2,329 | 0.5% | 1 | 1 | 0 |
| Transport | £693 | 0.1% | 2 | 1 | 0 |
| Lake Windermere | £255 | 0.1% | 1 | 1 | 0 |
| All departments, 2025/26 | £470k | 100% | 33 | 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 Westmorland and Furness 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 5 are shown for 2025/26.
| Expense type, as published | Value | Share of the rows shown | Payments |
|---|---|---|---|
| Non-Service Payments | £351k | 74.6% | 5 |
| Cultural Environmental Regulatory & Planning Services | £90k | 19.2% | 11 |
| Highways & Transport Services | £17k | 3.7% | 5 |
| Central Services | £6,054 | 1.3% | 7 |
| SLDC as Agent | £5,729 | 1.2% | 5 |
Source: Westmorland and Furness published payments over £500. Figures as of 30 October 2026.
The largest recipients
Every name below is the supplier name as Westmorland and Furness 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 | HMRC (CHAPS)matched as HMRC CHAPS | Other public body | £188k | - | 4 | 1 Apr 2025 | 1 Apr 2025 | 2Payroll Deductions | Payroll Deductionsshown at department level | published name only |
| 2 | National Westminister Bank PLC (CHAPS)matched as NATIONAL WESTMINISTER BANK PLC CHAPS | Company-shaped name, no register match | £166k | - | 5 | 1 Apr 2025 | 1 Jul 2025 | 2Payroll Deductions | Payroll Deductionsshown at department level | published name only |
| 3 | ALLSTAR BUSINESS SOLUTIONS LTD (NCR)matched as ALLSTAR BUSINESS SOLUTIONS LTD NCR | Company-shaped name, no register match | £90k | - | 11 | 1 Apr 2025 | 30 Jun 2025 | 4Kerbside Coll Recycling Client | Kerbside Coll Recycling Clientshown at department level | published name only |
| 4 | NPOWER LTD (NCR)matched as NPOWER LTD NCR | Company-shaped name, no register match | £15k | - | 7 | 1 May 2025 | 1 Jun 2025 | 2District Special Expenses | District Special Expensesshown at department level | published name only |
| 5 | ACCESS PAYSUITE LTD | Name matches a registered company | £10k | - | 4 | 1 May 2025 | 1 May 2025 | 2Car Parks | Car Parksshown at department level | register name match |
| 6 | ALLPAY.NET LTD (NCR)matched as ALLPAYNET LTD NCR | Company-shaped name, no register match | £1,327 | - | 2 | 1 May 2025 | 27 Jun 2025 | 1Bank Charges | Bank Chargesshown at department level | published name only |
| All recipients | £470k | |||||||||
Showing 6 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 6 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 |
|---|---|---|---|---|
| HMRC (CHAPS) | 1 | £188k | £188k | |
| National Westminister Bank PLC (CHAPS) | 2 | £165k | £166k | |
| ALLSTAR BUSINESS SOLUTIONS LTD (NCR) | 3 | £45k | £90k | |
| NPOWER LTD (NCR) | 2 | £14k | £15k | |
| ACCESS PAYSUITE LTD | 1 | £10k | £10k | |
| ALLPAY.NET LTD (NCR) | 2 | £702 | £1,327 |
Source: Westmorland and Furness 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: Westmorland and Furness 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/cmkpp5c5p009ufw8o6vq6jwha/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.