Practical guidance series, Theme 1, Part 4 of 6

Part 3 covered the legal foundation of the client bank account itself: trust status and the acknowledgment letter. Once that foundation is sound, the next place CASS audits generate findings is the everyday mechanics of moving money into and out of that account. Getting the calculation right (Part 1) and reconciling it properly (Part 2) only pays off if the funding that follows is handled correctly too.

What it looks like in practice

A handful of patterns come up again and again in CASS audit findings on segregation, top-ups and withdrawals.

The first is the gross-versus-net funding error. A reconciliation shows a shortfall, and the firm pays in the full shortfall amount without first netting it against money already sitting there from the previous day’s funding. The closing position looks fine, but a gross movement can create a temporary shortfall intraday, which is never permitted, even for a few hours.

The second is timing. CASS expects a shortfall identified by the internal reconciliation to be funded, or an excess removed, by close of business on the day the reconciliation is performed. In practice, firms often let this slip to “next day” as a matter of routine, treating the deadline as a target rather than a rule.

The third, and the one that causes the most persistent findings, is Prudent Segregation that never comes back out. A firm pays its own money into the client account to cover an anticipated risk (a system failure, a non-business-day exposure) and then simply leaves it there. Over time this turns into an informal buffer that nobody reviews, which is exactly what Prudent Segregation is not meant to be.

The fourth is confusing Prudent Segregation with Transaction Funding. The two look similar (both involve the firm’s own money going into the client account ahead of need) but they have different triggers, different record-keeping treatment, and different rules for when the money can come back out. Firms that don’t distinguish between them tend to get both wrong.

Why it tends to happen

These findings share a common root: top-ups and withdrawals are treated as a purely operational task bolted onto the end of the reconciliation process, rather than as something governed by a documented policy.

Without a clear funding methodology, whoever processes the transfer defaults to paying in the number the reconciliation throws up, rather than calculating the net movement against the prior day’s position. Without a policy that names the specific risks Prudent Segregation is meant to cover, there is nothing to measure against later, so nobody asks whether the money is still needed. And without training that draws the distinction between Prudent Segregation and Transaction Funding, both get logged the same way, which then unravels when the auditor asks why an amount wasn’t removed on discharge of the firm’s fiduciary duty.

Underneath all of this is a more basic issue: Prudent Segregation is sometimes used to paper over a known weakness, such as unreliable reconciliation software, instead of fixing it. The segregation may well cover the resulting shortfall. The breach has still occurred.

Steps firms can take

Fund shortfalls and remove excesses by close of business on the day the internal reconciliation is performed, and calculate the net movement against the previous business day’s position rather than the gross figure, to avoid creating an intraday shortfall.

Where an external reconciliation surfaces a shortfall that cannot be resolved immediately, keep the firm’s own money in the account until the discrepancy is finally corrected, not just until the next reconciliation cycle.

Put a written Prudent Segregation policy in front of the governing body, setting out the specific anticipated risks, why paying money in is a reasonable way to protect against each one, and the method used to calculate the amount. If the firm doesn’t use Prudent Segregation, document that decision too, and review it periodically rather than leaving it to a one-off statement.

Keep a separate Prudent Segregation record, distinct from the reconciliation itself, showing what was paid in or withdrawn, why, and the running total. This is a specific CASS requirement, not just good practice.

Build in a routine check, ideally at every reconciliation, asking whether Prudent Segregation is still needed. If the risk has passed, withdraw it as an excess. It should never become a standing balance that only gets questioned when an auditor asks about it.

Finally, treat Prudent Segregation as a mitigation, not a fix. If the underlying cause is a systems or process weakness, the fix is to address that weakness, not to keep topping up against it indefinitely.

Part 5 moves up a level, to the oversight function that should be catching all of this in the normal course of business: the record-keeping, training and escalation that turns these individual controls into something a board can actually rely on.