Case Lifecycle
Understanding how cases progress through Debitura's collection process from submission to resolution.
Overview
Every debt collection case goes through a series of stages, from initial submission to final resolution. This lifecycle ensures systematic and effective debt recovery while maintaining compliance and transparency.
Lifecycle Stages
1. Lead / Quote (Optional)
Status: lead
Before formally submitting a case, you can request a quote to understand:
- Estimated collection success probability
- Expected fees and costs
- Recommended collection strategy
- Timeline expectations
Typical duration: Instant to 24 hours
Actions available:
- Request detailed quote
- Submit case
- Decline to proceed
Next stage: Case Submission
2. Case Submission
Status: submitted
The creditor submits a case to Debitura with:
- Creditor information
- Debtor information
- Invoice details and documentation
- Any relevant communications or notes
Typical duration: Instant
System actions:
- Validate case data
- Generate case ID
- Create event log
- Trigger webhooks
Next stage: Verification
3. Verification
Status: verifying
Debitura reviews the case to ensure:
- Complete and accurate information
- Valid debt documentation
- Compliance with legal requirements
- Collectability assessment
Typical duration: 1-2 business days
Possible outcomes:
- Approved: Case moves to Active
- Rejected: Case cannot be collected (reason provided)
- Information needed: Creditor must provide additional details
Next stage: Active, Rejected, or back to Submitted (if more info needed)
4. Active Collection
Status: active
The case is actively being worked on. Collection activities include:
- Friendly reminders to debtor
- Phone calls and emails
- Payment plan negotiations
- Settlement discussions
Typical duration: 30-90 days (varies by jurisdiction and case complexity)
Sub-statuses:
active.initial_contact- First outreach attemptsactive.negotiating- Discussing payment termsactive.payment_plan- Debtor on agreed payment scheduleactive.escalated- Preparing for legal action
Possible outcomes:
- Payment received (full or partial)
- Payment plan established
- Settlement agreed
- Escalation to legal action
- Suspension requested
- Debtor bankruptcy/insolvency
Next stages: Collected, Escalated, Suspended, or Closed
5. Escalated (Legal Action)
Status: escalated
When friendly collection attempts fail, the case escalates to legal proceedings:
- Court filings
- Judgment enforcement
- Asset seizure
- Garnishment orders
Typical duration: 3-12 months (jurisdiction dependent)
Sub-statuses:
escalated.filing- Preparing court documentsescalated.litigation- Active court proceedingsescalated.judgment- Court judgment obtainedescalated.enforcement- Enforcing judgment
Costs: Legal fees apply (may be recoverable from debtor)
Next stages: Collected, Suspended, or Closed
6. Suspended
Status: suspended
Case collection activities are temporarily paused due to:
- Creditor request
- Debtor dispute
- Bankruptcy proceedings
- Court injunction
- Missing information
Typical duration: Variable (until resolution)
Actions available:
- Resume collection
- Close case
- Update case information
Next stages: Active, Escalated, or Closed
7. Collected
Status: collected
The debt has been fully or partially recovered.
Sub-statuses:
collected.full- 100% of debt recoveredcollected.partial- Less than 100% recoveredcollected.settlement- Agreed reduced amount paid
System actions:
- Calculate fees and costs
- Process payout to creditor
- Update financial records
- Send confirmation webhooks
Next stage: Closed
8. Closed
Status: closed
The case has reached a final state and no further action will be taken.
Closure reasons:
closed.collected- Debt fully recoveredclosed.partially_collected- Partial recovery, case closedclosed.uncollectible- Deemed impossible to collectclosed.debtor_deceased- Debtor passed away, no estateclosed.bankruptcy- Debtor bankrupt, case dischargedclosed.disputed- Creditor dispute, case withdrawnclosed.error- Case submitted in errorclosed.creditor_request- Creditor requested closure
Payout processed: If any amount collected
Records retained: For audit and compliance purposes
Lifecycle Diagram
Lead/Quote (optional)
↓
Submitted
↓
Verifying → Rejected
↓
Active ←→ Suspended
↓
Escalated ←→ Suspended
↓
Collected
↓
Closed
Status Transitions
Allowed Transitions
| From Status | To Status | Trigger |
|---|---|---|
lead | submitted | Case submitted by creditor |
submitted | verifying | Automatic system transition |
verifying | active | Verification approved |
verifying | rejected | Verification failed |
verifying | submitted | Information requested |
active | collected | Payment received |
active | escalated | Legal action initiated |
active | suspended | Suspension requested/required |
active | closed | Case closed without collection |
escalated | collected | Payment received |
escalated | suspended | Legal proceedings paused |
escalated | closed | Case closed without collection |
suspended | active | Case resumed |
suspended | escalated | Legal action resumed |
suspended | closed | Case closed while suspended |
collected | closed | Payout processed |
Timeline Expectations
Typical Case Durations
| Scenario | Expected Timeline |
|---|---|
| Simple B2C debt, cooperative debtor | 30-45 days |
| B2C debt, unresponsive debtor | 60-90 days |
| B2B debt, payment plan | 90-180 days |
| B2B debt with legal action | 6-12 months |
| Cross-border collection | 90 days - 18 months |
Factors affecting duration:
- Debtor cooperation
- Debt amount
- Jurisdiction
- Case complexity
- Legal requirements
- Collection partner workload
Monitoring Case Progress
Via API
GET /v1/cases/{case_id}
Response includes:
- Current status
- Status history with timestamps
- Last activity date
- Next scheduled action
- Amount collected to date
Via Webhooks
Subscribe to status change events:
case.status_changedcase.payment_receivedcase.escalatedcase.closed
Via Portal
Monitor case progress visually:
- Status timeline
- Activity feed
- Payment history
- Document uploads
- Communications log
Best Practices
For Creditors
- Provide complete information upfront - Reduces verification time
- Respond quickly to information requests - Prevents delays
- Keep documentation organized - Speeds up escalation if needed
- Monitor webhook events - Stay informed of progress
- Don't suspend unnecessarily - Reduces collection success rates
For Integration Partners
- Handle all status values - New statuses may be added
- Store status history - Don't just track current status
- Implement webhook handlers - For real-time updates
- Poll API sparingly - Use webhooks instead
- Map statuses to user-friendly labels - In your UI
Next Steps
- Learn about payments and payouts
- Understand pricing and fees
- Explore webhooks and events