Jump to content
Onchain Report

Crypto news from every chain

How businesses should track cross-chain crypto transfers

A cross-chain transfer can split records across ledgers. Businesses need one joined trail showing ownership, value, fees and each step of the transfer.

Onchain Report Newsroom#2436a93 min read

How businesses should track cross-chain crypto transfers

Businesses should record a cross-chain crypto transfer as one joined trail, with evidence from both the sending and receiving networks. A transfer may pass through a bridge, a service that moves assets or their representation between blockchains, and the records can end up in different wallets, apps and explorers. A complete trail helps the business explain what moved, where it went and how it was valued.

What should a business record for a cross-chain transfer?

Record the details that connect the business’s starting balance to its ending balance. Keep the date and time, token and amount, sending and receiving wallet addresses, network names and transaction IDs. A transaction ID is the unique reference for an on-chain action.

Save the bridge or service receipt too, along with any exchange or wallet export and a copy of the relevant accounting entry. Note the asset’s value in the business’s reporting currency at the time, how that value was determined, and any fees paid. If a fee is paid in crypto, record the token and amount used.

Route choice can change the evidence trail: a direct bridge, a wrapped token (a token designed to represent an asset on another network), and a swap followed by a bridge can leave different steps to reconcile. For more detail on comparing a biswap cross-chain route with other routes, see this guide to choosing a cross-chain route. Keep records for each step, even when the service presents the whole journey as one transfer.

Is moving crypto between company wallets a taxable event?

It depends on the route and the tax rules that apply to the business. A straightforward move between wallets the same business owns may be treated differently from a swap, a sale, or a bridge that changes the asset received. The on-chain record shows what happened technically; it does not, by itself, settle the tax treatment.

For that reason, label the purpose of the transfer and identify who controls each wallet. Keep evidence that both wallets belong to the business, such as internal wallet records and approvals. If the destination asset differs from the source asset, preserve the details of the conversion rather than describing the whole sequence as a simple transfer.

How can a business reconcile records across networks?

Reconcile the source and destination records against the business’s own ledger. Start with the outgoing amount, subtract fees, then match the remainder to the incoming amount or explain any difference. Timing gaps can happen when a bridge waits for confirmations or processes a transfer in stages.

  • Export wallet and exchange activity regularly; access to old records may not last.
  • Match each source transaction to its destination transaction or service receipt.
  • Record the value, fees and any asset change as separate details.
  • Keep a note when a transfer is pending, failed or returned.

Use a consistent process for every network and keep the original files alongside the accounting records. Tax rules vary by jurisdiction, so have an accountant review how the business should classify a bridge, swap or fee. The practical goal is simple: someone reviewing the books should be able to follow the assets from the company’s wallet, through each step, to their final destination.