What fragmented income systems really cost a council, and how to measure it
Real public sector problems: Episode 2
Tom Main
Senior Pre-Sales & Solution Consultant, HeyCentric
A resident pays their Council Tax on time. The money reaches the council’s bank account, but it isn’t matched to their account. A reminder follows, then further recovery notices, and eventually a summons to the magistrates’ court for a bill they have already paid.
The cause is rarely a single mistake. More often, it traces back to how the council’s income systems connect to each other.
Council Tax. Business Rates. Parking. Licensing. Housing Rents. Sundry Debts. A council processes money for dozens of services, and each one usually has its own system, chosen at a different time, by a different team, for its own needs.
The income management system sits in the middle. It’s where all of that money should come together, be matched to the right accounts and be reconciled with the bank. In practice, it’s often treated as one more separate system, and the cost of that rarely appears on a single budget line.
We spoke to Tom Main, Senior Pre-Sales & Solution Consultant at HeyCentric, about what that looks like inside a council, what it costs and how to measure it.
Every service has its own system. That isn’t the problem.
When Tom starts working with a council, the first thing he maps out is where the income comes from.
“All the services tend to run on separate line-of-business systems,” he explains. “So, we integrate with all the separate systems. Council Tax, Business Rates, Sundry Debts, Parking, Housing Rents and so on.”
On top of the service systems come the third-party payment files: bank files, files from the enforcement agents, an end-of-day file from the payment system, plus many more sources.
None of this is unusual. Councils provide a wide range of services, and it makes sense for each service to use a system that suits it. The difficulty comes in how those systems connect to income management, and who is responsible for keeping those connections working.
Every part works. Nobody sees the whole process.
In many councils, the connections were built one at a time, as each new system arrived. A macro was written for one file, a script for another, and a manual import for a third. Tom sees the result regularly.
“Invariably, the file that comes from the source system isn’t the file that gets imported into the income management system,” he says. “We can see straight away from our point of view that it’s fragmented, and we can make an instant positive change to the council’s processes.”
Each of those connections was built by someone, often someone who has since moved on, and each sits with a different team. Often, no single person can describe how all the income reaches income management from start to finish.
Some connections weren’t even built for the system they now feed. When a council replaces its finance system, a third-party system may still produce a file set up for the old one. Rather than rebuild that interface, someone adds a step to convert the file, and the data now goes through two conversions instead of one.
Picture an old wooden cartwheel. In a well-connected setup, income management is the hub, and each service system on the rim connects to it with its own spoke. In many councils there is no hub. Connections run straight across the wheel, from one system on the rim to another. Replace either system and that connection has to be rebuilt. Often, it isn’t. It gets bent and taped to fit, and that taped-up route is the one the council’s income now follows.
The problem isn’t the individual systems. It’s the extra steps between them, and the difficulty of maintaining those connections as the council’s needs change.
Change one system, and the others feel it
Because the systems are connected through workarounds, a change in one place can cause problems somewhere else. Tom gives an example from online payments. Some councils take card payments through a third-party payment service rather than through their income management system’s own web payments. When that money arrives, the bank file may show only the payment provider’s name, not the service or account the payment relates to. Staff learn to recognise that name and know which income it stands for.
“But obviously when that changes, we’re going to have to be aware of that,” Tom says.
If the provider or the bank file description changes, the matching rules need updating. Where someone owns the connections, that’s a planned piece of work. Where nobody does, the change may only come to light when payments stop matching.
From staff time to a court summons: what the gaps cost
Some of the cost is easy to see. The visible part is staff time: files converted by hand, payments moved out of suspense, the same information checked in two or three systems. Then there’s outside support. When a connection breaks and nobody in-house can fix it, the council pays someone else to. Tom’s view is that councils shouldn’t have to keep paying consultancy fees for this kind of work.
“We’d rather you were confident and knowledgeable enough in the platform you’ve bought to do it yourselves,” he says.
The less visible cost comes when something goes wrong for a resident, as in the example at the start. A payment that reaches the bank but isn’t correctly matched can lead to reminders, recovery action and, possibly, a court summons.
“The ultimate resident complaint is somebody having to go to magistrates’ court when they’ve already paid,” Tom says.
Putting that right takes time across several teams and damages the resident’s confidence in the council. In some cases, it can become a story in the local paper.
Each step in recovery also has a direct cost: letters printed and posted, calls answered, actions recorded. One council puts the cost of each letter it sends at around £1. And because the resident knows they’ve paid, each recovery notice makes them less willing to engage, which means more letters and more calls about a debt that doesn’t exist.
Why the saving is hard to put a number on
Councils often ask HeyCentric how much money a connected income process will save. Tom is open about why that’s difficult to answer.
“It’s extraordinarily difficult, when you’re with a council, to ask them how much time it saves, because inevitably the person you’re asking is the one whose time it’s saving, and that can be a tricky question for them to answer,” he explains. “And then you ask their manager how much time they spend on the task, and they don’t know. They don’t do the task.”
“Getting that information can be a challenge. So, it’s very, very difficult to quantify.”
Tom adds: “We want to help councils spend quality time on the outputs rather than on the manual inputs.”
Time spent on manual processes is rarely measured consistently. It’s spread across several people and teams, with nobody recording the total. The cost is real, but nobody sees it in one place.
Measure the process, not the people
A more useful approach is to measure the process itself, rather than relying on estimates of how much time people spend on it. Five numbers give you a starting point.
Five numbers to measure your income process
- How many income files arrive each day, and how many need converting before import.
- How many manual steps sit between the bank file and the resident’s account.
- How many items sit in suspense each week.
- How often staff step in to allocate payments by hand.
- What you spent on outside support for income interfaces last year.
These numbers give you a baseline. They show where the work is happening and where problems keep coming back, and they give finance and procurement teams something concrete to compare: the cost of the current approach against the cost of improving it.
One connecting point, not a collection of workarounds
HeyCentric’s approach is to make income management the hub of the cartwheel: every income stream connects to it directly with its own spoke, while the council’s service systems carry on doing their jobs. When one system changes, only that spoke changes. The aim isn’t to replace every system, but to make the connections consistent, visible and easier to manage.
Files are taken from the source systems and processed using HeyCentric’s ETL (extract, transform, load) tools, which removes the scripts, macros and manual conversions in between.
The council also doesn’t have to reshape its data to suit HeyCentric. Files can arrive in whatever shape the source system already produces, as long as it’s consistent: the same information in the same place, every time. Data going back to a service system is produced in a format that system already recognises. And teams no longer need to copy data into the income system by hand; the source file is loaded directly.
“By making the system more robust, we get rid of that middle bit,” Tom says.
The council ends up with one documented approach instead of a collection of workarounds, and a payment can be followed from start to finish.
“We like to tell the whole story, from the money getting paid by the bill payer to the bank reconciliation piece in the council,” Tom explains.
New income streams connect the same way. With training and documentation from HeyCentric, the council’s own team can set them up and test them before they go live, so routine changes don’t need outside support and knowledge of the process doesn’t sit with one person or one supplier.
Fewer workarounds, more capacity
What Tom sees is that the cost of a fragmented setup falls when the connections are visible, documented and owned.
“You’re future-proofing your organisation, because you’ve got far more people who are aware, and far better documentation as to what the source file contains and how it’s used.”
In many income teams, experienced people spend part of every day with spreadsheets, printouts and highlighter pens, working out where each payment came from. When the system does that matching, staff can manage by exception and spend the rest of their time on work that needs their experience, such as resolving complex queries or supporting residents who are struggling to pay.
This isn’t about reducing headcount. It’s about capacity: people who already know the council’s income process are free to take on the next priority, without the council having to recruit or pull someone from another team.
The question isn’t whether every service needs to use the same system. It’s whether the systems you already have can work together reliably, and whether you can see, manage and maintain the connections that make that possible.
About the series
Expert Insights is a series of conversations with HeyCentric specialists about real public sector problems. In this second episode, Tom Main, Senior Pre-Sales & Solution Consultant at HeyCentric, talks through what fragmented income systems cost a council and how to measure it.
Want to understand what your current approach is costing?
If you want to understand what your current approach is costing, our team can help you map how income reaches the right account, where manual work is needed and how much outside support those connections require.