Skip to main content

PSCR PUBLIC GUIDE

Relevant funds, segregation and the scope of safeguarding

The phrase “customer funds” can conceal important differences between activities, timing, entities and legal character.

01

Plain-language summary

Relevant funds are not simply every amount visible in a payment interface. The term must be read against the exact institution, activity, customer relationship, timing and applicable framework. A useful public explanation starts by defining what funds are in scope and what funds or activities are outside it.

Segregation describes keeping defined funds apart from the institution’s own funds through a stated arrangement. It is one part of a wider safeguarding system. Account designation, reconciliation, operational controls, record ownership, third-party dependencies and the route for returning funds all matter.

02

Why scope matters

Payment institutions can provide different services through multiple products, agents or territories. Money may be in transit, awaiting execution, held as electronic money, subject to a refund, reserved for a merchant or outside the defined safeguarding perimeter. Similar-looking balances can therefore require different analysis.

The legal entity receiving funds and the contractual service remain central. A brand statement cannot establish scope. Neither can a group-level policy if the customer relationship sits elsewhere. Evidence should show how the institution identifies relevant funds at the relevant time and how changes in transaction state are handled.

03

Segregation and reconciliation

A segregated or designated account may support a safeguarding method, but the account label alone does not show that the correct amount is present or that records identify the right customers. Reconciliation compares liabilities, transaction records and safeguarded resources according to a defined process. The frequency, data sources, exceptions, ownership and review date are therefore material.

Evidence may include policy documents, account confirmations, reconciliations, exception logs, governance records and independent work. Public fields should describe their character and date without exposing bank account numbers, security details or confidential customer information.

04

Evidence questions

A careful review moves from scope to method and then to operation.

  • Which activities produce relevant funds?
  • When does the institution treat those funds as entering and leaving scope?
  • Which entity owns the safeguarding process?
  • How are amounts calculated and reconciled?
  • How are shortfalls, excesses and exceptions handled?
  • Which sensitive details remain confidential?
  • What material changes have occurred since the evidence date?
05

What not to assume

Do not infer that every payment-related balance is safeguarded in the same way. Do not infer that segregation eliminates operational, bank, record or insolvency risk. Do not treat a historic account letter or reconciliation sample as proof of a current position. Do not treat safeguarding as deposit protection or a promise of recovery.

PSCR’s developing method keeps the source date, review date, limitations and return route visible. It does not convert documentary evidence into statutory assurance or an audit opinion.

06

Related PSCR and RMCA material

The Safeguarding page separates the main concepts. The Safeguarding Passport shows the proposed field architecture. Resolution Readiness examines records, access, communications and return processes. RCEF places these questions within the wider conduct-evidence framework.