Wallet Operations

Wallet operations help users monitor balances, holds, transactions, top-up requests, alerts, and reconciliation state.

Open Wallets -> Operations or the wallet monitoring workspace available to your role.

Workspace Reference

Workspace	Open From	Main Action	Main Record
Balances	Wallets -> Operations	Review balance	Available, held, ledger, settled, and reconciliation position.
Transactions	Wallets -> Operations	Review transaction	Wallet movement such as top-up, collection, disbursement, hold, release, settlement, fee, or reversal.
Holds	Wallets -> Operations	Review, release, settle, expire, or reverse hold	Reserved wallet funds awaiting final outcome.
Top-Up Requests	Wallets -> Operations or Wallet Top-Ups	Create, submit, approve, or reject top-up	Funding request to increase wallet balance.
Alerts	Wallets -> Operations	Assign or resolve alert	Integrity, balance, hold, disbursement, or reconciliation issue.
Reconciliation	Wallets -> Operations	Review drift	Difference between wallet tracking, provider, bank, settlement, or accounting evidence.

Balance Review

The balance view shows the current wallet position.

Before approving or executing payouts, review:

Balance Detail	What To Check
Available balance	Whether enough funds remain for new activity.
Held balance	Whether pending payouts or settlements already reserved funds.
Ledger balance	Whether total tracked wallet movement looks reasonable.
Currency	Whether it matches the intended transaction.
Service scope	Whether the selected service wallet is correct.
Rail or provider	Whether the wallet matches the selected payment rail.

Where service wallets are used, always filter by service before approving top-ups or executing payouts.

Transactions

Wallet transactions explain how a wallet balance changed.

Common transaction types include:

• top-up
• collection
• disbursement
• hold
• hold release
• settlement
• reversal
• adjustment
• fee or commission
• reconciliation correction

Use transaction history as the operational audit trail for wallet balance movement.

Important transaction fields:

Field	Meaning
Wallet or service wallet	Balance affected by the movement.
Transaction type	Top-up, collection, disbursement, hold, release, settlement, reversal, adjustment, fee, or reconciliation correction.
Amount and currency	Value of the movement.
Channel or rail	Payment rail or provider context where applicable.
Reference	Provider, bank, batch, top-up, settlement, or internal reference.
Status	Whether the transaction is pending, successful, failed, reversed, or under review.
Notes	Explanation or finance review context.

Holds

Holds reserve wallet funds for pending activity.

Examples:

• a payment batch reserves funds before provider confirmation
• a wallet-funded disbursement waits for settlement
• a provider response is pending
• a failed payout needs release or reversal review

Hold statuses may include:

Status	Meaning
Active	Funds are reserved and not available for new payouts.
Released	Funds were returned to available balance.
Settled	Hold was consumed by a completed transaction.
Expired	Hold passed its allowed waiting period and needs review.
Reversed	Hold was reversed due to failed or cancelled activity.

Stale holds can make available balance look lower than expected. Review them before topping up unnecessarily.

Important hold fields:

Field	Meaning
Wallet	Wallet where funds are reserved.
Amount and currency	Held value.
Source process	Payment batch, disbursement, settlement, or other workflow that created the hold.
Expiry or review date	When the hold should be released, settled, reversed, or investigated.
Status	Active, released, settled, expired, or reversed.
Notes	Provider response, failure reason, or finance action.

Top-Up Requests

Top-up requests add funds to a wallet after funding evidence is reviewed.

Typical flow:

1. Create a top-up request.
2. Select the wallet or service wallet.
3. Enter amount and currency.
4. Attach or record funding evidence.
5. Submit for review.
6. Approver verifies evidence.
7. Approver approves or rejects.
8. User confirms the wallet balance and reconciliation state.

Do not approve a top-up when the evidence, amount, currency, or wallet scope is unclear.

Reconciliation And Drift

Reconciliation drift means wallet tracking does not fully agree with expected provider, bank, settlement, or accounting activity.

Review drift when:

• provider activity does not match wallet movements
• a top-up was approved but balance did not change as expected
• a hold is stale
• a disbursement failed after funds were held
• settlement fees differ from expectation
• ledger balance and available balance movement look inconsistent

Resolve drift before using the wallet for high-volume payment batches.

Integrity Alerts

Integrity alerts flag wallet conditions that need attention.

Examples:

• low balance
• failed settlement
• stale hold
• failed disbursement
• large movement
• reconciliation difference
• notification failure

Assign alerts to the responsible finance or operations user and record the resolution.

Common Mistakes

Mistake	Better Practice
Reading consolidated wallet balance as service balance.	Filter by service wallet where service wallets are enabled.
Approving top-up without evidence.	Verify amount, currency, date, and funding reference.
Ignoring stale holds.	Release, settle, expire, or reverse holds according to outcome.
Running payment batches with unresolved drift.	Resolve reconciliation issues first.
Treating provider success as wallet reconciliation.	Confirm wallet movement, settlement, and accounting status.

Related Guides

• Wallet Setup
• Wallet Top-Ups
• Payment Batches
• Settlement And Reconciliation