Transactions ledger
The Transactions screen shows the wallet transaction history for the wallets you have enabled, together with their match status against documents in the Registry. It exists for engagements that need to reconcile on-chain activity with paper documentation.
If your pilot is documents-only, you will not need this screen.
How data appears
- Select a wallet from the wallet selector.
- Zeno CY loads transactions for that wallet.
- You filter by search or match status as needed.
If no wallet is selected — or if connector data is unavailable in this environment — the table stays empty until the scope is set.
Match statuses
Every transaction carries one of three reconciliation states, plus an unfiltered view:
- Matched — the transaction has a confident link to a registered document.
- Ambiguous — a low-confidence candidate exists and needs human review.
- Unmatched — no linked document was found.
- All — the full list, no status filter applied.
Ambiguous and unmatched items form your review queue — the gaps between what happened on-chain and what is documented in the Registry.
What stays manual
Zeno CY does not auto-confirm accounting matches. The matching engine produces suggestions, you produce decisions. Treat matched items as proposals that must be spot-checked before they enter your accounting system.
What the KPIs on screen tell you
The header cards summarise the current wallet scope:
- total transactions in the current view,
- matched / ambiguous / unmatched counts,
- currency mix and net flow snapshot,
- last sync timestamp.
Together they give you a quick read on coverage and on which wallets carry the heaviest review load.
Troubleshooting
- If transactions are missing, verify the wallet is enabled on the Wallets screen.
- If the screen shows stale data, reselect the wallet or refresh the source.
- If API access is unavailable, confirm that the environment is not in service-offline mode.