Client impact · Distressed assets

Legal and valuation staff stop rebuilding the recovery file

In distressed work the facts are scattered: claim documents with external counsel, recovery progress with regional teams, valuation assumptions with one analyst. We did three things: built a claim-level register that expands, moved valuation inputs into a reviewed table, and tied every recovery action, cost and cash receipt back to the same claim.

Client anonymised by defaultAMC and distressed-asset systemsFunction / data / field permissionsPrivate cloud · intranet deployment

The institution

Buy the pool, hold the claims, work the exit

The capital is own funds layered with bank facilities and structured co-investment. The chain runs acquisition — holding — resolution: pool bidding, claim and collateral administration, recovery, restructuring, litigation and enforcement, transfer and write-off. Four lines share the work: group asset management, regional teams, legal, and finance.

The files were complete; the facts were not retrievable. Diligence reports, valuation reports and litigation bundles sat in the archive or on a shared drive. What did not exist anywhere was a single queryable line saying what this claim is now worth, on what security, at what stage of proceedings, under which recovery assumption.

The constraints are hard: five-tier classification and impairment face audit and shareholder reporting, acquisition pricing needs a reproducible basis, and every step in resolution has to point at a document — or nobody can explain who decided what.

Before the change: where the effort went

This describes the work and how it was consumed, with no percentage for resolution time. The compressible part of the cycle can only be measured from the node history of pools you already manage — and the pace of court procedure is not ours to compress.

StepWho carried itHow the effort was spentWhy it never closed
Pool diligenceRegional team, external counsel, valuersClaim terms, collateral, litigation stage and enforcement progress held by three parties; gaps chased by phone; conclusions not provable claim by claimNo template and no owner per checklist item, so large pools get sampled and unsampled names are silently read as safe
Valuation and pricingOne analyst’s modelRecovery assumptions, resolution horizon, collateral haircuts, costs and taxes set by judgement; acquisition and resolution cases computed twiceParameters outside the ledger meant the same pool produced two answers, with nobody able to say which was wrong
Recovery processRegional team and legalVisits, filings, enforcement, settlements and outsourced actions recorded in weekly prose; costs in the expenses system; cash hard to attach to a claimActions, documents and approvals never formed a loop, so progress could not be totalled and responsibility could not be traced
Classification and reportingFinance and riskFive-tier classification set by hand, with impairment, supervisory and shareholder bases diverging; rework concentrated in the reporting windowReclassification carried no workflow and no stored rationale, so every variance had to be explained verbally

The judgement

Build the claim file before you talk about resolution speed

The unit of modelling in distressed work is the claim, not the pool. A pool decomposes into names, each carrying security, guarantors, several rounds of proceedings, extensions and partial recoveries. Keep the book at pool level and you can never answer "what is this name worth now, and on what basis".

So the register is built at claim level — collateral, guarantors and court nodes attach to the name, and the pool becomes a view over those names.

  • The register’s smallest unit is the claim
  • Assumptions stored beside the conclusion
  • Action, document and approval together make a trace
  • Reclassification keeps history instead of overwriting

Three steps we took

Open the file, table the inputs, close the loop

None of the three steps changes who holds pricing or investment authority. They only make the basis of those decisions retrievable.

01 · Register

One file per claim

Pool, project and claim become three object levels. Each claim carries principal and interest balances, security and collateral, litigation and enforcement stage, and limitation status. Diligence checklists are templated, so a gap shows up as outstanding rather than vanishing.

  • Deliverable: claim register and diligence checklist
  • Deliverable: gap board
  • Reviewed by: regional head and legal

02 · Parameters

Valuation inputs become records

Recovery assumptions, resolution horizon, collateral haircuts, costs and taxes enter a versioned parameter table shared by the acquisition case and the resolution case. Each valuation goes through a second reviewer.

  • Deliverable: valuation parameter ledger
  • Deliverable: four-eyes review log
  • Reviewed by: risk and the pricing authority

03 · Loop

Actions and cash land on the claim

Every visit, filing, enforcement step, settlement and outsourced action is stored as an action with its documents; costs and recoveries post against the specific claim. Reclassification runs through a workflow that keeps the rationale and the previous value.

  • Deliverable: resolution action register
  • Deliverable: reclassification workflow
  • Reviewed by: finance and compliance

Modules and counterparties in this scenario

Module names follow the company’s published product list; how the platform meets finance and case-management systems is settled in the assessment and the technical annex.

AMC business systemDistressed asset systemDebt trading and issuance systemOA and approval workflowVDR document repositoryPortfolio and fund risk monitoringRisk model judgementDesktop behaviour monitoringFunction / data / field permissionsPrivate cloud / offline intranet

