How to read a seller's payment ledger

Sellers often attach a servicer payment history to a listing, and it's the single most useful document in the package: actual posted payments, actual late charges, an actual balance. It is also the document most often over-read. Three rules.

Rule 1 — a ledger verifies only what it covers

A ledger that ends in September proves nothing about October. If the listing claims a payment more recent than the ledger's final entry, that claim is unsubstantiated — outside anything the document covers. That is different from contradicted: the ledger doesn't disprove the claim, it simply fails to support it. The honest response is to demand servicing history through the present before pricing the note as current.

Rule 2 — dates disagree for boring reasons and bad ones

A few days' difference between the listing's “last payment” and the ledger's is usually posting-versus-effective-date noise. A gap measured in months is not a posting artifact — it means the ledger ends before the claimed payments, and the claim needs current evidence. Never let a friendly explanation stretch to cover a 22-month gap.

Rule 3 — the pattern is evidence too

Two borrowers can both be “current” while one has paid on the first of the month for five years and the other attracts a late charge nearly every cycle. The second note carries real collection friction that a status field never shows. Read the pattern, not just the last row — chronic lateness belongs in your pricing even when the status reads performing.

What this looks like in practice

• Check the ledger's final entry date against the listing's claimed last payment — first, every time.
• Treat a covered-and-consistent ledger as substantiation; a stale one as an open question with a named resolver (the servicer).
• Scan for late charges and reversals — the pattern prices the note.
• Remember the ledger is the seller's attachment: confirm against the full servicing file before closing.