You can reconcile a cross-chain deposit cleanly by matching both chain legs and carrying the original asset’s basis forward, provided the destination receipt is the same asset and you control both wallets. The key is to record one movement across two chain accounts, then account separately for any fees or token swaps.
What counts as a cross-chain deposit?
A cross-chain deposit is usually a series of events: tokens leave a wallet on one network, a bridge or service processes the transfer, and tokens arrive at an address on another network. The destination transaction may have a different hash from the source transaction, so accounting software that sees only one chain can mistake the arrival for income or a purchase.
Start by identifying who owns the sending and receiving wallets, which asset left, which asset arrived, and whether the route swapped tokens. An ordinary bridge transfer between wallets you control is different from a payment received from someone else. A route that turns USDC into ETH also includes a token exchange; it is not simply a transfer of the same asset.
How do you match the two sides?
Match the source and destination records using the bridge’s transfer details where available, then verify them against each chain’s transaction record. A useful reconciliation row includes the date and time, chain, token and amount, sending and receiving addresses, transaction hash, fee, and transfer status. If the service provides a message ID or deposit reference, keep that too: it can connect the two hashes when the software cannot.
For example, suppose a wallet sends 1.00 ETH to Optimism, pays 0.002 ETH in source-chain gas, and receives 0.99 ETH after a 0.01 ETH bridge charge. Record the source wallet’s 1.00 ETH as transferred to the Optimism wallet, the 0.002 ETH gas separately, and the 0.01 ETH bridge charge separately. The destination wallet should show 0.99 ETH received—not 0.99 ETH of new income. If each ETH is valued at, say, $2,500 for the books, the destination receipt is $2,475; the two fees total $30 at that same illustrative rate.
When reviewing routes that include bungee bridge, keep the route and token details with the records because an aggregator can route through bridge and swap services. Checking Bungee bridge supported chains helps you confirm that the source and destination networks are supported before you try to match their records. If the destination token differs, classify the exchange as well as the transfer, using your accounting and tax rules for that event.
Which accounting method fits your records?
For a small number of transfers, a spreadsheet can work if you reconcile it to wallet balances and retain transaction evidence. It gives you direct control over matching, but each unmatched or delayed transfer needs follow-up. For frequent activity, automated wallet imports save time, but only if the software supports both chains and lets you correct transfer matches, fees, and token swaps.
A digital-asset subledger is useful when you need a traceable record of asset balances, cost basis, and activity across many wallets. Whichever method you choose, keep chain-specific accounts or tags: for example, “ETH—Ethereum” and “ETH—Optimism.” That makes it easier to spot an import gap or a duplicate entry when the combined balance does not agree with the on-chain wallets.
For a U.S. taxpayer, the IRS’s digital asset FAQs say that moving assets between accounts you own is generally not a taxable event, except for digital assets used or withheld to pay transaction services. That tax treatment does not settle how a fee should be classified in your books, and rules vary by jurisdiction. The AICPA’s 2026 digital-assets practice aid is a useful reference for accounting and audit questions; ask your accountant to confirm the policy you apply to fees and swaps.
What should you do with incomplete or unusual transfers?
Keep a transfer in a clearing or suspense account while one side is missing, rather than marking an unexplained deposit as income. Check that the source transaction succeeded, the destination address belongs to you, and the bridge status is complete; if the transfer failed or was refunded, record the refund against the original movement and keep both transaction records.
Also investigate a destination receipt that is wrapped, renamed, or slightly different in amount. A wrapped token may represent an asset on the new chain, while a shortfall may reflect a bridge fee or a swap. Confirm the token contract and route details before merging it with the source asset in your software.
I’d choose automated software only after confirming that it can match both chain legs and preserve the original asset history; otherwise, I’d use a controlled spreadsheet or subledger and review every unmatched deposit before closing the books.