Imperium(L) https://www.imperiuml.com/ Fri, 11 Sep 2026 07:53:41 +0000 en-GB hourly 1 https://wordpress.org/?v=7.1 https://www.imperiuml.com/wp-content/uploads/2026/02/imperiuml-circle-background-150x150.png Imperium(L) https://www.imperiuml.com/ 32 32 How to reduce month-end safeguarding reporting pressure https://www.imperiuml.com/insights/month-end-safeguarding-reporting-pressure/ Fri, 11 Sep 2026 07:39:17 +0000 https://www.imperiuml.com/?p=3712 Under the safeguarding regime introduced by Policy Statement PS25/12 and in force since 7 May 2026, payments and e-money firms produce a monthly safeguarding return that captures their relevant funds position, reconciliation activity, discrepancies and their status, and arrangements with banks and providers, attested to by a senior individual. The pressure firms feel at month-end […]

The post How to reduce month-end safeguarding reporting pressure appeared first on Imperium(L).

]]>

How to reduce month-end safeguarding reporting pressure

Month-end pressure is not really a reporting problem. It is a symptom of the work that should have happened earlier in the month, still needing to happen at month-end.

  • By Imperium(L)
  • September 2026
  • Approx 10 Minute Read

There is a specific week, or in demanding months a specific weekend, when the safeguarding team of a payments or e-money firm is quieter than usual, and not in a good way. Screens are open longer. Coffee is bad. Someone in finance is asking whether the numbers from the customer ledger match the numbers from the safeguarding accounts, and someone else is trying to explain why a break from the 12th of the month was corrected but is no longer easy to trace, and someone else is emailing the bank about an acknowledgement letter they thought was filed but cannot immediately find. Somewhere, the head of compliance is waiting to sign off, and the CFO is asking, gently, whether they can have the figures by Wednesday.

That is the monthly safeguarding return. Or rather, it is the two days that most firms mistake for the monthly safeguarding return, when what they are actually doing is trying to reconstruct a month of activity in a short enough window to hit a fixed deadline. The return itself, the form, the numbers, the attestation, is comparatively straightforward. It is the assembly work behind it that generates the pressure, and the assembly work is a symptom, not a cause.

This article is about how to reduce that pressure by treating it as what it is. Not a reporting problem, but a design problem. Month-end pressure is the visible surface of four upstream weaknesses that show up in the same week every month: data assembled too late, breaks resolved too late, evidence gathered too late, and sign-off compressed into a window that is too narrow for the review it is meant to provide. Each of those weaknesses can be pushed upstream. The return, when it comes, then becomes a summary of controlled activity, not the moment control gets applied.

What the monthly safeguarding return actually is

Before the diagnostic, a short grounding in what the return itself asks for. Under the safeguarding regime introduced by Policy Statement PS25/12 and in force since 7 May 2026, payments and e-money firms are expected to produce a monthly safeguarding return that captures the firm’s position on relevant funds, its reconciliation activity, its discrepancies and their status, its arrangements with banks and providers, and the attestation of a senior individual that the return is accurate. The return then goes to the FCA.

The important thing about the return is that it is a summary. It does not produce information the firm should not already have. Every number on the return corresponds to something the firm should have been able to produce on demand at any point during the month: the safeguarding balances, the customer positions, the reconciliation outcomes, the discrepancies identified, the corrections made, the evidence supporting them. In principle, producing the return should be an act of retrieval and aggregation. In practice, it is often the moment those numbers get assembled into a coherent picture for the first time, because during the month they lived across ledgers, bank portals, PSP exports, spreadsheets and the working memory of the people who produced them.

That gap is what generates month-end pressure. It is closable.

Data assembled too late

The first source of month-end pressure is that the picture of what the firm owes customers, and what it holds to protect them, has not been kept together during the month. The data exists. It has always existed. It is scattered across the customer ledger, the bank portals for each safeguarding account, the payment processor exports, internal cashbooks, FX conversion records and any number of spreadsheets that have accreted around the process. When the return is due, someone has to bring all of that together, in one place, in a form that reconciles internally.

The upstream fix is that the picture is kept together every business day rather than assembled at month-end. When the internal safeguarding position and the external bank and third-party records are compared daily, month-end no longer involves that comparison. It involves confirming that the last day of the month reconciles like every other day of the month, and producing the aggregate from data that has been kept current throughout. The two-day exercise becomes a two-hour one.

There is a secondary benefit. When data is assembled daily, the person who most recently touched a discrepancy is still available to explain it. When it is assembled at month-end, that person is often on the wrong shift, in the wrong week or, on occasion, in the wrong quarter. Institutional memory is a poor substitute for a record that was captured while the events were fresh.

Breaks resolved too late

The second source of pressure is that reconciliation breaks identified during the month were not resolved cleanly at the time, and now need to be traced, corrected and evidenced under time pressure. Some were flagged, worked on and closed properly. Others were flagged and left in a shared inbox. Others were noticed on a Wednesday and then, in the way of small operational discrepancies, quietly aged into the background as more urgent work displaced them.

At month-end, all of those breaks re-emerge. The unresolved ones need to be corrected before the return can be attested to. The partially resolved ones need to be traced, and the trace usually involves reconstructing an activity chain that has since been overwritten by later transactions. The properly resolved ones need their evidence checked, and often the evidence is thinner than the firm remembers.

The upstream fix is that break resolution happens as breaks are identified, not as month-end approaches. Every break carries an owner, a severity, a deadline and a closure test, and moves through investigation, correction, evidence and sign-off within the window the firm’s own policy requires. At month-end, the review of break activity becomes an exercise in reading closed items rather than closing open ones. The pressure of resolving under time constraint disappears, and with it the tendency for corrections to be made hastily rather than properly.

Evidence gathered too late

The third source of pressure is that the evidence supporting reconciliation activity, break resolution and sign-off has not been captured as the work happened. It has to be assembled now, from memory, email threads, screenshots taken after the fact and summaries written in the days before the return is due.

