Review wallet funding and usage reports

In **Reports > Wallet Funding**, choose the report that matches the transaction type. Wallet funding and wallet spending are different movements; they should not be added together as received revenue.

Client-funded credit

Open **User-Funded Wallet**. Set Date range, Currency, and Client where available. Review the funded totals and client rows. These summarize recorded client-funding credits associated with payment-gateway funding. Open the client and its ledger/invoice to verify an individual receipt.

Staff-funded credit

Open **Admin-Funded Wallet**. Choose **Ledger** for individual adjustment rows or **By Client** for aggregated client totals. Use Date range, Currency, Client, and Admin as available. In Ledger, compare Date, Client Name, Admin, Type, Credit, Debit, Net Amount, Balance, Reference, and IP. Types distinguish **Manual Credit**, **Unpaid Invoice Credit**, and **Rebate/Debit**.

Staff-added credit can be associated with an Unpaid invoice. It is not proof of external payment received. A rebate/debit is a wallet movement; it does not prove a provider refund.

Spending

Open **Wallet Usage Summary** and choose Date range, Currency, and Client. Compare **Total Orders** and **Total Spent**, then inspect the client’s related orders and ledger for the detail. Spending the same funded credit later is a separate event, not another funding receipt.

If figures do not agree

Match currency, date scope, client, and report type first. Check whether the movement was client funding, staff funding, an unpaid credit, or a rebate. Refresh before comparing recent activity. Use transaction references to reconcile individual differences rather than making wallet adjustments to force report totals to match.