Case types determine the fields, workflows, and behavior of a case. Each case type is designed for a specific borrower situation — from collections and bankruptcy to identity theft and compliance holds. This page documents every case type, its purpose, type-specific fields, and how it is created.
Availability: All clients. Some case types are created automatically by Peach's compliance monitoring and may not be available for manual creation depending on your company's configuration. Required permissions: case:update (to create or modify cases of any type)
A borrower has filed for bankruptcy protection. This case type tracks court filing details, chapter type, and disposition through the bankruptcy lifecycle.
Auto-creation: Yes — Peach's automated bankruptcy detection creates this case when a borrower is matched to a bankruptcy filing (via LexisNexis monitoring).
| Field | Description | Values / Format |
|---|---|---|
| Court case filed date | The date the bankruptcy was filed with the court. | Date |
| Court case number | The court-assigned case number. | Text |
| Court case chapter | The bankruptcy chapter filed under. | chapter7, chapter11, chapter12, chapter13, unknown |
| Court case debtor disposition | The final disposition of the debtor's case. | dismissed, discharged, reinstated |
| Court case debtor disposition date | The date of the disposition. | Date |
| Court case last status | The most recent court status. | filed, dismissed, discharged, conversion, reinstated, closedFiledInError, closedTransferredOut, closedDischargeNA, closedUndeterminedReason |
| Court case last status updated date | When the court status was last updated. | Date |
| Court case closed date | When the court case was closed. | Date |
| Creditor claim deadline date | The deadline for creditors to file claims. | Date |
| Anticipated case completion date | The expected date for case resolution. | Date |
| Listed outstanding debt | Whether your company's debt is listed in the filing. | True / False |
A loan is overdue and in the collections process. Collection cases track delinquency metrics, contact attempts, payment history, and collections intensity. Only one active collection case is allowed per borrower.
Auto-creation: Yes — When configured, Peach automatically creates collection cases when a loan meets the overdue thresholds defined in your company's collections settings. See Collections cases.
| Field | Description | Values / Format |
|---|---|---|
| Is first time collection | Whether this is the borrower's first non-canceled collection case. | True / False (read-only) |
| Number of loans overdue or accelerated | Count of active loans with overdue or accelerated status. | Integer (read-only) |
| Days overdue | Maximum days overdue across associated loans. | Integer (read-only) |
| Total amounts | Paid, expected, and overdue amounts across associated loans. | Amounts (read-only) |
| Loans reported to bureaus | Whether associated loans have been reported to credit bureaus. | yes, some, no |
| Attempts to contact by phone | Number of attempted and successful voice interactions. | Attempted / Successful counts |
| Payment counts | Total payments and failed payments. | Total / Failed counts |
| Last successful payment | Amount and date of the most recent successful payment. | Amount + Date |
| Next payment | Amount and date of the next expected payment. | Amount + Date |
| Collection reach-outs | Interaction intensity tracking against period-based limits (7-day, 30-day windows). | Capacity / Contact counts |
A borrower has formally requested that your company stop contacting them. This case tracks when the notice was received and ensures compliance with the request.
Auto-creation: No.
| Field | Description | Values / Format |
|---|---|---|
| Notice received date | The date the cease communication request was received. | Date |
A borrower disputes information reported to credit bureaus. This case tracks the dispute investigation and resolution.
Auto-creation: No.
A borrower has requested validation of the debt. This case tracks the request date and the borrower's state of residence, which affects validation requirements.
Auto-creation: No.
| Field | Description | Values / Format |
|---|---|---|
| Request date | The date the debt validation request was received. | Date |
| Current state of residence | The borrower's current state. State-specific rules may affect validation requirements. | 2-character state code |
| New York state city | If the borrower resides in New York, the specific city. Certain cities have additional requirements. | newYorkCity, yonkers, other, or blank |
A borrower has been reported as deceased. This case tracks the deceased individual's information and the estate representative contact.
Auto-creation: Yes — Peach's automated deceased detection creates this case when a borrower is matched through the monitoring service.
| Field | Description | Values / Format |
|---|---|---|
| Deceased first name | First name of the deceased. | Text |
| Deceased last name | Last name of the deceased. | Text |
| Deceased middle name | Middle name of the deceased. | Text |
| Deceased address | Address of the deceased (street, city, state, ZIP code). | Address fields |
| Date of death | The reported date of death. | Date |
| Date of birth | The deceased's date of birth. | Date |
| Exact date of death unknown | Whether the exact date of death is uncertain. | True / False |
| Representative of estate contact | Contact ID for the estate representative. | Contact ID |
A borrower disputes the validity or amount of the debt itself (as opposed to a credit bureau dispute about reporting).
Auto-creation: No.
A borrower disputes a specific purchase transaction (relevant for line of credit loans with purchase activity).
Auto-creation: No.
A borrower is affected by a federally declared emergency (such as a FEMA disaster). This case type is used with supercases that manage impacts across multiple borrowers.
Auto-creation: Created via supercase population commit when a FEMA-related supercase is established.
| Field | Description | Values / Format |
|---|---|---|
| Disaster ID | Reference to the FEMA disaster declaration. | Disaster ID |
A borrower reports that their identity has been stolen and used to open or access the loan account. This case tracks the report and investigation.
Auto-creation: No.
| Field | Description | Values / Format |
|---|---|---|
| Report received date | The date the identity theft report was received. | Date |
| Claim rejected reason | If the identity theft claim was denied, the reason. | requestedInformationNotReceived, invalidDocumentation, insufficientDocumentation, householdResponsible, namedOnAccount, other |
Legal proceedings related to the loan account. This case tracks key legal dates.
Auto-creation: No.
| Field | Description | Values / Format |
|---|---|---|
| Legal action initiated date | The date legal action was initiated. | Date |
| Legal judgment effective date | The date a legal judgment takes effect, if applicable. | Date |
A borrower is on active military duty and eligible for protections under the Servicemembers Civil Relief Act (SCRA). This case tracks duty dates, service details, and eligibility scope.
Auto-creation: Yes — Peach's automated SCRA detection creates this case when a borrower is matched through the DMDC (Defense Manpower Data Center) database.
| Field | Description | Values / Format |
|---|---|---|
| Member of Pennsylvania National Guard | Whether the borrower is a PA National Guard member (additional state protections may apply). | True / False |
| Claiming SCRA rights | Whether the borrower is claiming SCRA protections. If false, the borrower is waiving SCRA rights. | True / False |
| On-duty protection eligibility | The scope of duty protections. | federal, state, federalAndState |
| Duty start date | The date active duty begins. | Date |
| Duty end date | The date active duty ends. Blank if ongoing. | Date |
| Duty service match date | The date Peach matched the borrower to a service record. | Date (read-only) |
| Duty service component | The military service component code. | Text |
| Duty service component description | A description of the service component. | Text |
| Duty certificate ID | The certificate or reference number for the duty verification. | Text |
| Duty certificate file | An attached certificate file. | File reference |
A borrower appears on the Office of Foreign Assets Control (OFAC) sanctions list. This case type is for compliance tracking when a match is detected.
Auto-creation: Yes — Peach's automated OFAC detection creates this case when a borrower is matched against the OFAC sanctions list.
| Field | Description | Values / Format |
|---|---|---|
| OFAC actions required | The compliance actions required in response to the match. | Array of action values |
A general-purpose case type for situations that do not fit a specific category. Generic cases support a custom name and custom fields defined by your company's case type configuration.
Auto-creation: No.
Generic cases have no predefined type-specific fields. If your company has configured custom field schemas on the generic case type, those fields appear in the case detail view.
Any case type can have custom fields defined through the Peach API. Custom field schemas specify the field name, display order, data type (integer, real, string, boolean, dateTime), and length. Custom fields appear alongside the type-specific fields in the case detail view.