This is where a lot of the credibility risk lives. Evidence assembled late is evidence that depends on the person assembling it. A reconciliation output produced from a screenshot taken this morning does not prove what the firm’s records looked like on the 8th of the month. An email confirming that a break was reviewed does not by itself prove who authorised the correction or when. A summary written a week after the event fills in the gaps in the record with the assembler’s best recollection. Each of those substitutions is small in isolation and, over a full month of activity, adds up to a picture whose evidentiary support is thinner than it needs to be.

The upstream fix is that evidence is captured by the systems that do the work, at the time the work happens. Reconciliation runs are logged when they run. Break resolution stages produce their own records as each stage completes. Sign-offs are timestamped and attributable to the person who made them. Month-end evidence work becomes a matter of retrieval, not creation. What the auditor and the FCA see is what happened, not what the firm remembers happening.

Sign-off compressed into a window

The fourth source of pressure is that the reviews and approvals which should have flowed through the month get compressed into the final days. A senior manager who should have signed off ten decisions across four weeks signs off ten decisions in one afternoon. A head of compliance who should have reviewed the resolution pack progressively reviews it in one sitting. A CFO who should have attested to numbers they have been watching all month attests to numbers they are seeing in aggregate for the first time.

None of that is inherently wrong. It is inherently high risk. Compressed sign-off is the moment when reviewers are least able to spot the specific thing they are meant to be spotting, because they are reviewing volume under time pressure. It is also the moment when the appearance of oversight is easiest to produce and the substance of oversight is hardest to demonstrate. An auditor who sees ten approvals dated within a two-hour window on the 28th will have questions about the quality of each.

The upstream fix is that sign-off happens at the point of the action, not the point of the report. When a break is resolved, its closure is signed off then and there, by a person with the right authority, against the closure test the firm has defined. When a reconciliation is completed, its acceptance is recorded at the time. At month-end, senior management attests to the aggregate, having seen the components as they were produced. The review is real, and the record shows it.

Why this matters at leadership level

Reducing month-end pressure is a leadership question, not just an operational one. The design of the operating model, and the discipline with which controls actually operate through the month, sits with the CFO, COO and head of compliance in most firms. When the safeguarding team is under pressure at month-end, that is not primarily a story about a stretched team. It is a story about how the operating model has been designed and what senior management is signing off.

There is a specific accountability dimension here. The monthly return is attested to by a senior individual. Under the safeguarding regime, that attestation is not a formality. It is a personal statement that the return reflects the firm’s actual position on relevant funds, its reconciliation activity, its discrepancies and their resolution. Attesting under time pressure, to numbers seen in aggregate for the first time, is a different exercise from attesting to a summary of activity the attester has had visibility over throughout the month. Both are formally the same act. Only one of them is a defensible act.

The other leadership dimension is what the pattern says about safeguarding culture. Firms whose operating model produces a smooth month-end tend to be firms in which safeguarding is treated as a continuous discipline rather than a periodic exercise. Firms whose operating model produces a difficult month-end tend to be firms in which control is applied episodically. That distinction is invisible on the return itself and becomes obvious in an audit or a regulatory review. Leadership designs the operating model that produces one or the other.

What this changes in practice

Read together, the four upstream fixes describe a specific operational pattern. Data is assembled daily. Breaks are resolved as they arise, with defined ownership and a closure test. Evidence is captured by the systems that do the work, at the time the work happens. Sign-off happens at the point of the action, not the point of the report. Month-end then becomes what the regime intends it to be: a summary of controlled activity, produced from data already assembled, evidence already captured, breaks already closed and sign-offs already recorded.

This is the work Imperium(L) Prism is built for. Prism keeps the picture together daily, wraps every reconciliation break in a structured workflow with timestamped sign-off, captures evidence automatically as work happens, and generates the data behind the monthly safeguarding return from that controlled activity. The return is produced from the platform, reviewed inside it, and exported for the senior individual to attest to, rather than reconstructed from spreadsheets and email threads in the final week. 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.

The monthly safeguarding return is a summary. It is a summary of a month’s controlled activity, or it is a summary produced under time pressure by people trying to reconstruct that activity in the last week. The difference is not in the return. It is in what the firm did with the twenty-nine days before it. Firms that design their operating model around the return tend to find that month-end is a long week. Firms that design their operating model around continuous control tend to find that the return, when it comes, more or less produces itself.

Book a Demo

Frequently Asked Questions

What is the monthly safeguarding return?

The monthly safeguarding return is a return that payments and e-money firms produce under the safeguarding regime introduced by Policy Statement PS25/12, in force since 7 May 2026. It captures the firm’s position on relevant funds, its reconciliation activity, its discrepancies and their status, its arrangements with banks and providers, and the attestation of a senior individual that the return is accurate. It goes to the FCA.

No. Prism generates the data behind the monthly safeguarding return from controlled reconciliation activity, supports review and approval workflows, and exports the return in a structured format for the firm’s senior individual to attest to. The firm remains responsible for submitting the return itself, unless direct submission is separately configured and confirmed.

The attestation is made by an appropriate senior individual in the firm, confirming that the return reflects the firm’s actual position and activity. Attestation under the safeguarding regime is a personal statement, not a formality, and is one of the reasons continuous oversight through the month, rather than one-off review at month-end, matters.

By pushing four upstream weaknesses earlier in the month: assembling the safeguarding picture daily rather than at month-end; resolving reconciliation breaks as they arise, with defined ownership and a closure test; capturing evidence by the systems that do the work, at the time the work happens; and running sign-off at the point of each action, not the point of the report. Month-end then becomes a summary of controlled activity rather than the moment control is applied.

The post How to reduce month-end safeguarding reporting pressure appeared first on Imperium(L).

]]> Why audit trails matter under CASS 15 https://www.imperiuml.com/insights/audit-trails-cass-15-safeguarding/ Sun, 23 Aug 2026 19:06:59 +0000 https://www.imperiuml.com/?p=3697 Under CASS 15, in force since 7 May 2026, firms must maintain books and records that identify relevant funds at any time, without delay, and support an annual safeguarding audit under SUP 3A. (Firms whose relevant funds do not exceed £100,000 are exempt from the audit requirement.) The regime has moved the burden of proof: […]

