On-/Off-Chain Reconciliation Agent
Proves agreement among chain state, custody records, internal subledgers, cash, and general ledger.
Normalizes transaction identity and finality, performs event- and balance-level reconciliations, explains timing differences, and prevents forced matches from hiding economic breaks.
Authority
Monitor and intervene
Team role
Provides independent challenge
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Tokenized Markets, Books & Reporting
Desk workflow
Bind trade intent, coordinate delivery and payment, establish finality, reconcile books, surveil behavior, and report.
Collaboration
Separates preparation from review
Decision boundary
Monitors continuously and intervenes only within stated limits.
Systems and capabilities involved
Chain and token indexers
Custody and transfer-agent feeds
Subledger and general ledger
Break management
Handoffs
What this role gives and receives
Capabilities offered
Reconcile a digital-asset event
Performs finality-aware event and balance proof across chain, custody, and books.
- Receives:
- Event mandate, chain receipts, and ledger postings
- Returns:
- Matched proof or classified break with owner
Delegates
accounting policy specialist
Resolve material classification, recognition, or valuation ambiguity. Trigger: A break depends on accounting interpretation rather than missing data Returns: Approved accounting treatment and posting instructions.
Handoff to
Handoff to
Receives from
Receives from
External handoff
Operations break management
Context
What the role needs to do the work
- Current work
- The matter in flight: its assets, events, policy results, approvals, and unresolved facts
- Prior interactions
- Prior cases on the same asset or counterparty, exceptions, and reviewer outcomes
- Policies and reference
- Firm asset, chain, entity, jurisdiction, risk, control, and reporting taxonomies
- Working method
- The desk's own approved runbooks and escalation paths
Illustrative workflow
How the work moves
Starting point
Custody shows a settled token transfer that the subledger lacks
- 01
Anchor chain event and finality
- 02
Trace custody and subledger identifiers
- 03
Classify timing or economic break
- 04
Assign correction and prove closure
Result
Cross-domain reconciliation proof with owned exceptions and aging
Checks and boundaries
What must be tested or reviewed
- 01Seeded duplicate, reorg, fee, decimal, and cutoff breaks surface as breaks, not matches
- 02Transactions with unequal economic terms cannot be force-matched; the break stands until explained
- 03Balance proof ties event population to the general ledger within stated tolerance
Human authority
- Accounting or operations owner approves material write-offs, manual journals, and exception closure
Keep exploring