Create one record per transfer
Record the date, asset, amount, network, sending source, destination, transaction hash and any provider reference. Keep the blockchain transaction and the account entry connected but separate. One describes network activity; the other describes how a service recorded or credited that activity.
Use consistent values and time zones
Preserve the asset amount exactly as displayed and note whether any fee was deducted separately. Record fiat values as estimates with the price source and observation time. Use UTC alongside local time when reconciling events across exchanges, emails and explorers.
Match network status to account status
A confirmed blockchain transaction may still be pending within a receiving service. Record the confirmation count and the provider’s displayed status independently. Check deposit minimums, memo or tag requirements and supported token contracts before classifying a difference as an accounting error.
Preserve provider documentation
Keep withdrawal receipts, deposit notices, bank references and support tickets. If a service changes a displayed status, add a dated update rather than replacing the earlier observation. This creates a reviewable history of what each system reported.
Explain adjustments clearly
If a manual credit, fee, refund or balance correction occurs, record who authorized it, the reason, the amount and the related transaction or ticket. Avoid vague entries such as adjustment without a supporting reference. A reviewer should be able to understand the difference without relying on memory.
Close the record only when both sides agree
A transfer record is complete when the network activity, provider status and account balance can be reconciled or when the unresolved difference is clearly documented. Retain open questions and provider responses. Do not mark an item resolved merely because the on-chain status says success.