The post Why audit trails matter under CASS 15 appeared first on Imperium(L).

]]>

Why audit trails matter under CASS 15

Under the safeguarding regime, doing the work is not the same as being able to prove the work was done. The audit trail has quietly become the mechanism through which compliance is judged.

  • By Imperium(L)
  • September 2026
  • Approx 10 Minute Read

Ask a safeguarding lead in a payments or e-money firm whether the reconciliation ran yesterday, and the answer is almost always yes. Ask whether the shortfall found on Tuesday morning was corrected, and the answer is almost always yes. Ask whether the sign-off on that correction was recorded at the right level, whether the acknowledgement letter for the safeguarding account is current, whether the resolution pack reflects the state of things as of close of business Thursday, and the answer becomes slower and more qualified. Ask whether all of that could be evidenced, cleanly, to a CASS auditor next month, without reconstructing anything, and the answer often changes altogether.

That gap between having done the work and being able to demonstrate having done the work is where CASS 15 has quietly moved the ground under firms’ feet. The regime has always cared about outcomes. What is different now is that it also cares, in a specific and enforceable way, about the trail behind those outcomes. Records must be complete. Sign-offs must be attributable. Evidence must be produced without delay. The audit trail is no longer the paperwork behind the work. It is the evidence that the work happened.

This article is about why that shift matters. It matters because the burden of proof has moved. It matters because audit trails and the controls they record are two halves of the same sentence: neither is credible on its own. And it matters because the annual safeguarding audit under SUP 3A now provides the eventual test of both, in a form that leaves less room than firms sometimes assume for a plausible explanation of missing evidence.

What the regime actually expects on the record

Before the argument, a short grounding in what the rules ask for. Under CASS 15, introduced by Policy Statement PS25/12 and in force since 7 May 2026, firms must maintain books and records that identify relevant funds at any time, without delay. Reconciliation activity on each reconciliation day, the investigation and correction of any shortfall, the acknowledgement letters that govern safeguarding accounts, the mandatory documents that populate the resolution pack under CASS 10A, and the sign-off trail that runs through all of it are expected to be current, complete and available. The chapter does not treat records as an administrative byproduct of the operational work. It treats them as evidence that the operational work took place.

Sitting behind the day-to-day expectation is the annual safeguarding audit under SUP 3A. Firms holding relevant funds above the exempted threshold must arrange for a qualified auditor to conduct the audit and to report on whether the firm has complied with the safeguarding requirements. That report is not a private matter between the firm and its auditor. It goes to the FCA, which uses it as one of the more concrete inputs into how confident it is that customer money is properly protected. The auditor is looking for evidence that the controls the firm claims to operate actually produced the outcomes the firm claims they produced.

Between them, CASS 15 and SUP 3A make one thing clear. The regime has moved from asking whether the firm has controls to asking whether the firm can prove those controls operated.

The burden of proof has moved

The shift is subtle but complete. Under the previous position, a firm that did the work and could describe what it had done was, broadly, in a defensible place. If the reconciliation had run, and the person who ran it could explain how, that was often enough for internal purposes and, up to a point, for external ones. Under CASS 15, that position has narrowed. The firm still has to do the work. It also has to be able to show, in a form an auditor accepts, that the work was done, when it was done, by whom, and what it produced.

That is a genuinely different bar. Doing the reconciliation is not the same as having a timestamped, attributable record of the reconciliation running. Correcting a shortfall is not the same as being able to show the correction happened within the window the firm’s own policy requires. Maintaining an acknowledgement letter is not the same as being able to demonstrate that the letter reflects the current arrangements with the bank. Each of those gaps is small in isolation. Across a full audit cycle, and across the range of activity CASS 15 covers, they aggregate into a picture that either persuades the auditor or does not.

There is a specific pattern that experienced auditors recognise quickly. A firm that has done the work but has not built an audit trail commensurate with it tends to answer questions with a mix of description and reconstruction. The reconciliation ran; here is the person who ran it; here is an email confirming they did. The break was corrected; here is a screenshot of the current balance; here is the person who remembers approving it. The letters are up to date; here is the file where we keep them; the most recent one is from March, we think. None of this is dishonest, and much of it is broadly accurate. It is also, from an evidentiary standpoint, thin. What the regime asks for, and what an auditor will look for, is a trail that stands on its own without the person who created it standing next to it.

Audit trails and controls are the same sentence

A common mistake is to think of controls and audit trails as separate things. They are not. A control without an audit trail is only credible for as long as the person who operated it remembers what they did. An audit trail without a control is theatre: a record of activity that has no discipline behind it. The two are inseparable, and firms that treat them separately tend to build one at the expense of the other.

Consider a four-eyes sign-off on a shortfall correction. As a control, it is straightforward. The person who identifies the shortfall proposes the correction; a second person, with the appropriate authority, reviews and approves it before it is made. That is the control. The audit trail is the timestamped, attributable record of both steps: who proposed, who approved, when, and against what supporting evidence. If the control operates but the trail is not captured, the firm has done the right thing and cannot prove it. If the trail is captured but the control did not actually operate as designed, the firm has a record of activity with no discipline behind it. Either failure mode, presented to an auditor, produces the same response: this control cannot be relied upon.

What good looks like is easier to describe than to build. A strong audit trail is attributable, so every action is tied to a specific person or role rather than a shared login. It is timestamped, so the sequence of actions is unambiguous rather than reconstructed. It is sequential and complete, so each stage of a process produces its own record rather than being folded into a summary at the end. And it is unalterable in the sense that matters: past entries cannot be quietly edited to fix a problem the firm noticed later. Shared logins, editable spreadsheets, screenshots taken after the fact and summaries written from memory each fail one or more of these tests. The trail that survives an audit is the one that was captured as the work happened, by the systems that did the work, in a form that does not depend on anyone’s later description of events.

