Field Notes · 17 March 2026
Dual approval paths that exist only on paper
Field notes from remittance control testing where secondary approvers shared credentials or never received the queue notifications.
Policy manuals love dual approval. Production systems sometimes route both steps through one person with two logins. Remittance control testing exists to find that gap before a high-value corridor incident finds it for you.
Watch for shared mailboxes as “second eyes”
If the secondary approval lands in a team inbox, establish who is accountable when the inbox is quiet during a holiday week.
Retest after role changes
When a treasury lead leaves, dormant approver IDs often remain. Sampling old months will not catch that; include a current-state access listing in every remittance engagement.
Document emergency bypasses
Weekend liquidity events happen. What matters is whether the bypass had a post-event review and a named authoriser. Silence in the log is the finding.
See our remittance control testing engagement if you want this work scoped before peak season volumes rise.