The Receipts That Never Arrive: What Council Purchase Cards Hide About Off-Contract Spending

Corporate purchase cards occupy an awkward place in local government accountability. They are presented as a routine administrative convenience: a way for officers to buy stationery, pay for a training course or cover a small repair without raising a purchase order for every transaction. Yet the same cards can also become a route around formal procurement rules, and the published data on their use is often too thin to show whether that is happening.

A review of council disclosure pages, transparency returns and published card datasets for 2026 points to a familiar problem in a new form. Authorities are not short of spending data. They are short of data that can be reconciled — to a contract, to a supplier, to a budget line or to a reason. The result is a blind spot that sits below the threshold of formal procurement but above the level at which public scrutiny usually begins.

A card, not a contract

The Local Government Transparency Code 2015 requires English councils to publish spending over £500, along with contract and procurement information. It does not create a single, standard format for corporate purchase card transactions. Some authorities publish transaction-level card data voluntarily. Others publish summaries. Others seem to publish nothing that specifically identifies card use at all.

That matters because a purchase card is not simply a payment method. It is a decision about how public money is committed. When an officer uses a card, the normal procurement controls — competition, quotation, approval thresholds, contract records — may apply differently or not at all. A £400 purchase may look trivial in isolation. Repeated across months, directorates and teams, it can become a meaningful stream of off-contract spending.

The contract register is supposed to be the map of a council’s commercial relationships. Card transactions are often the dots that never appear on it. If a council buys the same low-value service from the same supplier every month on a card, the arrangement can function like a contract without being recorded as one.

What councils publish, and what they leave out

The disclosure landscape is uneven. Some councils publish monthly CSV files with transaction dates, amounts, directorates and merchant names. Others publish PDFs that cannot be easily sorted or totalled. Some provide a category such as office supplies or training, but no supplier. Some provide a supplier name but no description of what was bought.

Redactions compound the problem. Merchant names are sometimes withheld or generalised. Justifications are often reduced to a single word or left blank. Cost centres may be too broad to identify the team responsible. In some datasets, transactions are aggregated by month or by department, which removes the very detail that would allow a reader to spot repeat purchasing.

There are legitimate reasons for some withholding. Personal data, security concerns and genuinely sensitive commercial information can justify limits. But the pattern across published datasets suggests that inconsistency, rather than a consistent legal test, is doing much of the work. A resident in one council area may be able to see that £380 was spent with a named supplier for a named purpose. A resident in another may see only that £380 was spent on miscellaneous items.

The reconciliation problem

Without a merchant name, a description and a contract reference, card data cannot be reconciled to the contract register. Without a contract reference, it is difficult to tell whether a purchase was made under an existing framework or outside one. Without a consistent category, it is difficult to aggregate spending across authorities or even across departments.

This is not only a problem for journalists and campaigners. It is a problem for audit and scrutiny committees. A councillor reviewing a cabinet report may be told that procurement compliance is high. The card data may tell a different story, but only if the councillor can join the dots between a transaction, a supplier and a decision.

The risk of fragmented purchasing is well known. Low-value purchases can be split to stay under approval thresholds. Repeat purchases can avoid competition without ever triggering a formal waiver. A card can make those patterns harder to see because each individual transaction appears small and routine. The public record, in many authorities, does not make the pattern visible.

Why low-value matters

Low-value does not mean low-consequence. A council’s total card spend can run into millions of pounds across a year. The purchases may be individually modest, but they can still reveal how an authority prioritises suppliers, how it treats local businesses, how it controls officer discretion and how it responds when something goes wrong.

There is also a democratic point. Council spending data is meant to allow residents to follow public money. A dataset that cannot be sorted by supplier, matched to a contract or read alongside a decision record does not fulfil that purpose. It produces the appearance of transparency without the substance.

The 2026 test

A useful disclosure standard for purchase cards would not be complicated. Transaction-level data should include the date, amount, directorate, merchant, a plain-English description and a contract or framework reference where one exists. Where a reference does not exist, the dataset should say so. Redactions should be explained by category, not applied silently. Datasets should be published in a reusable format and retained over time so that repeat spending can be tracked.

None of that would expose personal data or genuinely sensitive commercial terms. It would simply allow the public record to do what it claims to do: show how money was spent, by whom and under what authority. In 2026, too many council card datasets still fail that basic test. The receipts are published, in some places, but the account they add up to is not.

A gap that scrutiny can close

The purchase card is not inherently a problem. It is a tool. The problem is the absence of a consistent public trail connecting the tool to the rules that are supposed to govern it. Councils already hold the data. The question is whether they are willing to publish it in a form that allows anyone outside the building to check the arithmetic.

For residents, reporters and backbench councillors, the card transaction is often the first visible sign of a purchasing decision. If it cannot be followed to a contract, a supplier or a justification, scrutiny stops at the point where it should begin. That is the gap that 2026 disclosures have not closed — and the one that local accountability cannot afford to ignore.