What SUP 3A auditors look for

An auditor conducting a safeguarding audit under SUP 3A is not looking for something exotic. The auditor is looking for evidence that specific things happened in specific ways over the period under review. In broad terms, and without pretending to speak for individual firms, that evidence typically includes the following.

Evidence that internal and external reconciliation ran on each reconciliation day, in a form that shows both sides of the comparison and the outcome. Evidence that any shortfall between the segregation requirement and the segregation resource was corrected promptly, with the mechanism of correction visible in the record. Evidence that discrepancies below the reporting threshold were nonetheless investigated and closed, so the firm’s own threshold policy is applied consistently rather than selectively. Evidence that sign-off happened at the level the firm’s policy required, by a person with the appropriate authority, not simply the person who was available. Evidence that mandatory documents in the resolution pack are current, that acknowledgement letters reflect the actual arrangements with banks, and that changes to any of the above are themselves recorded and dated.

What a firm that passes looks like, at a high level, is a firm whose audit trail is not different in character from its day-to-day operational activity. The two are the same activity, captured in the same place, in the same form, at the same time. Questions from the auditor tend to be answered by producing records rather than describing what happened. Discrepancies, where they exist, are ones the firm has already identified, investigated and closed.

What a firm that fails looks like, at a similarly high level, is a firm whose operational activity was probably fine but whose evidentiary support is thin. Records are recognisable but incomplete. Sign-offs are described but not attributable. The story is broadly plausible but requires the firm to fill in the pieces the record does not show. That gap is what auditors report on, and it is what firms most consistently underestimate until the report lands on the FCA’s desk.

What this changes in practice

Read together, the shifted burden of proof, the inseparability of controls and audit trails and the way SUP 3A audits are conducted describe a fairly specific operational requirement. The firm’s work and the firm’s record of the work should be the same activity, captured in the same place, as the work happens. Retrospective assembly, however careful, is a poor substitute.

This is the work Imperium(L) Prism is built for. Every reconciliation, every break resolution stage, every sign-off, every configuration change and every user action is captured, timestamped and attributable inside the platform. Role-based access controls determine who can do what, so segregation of duty is built into the system rather than relying on shared logins. Multi-tier sign-off enforces the firm’s own policy on who approves what, at what level. Mandatory-document tracking against the resolution pack surfaces gaps continuously rather than at audit. The audit trail is not something the firm produces at year end. It is a byproduct of running the system, which is exactly the form the regime and the auditor now expect it to take. 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.

Under CASS 15, the audit trail has quietly stopped being the paperwork behind the work. It has become the evidence that the work happened, and it is judged on its own terms. Firms that build their audit trail as a byproduct of running their controls, in a system that captures activity as it happens, tend to find that SUP 3A audits are exercises in retrieval rather than reconstruction. Firms that build their audit trail as an afterthought tend to find that the auditor’s report writes itself, and not in the direction they would have chosen.

Book a Demo

Frequently Asked Questions

What is SUP 3A, and does it apply to every payments or e-money firm?

SUP 3A is the chapter of the FCA Handbook that sets out the annual safeguarding audit requirement for payments and e-money firms holding relevant funds. Under the arrangements introduced by Policy Statement PS25/12, firms whose relevant funds do not exceed £100,000 are exempt from the audit requirement. Firms above that threshold must arrange for a qualified auditor to carry out the safeguarding audit and produce a report, which goes to the FCA.

At a general level, an auditor will typically look for evidence that internal and external reconciliation ran on each reconciliation day, that shortfalls between the segregation requirement and the segregation resource were corrected promptly, that discrepancies were investigated and closed consistently against the firm’s own threshold policy, that sign-off happened at the appropriate level, and that mandatory documents in the resolution pack (including acknowledgement letters) are current and reflect actual arrangements. The specifics vary by audit firm and by engagement.

A defensible audit trail is attributable, so every action is tied to a specific person or role rather than a shared login. It is timestamped, so the sequence of actions is unambiguous. It is sequential and complete, so each stage of a process produces its own record rather than being folded into a summary. And it is captured as the work happens, by the systems that did the work, rather than reconstructed later from memory, screenshots or summaries.

Shared logins break the attributability that an audit trail depends on: if two or more people use the same credentials, no action can be tied cleanly to a specific person. That failure mode is one of the more common sources of findings in CASS reviews. Individual user accounts, with role-based access controls that determine what each user can do, are the practical route to a defensible trail.

The post Why audit trails matter under CASS 15 appeared first on Imperium(L).

]]> What happens after a reconciliation break is found? https://www.imperiuml.com/insights/reconciliation-break-resolution-cass-15/ Thu, 06 Aug 2026 13:17:26 +0000 https://www.imperiuml.com/?p=3634 Under CASS 15, a reconciliation break identified on any business day must be investigated, corrected promptly where a shortfall exists, evidenced and signed off. The operational discipline that separates firms passing a CASS audit from those failing is not the finding of breaks but what happens after: a named owner for every break, a defined […]

The post What happens after a reconciliation break is found? appeared first on Imperium(L).

]]>

What happens after a reconciliation break is found?

Most firms have some form of reconciliation. The weakest link is what happens after a break is found: who owns it, what they do about it, and how it feeds into a resolution pack that has to be current, not archived.

  • By Imperium(L)
  • August 2026
  • Approx 10 Minute Read

A reconciliation break appears at 09:42 on a Tuesday. The internal comparison between what the customer ledger says the firm owes and what the safeguarding records say it holds no longer agrees. The gap is small, £412 across three transactions in one currency, and if the firm is paying attention, someone in the operations team sees it before their coffee is finished. What happens in the next hour is where CASS 15 firms are quietly separated into two groups.

The first group has a clear answer to a specific set of questions. Who owns this break, right now? What is its severity? By when does it need to be corrected? Who will investigate the cause? What evidence needs to be gathered along the way? Who signs it off, and what qualifies as closed? The break enters a defined workflow that leaves nothing to memory or chance.

