How to account for crypto transfers across a period-end

A treasury moving its own crypto across chains at a reporting cutoff should reconcile the amount sent, fees and amount received before closing the books. The transfer may span two accounting periods, but the delay alone does not make it a purchase or sale; the accounting depends on what the treasury controlled at the cutoff and what the bridge delivered.

• Match the source-chain transaction to the destination-chain receipt.
• Record network and bridge fees separately from the asset movement.
• Keep evidence of the transfer’s status at the reporting cutoff.
• Review the treatment of any wrapped or receipt token.

What counts as a treasury transfer across periods?

A cross-period transfer is one that starts before a reporting date and completes after it. A treasury may send tokens from a wallet on one chain, then wait for a bridge to release tokens or a claim on another chain. The ledger close falls in the middle of that process, so the wallet balances alone can give an incomplete picture.

Start by asking whether the treasury is moving an asset it already owns or exchanging it for something else. A transfer between wallets controlled by the same entity is generally a movement between accounts in its records, rather than a new acquisition. A bridge can complicate that simple picture because some routes lock or burn the original token and issue a wrapped token or receipt on the destination chain.

Those routes have different mechanics and can produce different evidence. For a plain-language explanation of the main route and swap options, see AcrossBridge bridge and swap types.

How should you record a transfer still in progress?

Record the source-chain movement using its transaction details, then keep the asset traceable while the destination leg is pending. A separate “in transit” ledger account can make that status visible: it shows that value has left one wallet but has not yet appeared in the other. This is a bookkeeping method, not a universal rule about when an asset must be recognised or removed from the balance sheet.

At the cutoff, gather the source transaction hash, the sending and receiving addresses, the token and quantity, the fee, and any bridge message or status record. Once the destination transaction settles, match it to the original transfer and clear the in-transit balance. If the destination receipt is smaller, investigate the difference: it may reflect fees, a conversion, a partial release or an unresolved transfer.

The key judgement is control: whether the treasury still has the rights and ability to direct or recover the asset during the gap. Network confirmation alone may not answer that question. A bridge’s design and terms matter, especially if an operator, validator set or smart contract controls release on the destination chain. The accounting policy should explain how the entity assesses these arrangements and apply that approach consistently.

How do bridge tokens and fees affect the close?

A wrapped token is a token issued on one chain to represent an asset held or locked elsewhere. A receipt token may instead represent a claim on a later release. Neither label settles the accounting by itself. Identify what rights the treasury receives, who controls the underlying asset, and whether the new token is a separate asset under the entity’s accounting framework.

Fees need their own record. The source network may charge a transaction fee, while the bridge or destination network may charge another. Preserve each fee’s asset, quantity, transaction and value under the treasury’s chosen measurement method. Do not hide these costs by comparing only the amount sent with the amount received.

Accounting treatment depends on the applicable reporting framework and the asset’s features. Under IFRS, for example, the IFRS Interpretations Committee concluded that the cryptocurrency holdings it considered fall under IAS 2 when held for sale in the ordinary course of business, and otherwise under IAS 38. That conclusion does not decide every question about a bridge arrangement or a wrapped token, so document the relevant facts and policy choices.

What should you check before signing off?

Reconcile by transfer, not just by wallet balance. A daily or period-end process should pair each source-chain outflow with a destination-chain inflow, while leaving genuinely pending transfers visible. If several transfers use the same bridge or token, retain distinct transaction references so a later receipt is not matched to the wrong sending event.

Keep a compact close file with the evidence and decisions behind each open transfer:

• Source and destination transaction identifiers, addresses and timestamps.
• Amounts sent, fees charged, amounts received and any conversion details.
• Bridge status at the cutoff and the later evidence of completion or failure.
• The control assessment and accounting treatment for any wrapped or receipt token.

If a transfer fails or is reversed, update the reconciliation and assess whether the treasury recovered control of the original asset or received a different claim. The practical takeaway is straightforward: the accounting period follows the facts about the asset and the treasury’s control, while the ledger should preserve the full path from send to settlement.