How Control and Audit Models Adapt to Always-on Payment Settlement
Teresa Cameron, CEO of Clear Junction
When payments begin to settle outside traditional banking hours, organisations have to decide which controls must be resolved before execution and which can still rely on review after the fact. That decision is rarely straightforward, and it affects audit, operations and risk teams differently depending on the rail involved. In batch-based environments, this tension has traditionally been managed through sequencing. Transactions are processed, records are reconciled later, and issues are investigated with the expectation that there is still time to intervene before balances are treated as final. That approach holds when settlement follows predictable windows and exceptions can be addressed before positions are locked in. As settlement cycles shorten or extend beyond those windows, that approach becomes harder to rely on. If a payment completes quickly, or outside standard processing hours, there is less opportunity to correct issues after execution without creating knock-on effects in downstream processes. Controls that once sat comfortably downstream start to move closer to the point where value changes hands.
Where control placement becomes contested
Under these operating conditions, practical disagreement often emerges between audit, operations and risk teams. Compliance functions emphasise consistent application of policy across timing and channel. Operations teams focus on keeping flows moving without unnecessary interruption. Audit teams look for clear evidence that decisions were taken in line with policy and can be reviewed later with confidence. Each perspective is grounded in legitimate concerns, yet they often lead to different conclusions about where controls should sit. What develops in response is a selective approach to control placement. Certain checks are resolved prior to execution because later correction would be impractical or disruptive. Others remain subject to review after the fact, provided the implications of delay are understood and accepted. The challenge lies in drawing this boundary in a way that holds across different rails and settlement models.
Evidence at the point of execution
As settlement accelerates, the timing of evidence takes on greater importance. In traditional models, audit trails are assembled after the event, drawing on logs, system records and reconciliations that sit alongside the payment. This approach relies on assumptions about sequence and availability that weaken when settlement runs continuously. Some programmable systems address this by enforcing checks as part of execution and producing records at the same moment value moves. From an audit perspective, oversight becomes easier to substantiate because evidence exists immediately. Review depends less on inference and reconstruction and more on records created at the point of action. The benefit here lies in clarity. When the outcome of controls is recorded alongside settlement, it becomes easier to demonstrate how policy was applied, particularly when payments occur outside familiar operating hours.
Maintaining consistency across settlement models As organisations operate across bank networks, permissioned platforms and always-on settlement environments, maintaining consistent control standards requires greater discipline. Each model brings different operating characteristics and failure modes, and inconsistent application of internal policy becomes a real risk without deliberate design. Institutions that handle this effectively focus on control placement rather than tooling. Checks are applied before value moves where the cost of correction is high, while review processes remain in place where timing allows. Evidence is captured in a form that supports review across settlement models, and fallback arrangements are documented for situations where assumptions break down. Most firms approach this through incremental adjustment, aligning control placement with how settlement actually occurs in practice rather than with legacy expectations. As payment activity extends beyond traditional processing windows, control, audit and evidence increasingly sit within execution itself, reshaping how oversight is exercised rather than whether it exists. Clear Junction’s Value in Transition report examines how banks, electronic money institutions and payment firms are addressing these questions across different settlement models, and what this means for control design, audit discipline and operational oversight as payments move beyond fixed settlement windows. For more information, download our new Value in Transition whitepaper.