The second group has some of those answers, some of the time, and a shared assumption that someone will look at it. The break enters an email thread. Sometimes a spreadsheet. Sometimes both. It usually gets resolved, eventually, but the trail behind that resolution is thinner than it needs to be, and no one in the firm could tell an auditor with complete confidence when the break was first spotted, who investigated it, or when it was actually closed.

Under CASS 15, finding the break is the easy part. The hard part is what happens next, and it is the part firms most consistently underestimate.

What CASS 15 and CASS 10A actually expect

Before the argument, a short grounding in what the regime asks for. The safeguarding chapter introduced by Policy Statement PS25/12 is clear about the immediate obligation. Where a firm identifies a shortfall between what it should be holding for its customers and what it actually holds, that shortfall is to be corrected promptly, the investigation into cause is to be evidenced, and the correction itself is to be recorded. The obligation does not distinguish sharply between small breaks and large ones for the purpose of finding and correcting them. Whether or not a specific breach must be individually notified to the FCA depends on materiality, resolution status and what it says about the firm’s controls, but the internal process of investigation, correction and evidence applies across the board.

Sitting alongside this is the resolution pack expectation in CASS 10A. A resolution pack is not, or should not be, a filed document. It is the firm’s live capability to identify relevant funds and return them to customers quickly if the firm fails. Mandatory documents, from account documentation and acknowledgement letters to reconciliation records and evidence of break resolution, are expected to be current, complete and ready to be used at short notice. What connects CASS 15 and CASS 10A operationally is straightforward. The resolution pack draws its confidence from the state of the firm’s day-to-day reconciliation and break resolution. If the break resolution is patchy, the resolution pack is untrustworthy, whatever the file it sits in says.

Ownership is the weak link

Most payments and e-money firms already have some form of reconciliation. What separates the ones that hold up under a CASS audit from the ones that don’t is not usually the reconciliation itself, but what happens to a break the moment it is found. The most common weakness we see is that a break has no clear owner.

“Someone will look at it” is not ownership. Ownership means a named person, or a named role covered by a named deputy, whose responsibility it is to move the break through investigation, correction, evidence and sign-off to closure, within a defined time, with a clear escalation path if any of those steps stalls. Without ownership, breaks tend to move sideways rather than forwards. They enter shared inboxes, group chats and multi-recipient emails, and each person who reads them assumes another person is dealing with them. Sometimes the assumption is right. Often it is not, until the reconciliation runs again the next day and the break is still there.

Ownership is not the same as authority. Some breaks require sign-off from a senior manager, notification to compliance or, in specific cases, notification to the FCA. Ownership is the operational thread that runs from first identification to formal closure. It says who is responsible for making sure each step happens, in order, with the appropriate escalation. Authority is what happens at each step. Both matter. Firms that confuse them, or that combine them into a single person who is expected to do everything, tend to find that breaks either move too slowly or bypass the checks that give the closure its credibility.

A properly-owned break carries five pieces of information from the moment it is opened: an owner, a severity, a deadline, an escalation path and a defined closure test. Firms that make sure every break carries all five, every time, find that resolution stops being ad hoc. Firms that leave any of them implicit find that resolution is only as reliable as the individual on shift that morning.

The stages of a defensible break resolution

Under that ownership, five stages describe what a defensible break resolution actually looks like in practice.

Investigation comes first. Understand what caused the discrepancy: an FX conversion error, a duplicate transaction, a missed refund, a late acknowledgement from a payment processor, a bank fee not accounted for in the internal cashbook. The cause matters more than the number. Two breaks of the same value can carry very different levels of risk depending on what produced them.

Correction is next. Where the segregation resource is below the segregation requirement, the shortfall is to be topped up promptly. That is not a monthly adjustment. It is an operational action, taken as soon as the shortfall is confirmed, with the mechanism recorded. Where the discrepancy is a matter of records not agreeing rather than money being wrong, the correction is to the records, but the same principle applies: prompt, mechanical, evidenced.

Evidence gathering runs alongside both. The evidence is not a summary produced after the fact. It is the trail of the underlying activity: system logs, bank confirmations, internal notes, the reconciliation outputs before and after, the timestamps of every action. Firms that leave evidence to the end find that they are reconstructing it. Firms that capture it as they go find that it is already there when it is needed.

Escalation and notification follow, where required. Some breaks stay within the operations team. Others require sign-off from a senior manager, notification to compliance or, where the regime’s reporting expectations are engaged, notification to the FCA. This step is not a matter of individual judgement in isolation. It should follow a defined threshold policy so that the trigger is the same regardless of who is on shift.

Sign-off and closure complete the cycle. A break is not closed because someone marks it closed. It is closed because a defined closure test has been met: the correction is in place, the evidence is captured, the sign-off has been recorded at the level the severity requires, and any downstream reporting has been triggered. Anything less leaves the break formally open, which is where auditors expect to see rigour and where boards expect to see risk.

The resolution pack is a daily readiness exercise, not an archive

CASS 10A introduces the resolution pack expectation, and most firms still misread it as a periodic document that lives in a folder somewhere until the auditor asks for it. It is not. It is the firm’s live ability to identify relevant funds and return them to customers quickly if the firm fails. Everything in the pack, from account documentation and acknowledgement letters to reconciliation records and evidence of break resolution, is expected to be current, complete and usable at short notice.

The connection to break resolution is the connective tissue. Every break that is investigated, corrected, evidenced and signed off contributes to the reliability of the pack, because it demonstrates that the firm knows what it is holding, why, and how any discrepancies have been handled. Every break that lingers, or is closed without a proper trail, weakens the pack by exactly the amount it would take to reconstruct that story under time pressure.

Most firms discover the gap between what a resolution pack says and what the underlying operational reality can support only when an auditor or the FCA asks a specific question. Which acknowledgement letter is missing. Which reconciliation break has no evidence of sign-off. Which mandatory document has not been updated since the account changed. The firms that answer cleanly are the ones that have treated the pack as something that gets a little more accurate every day, not something that gets pulled together at year end.

