FCA Safeguarding Reconciliation & Client Money Proof
Daily deterministic reconciliation across designated safeguarding accounts, segregated client funds, and internal virtual balances.
The Daily Safeguarding Calculation Framework
Institutions must aggregate all relevant funds received from customers for payment transactions or in exchange for e-money. The total client liability balance at close of business (T) forms the safeguarding requirement. The NAYA Proof Engine pulls transaction events across all payment channels to compute this requirement in real time, preventing reconciliation delays.
Internal vs External Safeguarding Reconciliations
The internal reconciliation compares transaction logs, customer balances, and uncleared settlement batches to verify ledger integrity. The external reconciliation verifies that bank balances across designated safeguarding accounts match or exceed the internal requirement. Discrepancies caused by uncollected fees, pending card settlements, or foreign exchange shifts are flagged instantly with root-cause lineage.
Deterministic Audit Trails with the NAYA Proof Engine
Regulatory audits demand verifiable proof of daily reconciliation execution. The NAYA Proof Engine generates immutable daily reconciliation snapshots, recording exact account balances, bank statement extracts (MT940/camt.053), and remediation transfers, providing external auditors and regulators with cryptographic attestation of compliance.
Frequently Asked Questions
Common questions about this topic
QWhat is FCA safeguarding reconciliation compliance?
It is the regulatory requirement for e-money and payment institutions to accurately match their internal records of customer funds with the actual funds held in external safeguarding accounts, ensuring customer money is fully protected.
QWhy is May 2026 significant for fintechs?
May 2026 marks the mandatory implementation deadline for the FCA's updated safeguarding regime for payment and e-money institutions. The rules mandate rigorous, continuous reconciliation of client balances against designated safeguarding bank accounts, backed by verifiable audit trails and daily shortfall resolution.
QHow does automated reconciliation help with compliance?
Automated reconciliation infrastructure programmatically ingests safeguarding bank statements, normalizes internal transaction events, and executes deterministic matching on a daily schedule. This eliminates manual calculation errors, provides instant notification of safeguarding discrepancies, and produces regulator-ready audit packs upon request.
QHow often must e-money institutions perform safeguarding reconciliation?
Under the new FCA safeguarding rules, institutions must perform reconciliation as often as necessary to ensure accuracy. For most fintechs, this means transitioning from periodic or end-of-month checks to daily or even continuous automated reconciliation.
QCan manual processes meet the new FCA safeguarding reconciliation rules?
No. Spreadsheets and manual matching processes are error-prone and too slow to meet the FCA's strict standards. Firms must adopt robust, developer-first financial infrastructure to ensure continuous, accurate matching.
QWhat is the difference between standard reconciliation and FCA safeguarding reconciliation?
Standard reconciliation often focuses on general ledger accuracy for reporting, whereas FCA safeguarding reconciliation specifically verifies that the internal ledger of customer balances perfectly matches the actual funds held in external safeguarding accounts with absolute precision, protecting customer money from firm failure.
Get technical insights weekly
Join 4,000+ fintech engineers receiving our best operational patterns.