Maker-checker that survives urgent payouts
Weekend settlement windows are where dual control quietly collapses. Here is how fintech treasuries keep second approval real when the clock is loud.
Every treasury policy promises dual control. The breach usually arrives as a chat message: a partner needs funds before a cut-off, the second approver is offline, and someone with both tokens “just this once” releases the file. Auditors see the exception months later; partners feel it earlier when a disputed payment cannot be reconstructed.
Hard stops beat reminders. Systems that allow a single user to initiate and release above a threshold are design failures, not training gaps. Where banking portals cannot enforce segregation, compensating controls—pre-funded corridors, delayed release batches, or call-back confirmations—need owners and evidence, not slogans.
Sample the noisy days. A clean weekday sample flatters the control. Pull Friday evenings, month-end, and the first trading day after a holiday. That is where bypasses hide.
Document residual risk in plain language. Boards accept controlled exceptions with ageing and owners. They distrust silence dressed as compliance.