The practical problem most firms face is not a shortage of data. The data exists. It is simply spread across customer ledgers, bank portals, payment processor exports, spreadsheets and the working memory of whoever ran the last reconciliation. Assembling that picture once a month is demanding enough. Assembling it every business day, to a standard that survives an audit, is a different order of task altogether. That is the operational control challenge PS25/12 has created, and it is precisely the part that never appears on the face of the return.

What this changes in practice

Read together, ownership, staged resolution and a daily resolution pack describe an operational rhythm that is genuinely different from break management run through spreadsheets and email threads. It is a specific set of habits: every break carries an owner, a severity, a deadline, an escalation path and a closure test; every stage produces evidence as it happens rather than after; every closure feeds into a resolution pack that is treated as live rather than filed.

This is the work Imperium(L) Prism is built for. Prism wraps every reconciliation break in a structured workflow: owner, severity, deadline, evidence, escalation and sign-off, with a timestamped audit trail of every action. Resolution-pack completeness is tracked continuously against a mandatory-document checklist, so gaps surface immediately rather than at audit. The evidence trail is captured automatically inside the system, not reconstructed from workbooks and emails after the fact. 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.

Finding a reconciliation break under CASS 15 is now the easy part. The hard part, the part that decides how a CASS audit reads, is what happens between the moment the break appears and the moment a defined closure test is met. Firms that make that part of the work a disciplined workflow tend to find that resolution stops eating their operations time. Firms that leave it to memory, judgement and shared inboxes tend to find, at audit, that memory, judgement and shared inboxes are exactly what auditors do not accept as evidence.

Book a Demo

Frequently Asked Questions

What is a resolution pack under CASS 10A?

A resolution pack is the set of records and documents that would allow relevant funds to be identified and returned to customers quickly if the firm failed. Under CASS 10A, mandatory documents including account documentation, acknowledgement letters, reconciliation records and evidence of break resolution are expected to be current, complete and ready to be used at short notice. It is a live operational capability, not a filed document.

No. Every reconciliation break identified on a reconciliation day has to be investigated, corrected promptly if a shortfall exists, and evidenced internally. Whether a specific breach must be individually notified to the FCA depends on its materiality, its resolution status and what it indicates about the firm’s controls. Firms should follow a defined threshold policy so that the notification trigger is consistent regardless of who is on shift.

A break should have a named owner, or a named role covered by a named deputy, whose responsibility it is to move the break through investigation, correction, evidence and sign-off to closure, within a defined time, with a clear escalation path. Ownership is the operational thread from identification to closure. It is distinct from authority, which is what happens at each individual step, such as sign-off or notification.

Five stages: investigation, to understand the cause; correction, to top up any shortfall or fix the records; evidence gathering, captured as the work happens rather than reconstructed after; escalation and notification where required, following a defined threshold policy; and sign-off and closure against a defined closure test. A break is not closed because someone marks it closed. It is closed because the closure test has been met.

The post What happens after a reconciliation break is found? appeared first on Imperium(L).

]]> Why daily reconciliation matters under CASS 15 https://www.imperiuml.com/insights/why-daily-reconciliation-matters-under-cass-15/ Mon, 20 Jul 2026 00:39:25 +0000 https://www.imperiuml.com/?p=3572 Under CASS 15, in force since 7 May 2026, payments and e-money firms must reconcile safeguarding positions on each business day, running both an internal reconciliation of the customer ledger against safeguarding records and an external reconciliation of those records against bank and third-party data. Discrepancies must be investigated and corrected promptly. Daily reconciliation matters […]

The post Why daily reconciliation matters under CASS 15 appeared first on Imperium(L).

]]>

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. 

  • By Imperium(L)
  • July 2026
  • Approx 10 Minute Read

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.

Book a Demo

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. 

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. 

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. 

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. 

The post Why daily reconciliation matters under CASS 15 appeared first on Imperium(L).

]]> CASS 15 Operational Control Challenge https://www.imperiuml.com/insights/cass-15-operational-control-challenge/ Tue, 23 Jun 2026 12:12:26 +0000 https://www.imperiuml.com/?p=3535 CASS 15, introduced by FCA Policy Statement PS25/12 and in force since 7 May 2026, is not just a reporting requirement. It makes safeguarding a daily operational control discipline for payments and e-money firms, requiring regular internal and external reconciliation, comparison of the segregation requirement against the segregation resource, prompt correction of shortfalls, a resolution […]

The post CASS 15 Operational Control Challenge appeared first on Imperium(L).

]]>

CASS 15 is not just a reporting issue.
It is an operational control challenge.

The FCA’s new safeguarding regime comes with a deadline, a monthly return and an audit. Treat it as form-filling and you miss the point, and the risk.

  • By Imperium(L)
  • June 2026
  • Approx 8 Minute Read

When the FCA published Policy Statement PS25/12 in August 2025, confirming its changes to the safeguarding regime for payments and e-money firms, much of the early reaction settled on the obvious. There was a new monthly safeguarding return to produce, an annual safeguarding audit to pass and more records to keep. In a lot of firms, the instinct was to treat it as a reporting upgrade. Build the return, satisfy the auditor, move on. That reading is understandable. It is also wrong, and the distance between the two interpretations is exactly where regulatory and customer-protection risk now sits.

What PS25/12 actually changed

Since 7 May 2026, the Supplementary Regime set out in PS25/12 has been in force. Following its consultation in CP24/20, the FCA gave firms a nine-month implementation window, longer than the six months it had originally proposed, precisely because what it expects is not a quick configuration change. The new rules introduce a dedicated safeguarding chapter in the Client Assets Sourcebook, CASS 15, and they do not sit alone. They are accompanied by a resolution pack chapter in CASS 10A, a safeguarding audit requirement in SUP 3A and the monthly safeguarding return in SUP 16.14A.

Read those four pieces together and a pattern emerges. This is the description of an operating model, not a reporting cycle. PS25/12 also confirmed that the FCA is not, for now, pressing ahead with the more far-reaching end-state, sometimes called the post-repeal, regime it had floated, choosing instead to let the Supplementary Regime bed in and to review it once a full audit cycle has run. The direction of travel, though, is set, and firms should plan around it rather than against it.

