Property
2518 Sunset Ln
Loan 10005197 · Meitav · Lutz, FL
UPB
$1.8M
Operating Summary
Current situation
—
Next action
—
Owner
—
Due date
—
Blocking issue
—
Expected recovery
—
Best bid
—
Monthly carry cost
—
Cost of delay
—
Expected time to cash
—
Risk level
—
Confidence
Low — 25 of 209 fields available from connected sources (12%)
Financial Position4/15 · Partial
UPB
$1.8M
Grand Summary · UPB · row 73
Participation %
100.0%
Grand Summary · Reigo_Participation_Percent · row 73
Outstanding balance
$1.9M
Grand Summary · Investment_To_Date · row 73
Loan amount (gross)
$2.2M
Grand Summary · LOAN_AMOUNT · row 73
Expected recovery
Expected recovery is not a column in the Grand Summary Loans list
Realized recovery
Realized recovery is not a column in the Grand Summary Loans list
Recovery %
Recovery % is not a column in the Grand Summary Loans list
Forecast
A recovery forecast is not a column in the Grand Summary Loans list
Cash expected
Cash expected is not a column in the Grand Summary Loans list
Legal spend
Legal spend is not a column in the Grand Summary Loans list
Property spend
Property spend is not a column in the Grand Summary Loans list
Protective advances
Protective advances is not a column in the Grand Summary Loans list
Recovery vs. UPB
Recovery vs. UPB is not a column in the Grand Summary Loans list
Scenario analysis
Scenario analysis is not a column in the Grand Summary Loans list
Forecast vs. actual
Forecast vs. actual is not a column in the Grand Summary Loans list
Carry Cost0/10 · Not connected
Missing cost line items are never treated as zero.
No carry-cost ledger is connected. The Prisma schema has a home for this (RecoveryExpense/ProtectiveAdvance), but no database is connected — see LOAN_COMMAND_CENTER_DESIGN.md.
Fields in this section: Monthly carry, Carry to date, Remaining carry, Line items, Cost to hold, Cost of delay, Break-even reduction, Net after carry, Carry vs. recovery, Carry vs. UPB
LMS12/15 · Partial
LMS snapshot — not live. Read-only, captured 2026-08-05; see LMS_LOAN_MATCH_REPORT.md. Original maturity date is LMS's un-updated term-of-origination field, not the loan's current maturity — see the conflict note. Legal fee signals are comment-derived, never promoted to a structured foreclosure stage.
Match status
confirmed
LMS (snapshot, not live) · match.status
Match evidence
LMS deals_input.LOAN_ID "10005197" is an exact match — LMS's own primary key.
LMS (snapshot, not live) · match.evidence
Borrower entity
Borrower BW LLC
LMS (snapshot, not live) · BORROWER_ENTITY_NAME
Borrower principal
Individual Borrower BW
LMS (snapshot, not live) · BORROWER_PRINCIPAL_NAME
Borrower FICO
BORROWER_FICO_SCORE is blank for this loan in LMS
Delinquency status
Current
LMS (snapshot, not live) · lms_read_loan_status.delinquency
General loan status
REO
LMS (snapshot, not live) · lms_read_loan_status.general
Maturity/default status
Maturity Default 120+
LMS (snapshot, not live) · lms_read_loan_status.maturity_default
Original maturity date (LMS)
2023-10-05
LMS (snapshot, not live) · LOAN_MATURITY_DATE
This is the original term only — LMS never updates it after a real extension. Never treat as current maturity.
Current maturity (Grand Summary)
2023-10-05
Grand Summary · Current_Maturity
Maturity conflict
No maturity-date conflict detected between Grand Summary and LMS for this loan.
Servicer
No payment carries a SERVICER value for this loan
Legal fee total (LMS-derived)
$2.4K
LMS (snapshot, not live) · payment_lifecycle.COMMENT (legal-fee pattern match)
Legal fee signals
5 records
LMS (snapshot, not live) · payment_lifecycle.COMMENT (legal-fee pattern match)
LMS record created
2022-10-06T16:53:36
LMS (snapshot, not live) · CREATED_DATE