How to Record a Cross-Chain Crypto Transfer

A cross-chain transfer creates records on two blockchains, so bookkeeping means matching the outgoing transaction to what arrives. A bridge may lock or burn tokens on the source chain and release or mint tokens on the destination chain; the asset is represented across networks rather than physically moved between them.

Linking both sides of the transfer keeps a bridge receipt from being mistaken for new income or a second purchase.

What records should you keep for a bridge transfer?

Keep the transaction details for both chains and connect them with a single transfer note in your ledger. Record the date and time, source and destination networks, wallet addresses, token names and contract addresses, amounts, transaction IDs, and any bridge or network fees.

The source transaction hash identifies the send; the destination hash identifies the arrival. A bridge’s status page or transaction history can help connect them, but retain the on-chain records too. For a fuller explanation of the steps involved, see this Biswap bridge-and-swap walkthrough.

How do you avoid counting the same crypto twice?

Record the outgoing and incoming legs as parts of one transfer, not as a disposal followed by a new acquisition by default. The ledger should show that the same holding moved between wallets or networks, while preserving the amount sent, amount received, and any difference.

That difference may come from a fee, a bridge charge, or a conversion performed as part of the route. If the service swaps one token for another, record the swap as a separate event linked to the transfer; otherwise, a change in token can disappear inside what looks like a simple deposit.

• Use one ledger entry or reference to connect the two transaction hashes.
• Keep the received token’s network and contract address; matching ticker symbols do not prove two tokens are identical.
• Record fees separately, including which asset paid each fee.
• Mark transfers as pending until the destination transaction is confirmed, then update the record with its hash and amount.

How should you value fees and token changes?

Use a consistent valuation method for the date and time of each event, and save the price source or calculation with the record. If a fee is paid in a token, note both its token amount and its value under that method. The network fee and a bridge service charge can be separate costs, so check the transaction details rather than assuming one line covers both.

For a route that includes a swap, keep the before-and-after token amounts and the swap details. This gives you a record of what changed, while the linked transfer IDs explain why assets appear on different networks. The right tax treatment depends on where you file and what the transaction actually did, so don’t assume every bridge route is treated alike.

What if the transfer is delayed or fails?

Keep the original source record and note the bridge status, any refund, and the eventual destination transaction. A pending transfer is not a completed arrival; updating the ledger only when the second leg is confirmed prevents balances from drifting.

For routine bookkeeping, the practical rule is simple: match both chain records, separate fees and swaps, and preserve the evidence behind each valuation. Biswap is one example of a bridge-and-swap route where those steps can help explain why the destination asset or amount differs from what was sent.