Document note only. Field Ledger is not a tax firm, cloud reseller, dental office, or insurer. Read your own form and confirm it with the preparer, billing desk, carrier, or another licensed professional.
Dust sweep row entries must be properly logged to maintain accurate, compliant records on official crypto gain sheets. These rows capture small, leftover crypto balances from batch swaps, transaction fee rounding, and automated wallet consolidations that are often overlooked during initial gain/loss calculation workflows. Omitting these entries can lead to mismatches between on-chain transaction histories and filed tax records, resulting in processing delays if returns are selected for review. You can use the structured process below alongside your existing crypto tax folder and Field Ledger templates to standardize logging these entries across all tax periods.
Field Ledger
Dust sweep row entry form completion requirements
All entries must be completed within 3 business days of the dust consolidation event to avoid gaps in memory or missing transaction records. All entries must tie to a verifiable on-chain transaction ID; no manual entries are permitted without supporting proof. Required fields on the standard dust sweep entry form include: transaction timestamp (UTC), wallet address of origin, wallet address of destination, total dust amount consolidated per asset, associated network fee paid, and a unique reference ID that links directly to the corresponding gain sheet row. You may not aggregate dust across different assets or different tax quarters on a single entry line; each discrete consolidation event gets its own form entry. Even if the dust amount is below the reporting threshold for your jurisdiction, you still must log it on the gain sheet for reconciliation purposes, even if it does not generate a reportable gain or loss per your preparer’s guidance. You may not alter a submitted dust sweep entry form without adding a dated amendment note that explains the change, and a copy of the amended form must be shared with your tax preparer immediately. If a dust sweep is reversed due to a network error, you must log both the original sweep and the reversal as separate entries, with cross-references to each other’s unique consolidation IDs. Never estimate the value or amount of swept dust; use exact values pulled directly from your wallet export and blockchain explorer records to avoid discrepancies.
Crypto gain sheet column mapping instructions
Each dust sweep row entry must be mapped to the corresponding columns on your official gain sheet to ensure alignment with standardized tax record formats. Do not add custom columns that are not approved by your tax preparer, as this can break automated reconciliation tools and create extra work during review periods. The table below outlines the dust-row card field to gain sheet column mapping for reference, to be adjusted per your preparer’s formal requirements. If your gain sheet uses a different naming convention for columns than what is listed in the dust-row card mapping table, create a separate cross-reference document that lists your gain sheet’s column names alongside the corresponding dust-row card fields, and save that cross-reference in your main tax records folder for the year. This will allow third-party reviewers to quickly align your entries without requesting additional clarification.
| Dust-Row Card Field | Gain Sheet Column Name | Required for Reconciliation | Notes |
|---|---|---|---|
| Unique Consolidation ID | Transaction Reference ID | Yes | Links directly to the on-chain transaction hash saved in your supporting records folder |
| UTC Transaction Timestamp | Disposition Date | Yes | Must match the timestamp recorded on the blockchain explorer export for the associated transaction |
| Total Asset Amount Swept | Quantity of Asset Disposed | Yes | Report to the same decimal precision used for all other transactions of that asset on your gain sheet |
| Fair Market Value at Time of Sweep | Proceeds from Disposition | No (unless required by your jurisdiction) | Use the same pricing source applied to all other transactions of that asset in the same tax period |
| Network Fee Paid for Sweep | Transaction Expenses | No (unless required by your jurisdiction) | Classify per formal written guidance from your licensed tax preparer |
Monthly reconciliation schedule cross-check steps
Set a recurring calendar event for the last business day of each month to cross-check all dust sweep entries logged that month against your wallet export and gain sheet drafts. Step 1: Pull all dust consolidation transaction IDs from your wallet’s transaction history export for the month, and cross-reference each ID against the unique consolidation IDs listed on your dust sweep entry forms for the same period. Flag any missing entries for immediate logging. Step 2: Confirm that every dust sweep entry form has a corresponding row on your working gain sheet, with all mapped fields matching exactly across both documents. Step 3: Reconcile the total amount of each asset swept during the month against the change in balance across your origin and destination wallets, to ensure no dust amounts were omitted or double-counted. Step 4: Sign and date the monthly reconciliation log, and save it in the same folder as your dust sweep entry forms for the tax year. Illustrative example: If you logged 12 dust sweep entries for Bitcoin during the month, confirm that the total amount of Bitcoin swept across all 12 entries matches the difference between the total Bitcoin sent from your hot wallets and the total Bitcoin received in your consolidation wallet for the same month. If you identify a discrepancy during the cross-check, flag the entry for follow-up with your preparer before proceeding with final gain sheet updates. Do not adjust entries on the gain sheet without first verifying the correct value against on-chain records, as unsubstantiated changes can lead to compliance issues. If you process more than 100 dust sweeps per month, you may choose to run this cross-check on a bi-weekly schedule to reduce end-of-month workload, per your preparer’s formal approval.
Transaction detail note filing best practices
All supporting documentation for each dust sweep row must be filed in a dedicated subfolder of your crypto tax records folder, labeled with the tax year and “Dust Sweep Supporting Notes”. For each entry, save a PDF export of the blockchain explorer record for the transaction hash, a screenshot of the wallet balance change for both origin and destination wallets at the time of the sweep, and a copy of the corresponding dust-row card. Do not combine supporting documents for multiple dust sweep entries into a single file, as this will slow down review processes if your records are requested by tax authorities or your preparer. Name each file using the format [Tax Year]_[Unique Consolidation ID]_[Asset Ticker], so you can quickly locate records during reconciliation or review. If you use a digital records management system, add tags for the tax period, asset type, and transaction type to make cross-searching easier. Do not edit or redact any information on the blockchain explorer exports, as unaltered records are required for valid verification. If you use a crypto tax software tool to track transactions, export a copy of the software’s record of the dust sweep and save it alongside your other supporting documents for the entry. Retain these supporting notes for a minimum of 7 years, per standard tax record retention guidelines, or longer if required by your jurisdiction. You can scan physical copies of any signed reconciliation logs and save them in the same subfolder to ensure all records are stored in a single, accessible location.
Archived record folder indexing guidelines
When you finalize your gain sheet for a tax year and archive your records, create a single index file for the dust sweep entry subfolder to simplify future access. The index file must include a list of all unique consolidation IDs for the year, the date of each sweep, the asset ticker, and the row number of the entry on the final filed gain sheet. Save the index file in both the dust sweep subfolder and the main tax year folder, so you can locate the dust sweep records without navigating through nested folders if needed. If you are using physical folders, print a copy of the index and place it in the front of the dust sweep records divider, and label the outside of the folder with the tax year, record type, and total number of dust sweep entries included. Do not mix dust sweep records from multiple tax years in the same archived folder, as this can lead to misclassification during future reviews. You may reference Field Ledger indexing templates if you need a pre-built structure for your index file. This document cannot file your tax return, and you should confirm all indexing requirements with your licensed tax preparer before archiving records. If you share your archived records with a third party, include a copy of the index file to ensure they can navigate the dust sweep records without additional guidance. Never delete archived dust sweep records before the end of the required retention period, even if you believe the entries do not impact your filed tax returns.
Pull your last 30 days of wallet transaction exports, flag all dust sweep events, and log them on a draft dust-row card before completing your next monthly reconciliation.