Mining Pool Payout Memo Separate from a Later Sale

This reference compares standard fields for mining pool payout memos and later crypto sale tables for US tax documentation. It is designed for individual miners who receive regular rewards directly from mining pools, to ensure they track cost basis at the time of payout separately from capital gains or losses realized when they dispose of the mined crypto at a later date. Settlement Desk provides this as an educational resource only, and all users should confirm record-keeping requirements and tax reporting rules with their licensed tax preparer before submitting any official forms. No content on this page constitutes tax advice, nor does it replace official guidance from the Internal Revenue Service.

Payout memo date column specifications for mining reward entries

All date columns for mining payout memos must be formatted in UTC, not local time, to align with blockchain transaction timestamps, which are universally recorded in UTC. Core required columns for each reward entry include the exact date and time of payout posting, the block height the reward was generated for, the pool’s internal payout batch ID (if applicable), the wallet address the reward was sent to, and the official blockchain transaction hash for the payout. You should also include adjacent columns for the gross reward amount before pool fees, the net amount deposited to your wallet, the pool fee percentage and corresponding USD value at the time of payout, and the fair market value (FMV) of the net reward in USD at the exact time of on-chain confirmation. This FMV figure is used to calculate ordinary income owed for mining activity, and cannot be substituted for the FMV at the time of later sale, per IRS guidance for crypto earned as income. For pools that batch payouts to multiple miners in a single on-chain transaction, include the batch ID in the date column notes, so you can match your individual reward entry to the shared on-chain transaction if needed. Illustrative example: A pool that pays out weekly on Sundays may send a single 0.05 BTC transaction to 20 different miners, so your individual payout memo will list the batch ID alongside your specific 0.0025 BTC net reward to help you locate your portion of the on-chain transaction quickly.

Later-sale transaction ID box formatting for crypto disposal records

When you sell, exchange, or use mined crypto to pay for goods or services, you must track each disposal separately with a dedicated transaction ID box placed in the top right corner of every disposal record, whether digital or printed, for immediate visibility. The box must include the exchange or self-custody transaction hash for the disposal, the exact date and time of disposal in UTC, the cross-reference ID tied to the original mining payout the disposed asset came from, the exact amount of crypto being disposed of (with full decimal precision), the gross USD proceeds from the disposal before any fees, and any transaction fees or exchange charges associated with the disposal. If you are submitting digital records to your tax preparer, name each disposal file with the cross-reference ID first, followed by the transaction hash, so your preparer can sort files in alphabetical order to match them to your payout memo log quickly. For disposals that involve partial amounts of a single mining payout, note the exact fraction of the original payout being disposed of in the transaction ID box, to avoid overcounting or undercounting cost basis for remaining holdings. Leave a 1-inch blank margin next to the transaction ID box on printed copies for your tax preparer to add adjustment notes if needed.

Cross-reference tracking folder structure for paired document sets

A standardized folder structure ensures you can pull paired payout and disposal records in 10 seconds or less if you receive an IRS inquiry, and reduces time spent sorting records during tax season. The root folder should be named [Tax Year] Mining Payouts & Disposals, with four nested subfolders. The first subfolder, Original Pool Payout Memos, contains files sorted by month, named with the format YYYY-MM-POOLNAME-PayoutID.pdf, and includes all official payout receipts directly downloaded from your mining pool account. The second subfolder, Disposal Transaction Records, contains files sorted by disposal date, named with the format YYYY-MM-DD-ExchangeName-TxHash.pdf, and includes trade confirmations, receipt records for goods purchased with crypto, and on-chain transaction receipts for peer-to-peer disposals. The third subfolder, Cross-Reference Matching Logs, contains the reconciliation schedule detailed later in this guide, plus any notes about partial disposals, commingled holdings, or chain forks that affect asset classification. The fourth subfolder, Tax Preparer Submission Copies, contains redacted versions of all relevant records with sensitive information such as full wallet addresses removed, unless your preparer requests that information to verify transactions. Keep a plain text note in the root folder listing all mining pools you used during the tax year, their support contact information, and their record retention policies, so you can request copies of lost memos if needed. Save a read-only copy of the full folder structure to an offline external hard drive once you file your return for long-term storage, as the IRS can audit returns for up to three years after filing, or longer if underreporting is suspected.

Crypto asset ID form field alignment across both record types

To avoid mismatches between payout memos and disposal records, every field related to the crypto asset itself must be exactly consistent across both document types. Required aligned fields include the full standardized asset ticker (e.g., BTC, not “Bitcoin,” to align with IRS Form 8949 requirements), the official contract address if the asset is an ERC-20 or other chain-specific token, the chain the transaction was settled on (e.g., Bitcoin Mainnet, not just “Bitcoin,” to avoid confusion with layer 2 payouts), and the exact decimal precision of the asset amount received and disposed of, with no rounding unless explicitly allowed by your tax preparer. If you receive a payout in a wrapped token, note the underlying asset and wrapping protocol on both the payout memo and disposal record, so your preparer can correctly classify any unwrapping transactions that occur before disposal. Avoid using custom nicknames for crypto assets in your personal records, as these nicknames will not match the standardized identifiers used by exchanges and tax software, leading to avoidable uncategorized transaction flags. Illustrative example: If you receive 0.05 WETH on Arbitrum on June 3, 2024, both the payout memo and any later disposal record must list the asset as WETH, chain as Arbitrum One, and contract address 0x82aF49447D8a07e3bd95BD0d56f35241523fBab1, to align with exchange records for the same asset.

Payout value matching schedule setup for annual tax reconciliation

The below illustrative matching schedule compares required fields for payout memos and later sale records to streamline annual tax reconciliation, and can be imported as a CSV into most popular crypto tax software tools.

You can extend this schedule to include additional columns as needed, such as short-term or long-term capital gain classification (based on whether you held the asset for more than 12 months between payout and disposal), or notes about any adjustments needed for split payments, lost rewards, or chain forks that affect the asset’s value. At the end of each tax year, sum the total FMV of all mining payouts to confirm it matches the total ordinary income you report for mining activity, and sum the total cost basis of all disposed assets to confirm it matches the cost basis reported on your Form 8949. Any discrepancies between these totals should be resolved before you file your tax return, to avoid inquiries from the IRS.

Before compiling your annual tax records for mining activity, cross-check three randomly selected payout memos against their corresponding on-chain transaction records to confirm date, amount, and FMV entries are fully aligned.