How to reconcile e-money safeguarding accounts with an AI agent

Each day the agent calculates what you owe e-money holders from your own ledger, reads what sits in the safeguarding accounts, and explains every difference. It drafts a top-up or a withdrawal with the reasons. A named person in finance approves the result and releases any transfer, and decides whether a shortfall needs reporting.

What is a safeguarding reconciliation, and who owns it?

An e-money or payment institution holds customer funds that are not its own money. Safeguarding keeps them apart, usually in designated accounts at a bank, so that customers can be repaid if the firm fails. The reconciliation compares two numbers: the requirement, meaning what the firm owes its customers according to its own records, and the resource, meaning what actually sits in the safeguarding accounts. A shortfall must be made good quickly. An excess is the firm's own money and may be withdrawn once it is confirmed.

Finance runs the reconciliation. A senior manager is usually accountable for safeguarding, and the board sees the results. Supervisors take safeguarding failures seriously because they put customer money at risk. That makes this a good job for an agent to prepare and a bad one for an agent to finish. The adjacent question of whether an agent can reconcile safeguarded customer funds is answered the same way: it prepares, a person signs.

What does the agent prepare?

1. Agent, depth 1: calculates the requirement. From your customer ledger: balances owed to customers, by currency, at the reconciliation point.
2. Agent, depth 1: reads the resource. Balances in each safeguarding account at the same point, from the bank's statement feed.
3. Agent, depth 1: matches movements. Receipts, payouts and card settlements between ledger and statement, so differences can be traced to items.
4. Agent, depth 1: explains differences. Each break is classified: timing, such as funds in transit; unallocated receipts; fees not yet due to the firm; errors.
5. Agent, depth 2: drafts the reconciliation. Requirement, resource, difference, every break with its explanation, and a proposed top-up or withdrawal.
6. Person: approves the reconciliation. The finance owner reviews breaks and approves or challenges.
7. Person: releases any transfer. A top-up or withdrawal is depth 4 work, released by a named person.
8. Person: decides on escalation. Unresolved shortfalls, or a day when the reconciliation could not be done, go to the accountable manager, who decides whether a report is needed.

Which controls apply, and what evidence do they leave?

Same cut-off on both sides. Requirement and resource must be measured at the same point. The record shows the timestamps of the ledger extract and the statement.

Provenance on the resource. Your ledger is sealed. A statement received through an authenticated bank feed is stronger than a figure keyed in from a portal. The reconciliation shows which source was used for each account.

No netting across currencies. A shortfall in one currency is not covered by an excess in another. The agent reconciles each currency on its own and the bound refuses any proposal that nets them.

Transfers held. The agent has no capability to move money between safeguarding and operating accounts. Moving money between accounts is depth 4 work, and here even the top-up waits for a person. Evidence: the held verdict, the releasing person and the time.

Ageing of breaks. Each break carries its first-seen date. Timing differences that persist are no longer timing differences.

Where does it usually go wrong?

Fees treated as earned too early. A fee shown in the ledger but not yet due to the firm is still customer money. Counting it as the firm's own makes the requirement look smaller than it is.

Aged timing breaks. "In transit" accepted every day for weeks hides a real shortfall. The draft should list breaks by age and push old ones to the top.

Withdrawing excess on a bad day. An excess caused by an unrecorded payout is not an excess. Proposals to withdraw should require the previous days' reconciliations to be clean as well.

Unallocated receipts left hanging. Money received but not matched to a customer still belongs to someone. Some unallocated receipts are payments from customers that never reached their wallets; others can signal accounts receiving funds they should not, which is a case for the fraud team and the approach in investigating suspected money mule accounts.

Copying the bank reconciliation process. Safeguarding is not a simple bank-to-ledger reconciliation. The requirement side has its own rules. For the more familiar pattern, see reconciling nostro accounts, and note where the two differ.

What should you measure?

• Reconciliations completed by the daily deadline.
• Shortfalls, size and time to top-up. The core safety measure.
• Breaks older than your policy's threshold.
• Proposed transfers changed by the approver.
• Days the reconciliation could not be performed, and why.

Where Pryme fits

In Pryme, the safeguarding reconciliation is certified through Attest on your own past reconciliations, including days with real shortfalls. Ledger data arrives sealed through the Pryme Context Protocol, statement data is labelled by source, and no agent holds a transfer capability on safeguarding accounts. The general bounds are in AI agents in banking.