Why Daily Reconciliation Matters Under CASS 15

Why daily reconciliation matters under CASS 15.

CASS 15 changed the tempo of safeguarding. The old rhythms of weekly or monthly reconciliation no longer keep up with what the regime asks a firm to prove.

There is a specific, quiet moment in the day of any well-run payments or e-money firm since 7 May 2026. Someone, somewhere in the operations team, closes yesterday’s books, opens today’s records against yesterday’s balances, and asks whether the two sides still tell the same story. Under the safeguarding regime introduced by Policy Statement PS25/12, that moment is no longer optional, and no longer monthly. It is a daily discipline the regulation now expects the firm to live inside.

For firms whose reconciliation has historically been weekly, or fortnightly, or a large piece of month-end work, that change is more than administrative. It changes the rhythm of the finance and operations function, the way exceptions are handled, and the way evidence is captured. It changes what a firm can say to an auditor with a straight face, and how quickly the CFO can answer a question from the board about safeguarding exposure. Most importantly, it changes what happens between the moment a discrepancy appears and the moment it gets fixed.

This article is about why the change is worth taking seriously, and why the practical answer to “how often should we reconcile” is not weekly, not fortnightly, and not at month end. It is every business day. It matters for three connected reasons: latency compounds, the regime does not offer a materiality floor beneath which small breaks can be ignored, and CASS 15 asks for two different reconciliations, not one. Each one deserves examining.

What CASS 15 asks for on each reconciliation day

Before the three reasons, a short section on what the regime is actually asking for, because much of the confusion about daily reconciliation stems from a loose reading of the requirements.

The safeguarding chapter, CASS 15, introduces the concept of the reconciliation day: in essence, each business day for which safeguarding records must be produced and compared. On each reconciliation day, a firm is expected to carry out an internal reconciliation, which compares what its customer ledger says it owes with what its safeguarding records say it is holding, and an external reconciliation, which compares those internal records against bank statements and third-party data such as payment processor confirmations. The technical shorthand for the comparison is the segregation requirement, meaning what the firm should be holding to cover its liabilities to customers, set against the segregation resource, meaning what the firm is actually holding in safeguarding accounts. A shortfall between the two is not left for later. It is to be corrected promptly, and the correction evidenced.

Sitting behind that, the books and records expectation is that a firm must be able to identify the funds it holds as relevant funds, at any time, without delay. That phrase does a lot of work. It rules out any reading of CASS 15 that treats safeguarding as a monthly reporting cycle with occasional deep dives. A monthly cycle cannot deliver “at any time, without delay”. A daily cycle can.

It matters because latency compounds

Daily reconciliation matters, first, because latency compounds. A break caught the same day it appears is cheap to investigate and cheap to fix. The team can trace the transactions that produced it while they are still fresh in the underlying systems, still visible on the working screens of the people who processed them, still recent enough for banks and payment processors to explain if asked. The correction typically takes minutes, and the evidence trail is short, clean and defensible.

A break caught two weeks later is a different animal. The transactions behind it have moved through downstream systems, been aggregated into batch reports, been offset by subsequent activity or, worst of all, been quietly absorbed into a later reconciliation nobody thought to double-check. The investigation now involves reconstruction, and reconstruction is where the audit trail decays. What was a small operational query in real time becomes a compliance question with an uncertain answer.

There is a second, subtler dimension to this. Late detection changes the character of a break. A same-day discrepancy is usually just that: an operational issue with a specific cause, and often a specific fix. The same discrepancy left for two weeks starts to look, to an auditor or a regulator, like a control weakness. The firm’s inability to catch it quickly becomes part of the finding, not just the finding itself. Firms that have been through a CASS audit know this pattern well. The question is not only whether the reconciliation was done. It is how quickly the firm noticed something was wrong.

It matters because the regime has no materiality floor

Daily reconciliation matters, second, because the regime does not offer a materiality floor beneath which small discrepancies can be quietly ignored. Under CASS 15, any discrepancy identified on a reconciliation day has to be investigated and, if a shortfall exists, corrected promptly. Whether or not a specific break has to be individually notified to the FCA depends on its severity, its resolution status and what it indicates about the firm’s controls, but the initial obligation to find and act on it does not go away.

That is the point of the “even a one-pound break” argument. It is not an argument about reporting thresholds. It is an argument about what a firm has to be able to do operationally. If a firm has no reliable way of catching a one-pound discrepancy at all, then by extension it has no reliable way of catching a five-thousand-pound one either, at least not before the discrepancy has aged into something harder to explain. A regime that expected less would be one that gave firms cover to let small breaks accumulate quietly, and neither the language in Policy Statement PS25/12 nor the design of the reconciliation-day mechanism gives that cover.

