Help Center/Admin Operations/Read the Payment Reconciliation page and annotate a system account
Admin Operations•Last updated: 2026-10-20•5 min read

Read the Payment Reconciliation page and annotate a system account

The page lists everything that does not reconcile, unhidden: wallets whose balance differs from the net of their ledger entries, succeeded payments without a ledger credit, ledger credits without a succeeded payment and unmatched chain transfers.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the page

Open "Finance & Payments" then "Reconciliation" (/admin/payments/reconciliation).

2

Read the KPI tiles

Wallets and ledger entries audited, wallets drifting (with how many are annotated), payments without credit, credits without payment, unmatched chain transfers and the status of the last recorded run.

3

Read a row

Check, Subject, Currency, Recorded, Ledger Net, Difference, Status (DRIFT, ANNOTATED, UNCREDITED, ORPHAN, UNMATCHED) and a Note. A large difference on a treasury wallet usually means a mint or system account that is not modelled as transfers; the page shows it anyway.

4

Annotate a mint or system account

Click "New Record" (super admin), enter the "Wallet DID" exactly as shown, the "Currency" and a "Reason" of at least 15 characters. The row becomes ANNOTATED with your reason and name; the drift and its numbers stay visible.

5

Revoke an annotation

Delete the ANNOTATED row and give a reason: the annotation is revoked (status change, history kept) and the row shows as DRIFT again.

6

Record a run

Click "Record a run (last 24h)" and confirm. The message states the stored status. The external provider statement is not compared in this deployment, so a clean run reads NOT_VERIFIED, not "reconciled".

Expected Operational Outcome

You can see every discrepancy, have labelled legitimate system accounts with an explicit reason, and recorded a run honestly.

Troubleshooting & Failure Modes

Symptom: "The tables for this page are not in the database yet."
Likely Cause: Annotations need the finance-payments schema.
Resolution: Ask the platform owner to run npm run db:apply:finance-payments.
Symptom: "Only a row labelled ANNOTATED has an annotation to revoke."
Likely Cause: You tried to delete a drift row.
Resolution: Drifts are never removed; only annotations can be revoked.

Was this guide helpful?

Help us refine our platform documentation