Reconciliation and Break Resolution

Match transactions across systems, explain the breaks, and propose resolutions for ops to approve.

What It Does

The agent matches records deterministically across the general ledger, custodian files, and bank statements, classifies every remaining break with a likely cause and the evidence behind it, and prepares the correcting posting. Ops approves it, anything above the bank's thresholds routes to a named signer, and every posting is logged.Without it: Daily recs consume ops teams, and unexplained breaks age while analysts chase data across systems.

  • Separates timing differences that will clear tomorrow from true breaks
  • FX and fee differences inside tolerance are classified, never matched away
  • A break it cannot explain is aged and handed over with what it ruled out
  • The agent that investigates a break is not the one that posts it

Illustrative example

The nostro run closes leaving 212 exceptions. One is a $1,840 shortfall on the USD correspondent account, which the agent ties to a wire fee the correspondent netted at settlement, rules out as a duplicate by matching on the payment reference, and prepares as a correcting posting to the fees account. It sits under the $5,000 threshold that would send it to a named signer, so the ops approver takes it, and the whole chain lands in the audit log.

Reads

GL

Book-side postings

Bank and custodian files

Statement lines, fees

Rec platform

The run's exceptions

Runs

Reconciliation and break resolution

Execute

Starts when

A reconciliation run completes and leaves exceptions

How far it goes

it acts inside set limits, and every call is logged

Never

LEDGER: enforced below the model, not asked of it

Produces

Matched records

Matched on keys, never guessed

Breaks

Classified with causes

Correcting posting

Prepared for approval

Reconciliation and break resolution. Reads GL, Book-side postings; Bank and custodian files, Statement lines, fees; Rec platform, The run's exceptions. Execute autonomy: it acts inside set limits, and every call is logged. It never ledger. Produces Matched records Matched on keys, never guessed; Breaks Classified with causes; Correcting posting Prepared for approval.

Give Us One Stuck Pilot.

We'll have it in governed production before your next board meeting.