When Treasury Can Credit a Portal Bridge Transfer

A treasury should count a Portal Bridge transfer as available funds only after the destination transaction succeeds and the expected asset reaches the named wallet. A source-chain confirmation starts the transfer; it does not prove the receiving balance exists.

That distinction keeps an in-flight transfer from being counted as spendable cash.

What confirms that a transfer has arrived?

The destination-chain transaction is the operational point at which treasury can credit the received balance. In a typical Wormhole wrapped-token transfer, the source contract locks the original asset or burns an existing wrapped token, Guardians sign a message, and that proof must be submitted on the destination chain before tokens are released or minted.

That destination step can happen automatically through a relayer or require manual redemption. A signed proof alone is not delivery: check for the successful destination transaction and the balance at the intended recipient address. A fuller account of route differences and treasury checks is in this guide to the portal bridge.

What should treasury verify before posting?

Match the destination transaction to the source transfer before updating the available balance. The ticker alone is not enough: a token with the same symbol on another chain may be a wrapped representation rather than the asset treasury expects.

• Confirm the source transaction succeeded and record its hash.
• Verify the destination chain, recipient address and completed transaction.
• Check the token contract or mint address, and distinguish native tokens from wrapped versions.
• Reconcile the amount actually received against the amount sent, accounting for any displayed fees or deductions.

Keep the source hash, destination hash, chain, token identifier and received amount together in the reconciliation record. This gives finance and operations a way to trace one transfer across two ledgers if a balance is disputed.

How should a pending transfer be treated?

Treat a transfer without destination delivery as in transit, not as available funds. The source transaction may be final while the proof is still being prepared, or the proof may be ready while nobody has submitted the destination transaction.

Check the transfer’s status and use its original route’s redemption process if manual completion is offered. Avoid sending a replacement transfer just because the first one is pending; if the original later completes, the treasury may receive both. Manual completion also means someone must submit a destination transaction and pay its network fee.

For treasury planning, the practical rule is simple: source confirmation supports tracking the outgoing movement; destination confirmation supports crediting the received asset. Internal accounting may record an in-transit amount earlier under the organisation’s policy, but it should remain separate from cash available to deploy until the destination balance is verified.