R2, R1, R5 and R3
Safeguarding and Reconciliation
The figure you report should be the one the money made. The safeguarding requirement is computed from the ledger the payments moved through, compared daily against what is actually held, and the comparison reports a heartbeat so that a check which stops running is an alert rather than a silence.
Covered, shortfall or excess, every day.
Three outcomes, and the third one matters more than people expect. An excess is your own money sitting in a safeguarding account, which is a different problem from a shortfall but still a problem, and a system that only alarms on shortfalls will never tell you about it.
The run reports a heartbeat. A reconciliation that silently stopped looks exactly like one that keeps passing, so the absence of a run is itself raised by ops.job_heartbeats.
The run reports a heartbeat. A reconciliation that stops is raised as its own alert by ops.job_heartbeats, because a check that silently stopped running looks exactly like a check that keeps passing.
What goes into the requirement.
Three components, because client balances alone understate it. Money you have received and not yet placed is still client money.
And what counts as holding it.
Breaks are typed, not noted.
CASS 15 requires timing differences to be distinguished from substantive discrepancies, and a supervisor asks for them separately. So the reason two sets of records disagree is a type on the break rather than a sentence in a comment field. Breaks also age: an unresolved one gets older in a queue rather than quietly becoming part of the furniture.
DUPLICATE_CANDIDATE outranks everything else for urgency, because two of ours against one of theirs is possibly a payment made twice. DATE_MISMATCH is its own type rather than a note on a generic break, because a timing difference is usually benign and a supervisor asks for the two separately.
Reporting, and fees.
Both computed from the same ledger, which is the whole argument of this page.
What it guarantees.
Each of these is enforced rather than intended, and each is something you can sit down and try to break on a call. We would rather you did.
- The requirement is derived from the ledger the payments moved through, so the figure you file and the figure you hold are the same arithmetic.
- A reconciliation that stops running raises an alert of its own. Silence is a failure state, because a check that quietly stopped looks exactly like one that keeps passing.
- Breaks are typed rather than noted, so a timing difference and a substantive discrepancy are counted separately, which is how a supervisor asks for them.
- The general-ledger export ties to the trial balance. An export that does not reconcile to the book it came from is a spreadsheet.
Bring last month's safeguarding calculation.
We will compute it from a ledger seeded with your transaction types and show you where the two disagree.