Safeguarding Reconciliation Software for EMIs and Payment Institutions

The reconciliation population is wider than the safeguarding account

Firms usually describe their safeguarding reconciliation as bank versus ledger. In an EMI or PI of any scale, that description is incomplete and the incompleteness is where breaches originate.

Relevant funds sit in safeguarding accounts, but they also sit temporarily with acquirers pending settlement, with card schemes, with agents and distributors collecting on the firm's behalf, with correspondent banks in cross-border corridors, and occasionally with e-money distributors holding float. Each of those is a separate balance with a separate reporting cadence and a separate failure mode.

A reconciliation that covers the safeguarding account and treats everything else as in transit is asserting, without testing, that the in-transit amount is correct. That assertion is exactly what an external reconciliation exists to test.

The first thing a serious platform does is enumerate the population. Every account, every counterparty, every corridor. An account that stops reporting becomes a raised exception rather than a silent omission.

Timing differences are not variances, and confusing them is expensive

Most breaks in payments reconciliation are timing. A settlement initiated on Friday lands Tuesday. A scheme reports net where the ledger records gross. A refund is booked at authorisation and settles days later.

The compliance risk is not the timing difference itself. It is the habit of treating every difference as timing. Once a team learns to clear breaks by ageing them, a genuine shortfall ages alongside the noise and is discovered late.

The correct discipline is to prove the timing hypothesis for each break rather than to assume it. That means locating the specific expected settlement, confirming its value and date, and attaching that evidence to the break. Doing this manually across thousands of items is the single largest operational cost in safeguarding, and it is the cost automation actually removes.

The controls an FCA-ready platform must evidence

Daily internal reconciliation of customer entitlement records against the firm's safeguarding obligation, performed, reviewed, and retained.

Daily external reconciliation against confirmed third-party balances, with any non-reporting counterparty raised as an exception.

Immediate correction of shortfalls from the firm's own resources, and prompt withdrawal of excesses, each recorded as an attributable event linked to the run that identified it.

Records that distinguish, without delay, relevant funds held for one customer from those held for another and from the firm's own money.

The monthly FCA safeguarding return, generated from the same data as the daily positions.

A resolution pack maintained current and producible on request.

Senior management reporting sufficient for SM&CR accountability to be exercised in real time rather than in arrears.

Safeheld's approach

Safeheld ingests statements, settlement files, scheme reports, and ledger extracts in whatever format the counterparty provides, mapping unfamiliar schemas automatically rather than requiring a data project per source.

Reconciliation runs continuously across the full population. Each break is investigated autonomously: the engine retrieves the candidate settlement, tests the timing hypothesis, values it, and either resolves the break with evidence attached or escalates it with its reasoning visible. Only genuinely ambiguous items reach a human.

Runs are sealed with a SHA-256 Merkle root and are independently verifiable. Corrections attach to the run that identified them. Returns, resolution packs, board reporting, and audit evidence are generated from those sealed runs, so the firm has one safeguarding record and every artefact traces to it.

Frequently asked questions

What should a safeguarding reconciliation cover beyond the bank account?

Every location where relevant funds sit: safeguarding accounts, acquirer settlement balances, scheme positions, agent and distributor float, and correspondent balances in cross-border corridors. Anything treated as in transit without being tested is an untested assertion.

How are timing differences handled correctly?

By proving the hypothesis rather than assuming it. Each break should be matched to the specific expected settlement, with value and date confirmed and the evidence attached, so that a genuine shortfall cannot age quietly alongside routine timing noise.

Can the platform reconcile multi-currency safeguarding positions?

Yes. Positions are reconciled in the currency of the underlying obligation, with revaluation treated as a distinct, evidenced adjustment rather than absorbed into the match.