What to Record for Each Crypto Transaction

Deciding to keep records is the easy part. Deciding what to record is where many people either capture too little to be useful or so much that they give up. This guide lists the fields that matter for most crypto transactions and explains why each one helps later.

It is general information about good record-keeping practice, not tax or legal advice. Requirements for any reporting depend on where you live.

The essential fields

Date and time

Record when the transaction happened, including the time zone you are using. Use the block timestamp from the explorer if you want precision. Dates matter for matching payments to invoices, for any period-based reporting and for disputes about deadlines.

Type of transaction

Classify each transaction with a simple label, for example:

• Buy — exchanging local currency for crypto.
• Sell — exchanging crypto for local currency.
• Swap — exchanging one crypto for another.
• Payment — spending crypto on a product or service.
• Transfer — moving funds between your own accounts.
• Receive — receiving crypto from someone else.
• Refund — funds returned to you.

The label "transfer" is especially important: it tells you that the movement was not spending, which prevents double-counting later.

Asset, amount and network

Record:

• the token (for example USDT),
• the amount with all decimals,
• the network (for example Tron or Ethereum).

The network matters because the same token on different networks has different contracts and explorers.

Fees

Record each fee separately:

• network fee (and in which coin it was paid),
• exchange withdrawal fee,
• trading fee for buys and sells.

Fees often matter for calculating real costs and may be relevant for reporting. Our article on network fees vs service fees explains which is which.

Value in your local currency

Record the value of the transaction in your local currency at the time. For stablecoins, this is usually close to the dollar amount converted at the day's exchange rate. For other coins, use the market price at the time of the transaction. Note the source of the price so you can use it consistently.

Transaction hash

The transaction hash is the unique identifier of an on-chain transaction. It lets you or anyone else find the exact transaction on a block explorer. Internal exchange transfers may not have one; note the exchange's internal reference instead. See saving transaction hashes and receipts.

Addresses

Record the sending and receiving addresses, or at least label which of them are yours. Over time, a list of your own addresses with labels makes it easy to recognize transfers between your accounts.

Counterparty and purpose

Who did you pay, and for what? A short description — "software subscription, March", "card order for online purchases" — gives the transaction meaning months later.

References

Record any order number, invoice number or support ticket number connected to the transaction. References link your record to the other party's records.

Useful optional fields

• Account or wallet name: which of your accounts was involved.
• Exchange rate used: if you converted between currencies.
• Status notes: "arrived short, topped up", "refunded on…".
• Attachments: invoice PDFs, order confirmation emails, screenshots.

An example record in words

A complete record of a payment might read: on a given date and time, a payment of a stated amount of USDT on Tron from your exchange account to a service's order address, with the exchange's withdrawal fee, worth a stated amount in your local currency, transaction hash saved, for a card order with its reference number, status "card issued".

That single line answers almost every question that could come up later.

Keeping it manageable

You do not need every optional field for every transaction. A practical approach:

• Record the essential fields for every transaction.
• Add optional fields for larger payments, business costs or anything unusual.
• Rely on exports from exchanges for routine buys and sells, adding notes where needed.

Our template for a simple spreadsheet for crypto spending puts these fields into columns.

Recording refunds and corrections

Payments do not always end with the first transaction. A payment may arrive short and need a top-up, an order may be cancelled and refunded, or a merchant may return part of a purchase. Each of these deserves its own record, linked to the original:

• Give the follow-up its own row with the right type, such as "refund" or "top-up".
• Include the original transaction's hash or reference in the notes.
• Record any fees on the follow-up separately.

Linking related transactions keeps the story of each payment complete. Without the link, a refund can look like unexplained income and a top-up like a second purchase.

Consistency matters more than perfection

The most useful records are consistent: the same fields, the same labels, the same price source, the same time zone. Choose your conventions once and stick to them. Inconsistent records are harder to work with than slightly incomplete but consistent ones.

Common gaps

• Missing fees, especially withdrawal fees deducted from the amount.
• Unlabeled transfers between your own wallets, which look like spending later.
• No local-currency value, which is hard to reconstruct accurately.
• No purpose noted, leaving you guessing months later.

Records for card orders

For an order on BuyCryptoCard, the useful fields are the order reference, the order total, the network and token you paid with, your exchange's withdrawal fee, the transaction hash and the date. The order page in your account shows the reference, total and status, and the how it works page explains each status you might note.

Frequently asked questions

Do I need to record transfers between my own wallets?

Yes. Labeling them as transfers prevents them from being mistaken for spending or income later.

Which price source should I use for local-currency values?

Choose a reputable source and use it consistently. Note which one you use.

What if I do not have a transaction hash?

For internal exchange transfers, record the exchange's internal reference instead.

Summary

For each crypto transaction, record the date and time, type, asset, amount, network, fees, local-currency value, transaction hash, addresses, purpose and any references. Label transfers between your own accounts clearly, use consistent conventions and add optional details for larger or business payments.