Reconcile records and balances
Make agreement, discrepancies and unavailable data explicit in your operations workflow.
Reconciliation connects the integration's recorded balances and activity to the sources your team uses to verify them. It should produce a clear outcome and an owner for the next step.
Partner-scoped records
Partner keys can read reconciliation balances, ledger entries and snapshots for their account. Use these resources to inspect attributed positions and their recorded events.
The reconciliation ledger supports cursor pagination. The user ledger is a different method with a bounded recent-event limit; do not apply the same pagination loop to both.
Protocol-wide comparison
GET /reconciliation/report requires administrative read access. It compares the internal view with the configured monitoring source and reports reconciled, mismatch or unavailable.
| Result | Meaning for operations |
|---|---|
reconciled |
The compared values satisfy the report's configured tolerance. |
mismatch |
The comparison found a discrepancy to investigate. |
unavailable |
A required source or observation could not support the comparison. |
Do not interpret unavailable onchain data as a zero balance or successful reconciliation.
Define the response to a discrepancy
Record the affected asset, time, expected source, observed value and tolerance. Assign an owner who can inspect the underlying position and event records. Decide how the customer interface behaves while the investigation is open.
For launch, agree which records are authoritative for customer accounting and transaction settlement. The report is one part of that operating design, not a substitute for choosing the source of truth.