A goneaway ledger is the collection of accounts a lender has coded as untraceable, non-responsive, or no known assets, and which are now sitting dormant ahead of write-off or sale. In our experience, a meaningful proportion of those accounts are not unrecoverable at all. They are unverified, and the two are routinely confused.
The word describes a process outcome, not a financial finding. An account is usually coded goneaway when correspondence is returned, contact attempts fail, and a credit reference trace produces no new address. Each of those steps is reasonable. None of them establishes that the customer cannot pay.
What the code actually records is that the lender's existing contact route stopped working. It says nothing about the customer's current address, current employment, current assets, or current circumstances. That distinction sounds academic until you consider what happens next: the account stops receiving activity, the balance ages, and eighteen months later it is written off or sold at a fraction of face value on the strength of a conclusion nobody tested.
Across twenty five years of reviewing dormant books, the same four causes appear repeatedly.
The trace produced a stale address. Credit reference data lags reality, frequently by up to ninety days and sometimes considerably longer. A customer who moved after their last credit application leaves a footprint that has not caught up. Any visit or correspondence sent to that address tested the wrong doorstep, and the nil return that followed was accurate about the address and meaningless about the customer.
The assets were never visible from a credit file. Employment and income, property held in another capacity, a vehicle registered elsewhere, a directorship generating drawings. None of these appear on a standard trace, and their absence from one proves nothing.
The person was traced but the assets never were. These are two separate exercises, and in a high proportion of dormant files only the first was ever commissioned. The account was closed on the basis of a question nobody asked.
The file simply went cold. Coded goneaway, moved to a dormant queue, and left. Circumstances change considerably in eighteen months. Customers move into work, inherit, sell property, or reach a point where they want the matter resolved. None of that reaches a file nobody is looking at.
A dormant book review is a different exercise from tracing individual accounts, and it is normally run in three stages.
Stage one: segmentation. Not every dormant account justifies the same spend. The book is segmented by balance, age, security, last verified contact, and the reason the account went quiet. This produces a priority tier that warrants full investigation, a middle tier suited to batch desktop tracing, and a residual tier where the honest answer is that pursuit is uneconomic. Telling you which accounts are in that last group is part of the job.
Stage two: batch verification. The priority and middle tiers are run through desktop tracing against multiple data sources simultaneously, rather than the single-source check that produced the original nil return. Cross-referencing Credit Reference Agency data, electoral roll information, Companies House records, Land Registry, DVLA, specialist proprietary databases, and OSINT identifies patterns that no individual source shows on its own. Each confirmed address is supported by at least two independent sources and carries a confirmation date.
Stage three: asset and circumstance assessment. For the accounts that verify, the question becomes what is recoverable and by what route. Identified property interests, vehicles, employment or self-employment, and directorships each point to a different enforcement or re-engagement strategy. Where genuine hardship or vulnerability is identified, that is a finding too, and it should stop enforcement spend rather than trigger it.
The output of a ledger review is not a list of addresses. It is a decision framework covering four groups of accounts: those that verify and support enforcement; those that verify and are better suited to structured re-engagement; those where genuine inability to pay is established, which protects you under Consumer Duty and stops further cost; and those that remain genuinely untraceable, which after a proper investigation is a defensible write-off rather than an assumed one.
That last category matters more than it appears. Writing off an account you have tested is a commercial decision. Writing off an account you have not tested is a guess that happens to be recorded as a decision.
There is a compliance dimension to this that is easy to miss. Under the FCA Consumer Duty, lenders are expected to deliver good outcomes and avoid foreseeable harm. An account left dormant for two years, with interest or charges accruing and no attempt made to establish whether the customer is in difficulty, is not obviously an example of good customer support.
A properly conducted ledger review addresses both sides at once. It identifies the customers who can pay and the ones who genuinely cannot, and it documents which is which. That record is as valuable to your compliance position as the recoveries are to your balance sheet.
We recommend a dormant ledger review at four points: ahead of any scheduled write-off run; before a portfolio sale, where verified accounts materially affect the price you achieve; at the point of any acquisition, where an inherited book has been managed to an unknown standard; and annually as routine hygiene on any book with a material dormant population.
We have been recovering value from other people's closed files since 1999. Across more than seventy institutional clients we have recovered over 97 million in assets, with a 91.7% success rate across trace, serve, and recovery, and a meaningful share of that has come off accounts another firm had already given up on.
That is not luck, and it is not a claim that every dormant account is recoverable. Most books contain accounts that are genuinely finished. The point is that nobody knows which ones until somebody looks past the credit footprint.
Before your next write-off run, two questions are worth putting to your team. How many of those nil returns were genuinely tested rather than inherited? And how many of them rest on an address nobody has verified since the file went quiet?
If you would like an honest answer on your own book, Towerhall Solutions will review a sample of dormant accounts and tell you what is realistically there. Contact our team for a confidential conversation.
