Entity

Collections Case

The tracking record for each delinquent account under collection — containing delinquency amount and age, contact attempts, payment arrangements, workout options considered, and the resolution outcome that determines loss recognition.

Last updated: February 2026Data current as of: February 2026

Why This Object Matters for AI

AI cannot optimize collection strategies without structured case data; without it, 'which collection approach works best for this type of borrower' relies on collector intuition rather than systematic analysis.

Credit & Lending Operations Capacity Profile

Typical CMC levels for credit & lending operations in Financial Services organizations.

Formality
L3
Capture
L3
Structure
L2
Accessibility
L2
Maintenance
L2
Integration
L2

CMC Dimension Scenarios

What each CMC level looks like specifically for Collections Case. Baseline level is highlighted.

L0

Collections cases exist only as verbal handoffs between loan officers and collections staff. When a borrower misses payments, the branch manager mentions it in a morning meeting or sends a quick email to the workout team. There is no written case record — the collector relies on memory, sticky notes, or personal notebook entries to track which delinquent borrowers they have contacted and what was discussed. If the assigned collector is absent, no one knows which accounts are in active workout, what promises to pay were made, or whether any skip-tracing efforts are underway. Charge-off decisions are made based on the collector's verbal summary to a supervisor, with no documented trail of collection activity. Regulatory examiners asking for collections activity logs receive apologetic explanations that records were not kept. When borrowers dispute the collection timeline or claim they were never contacted, the institution has no evidence to support or refute those claims. Recovery rates are unknown because no one tracks the progression from delinquency through resolution.

None — AI cannot assist with collections prioritization, contact scheduling, or recovery prediction because no machine-readable collections case record exists.

Create any written record for each delinquent loan workout — even a spreadsheet row capturing borrower name, loan number, days past due, last contact date, and current status.

L1

Collections cases are tracked in personal spreadsheets or shared Word documents maintained by individual collectors. Each collector has their own format — one might track by borrower name and phone number, another by loan number and last contact date. When a supervisor asks for the total number of active workout cases, collectors manually count their rows and report back. Promise-to-pay agreements are noted in free-text comments like 'borrower said they will pay $500 by Friday' with no standardized fields for amount, date, or follow-up action. Skip-tracing results appear as notes such as 'tried new number, no answer.' Charge-off recommendations are written in emails to the credit officer with varying levels of detail. Some collectors maintain excellent personal records; others have gaps spanning weeks. There is no way to see the full collections pipeline or assess whether the team is following consistent contact strategies across all delinquent accounts. Charge-off timing is inconsistent because there is no documented standard for when a delinquent loan should be written off versus continued in workout. Different collectors apply different thresholds based on personal experience, and the institution cannot demonstrate a consistent loss recognition practice to examiners. The lack of formality means that similar delinquent accounts receive different treatment depending on which collector is assigned.

AI could scan collector spreadsheets for keywords like 'promise to pay' or 'charge-off,' but cannot reliably extract structured payment commitment data or calculate portfolio-level delinquency trends from inconsistent free-text formats.

Standardize the collections case template with required fields — loan ID, borrower contact information, delinquency bucket, last contact date, contact outcome code, promise-to-pay amount and date, assigned collector, and case status.

L2

Collections cases follow a standardized template with consistent sections: borrower identification, loan details, delinquency classification, contact history log, promise-to-pay commitments, and case status. Every collector uses the same form, and required fields are enforced before a case can be updated. The template includes dropdown menus for contact outcome codes such as 'right-party contact,' 'left message,' 'wrong number,' and 'promise to pay.' However, the case record lives as a document in a shared network drive or a basic tracker rather than a purpose-built collections system. Supervisors can review individual case files but cannot easily query across all cases to find, for example, every account with a broken promise-to-pay in the last thirty days. Charge-off packages are assembled manually by copying information from the case template into a separate recommendation form. The collections framework provides clear escalation paths from early-stage delinquency through late-stage workout to charge-off or recovery. Each stage has defined entry criteria, required documentation, and expected timelines. Collectors can quickly determine where any account stands in the lifecycle and what actions are required next. Management reporting draws directly from the structured case data to produce regulatory call report figures and internal loss forecasting.

AI can search and retrieve collections case documents by borrower name or delinquency bucket, but cannot programmatically aggregate promise-to-pay fulfillment rates or identify collectors with the highest right-party contact ratios without manual data extraction.

Move collections case records from document-based templates into a collections management system where each field — contact outcome, promise amount, skip-trace result, charge-off recommendation — is stored as a discrete queryable value.

L3Current Baseline

Collections cases are managed in a dedicated collections system with discrete fields for borrower demographics, loan details, delinquency aging bucket, contact attempt log with timestamps, contact outcome codes, promise-to-pay records with amount and target date, skip-tracing results, and workout strategy assignment. The system enforces mandatory documentation before status transitions — a collector cannot mark a case as 'resolved' without entering a resolution code and payment confirmation. Each case carries a unique identifier linked to the originating loan record. Supervisors run daily reports showing cases by aging bucket, contact attempts per case, promise-to-pay pipeline, and charge-off queue. The system timestamps every action, creating an audit trail that satisfies examiner requests for collections activity documentation. The collections framework provides clear escalation paths from early-stage delinquency through late-stage workout to charge-off or recovery. Each stage has defined entry criteria, required documentation, and expected timelines. Collectors can quickly determine where any account stands in the lifecycle and what actions are required next. Management reporting draws directly from the structured case data to produce regulatory call report figures and internal loss forecasting.

