A number is only as good as its history
When a balance is questioned six months later, the answer is not the number — it is the record of how the number got there. That record is the audit history, and it is what turns "trust me" into "here is exactly what happened."
What to capture on every change
| Field | Example |
|---|---|
| What changed | Interest rate |
| From → to | 10.50% → 11.25% |
| Effective date | Mar 1, 2026 |
| Entered | Mar 3, 2026 by m.delgado |
| Reason + document | Extension re-rate · Amendment-3.pdf |
Why each field earns its place
Each field answers a question someone will eventually ask. What changed and from → to reconstruct the number; the effective date decides which invoices recompute and which stay untouched; who and when assigns accountability; and the reason plus document turns a change from an assertion into evidence. Drop any one and the record still looks complete — right up until the day it has to hold up in front of a borrower, an investor, or an auditor.
Before-and-after, not just after
Storing only the new value tells you where you are, not how you got there. Keeping the prior value read-only is what lets you explain a figure without reconstructing it.
Take Harbor Mixed-Use. The rate change from 10.50% to 11.25% effective March 1 moves the month's interest:
Calculation
Before: $680,000 × 10.50% × 31 ÷ 365 = $6,064.11
After: $680,000 × 11.25% × 31 ÷ 365 = $6,497.26
The audit record shows both the term change and its effect — not a single overwritten cell that leaves you guessing why March jumped by $433.
Attention
⚠ Operational note: compare periods on the loan's actual basis and day count. Two months eyeballed with flat monthly figures hide the day-count differences that actually explain the change.
What lives outside the servicing audit
Account access, invitations, and some platform-owned activity have their own histories. The servicing audit covers operating-record changes — not everything a system does — so don't claim it captures literally everything.
Where LoanConsole fits
Covered operating-record changes are captured with the actor, timestamp, and before-and-after values. Issued documents and closed periods are preserved; corrections use a void or reissue path that retains the prior artifact.
Note
This article is operational guidance, not legal, tax, or accounting advice.