Why the rules look like this

The rationale is uncomfortable, and instructive. The FCA’s own analysis of firm failures found that when payments and e-money firms went under, customers were left badly short. The money actually available to return to those customers fell well below what they were owed, with average shortfalls running to roughly two thirds of relevant funds in the cases the regulator examined. A regime built around a monthly form would never have closed a gap that large. A regime built around continuous control has a chance of doing so. That logic runs through every part of CASS 15, and it explains why the obligations are weighted so heavily towards daily operational discipline rather than periodic disclosure.

The return is the tip of the iceberg

The monthly return is the visible output. The work that actually protects customers sits beneath it, and most of that work happens every business day. CASS 15 expects firms to reconcile what they owe customers against what they hold in safeguarding, and to do it on each reconciliation day rather than once a month. It draws a sharp distinction between the segregation requirement, meaning what the firm should be holding, and the segregation resource, meaning what it actually holds, and it asks firms to compare the two and put right any shortfall promptly. A discrepancy is no longer something to flag and revisit at month end. It is something to find today and fix today.

Around that daily core sit further obligations, and none of them is a reporting task. Firms must maintain a resolution pack, so that if the worst happens relevant funds can be identified and returned to customers quickly. They must carry out due diligence on where safeguarding funds are held and avoid undue concentration in any one place. Where they rely on the insurance or guarantee method, they must meet specific conditions, including allowing enough lead time to put replacement cover in place. They must hold acknowledgement letters for their safeguarding accounts. And they must support an annual safeguarding audit, although the FCA has carved out the smallest firms, those whose relevant funds do not exceed £100,000, from the audit requirement.

Why this is an operating challenge, not a reporting one

Seen as a whole, the message is hard to miss. CASS 15 asks firms to run a control environment, to evidence that it is working, and only then to report on it. Reporting is the third step, not the first. That ordering is why a spreadsheet, however carefully maintained, struggles under the new regime. A spreadsheet can hold numbers well enough. It is far weaker at proving, weeks or months later, who reviewed a discrepancy, when it was escalated, what action was taken and who signed it off. When an auditor or the FCA asks how a particular break was handled, a workbook and a folder of emails will not carry the weight.

The practical problem most firms face is not a shortage of data. The data exists. It is simply spread across customer ledgers, bank portals, payment processor exports, spreadsheets and the working memory of whoever ran the last reconciliation. Assembling that picture once a month is demanding enough. Assembling it every business day, to a standard that survives an audit, is a different order of task altogether. That is the operational control challenge PS25/12 has created, and it is precisely the part that never appears on the face of the return.

Where this leaves firms

This is the work Imperium(L) Prism is built for. Prism brings the owed side and the held side into a single view, runs internal and external reconciliation daily, and surfaces breaks the same day they happen rather than three weeks later when someone opens the file. It wraps each break in a structured resolution workflow, with an owner, a severity, a deadline, evidence and sign-off, and it tracks resolution-pack completeness against the documents the pack actually needs. Every reconciliation, action and sign-off is captured, timestamped and attributable, and the monthly safeguarding return data is generated from controlled reconciliation rather than rebuilt by hand at month end.

It is worth saying that this is not untested thinking. Prism is built on reconciliation and customer-fund-protection technology that has supported businesses in live, high-volume environments for over 12 years, so the operational logic behind it has already been proven against real money, real reconciliations and real audits.

CASS 15 set a deadline, and that deadline has passed. The firms that will find the regime manageable are the ones that treat it as what it is, a continuous control discipline that happens to produce a monthly report, rather than a monthly report that happens to require some control. The return is the easy part. The control behind it is the point.

Book a Demo

Frequently Asked Questions

Is CASS 15 just a new reporting requirement?

No. The monthly safeguarding return is only the visible output of CASS 15. The regime set out in PS25/12 is built around daily operational control: regular internal and external reconciliation, prompt correction of discrepancies, a resolution pack, acknowledgement letters, due diligence and an annual safeguarding audit. The reporting sits on top of that control, not in place of it.

The Supplementary Regime came into force on 7 May 2026, following a nine-month implementation period after PS25/12 was published in August 2025.

The segregation requirement is what a firm should be holding in safeguarding to cover what it owes customers. The segregation resource is what it actually holds. CASS 15 asks firms to compare the two on each reconciliation day and to correct any shortfall promptly.

Not all. The FCA has exempted the smallest firms, those whose relevant funds do not exceed £100,000, from the safeguarding audit requirement. Firms above that threshold must support an annual audit.

The post CASS 15 Operational Control Challenge appeared first on Imperium(L).

]]> Safeguarding Visibility Starts with a Unified Ledger https://www.imperiuml.com/insights/safeguarding-visibility-starts-with-a-unified-ledger/ Tue, 23 Jun 2026 11:56:02 +0000 https://www.imperiuml.com/?p=3519 Under the FCA’s CASS 15 safeguarding regime, in force since 7 May 2026, payments and e-money firms must identify relevant funds at any time without delay, reconcile what is owed to customers against what is held in safeguarding on each reconciliation day, and maintain a resolution pack. A unified ledger is the operational layer that […]

The post Safeguarding Visibility Starts with a Unified Ledger appeared first on Imperium(L).

]]>

Why safeguarding visibility starts with a unified ledger.

Most payments and e-money firms do not have a safeguarding data problem. They have a safeguarding data assembly problem. CASS 15 has made that distinction expensive.

  • By Imperium(L)
  • June 2026
  • Approx 8 Minute Read

Ask a payments or e-money firm whether it knows what it owes its customers, and the answer is almost always yes. Ask whether it knows what it holds in safeguarding accounts to protect them, and the answer is yes again. Ask whether it can show, right now, the two numbers side by side, drawn from current data, on the same screen, with a complete record of what has moved between them since this morning, and the answer becomes more interesting. In most firms, that is not a question the systems can answer without help.

