Maker-checker design that survives busy settlement days

Maker-checker charts look tidy on paper. Live exception queues on a busy Friday tell a different story. When a payment rail drops a batch, the same person who rebuilds the file often signs the approval because the named checker is already in another call.

In our reviews we compare the written matrix to a sample of high-value or high-risk actions: manual credits, fee waivers above a threshold, and custody adjustments. We ask who performed the action, who approved it, and whether those roles can be held by the same login in practice.

A mild pattern we see in Taiwan-based fintech teams is over-reliance on chat screenshots as approval evidence. Screenshots fade; they also omit the amount that was finally posted. Prefer a dated approval record tied to the transaction reference.

Strengthening dual control rarely means buying new software. It often means narrowing who can force-post, publishing a back-up checker roster for settlement windows, and refusing to close the day until the second signature exists for every item above the threshold.

If your board asks whether dual control ‘works,’ answer with the last month’s override sample—not with the policy diagram alone.