Separate Wallet Deposits Need Separate Records Before Aggregation

To reconcile deposits from separate wallets, match each incoming transfer to the record on its network before adding it to a combined balance. A single total can show how much crypto is held, but it cannot explain which wallet supplied it or whether a transfer is still pending. Keeping wallet-level records first makes the final total easier to verify and correct.

What records should you keep for each deposit?

Keep one entry per transfer, with the wallet address, asset, network, amount, transaction hash and status. Add the date and time shown by the network, the date your own system recorded the deposit, and any memo or destination tag required by that network. For a token transfer, record the token’s contract address as well as its ticker: two different tokens can share a ticker, while the contract identifies which one moved.

Use the transaction hash to find the transfer on the relevant network, then compare its destination and amount with your wallet records. Token transfers can have several events in one transaction, so include the event or log index when the network provides it. The linked explainer on how Manta bridge routes vary by asset, network and return plan covers why the route itself matters when a deposit has crossed between networks. A familiar asset name alone does not establish that two balances belong to the same network.

How do you combine deposits without losing the audit trail?

Reconcile each wallet as its own small ledger, then roll up the balances. For every entry, compare the recorded amount with the network transfer and note any fee or conversion separately. A wallet’s balance is not always the sum of incoming transfers: outgoing transfers, network fees and pending transactions also affect what remains. Keep those movements visible instead of adjusting deposit amounts to force the ledger to match.

A practical sequence is:

• Group incoming transfers by wallet and network.
• Match each record using its transaction hash and, for tokens, the relevant event index.
• Mark transfers pending until the wallet or receiving service recognizes them as confirmed.
• Compare each wallet’s reconciled balance with its on-chain balance, then sum the verified balances.

If funds move between wallets you control, record both sides as an internal transfer and connect them with the same reference. That preserves the trail without counting the movement as a new outside deposit. When an exchange or custodian receives the funds, compare its credit record with the network transfer; the service’s credited amount may reflect its own processing or fee treatment.

What should you do when the totals do not match?

Check the network and destination first, then look for a missing transaction, duplicate entry, unrecorded outgoing transfer, fee, or pending credit. Also check whether a memo or tag was required. If the network shows the transfer but the receiving service does not, keep the transfer marked as sent or pending in your records rather than treating it as available balance.

For most readers, the clearest method is to reconcile at the wallet-and-network level and aggregate only after every entry has a matching record. The extra detail takes more work than maintaining one portfolio total, but it narrows errors to a specific transfer instead of obscuring them in a combined figure. Watch for unmatched hashes, balances that diverge after fees, deposits awaiting confirmation, and changes in the route or destination used for cross-network transfers.