Field notes
How to sample settlement batches before an examiner asks
A practical approach to sampling settlement batches for fintech audits — sizing the sample, documenting cut-offs, and keeping the binder examiner-ready.
Examiners rarely begin with your policy PDF. They ask for last Tuesday’s settlement batch, the correspondent confirmation, and the person who posted the cut-off. Sampling before that moment arrives is not theatre — it is how you learn whether your calendar actually closes.
Size the sample to volume, not comfort
If you settle daily, pulling five “clean” days teaches little. Tie the sample size to volume bands: peak days, month-end, and at least one day with known exceptions. Record why each day entered the sample so the working paper can defend the selection later.
Document cut-offs as they happened
Write the time the local book closed and the time the correspondent confirmed. Timing gaps that look minor in a dashboard become material when customer money is already moved. Fintech audits for remittance and wallet rails often fail here first.
Keep the binder boring
Each sample day should hold the same artifacts: batch summary, bank or partner statement extract, exception list, and sign-off. Fancy formatting does not help. Consistency does.
When Oak Ledger runs a Payment Control Framework Review, this sampling discipline is the first thing we agree in scoping — before anyone opens a laptop in your document room.