Still running Experian Tallyman? How to optimize it and plan what comes next

Why Tallyman remains important

Tallyman was introduced to the market in the 1980s by Sanderson CFL, bought by Talgentra in 2002, and acquired by Experian in 2007. It manages accounts in arrears from the first missed payment through to recovery, write-off or resolution: collections strategies, account treatment, agent and automated contact, workflow and exception handling, with strategies changed in its configuration tooling and promoted from test into production. It integrates with the billing and customer management systems, decision engines, data warehouses and document management around it.

Although PowerCurve Collections has superseded Tallyman as Experian's strategic collections platform, many organizations continue to operate highly configured Tallyman estates that remain central to day-to-day collections and recoveries. Tallyman has been used across banking, utilities, telecommunications and automotive finance in the UK and internationally. Many remaining estates are found in organizations with large portfolios, complex processes and substantial configuration built up over a number of years.

We continue to encounter long-established Tallyman estates with substantial client-specific configuration and integrations accumulated over many years. The product naming is not always consistent, so the first step is to establish exactly which product, release, infrastructure and support arrangement is in place.

How long should an existing Tallyman estate remain in service?

The question is not whether Tallyman remains a current strategic product in the market. PowerCurve Collections has superseded it. The practical question is whether the existing Tallyman estate can continue to operate safely and effectively for an appropriate period while the organization improves it, prepares its transition, or both.

1. Is the specific estate adequately supported? Confirm the position for the exact version, infrastructure, integrations and contractual arrangement. Avoid assuming a single product-wide support date applies to every customer.

2. Can the organization change it quickly and safely? Assess whether routine strategy, workflow, communication and reporting changes can still be delivered with proportionate effort and acceptable operational risk.

3. Can it support the organization's current requirements for the period it is expected to remain? Consider customer journeys, digital self-service, data, decisioning, controls, auditability, integration, reporting and the ability to evidence customer outcomes.

If the estate remains supported, changeable and capable of meeting requirements for its expected remaining life, targeted optimization may still create meaningful value. If those conditions are no longer met, the organization should move from tactical improvement to a structured transition plan.

What can still be improved?

A future migration is not a reason to stop improving today's operation. If Tallyman will remain in place for a further period, targeted changes can still improve customer treatment, reduce manual effort and remove unnecessary complexity. Simplifying strategies, workflows and exceptions can also reduce what later needs to be understood, mapped and recreated during migration.

A common opportunity is to simplify collections strategies and automate manual or exception-based processes that have accumulated over time. Processes such as bankruptcy, deceased, dispute or vulnerability often rely on heavy agent involvement to check and move accounts. Where the right data is available, much of that can be automated: an account can be held in a monitoring state for a defined period, moved automatically when confirmation arrives, and generate the right communications to the customer and third parties at each stage.

The value is usually seen in reduced agent effort, fewer manual hand-offs, faster and safer change, and more consistent customer treatment. We would normally quantify that against the organization's own volumes, handling time and cost base rather than apply a standard percentage saving.

Any change benefits from the same discipline: clearly defined requirements, design, training for the users affected, thorough testing, and monitoring after go-live to confirm the change delivered what was intended. Optimization is not an argument for keeping Tallyman indefinitely. It is a way to improve outcomes and reduce avoidable cost while the platform remains in service, and to make the eventual migration simpler.

When optimization is no longer enough

The strongest signals are usually operational rather than simply technical: routine changes are becoming disproportionately difficult or expensive; knowledge is concentrated in too few people; integrations or infrastructure increasingly constrain the business; support options are narrowing; or the platform prevents the organization delivering the customer journeys, controls, data, automation and decisioning it now requires. At that point, further optimization may still stabilize the operation, but it will not remove the need for a planned transition.

Planning the transition

For organizations still running Tallyman, the practical choices are usually to continue optimizing and supporting the existing estate for an appropriate period, transition to PowerCurve Collections, or move to another platform from the wider market. The right route depends on the verified support position, business requirements, target architecture, economics, delivery risk and appetite for wider operating-model change.

PowerCurve Collections succeeded Tallyman as Experian's strategic collections platform. It combines collections workflow with the wider PowerCurve approach to segmentation, decisioning and strategy management. Many organizations have already transitioned from Tallyman to PowerCurve Collections, while others continue to operate established Tallyman estates. Because it is the established successor, PowerCurve Collections will normally form part of any future-platform assessment for a Tallyman user, but it should still be assessed against the organization's requirements and credible alternatives from the wider market.

A major upgrade or replacement of an enterprise collections platform can take many months and, for complex estates, considerably longer. The duration depends on scope, data, integrations, operating-model change, testing, regulatory assurance and organizational readiness.

Clients most often underestimate how much business logic, operational knowledge, historical data, integrations and exception handling has accumulated within Tallyman over many years. The move is not simply a technical extract-and-load exercise. The aim should not be to recreate Tallyman automatically in the target platform. Existing treatments, controls and operational knowledge need to be understood, but each capability should be classified deliberately: preserve where continuity is essential, improve where the current design constrains outcomes, and retire where historic complexity no longer serves a purpose. That sits alongside detailed data mapping, reconciliation, testing, operational readiness and the need to keep the existing service stable through cutover.

Next step

If you are still running Tallyman, arum can help you establish three things: the realistic remaining life of the current estate, the improvements worth making while it remains in service, and the right route and timing for transition. The starting point is a focused review of the platform, its dependencies, support position and change priorities. Book a conversation with Matt.