AI can prioritize the collections queue by scoring accounts based on delinquency severity, payment history patterns, and contact success rates. Automated dialer integration can schedule outbound calls based on optimal contact time analysis. Promise-to-pay tracking with automated reminder generation is feasible.

Add formal entity relationships linking each collections case to the originating loan, borrower's other accounts, collateral records, prior workout history, and regulatory hold flags — creating a traversable graph from delinquency through resolution.

L4

Collections cases are schema-driven entities with explicit relationships to the originating loan, borrower profile, collateral valuation records, prior workout history, bankruptcy filings, and regulatory compliance flags. Each case carries a machine-readable workout strategy tree showing which interventions were attempted, in what sequence, and with what outcomes. The system understands that a 90-day delinquent commercial real estate loan with declining collateral value requires different treatment than a 30-day delinquent consumer auto loan. An AI agent can query 'show all cases where the borrower has broken two or more promise-to-pay commitments and the collateral LTV now exceeds 100 percent' and receive a structured result set with recommended next actions. Charge-off analysis includes net present value calculations of recovery scenarios. The institution can demonstrate to regulators and auditors that every delinquent account follows a consistent, policy-driven lifecycle from initial delinquency notification through final resolution. Cross-portfolio analysis reveals which workout strategies produce the best recovery rates for different borrower segments, property types, and delinquency causes. The formalized framework has reduced average time-to-resolution and improved net recovery rates measurably.

AI can generate dynamic workout strategy recommendations based on borrower behavior patterns, collateral trends, and recovery probability models. Automated settlement offer generation with authority-level routing and regulatory compliance checks is possible.

Implement adaptive case schemas that auto-extend based on loan product type, jurisdictional requirements, borrower behavior signals, and real-time collateral market conditions without manual template reconfiguration.

L5

Collections case records are living entities that self-assemble from loan servicing feeds, payment processing systems, credit bureau updates, collateral monitoring services, and regulatory rule engines. When a loan crosses a delinquency threshold, the system automatically instantiates a case record, populates it with borrower contact history from across all relationships, pulls current collateral valuations, checks for bankruptcy filings and regulatory holds, and assigns an initial workout strategy based on the institution's current loss mitigation policies. The case schema adapts dynamically — when new regulations modify collections contact frequency limits or when the institution adjusts its charge-off timing policies, case validation rules and workflow triggers update automatically. The collections case is a real-time reflection of the borrower's workout status against current institutional policy and market conditions, continuously enriched by external data feeds. The institution can demonstrate to regulators and auditors that every delinquent account follows a consistent, policy-driven lifecycle from initial delinquency notification through final resolution. Cross-portfolio analysis reveals which workout strategies produce the best recovery rates for different borrower segments, property types, and delinquency causes. The formalized framework has reduced average time-to-resolution and improved net recovery rates measurably.

Fully autonomous early-stage collections management is possible. AI can execute contact strategies, negotiate payment arrangements within delegated authority, escalate complex cases with full context packages, and optimize portfolio-level recovery rates through continuous strategy refinement without human intervention for standard delinquency scenarios.

Ceiling of the CMC framework for this dimension.

Capabilities That Depend on Collections Case

Other Objects in Credit & Lending Operations

Related business objects in the same function area.

Loan Application

Entity

The submission record for each credit request — containing applicant information, loan purpose, requested amount and terms, supporting documents, underwriting status, and the decision timeline from submission through approval or decline.

Loan Account

Entity

The master record for each funded loan — containing principal balance, interest rate, payment schedule, collateral details, covenant requirements, payment history, delinquency status, and the modification history that tracks restructurings.

Collateral Record

Entity

The managed inventory of assets pledged as loan security — containing collateral type, appraised value, valuation date, lien position, insurance status, and the relationship to the loan accounts it secures.

Covenant Compliance Record

Entity

The tracking record of borrower compliance with loan covenants — containing covenant definitions, testing frequency, compliance calculations, breach history, and the waiver requests that document exceptions granted.

Underwriting Policy

Rule

The codified credit criteria that govern loan approvals — including minimum credit scores, debt-to-income limits, loan-to-value thresholds, documentation requirements, and the exception authority matrix for out-of-policy loans.

Pricing Model

Entity

The calculation framework that determines loan pricing — containing base rate indices, credit spreads by risk grade, fee structures, relationship discounts, and the competitive pricing adjustments that balance profitability with market share.

Loan Modification Decision

Decision

The recurring judgment point where workout specialists evaluate whether to modify loan terms for distressed borrowers — weighing borrower hardship, recovery probability, modification economics, and investor guidelines to determine the optimal restructuring approach.

What Can Your Organization Deploy?

Enter your context profile or request an assessment to see which capabilities your infrastructure supports.