Acceptance measures

Same formulas, read as operations — finance — filings

Three of the four published measures apply here. In the consistency formula the tiers are read as operations register — impairment accounting — external filing; alert precision is assessed on asset-status and limitation-period warnings. The formulas themselves are not edited.

How we recomputed them here

MeasureCalculation (as published)Recomputation in this engagementSample and timing
Definition consistencyShare of identical metrics where the three tiers agree with zero varianceFour metrics — claim balance, interest accrual, collateral value, cash recovered — compared across operations, accounting and the filed pack; a variance closes only when explained by date, impairment policy or definitionStratified across live pools, including written-off and partly resolved ones, not only newly acquired paper
Manual fallback hoursOvertime hours during filing season ÷ people involved, from system-captured effortCounted only for attaching recoveries to claims, reclassification work and reporting rework, from logged effort rather than recollectionReported for two consecutive reporting periods, separate from implementation hours
Alert precision on reviewShare of triggered warnings confirmed as real risk by the businessLimitation, collateral-status and obligor-distress alerts each store an owner and a conclusion; misses are listed separately so "no false positives" is never read as "no misses"Reported by alert class across two full quarters
Resolution capability is not decided at the negotiating table. It is decided by whether you can state a claim’s balance, security and last action inside ten minutes.Catalpa delivery methodology

500+

institutions served on the platform (company disclosure, not this client)

5.6RMB tn+

assets covered (RMB, platform book basis)

10+

years of investment-sector experience (company basis)

15

offices nationwide, delivery near the client

Where this approach does not apply

Teams that flip single names or bridge positions without holding claims over time do not need a claim register; a structured diligence template is enough. And where resolution is fully outsourced and process data cannot be brought back, the platform can only record the mandate and the outcome, so the trace benefit is thin. In that case we first write the action and document requirements into the outsourcing agreement, then discuss the system.

Questions specific to distressed-asset delivery

Mechanism answers. They commit to nothing about recovery outcomes, court progress or audit conclusions.

How far back do you backfill pools already under management?
Only until the current position is explainable: live principal and interest, security and collateral status, open litigation and enforcement, and the latest valuation conclusion. Fully resolved or written-off pools are not backfilled; they keep an archive index. Historical values the business cannot confirm are marked not comparable and excluded from the base for classification and impairment. The backfill list is agreed pool by pool before go-live, so gaps are handled as scope rather than absorbed as legacy noise.
Where does litigation and enforcement progress come from? Can it be pulled automatically?
From legal staff and appointed counsel, entered at each node, with the document — acceptance notice, ruling, enforcement receipt — attached to the claim. We do not promise connections to court or registry systems and we advise against writing such an obligation into a contract: in practice the reliable source is still a person. What the platform changes is that who entered what, and when, becomes visible, chaseable and measurable.
Downgrading a classification hits people’s bonuses. How do you stop the book being flattered?
Three controls. Reclassification runs through a workflow with a rationale that cites the valuation parameter version and the action history; previous classifications stay visible rather than being overwritten; and reports show classification alongside impairment, forcing a written reason where the two diverge. The system cannot make the classification judgement and does not police performance targets — it does turn flattering into a traceable act.
What is the relationship to accounting and the case-management archive? Do they get replaced?
Neither is replaced. Accounting holds accounts, vouchers and impairment; the case archive holds document originals; the asset register holds the business facts of the claim. The delivery joins them through one claim identifier and shared document references, so finance drills down to the business basis and operations sees the booked result — instead of merging two ledgers into one.
Outsourced recovery agents are not on staff. How are they traced?
A minimum action set is required: appointment, contact, visit or legal step, recovery, closure — each with its document, costs and cash posted against the claim, acceptance judged on collected money and a stated outcome. Percentage-complete prose in a weekly report is not accepted. External agents are not given internal accounts: they come in through a portal or a delegated submission entry, with permissions isolated at claim level and every action logged.
Does any of this actually shorten the resolution cycle?
Depends which segment. Court timetables, auction pace and an obligor’s ability to pay sit outside the software, and anyone promising to compress that deserves scepticism. What compresses is internal waiting: finding documents, rebuilding models, routing approvals, aligning classification with impairment. That is why our acceptance measures here are manual fallback hours and filing cycle, and why no percentage for resolution time appears on this page.

Next step

Take one pool you are holding right now

In a 45-minute assessment we work that pool live: which fields are missing, which assumptions were never tabled, where the trace breaks — then the order in which claim registration should precede classification closure.