Why income visibility remains one of transformation’s most underestimated risks

Every transformation programme has a list of things that could go wrong. Systems may not integrate as planned. Data migration may take longer than expected. Changes that look straightforward on paper may prove much harder once people start working with them. These familiar risks tend to receive attention early. Yet one risk often remains less visible: whether the organisation understands how income moves between services, systems and teams.

Income rarely receives the same attention, even though it connects financial performance, operational efficiency and resident experience.

Payments continue to be collected, accounts are updated and reports are produced. On the surface, everything appears to be working. What is harder to see is the effort required to keep it working: the failed Direct Debits that need chasing, the transactions entered manually into another system and the time finance teams spend reconciling records at month end.

Across local government and social housing, that hidden workload can affect financial performance and service delivery. Residents feel the consequences when accounts are slow to update, payment queries take too long to resolve or warning signs are missed.

Why income is easily overlooked

Research commissioned by Access PaySuite among 100 local authority finance leaders puts some numbers around a problem many organisations will recognise. Nearly three in ten councils map their payment and income infrastructure late in a transformation programme or not at all. A further 89% reported that inherited technology was shaping their transformation decisions. The implication is wider than any one platform: important design decisions may be made before leaders can see how money, information and responsibility move across the organisation.

Organisations can find themselves making important decisions before they fully understand how income moves across their services. They may not know where manual work still exists, which records depend on one another or what happens between a payment being made and reaching the relevant account.

This is understandable. Major platforms, governance arrangements and changes to service structures demand immediate attention.

But “working” can hide a great deal of effort. A process may deliver the required result while depending on spreadsheets, manual checks and workarounds that only a small number of people fully understand. When the organisation changes, those dependencies become much more important.

By the time they surface, the programme may already have made decisions that are difficult or expensive to revisit.

What income actually costs

The transaction fee tells only a small part of the story.

There is also the failed Direct Debit that needs investigating. The payment that arrives in one system and must be entered into another. The resident who calls because their account does not show what they have paid.

Each issue may seem small on its own. Repeated across thousands of transactions, they add up to a significant amount of staff time and avoidable contact.

One authority found that bank reconciliation had previously required three full-time employees. After changes were made to its processes and systems, the same work took four hours a week. As one senior financial systems officer put it:

“Cost savings is abstract. Bank rec going from 3 FTE to 4 hours a week, that’s real.”

The saving had been there all along, but it only became visible once the organisation looked closely at the existing process.

The authority knew the process was better. What it hadn’t realised was how difficult improvement is to prove when nobody records where they started. Without a baseline, performance is often measured against memory rather than evidence.

In social housing, these problems can also affect the relationship with residents. Rent supports repairs, investment in homes and the services people rely on. Service charges, garage rents and former resident arrears may arrive through different channels before being reconciled with the housing management record.

The account a resident sees needs to match the one the housing officer uses. When it does not, trust can quickly erode and conversations about arrears become harder.

The moment of truth

For residents, payment is a practical moment of truth between an organisation and the people it serves.

Structures, processes and digital services are all tested when a resident tries to pay. In that moment, the service either works or it does not.

Residents do not see programme plans or technology roadmaps. They see whether they can pay their rent or Council Tax, whether their account updates and whether someone can help when something goes wrong.

A resident who cannot complete a payment online may call the contact centre instead. Someone whose account has not updated may receive an arrears letter before the record is corrected. A housing officer working from information that is several hours or days behind may miss the first opportunity to offer support.

The cause may sit within a system or a process, but the resident experiences it as part of the service. That everyday interaction is where much of the work behind a transformation programme is tested.

Where fragmentation creates cost

Income management becomes difficult when the place where money is collected is separate from the systems, records and teams that need to understand it.

A transaction may enter through a payment platform while the related account sits in a Revenues & Benefits application or housing management system. Frontline teams need an up-to-date record so they can answer questions and recognise when someone may require support.

When those connections depend on manual work, delay becomes part of the process. Staff spend time transferring and checking records. Residents make contact because their balances appear incorrect. Warning signs of arrears may reach housing officers or Revenues teams after the best opportunity for an early conversation has passed.

These problems usually build gradually. Another payment channel is introduced. A team creates a spreadsheet to cover a gap. An exception process becomes part of the monthly routine. Each change solves an immediate problem, but the combined effect can be difficult to see without mapping the entire payment journey.

Reducing that effort depends on more than technology. Some organisations may find that process redesign, clearer ownership or the removal of duplicated controls delivers the first improvement. Others may need to address integration or replace parts of the technology estate. The starting point is evidence, not a predetermined product decision.

When efficiency improves the service

Cost reduction and service quality are often discussed as if improving one must come at the expense of the other. Income management shows that this does not always need to be the case.

Automated reconciliation reduces manual work for finance teams and gives frontline staff access to more current account information. Offering familiar payment options can reduce failed transactions and make it easier for residents to pay. Earlier visibility of a missed payment gives housing or Revenues teams more time to understand what has happened before the issue grows.

In housing, that timing can change the whole nature of the conversation. A housing officer who sees a missed payment promptly may be able to contact the resident while the situation is still manageable. If the reconciliation is running behind, the same issue may only become visible after the arrears have grown.

The first conversation can focus on support. The later one is more likely to involve debt and formal recovery.

Reducing administrative work gives teams more time for those earlier conversations. Staff spend less time correcting records and resolving avoidable queries, leaving more time for residents whose circumstances require judgement and personal support.

What stronger organisations do differently

Organisations with a clear understanding of income tend to involve finance, transformation and service teams in the same conversation. They examine the whole journey, from the point at which a resident makes a payment to the point at which it appears in the relevant account or case record.

They also measure what is happening before making changes. Collection rates are important, but so are reconciliation times, failed Direct Debit volumes, manual exceptions and the number of queries caused by payment issues. These measures give leaders a starting point and make it easier to see whether changes are delivering a genuine improvement.

Clear ownership is equally important. Connecting payment platforms with finance applications and operational services affects more than one team. Responsibilities need to be understood, controls maintained and unresolved issues followed through.

Three practical actions can help any organisation, whatever systems or suppliers it currently uses:

• Map the full income journey. Record every provider, contract, payment channel and system involved before money reaches the ledger or resident account.
• Measure the work behind collection. Establish how much time is spent on reconciliation, manual exceptions, failed payments and avoidable resident queries.
• Give the journey an owner. Make someone responsible for improvement across departmental boundaries, including the controls and follow-through needed to sustain it.

Building stronger foundations for change

Transformation programmes tend to focus on the risks that could emerge during delivery. Income management can reveal the inefficiencies already embedded in everyday operations.

It shows where records connect and where they do not. It highlights the work teams perform manually. It can also reveal costs that conventional reporting does not capture.

Organisations do not need the newest technology or the largest programme budget to examine these issues. They need an honest view of the work taking place today and reliable evidence of where change would make the greatest difference.

Before the next transformation decision, leaders should ask three questions: How many systems and teams touch a resident payment before it reaches the correct account? How much staff effort is spent on reconciliation, exceptions and avoidable queries? Who owns the whole journey from collection to understanding?

The ability to answer those questions with evidence may reveal more about transformation readiness than the name of any platform in use.

Enjoy this? Share the post with others, and follow me, Tom Osborne, for more.