Reconcile a cross-chain treasury transfer by matching the source debit to the destination credit and keeping the evidence that connects them. Treat it as one business payment with at least two on-chain records, because the chains do not share a ledger or a single settlement moment.
What should each transfer record contain?
Give every transfer a unique internal reference, then save the source transaction hash and the destination transaction hash against it. Record the asset and network on each side, the sending and receiving addresses, the amount debited, the amount credited, the timestamp, and the purpose or payout batch.
If a payout starts on one network and needs to arrive as a different supported asset, a bridge-and-swap service can move and swap the assets in one flow. For a treasury case that routes funds through Mantle, fast Mantle bridge transfers can be part of that route; record the input and output assets separately so the conversion does not look like a payment shortfall.
A useful ledger row has these fields:
- Internal payment or batch reference
- Source and destination network, token, and wallet address
- Source amount, destination amount, and any conversion rate used
- Source transaction hash and destination transaction hash
- Status, timestamps, and reviewer or approver
Use the transaction hashes as evidence, not as the business reference: one payout may be split across several transfers, and one batch may include many recipients. For USDC, also record the network and token contract address, since the ticker alone does not identify which token was received.
When is the transfer settled?
Mark it settled only after the source debit is confirmed, the cross-chain message has completed where the route uses one, and the destination credit is visible at the intended address in the expected asset. A source transaction marked successful proves that the source chain processed it; it does not by itself prove that the destination side has paid out.
The steps between those records can differ by route. In a message-based transfer, the source transaction emits a message, the route’s verification process checks it, and a destination transaction executes the credit. LayerZero describes that source, verification, and destination sequence; its message GUID can connect the records when the route uses LayerZero. A Mantle bridge transfer may have its own route-specific settlement evidence, so reconcile against the actual destination transaction rather than assuming every route exposes the same message ID.
Set a confirmation policy by network and route, then apply it consistently. For example, a team might wait for 12 source-chain confirmations before treating a transfer as ready for review, while still requiring the destination credit before closing the payment; that number is an internal example, not a universal safety threshold. Mantle’s block explorer lets a reviewer inspect transactions and token transfers, but your policy should also specify who checks a stalled or unusual transfer.
How should the team close a regular transfer?
For a monthly payout, say the treasury sends 10,000 USDC from one chain to pay 20 vendors on another. Keep the batch amount and approved recipient list in the internal record; if the route converts assets or splits payments, reconcile each destination credit to its own payout before closing the batch.
- Create a transfer reference tied to the approved treasury instruction.
- Save the source hash and confirm the debit, asset, and sending address.
- Track the route until the destination transaction appears, then save its hash.
- Match the destination asset and amount to the intended payout, accounting for any disclosed conversion.
- Have a second reviewer resolve mismatches or delays before marking the record settled.
If the source debit is present but no destination credit appears, leave the item pending and check the route’s status before resending; a second transfer can duplicate a payout if the first later completes. If the destination amount differs, compare token identity, conversion, and any route-level deductions with the expected amount, then document the variance rather than silently adjusting the books.
Before acting, ask: can another reviewer trace this payment from the approved instruction through the source debit to the exact destination credit?
Top comments (0)