There is, again, a subtler point behind the loud one. Breaks that are caught cleanly, corrected promptly and evidenced properly are not the risk. Breaks that are missed until aggregation blurs their origin, or breaks that turn out on inspection to have been happening for weeks, are the risk. The reconciliation cadence a firm chooses determines which category most of its breaks will end up in. A daily cadence produces the first sort. A monthly cadence, whatever its other merits, produces the second.

It matters because internal and external answer different questions

The internal reconciliation asks whether the firm’s own records agree with themselves. It compares what the customer ledger says the firm owes with what the firm’s safeguarding records say it is holding. It proves that the internal system is internally consistent: that a payment recorded in the customer ledger produced a corresponding movement in the safeguarding records, that the firm knows which customers the safeguarded funds are being held for, and that there are no ghost balances or missing entries. If the two sides of the internal reconciliation disagree, the firm has a bookkeeping problem, and knowing that quickly matters.

The external reconciliation asks a harder question: whether the firm’s records agree with reality. It compares those same internal safeguarding records against what the bank statement or the payment processor confirmation actually shows. It proves that the money is where the firm believes it is. If the internal reconciliation says the firm is holding a certain balance at Bank A, and the bank statement for the same day says something different, the internal reconciliation was, at best, half of a check. The firm’s records were consistent with themselves, but wrong.

Skipping either reconciliation leaves a real hole. A firm that runs only the internal reconciliation can be internally coherent and externally wrong for weeks without knowing it. A firm that runs only the external reconciliation might reconcile to the bank but not to its own liabilities to customers. Both blind spots have shown up in enforcement histories, and neither is compatible with the CASS 15 books and records expectation. The regime asks for both, on each reconciliation day, precisely because either alone tells the firm too little.

What this changes in practice

Read together, the three reasons describe a fairly specific operating change. The reconciliation is no longer an event. It is a rhythm. It happens every business day, in a way that is repeatable enough to fit into the operations schedule, cheap enough not to consume disproportionate time, and traceable enough to survive an audit. That is a genuinely different mode of working from the manual assembly, spreadsheet comparisons and end-of-month deep dives many firms have relied on.

This is the work Imperium(L) Prism is built for. Prism runs internal and external reconciliation daily against the same underlying data, so both sides of the check happen every business day rather than on separate cadences. Breaks surface the day they appear, and each one carries an owner, a severity, a deadline and a timestamped evidence trail through to sign-off. The data behind the monthly safeguarding return is generated from that controlled reconciliation, rather than reconstructed at month end. The technology behind Prism has supported businesses in live, high-volume environments for over 12 years, so the operational logic has already been tested against real reconciliations and real audits.

CASS 15 changed what “reconciled” has to mean. It is no longer a state a firm can enter once a month, or once a quarter, and leave again. It is a state a firm has to be able to demonstrate on any business day, against two different sources of truth, without the delay that lets small breaks become large ones. Firms that make that transition well tend to find that reconciliation stops being the piece of work that hangs over everything else. Firms that put it off tend to find, at their next CASS audit, that the piece of work has hung over them anyway. The tempo has changed. The question is how quickly a firm’s operations, systems and evidence trail can change with it.

Frequently Asked Questions

What is a reconciliation day under CASS 15?

A reconciliation day is, in essence, each business day for which safeguarding records must be produced and compared under CASS 15. On each reconciliation day, a firm carries out both an internal reconciliation of the customer ledger against its safeguarding records, and an external reconciliation of those records against bank and third-party data, correcting any shortfall promptly.

What is the difference between internal and external reconciliation?

The internal reconciliation compares the firm’s customer ledger with its own safeguarding records to prove that the firm’s books are internally consistent. The external reconciliation compares those internal records against bank statements and third-party data to prove that the firm’s records match reality. CASS 15 expects both, on each reconciliation day.

Does CASS 15 set a materiality threshold below which reconciliation breaks can be ignored?

No. CASS 15 does not offer a materiality floor beneath which small discrepancies can be ignored. Every discrepancy identified on a reconciliation day has to be investigated and, if a shortfall exists, corrected promptly. Whether or not a specific break must be individually notified to the FCA depends on its severity, its resolution status and what it indicates about the firm’s controls, but the operational obligation to find and act on it is not diluted by size.

What does “correct promptly” actually mean?

CASS 15 does not set a single numeric deadline, but the expectation is straightforward: shortfalls between the segregation requirement and the segregation resource should be topped up as soon as they are identified, and the correction evidenced. In practice, that means same-day action for most operational breaks, with escalation and additional review where the cause is unclear or the amount material.