Answer first: A payment firm's safeguarding control is credible only when it can identify relevant funds, reconcile internal records to external accounts, explain and clear differences, evidence governance and support an orderly return of funds. The daily control must follow the legal scope and timing of the regime, not a convenient ledger balance or monthly spreadsheet ritual.

Key takeaways

  • Determine which funds, products and legal entities fall into the relevant-funds population.
  • Perform and evidence internal and external reconciliations on the required timetable.
  • Age exceptions, fund shortfalls and escalate control failure without delay.
  • Keep acknowledgement letters, due diligence and resolution-pack evidence current.

Decision framework

Decision area Evidence to require Risk it controls
Population Product-to-legal-basis map and client-level liability Wrong safeguarding requirement
Internal reconciliation Books and records support aggregate relevant funds Hidden liability gap
External reconciliation Bank/custodian evidence agrees or exception is logged Unexplained shortfall
Exception Owner, value, cause, funding and deadline Permanent suspense
Resolution Current accounts, contacts, letters and retrieval evidence Delayed return on failure

A payment firm needs to establish what it owes customers, which funds meet the applicable safeguarding requirements and whether its records reconcile. A large balance in a designated account cannot answer those questions on its own. The firm must be able to explain the difference between customer liabilities, money in transit and its own cash.

This is a daily operating discipline. It depends on product design, finance systems, payment-provider files and accountable review. Treating it as an annual audit preparation exercise leaves the business exposed to errors created throughout the year.

Understand the regime that applies now

The FCA's PS25/12 introduced a Supplementary Regime effective from 7 May 2026. Its safeguarding page points firms to the relevant payment-services or electronic-money regulations and applicable CASS and SUP provisions. 12 A firm should therefore identify its exact obligations and implementation status rather than continue relying on an older generic policy.

Create an applicability record approved by the responsible specialists. Include legal entities, permissions, products, funds flows, safeguarding method and relevant exclusions. A group with several products may need more than one answer.

The applicable rules determine which balances and methods qualify. The operational work is to connect those requirements to the firm's actual funds flow and records.

Map the liability before choosing the spreadsheet

Trace a customer's money from receipt through processing, settlement, fees, refunds and withdrawal. Identify when each event changes the customer liability and where evidence of that event originates.

Do not assume the processor's available balance is the customer liability. A settlement delay, reserve or deducted fee can create a different number. Equally, a customer-facing wallet balance may include an authorised transaction that has not yet settled.

For each event record a stable identifier, currency, amount, timestamp, legal entity and status. Agree which system is authoritative for each fact. Reconciliation becomes fragile when two teams can edit the same balance without an auditable adjustment record.

Reconcile populations and timing

A reconciliation needs a defined cut-off and a complete population. State which transactions belong to the day and how late-arriving files are handled. Retain the source extracts used, so a reviewer can reproduce the calculation.

CASS 15 contains detailed safeguarding requirements, including reconciliation provisions. 3 Translate the applicable requirements into documented procedures, rather than assuming a software vendor's report is sufficient.

An illustrative difference of £8,000 might comprise £5,000 of unsettled receipts, £2,000 of refunds recorded in different periods and £1,000 with no explanation. These are three separate issues. Labelling all £8,000 timing difference conceals the unexplained amount.

Give exceptions an expiry date

Each exception should have an owner, amount, age, customer impact, evidence and next action. Track how long it has remained unresolved and whether it recurs. A small repeated error can reveal a broken integration even when the daily net difference looks immaterial.

Avoid compensating adjustments that make totals agree without fixing the underlying record.

They can create a false impression of control and make later customer claims harder to reconstruct.

Escalation should depend on the applicable requirements and the nature of the issue, not just an internal financial threshold. A system failure affecting completeness deserves attention even before its monetary effect is known.

Keep operating cash out of the picture

Customer funds must not be mistaken for the firm's available runway. Finance reporting should distinguish restricted or safeguarded balances from money available to pay salaries and suppliers.

Model provider insolvency, missing settlement files and loss of access to a key account. Ask how the firm would reconstruct customer entitlements from preserved records. A technically sound ledger is of limited use if the only person who knows how to operate it has left.

Test a new product before the first customer balance

Ask finance to walk through an ordinary receipt, fee, refund, failed payment and closure in the proposed product. Identify which events create or extinguish a liability and which source records prove them.

Suppose a hypothetical instant-refund feature credits the customer's view before the external refund settles. The firm needs a documented treatment of the intervening state, rather than letting engineering and finance independently choose what the balance means.

Include weekends and unavailable files. A control designed around a provider report delivered on working days needs an understood process for other periods, consistent with applicable requirements.

Make reviewer independence practical

A reviewer should challenge completeness and exceptions, not simply confirm that a spreadsheet contains no visible error. Provide the source population, method, changes and unresolved items.

Where the team is small, document how responsibilities are separated and which compensating checks apply. Do not claim independence when the reviewer generated the same figures and has no separate evidence.

Review manual access too. A reconciliation may be mathematically correct while an unauthorised adjustment changes the underlying liability. Preserve who changed what, why and with which approval.

The useful standard is that someone can reproduce the result and question its assumptions.

This supports continuity when staff change and gives management an evidential basis for asking whether a larger product volume can be controlled with the current process.

What should the board see?

Show reconciliation completion, unresolved exceptions, ageing, control failures and remedial work. Add evidence of independent review and changes to products or providers that alter the funds flow.

Ask a reviewer to reconstruct one day's customer liabilities and safeguarded position from the preserved records. Any difference that cannot be explained needs an owner and a remedy. That exercise provides more assurance than a large account balance or a completed checklist.

A practical 90-day implementation plan

  1. Rebuild the relevant-funds population from products, flows and legal entities.
  2. Trace one day's opening balance, receipts, payments, adjustments and closing liability to external evidence.
  3. Introduce aged-exception, shortfall-funding and notification triggers with named owners.
  4. Run a resolution-pack retrieval test and report the elapsed time and missing evidence to the governing body.

Frequently asked questions

Is a positive safeguarding account balance enough?

No. The firm needs evidence that the amount and population safeguarded correspond to relevant-funds obligations and that differences are identified and resolved.

How should unidentified receipts be treated?

Follow the applicable CASS 15 rules and guidance: investigate promptly, record them appropriately and do not assume unidentified money is operating cash.

When should product teams involve safeguarding owners?

Before launch or any flow change. New collection, refund, fee or timing mechanics can alter the relevant-funds population and reconciliation design.

Reporting by Shoreditch Talk