This is the visibility problem the new safeguarding regime has put a spotlight on.

It is not, in the usual sense, a data shortage. Most firms have everything they need, somewhere. The customer ledger knows what is owed. The bank portals know what is held. The payment processor exports show what is in flight. Internal cashbooks, claims systems, refund logs, FX conversion tables and a string of spreadsheets each carry part of the picture. The trouble is that no single place in the business carries all of it at once, in a current and reviewable form. Pulling it together once a month, for the return or for the auditor, is demanding enough. Doing it every business day, to a standard that survives scrutiny, is a different task altogether.

What CASS 15 actually expects firms to see

Under the chapter introduced by Policy Statement PS25/12 and in force since 7 May 2026, the safeguarding rules set a books and records expectation that does not bend. A firm must be able to identify the funds it holds as relevant funds, distinguish them from its own, and do so at any time, without delay.

That phrasing matters. It describes a state of continuous visibility, not a monthly assembly job.

Sitting on top of that, the chapter requires reconciliation of what is owed against what is held, both internally between the customer ledger and the firm’s records of safeguarded amounts, and externally against bank and third-party data, on each reconciliation day. Any discrepancy is to be corrected promptly. The resolution pack expectation in CASS 10A then assumes that, if the worst happens, the firm can produce a clear, current picture of relevant funds and the customers they belong to, so that money can be returned without delay.

Read those three obligations together and a single operational requirement falls out of them.

The firm needs to see, in one place, what it owes and what it holds, with the underlying detail intact, every business day. Fragmented data cannot deliver that. It can deliver the appearance of it once a month, with enough effort, but the appearance is the part the regime is moving away from.

What goes wrong when the picture is fragmented

Three things, predictably, in the firms we have looked at.

  1. The first is timing. If the picture lives across five sources, the firm can only see it when someone takes the time to assemble it, and that time tends to fall at month end. By then, the small discrepancy from two weeks ago has either resolved itself, quietly, or grown into something larger. Breaks that should have been corrected the same day get caught in the next cycle instead, or the cycle after that. The cost of late detection is not always financial. Often, it is the loss of the trail that would have explained how the break happened in the first place.
  2. The second is evidence. When an auditor or the regulator asks how a particular break was handled, a stitched-together story drawn from four spreadsheets and an email thread does not carry the weight. The firm did the work, very often. It just cannot prove it cleanly. In a regime that is increasingly built around demonstrable control rather than periodic disclosure, work that cannot be proved is, for practical purposes, work that did not happen.
  3. The third is speed in resolution. The CASS 10A resolution pack is not really about a document. It is about the firm’s ability to move quickly under stress, with a clear picture of relevant funds and the customers they belong to. Fragmented data makes that act of assembly slow exactly when speed matters most. The firms that have thought hardest about this are the ones that have realised the resolution pack is, in effect, a daily readiness exercise, not an annual paperwork one.

What a unified ledger actually is

The term unified ledger does not appear in the rules.

It is not a regulatory artefact.

It is the operational answer to what the rules now require.

In plain language, a unified ledger is a single view of what is owed to customers, set against what is held to protect them, drawn from all the underlying sources, kept current, and reviewable. Customer ledger data, safeguarding account balances, bank and third-party records and exception activity sit together, and when one of them moves, the picture moves with it.

Two things are worth being clear about. A unified ledger is not a dashboard in the cosmetic sense. It is the connecting tissue underneath one. And it does not replace the firm’s existing systems. The customer ledger, the cashbook, the bank feeds and the payment processor records all still matter. The unified ledger is the layer that brings them into a single operational view and reconciles the result. Done well, it makes the question “what is happening with safeguarding right now” answerable without phoning anyone.

What changes when a firm has a unified ledger?

The change is easier to describe than to engineer.

Breaks surface the day they happen rather than three weeks later, because the comparison runs every business day. The trail behind every action is captured automatically, because the actions take place inside the system that holds the picture, rather than in messages and workbooks outside it. Senior

managers get a current view of safeguarding exposure rather than a monthly snapshot, which changes the questions they can ask and the speed at which they can ask them. And when a regulator, auditor or board member wants the firm’s safeguarding position, the firm produces it rather than reconstructs it.

This is the work Imperium(L) Prism is built for. Prism brings the owed side and the held side together, runs internal and external reconciliation daily, surfaces breaks the same day, captures a timestamped audit trail of every action and turns controlled reconciliation into the data behind the monthly safeguarding return. The technology has supported businesses in live, high-volume environments for over 12 years, so the operational logic behind it has already been tested against real money, real reconciliations and real audits.

Safeguarding under CASS 15 starts with a question that sounds simple. What does the firm owe its customers, and what is it holding to protect them, right now? The firms that can answer cleanly will find the rest of the regime manageable. The ones that cannot will spend the next audit cycle trying to assemble an answer they should have been able to see all along.

Book a Demo

Frequently Asked Questions

What is a unified ledger?

A unified ledger is a single, current view of what a firm owes its customers set against what it holds to protect them, drawn from the firm’s customer ledger, safeguarding account balances, bank and third-party records and exception activity. It is the connecting layer beneath any safeguarding dashboard, not a replacement for the underlying systems.

No. The CASS 15 rules do not mandate a unified ledger by name. They require firms to maintain accurate books and records that identify relevant funds at any time without delay, to reconcile what is owed against what is held both internally and externally on each reconciliation day, and to maintain a resolution pack. Meeting those obligations daily, on fragmented data, is the operational difficulty a unified ledger is built to remove.

CASS 15 requires reconciliation of what is owed against what is held on each reconciliation day, both internally between the customer ledger and the firm’s safeguarding records, and externally against bank and third-party data. Discrepancies are to be corrected promptly.

No. A unified ledger sits across the firm’s existing customer ledger, cashbook, bank feeds and payment processor records and brings them into a single operational view. The underlying systems remain, and the firm continues to rely on them.

The post Safeguarding Visibility Starts with a Unified Ledger appeared first on Imperium(L).

]]>