Field notes
Tracing wallet settlement gaps before they become findings
Settlement is where wallet narratives fray. Authorization looks clean in the product dashboard; the file that lands overnight tells a quieter story—missing merchant IDs, partial refunds that never rejoined the consumer balance, or a cutoff that shifted without a change ticket.
Start by naming the rails in scope. A single wallet often settles across card networks, bank transfers, and internal ledger books. If your population definition mixes those rails, your sample will look random and your exceptions will look mysterious.
Build a cutoff calendar
Write down when each rail claims the day ends. Then ask operations when the file actually arrives. The gap between those two clocks is where chat-thread “temporary” fixes accumulate. In our Studio settlement lab, students recreate that calendar before they touch sample selection.
Follow one exception across systems
Pick a known late settlement from the prior month. Trace it from customer complaint or monitoring alert through the ledger adjust, the vendor ticket, and the final balance. Document every handoff. Teams that skip this warm-up invent controls that exist only in policy.
What “good enough” looks like
You do not need perfection on day one. You need a workpaper that states which population was tested, which cutoff applied, which exceptions remained open, and who owns the aging. That package survives second-line review far better than a green dashboard screenshot.