An NFT transaction records template helps you capture the details needed to understand purchases, sales, fees, transfers, and potential tax reporting. This guide provides a spreadsheet structure, calculation methods, and worked examples you can reuse at month-end, before a sale, or when preparing records for a tax professional. It is general recordkeeping guidance, not tax advice; reporting rules depend on your country, activity, and individual circumstances.
Overview
NFT activity is rarely limited to one marketplace purchase. A typical history may include a wallet-to-wallet transfer, a bridge between networks, a mint, a secondary-market sale, gas paid in a separate token, marketplace fees, and creator royalties. If these events are recorded only as wallet screenshots or marketplace receipts, important details can be difficult to reconstruct later.
A useful NFT tax tracking spreadsheet should preserve both the blockchain evidence and your accounting interpretation. The blockchain record shows what happened: the network, transaction hash, wallet addresses, contract address, token ID, and transferred assets. Your own record adds context such as the purpose of the transaction, the fiat value used, acquisition cost, disposal proceeds, and whether the event was a purchase, sale, transfer, or bridge.
Use one row per event rather than one row per NFT. A single NFT can have several rows over its lifetime: acquisition, transfer to a hardware wallet, listing-related transaction, sale, and movement of proceeds. This approach makes it easier to reconcile wallet activity and distinguish a taxable disposal from a transfer between wallets you control, subject to the rules that apply where you live.
For wallet security, keep the spreadsheet separate from seed phrases and private keys. A transaction record may include public wallet addresses, but it should never contain secret recovery words, private keys, or signing credentials. For a broader backup process, see the NFT wallet backup and recovery plan.
How to estimate
Start by defining the event you are recording and then calculate its values in a consistent fiat currency. The basic formulas are:
- Total acquisition cost: purchase price in fiat + gas cost in fiat + marketplace fee in fiat + other directly related costs.
- Net sale proceeds: sale price in fiat − marketplace fee − royalty or other seller deductions − gas cost paid by the seller.
- Illustrative gain or loss: net sale proceeds − allocated acquisition cost.
- Effective transaction cost: gas cost + marketplace fees + other payment charges.
These calculations are organizational estimates, not a universal tax formula. Some jurisdictions may treat gas, fees, transfers, creator income, or digital assets differently. If a transaction has mixed assets, multiple NFTs, or uncertain valuation, preserve the raw details and ask a qualified tax professional how to classify it.
For each event, record the asset amount in its native unit and the conversion used for your fiat estimate. For example, do not record only “0.4 ETH.” Record the token, the quantity, the valuation currency, the rate or reference used, and the timestamp or date associated with that valuation. If your marketplace or wallet displays a fiat value, save the export or receipt as supporting evidence rather than treating the displayed value as automatically authoritative.
Network fees deserve their own fields. Record the gas token, amount spent, fiat estimate, and transaction hash. A gas fee calculator can help you estimate a future transaction, but your final records should use the amount actually paid after the transaction confirms. The NFT gas fee estimation guide explains how to separate an estimate from a completed fee.
Inputs and assumptions
Create a spreadsheet with the following columns. You can add columns for your jurisdiction, accounting software, or adviser’s preferred format.
- Event ID: your internal reference, such as 2026-001.
- Date and time: include the time zone when it matters.
- Event type: purchase, sale, mint, transfer, bridge, swap, fee, royalty receipt, or other.
- Marketplace or counterparty: identify the platform or wallet involved.
- Network: record the blockchain separately from the marketplace name.
- Wallet sent from and wallet sent to: use complete public addresses, not shortened display versions.
- Contract address and token ID: capture the NFT’s collection identifier and individual asset identifier where applicable.
- Asset and quantity: record the NFT, cryptocurrency, stablecoin, or other token involved.
- Unit price and total price: show both native-token and fiat amounts.
- Gas token, gas amount, and gas value: keep network fees separate from marketplace charges.
- Marketplace fee: record whether it was paid by the buyer, seller, or deducted from proceeds.
- Royalty or creator split: record only when shown or relevant to the transaction.
- Transaction hash: use the block explorer link or complete hash.
- Fiat currency and conversion basis: document the currency and rate source or statement used.
- Notes and evidence: link to receipts, CSV exports, invoices, screenshots, or correspondence.
Use a separate wallet register with the wallet label, public address, network, date added, and date closed. This helps prevent the common mistake of treating an internal transfer as a purchase or sale. When moving an NFT between wallets you control, record both sides of the movement and link them with the same Event ID. For bridges, create a row for the outgoing transaction and another for the receiving transaction, noting the bridge service, network pair, fees, and any delay or discrepancy.
Save original CSV files before editing them. Marketplace exports can change their column names or omit blockchain fees, while wallet histories may show transfers without identifying the commercial purpose. Keep an untouched “raw imports” folder and use a separate working sheet for categorization.
Worked examples
Example 1: NFT purchase. Assume a collector buys one NFT for 0.50 ETH. The marketplace charges a buyer fee, and the wallet pays gas in ETH. Enter the purchase price as 0.50 ETH, the fee as a separate line or field, and the gas amount from the confirmed transaction. Convert each component to the chosen fiat currency using the documented valuation basis. The estimated total acquisition cost is the fiat value of the NFT plus the fiat value of the marketplace fee and gas.
Do not overwrite the native amounts after conversion. Keeping both values lets you reconcile the record with the wallet and marketplace export. Attach the receipt and transaction hash to the row.
Example 2: Transfer between wallets. A collector moves the NFT from a browser wallet to a hardware-wallet address they control. Record the outgoing wallet, receiving wallet, contract address, token ID, network, gas amount, and transaction hash. Label the event as an internal transfer, not a new purchase. The spreadsheet should preserve the original acquisition reference so the asset’s history remains connected.
Example 3: Sale. Assume the NFT later sells for 0.80 ETH. The seller pays a marketplace fee and gas, while a royalty or creator deduction is displayed in the settlement details. Record gross proceeds, each deduction, net proceeds, and the original acquisition-cost reference. The illustrative result is net sale proceeds minus the allocated acquisition cost. Do not rely on the wallet’s incoming amount alone: it may already exclude fees, royalties, or other deductions.
Example 4: Bridge or multi-chain movement. An NFT or payment asset moves from one network to another. Record the source transaction and destination transaction separately, including both hashes and networks. Add bridge fees, wrapped-asset details, and any difference between the amount sent and received. A multi-chain payment workflow can look like a sale or disposal if only one side is reviewed, so the event type and wallet ownership notes are important.
When to recalculate
Review the spreadsheet at least monthly and whenever you make a significant NFT payment, sale, transfer, bridge, or wallet change. Recalculate immediately when a transaction confirms, because estimated gas can differ from the final amount. Also revisit entries when a marketplace issues a corrected receipt, a wallet export changes, an asset is sold in a bundle, or you discover that a wallet was omitted.
Before filing or handing records to an adviser, reconcile every wallet address and compare spreadsheet rows with marketplace exports and block explorer history. Filter for blank transaction hashes, missing fiat values, duplicate hashes, and events with unexplained token movements. Check that internal transfers have linked source and destination rows and that sale proceeds are recorded net and gross where available.
Update your template when networks, marketplaces, wallet tools, or CSV formats change. Review conversion assumptions when your reporting currency changes or when a transaction crosses a year-end boundary. Keep a dated copy of the completed spreadsheet and the supporting exports. For security, protect the files with strong access controls and never store wallet recovery secrets alongside financial records.
For a practical workflow, begin with one month of activity: export each wallet and marketplace history, populate the required columns, verify hashes, classify events, and calculate fees. Then reuse the same structure for future months. Related guidance on NFT payment scam prevention, wallet permissions, and NFT royalty payment records can help fill gaps that a basic transaction export may not show.