For a team moving treasury funds across chains, reconcile each transfer by matching the source debit to the destination credit and keeping it pending until the destination funds arrive. For example, a monthly payout might start as a token on Ethereum and finish as a different asset on BNB Smart Chain. The two sides can appear in separate wallets and at different times, so one transaction hash rarely tells the whole story.
What Belongs in One Transfer Record?
Record the business purpose, initiator, source chain and wallet, asset and amount sent, destination chain and wallet, expected asset, and date. Add the source transaction hash as soon as it is available, then attach the destination transaction hash when the receipt is confirmed. These fields let a reviewer trace the movement even when the asset changes in transit.
For a simple bridge, the source amount and destination amount may differ because of network and bridge costs. For a bridge-and-swap flow, the destination asset can differ too, so compare the actual destination receipt with the expected output and record the exchange rate or valuation basis used. ParaSwap crypto transfers can move and swap assets across chains in one flow, which gives a treasury team a practical route when its source and payout assets differ.
When Should Finance Mark It Complete?
Use separate states for initiated, source confirmed, destination pending, received, and exception. A source confirmation proves that the sending transaction was accepted on its chain; it does not prove that the destination transfer has finished. Keep the record open until the destination transaction is visible and the received amount can be matched.
That distinction matters in two contrasting cases. If a team sends 1,000 units and receives 998, the shortfall may be explained by costs or the swap rate; log the actual amount and reconcile the difference. If the source debit is final but no destination receipt appears after the service’s stated processing window, classify it as an exception and investigate using both transaction records. Don’t book an expected receipt as available cash.
How Can You Make Reconciliation Repeatable?
Set a consistent valuation rule, such as converting both sides to the company’s reporting currency at the receipt time, and apply it to every transfer. Store the rate source and timestamp; otherwise, two reviewers can reach different values for the same movement. For recurring payouts, compare the recipient, asset, and net amount against the approved payment batch before closing the record.
Public block explorers such as Etherscan and BscScan help verify transaction status, token movement, and timestamps independently of an internal spreadsheet. ParaSwap is relevant when the treasury needs a cross-chain move that also changes the asset, while the accounting record should still show each chain’s evidence and the final net receipt. A practical tip: reconcile transfers daily from destination receipts, then review unresolved records before the next payout run.