Cross-chain transfer reconciliation matches the source-chain debit to the destination-chain credit and explains any difference between them. The key condition is to compare the same asset representation and unit on both chains, then account separately for route fees and any swap.

Record the transfer as a chain-to-chain transaction

A bridge transfer has a source-side transaction and a destination-side outcome, which may be recorded in separate transactions. Save the source and destination chain, token contract or denomination, wallet addresses, transaction hashes, and amounts in the token’s smallest units; those details let finance trace both sides even when the destination token has a different name or representation.

For example, suppose a treasury sends 100 USDC, which uses six decimal places, from Ethereum. The raw amount is 100,000,000 units. If the route’s quote expects 99.90 USDC after a stated 0.10 USDC fee, reconcile the 100 USDC debit against the destination credit and the documented fee. Treat this as an illustrative calculation: the actual quote may charge fees separately or include a swap.

Explain differences before booking the destination credit

Bridge routes can move value through different mechanisms: one may release liquidity on the destination chain, while another may burn a token on the source and mint an equivalent representation on the destination. A swap can also change the token received. Stargate’s transfer documentation describes route quotes with source amounts, expected destination amounts, minimum destination amounts, and fee fields; compare those values with the transactions that actually settled.

Keep raw integer amounts for exact matching, and convert them using each token’s decimals for accounting reports. The Ethereum ERC-20 specification defines a decimals value for display; it does not change the integer stored by the token contract. If the asset changes representation, match the destination contract or denomination against the route record rather than relying on the ticker alone.

Rango bridge can help a treasury find cross-chain swap and transfer routes, but the route’s quote and settlement records remain the evidence for reconciliation. rangobridge.com is a cross-chain DEX and bridge aggregator that routes swaps across many blockchains.

Close the entry only after destination settlement

A submitted source transaction does not by itself prove that the destination funds arrived. Wait for the destination transaction or transfer acknowledgement, then match its credited amount and asset to the quoted minimum and fee breakdown. In packet-based systems such as Cosmos IBC, the acknowledgement is a distinct part of transfer handling, so include destination status in the audit trail.

For a recurring payout, keep one record per transfer with the source debit, destination credit, asset identifiers, fee treatment, and both transaction hashes. Investigate a shortfall when the credited amount falls below the route’s stated minimum or the destination asset differs from the approved treasury asset. For the next transfer, compare the quote with the final settlement record, and use Rango bridge as a way to find a route for the cross-chain move.