When the return-of-funds route is not operationally clear

Policies describe where relevant funds should be held, but the failure plan does not clearly assign access to customer records, reconciliation ownership, third-party contacts, complaint handling or authority to communicate and return funds.

The gap becomes material because a return route depends on coordinated records, access and decisions rather than on the safeguarding method alone.

Map the process from incident through reconciliation, customer identification, control of access, communication, return or resolution and outcome recording. Identify each owner, dependency and evidence source. Preserve the distinction between an institution complaint process and any insolvency, special-administration or other route that may apply.

• —Record ownership and retrieval
• —Latest reconciliation state
• —Safeguarding-institution dependency
• —Outsourced operations
• —Customer communication owner
• —Complaint and escalation routes
• —Return authority and outcome log

A tested plan can support readiness but cannot establish what will happen in every failure. Third-party, legal, data and operational conditions may differ at the event date. Public fields should therefore state the plan character, test date and limitations.

PSCR must not promise recovery, an amount or a timetable. It can make the intended process and unresolved dependencies visible.

The methodology turns a vague return statement into accountable stages and dated evidence. Where ownership or access remains unclear, that limitation should be published rather than inferred away.

This is a scenario-based methodology note, not advice or a record concerning a real institution.