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.
This lost-access memo template standardizes crypto wallet access loss reporting for internal finance and regulatory compliance records. It is designed to be used exclusively for self-reporting lost private keys, seed phrase damage, or custodial wallet lockouts in your personal or business crypto tax records folder, no matter the chain or wallet type. All fields required by this template align with IRS recordkeeping guidance for digital asset reporting, and may be shared with your enrolled agent or tax preparer at your discretion. Field Ledger provides this template for educational use only, and it does not constitute legal or tax advice.
Field Ledger
Below is a standardized reference table for all mandatory fields included on this memo:
| Field Name | Placement on Memo | Required Input Type | Validation Check |
|---|---|---|---|
| Confirmed Access Loss Date | Top right, 1 inch below header | MM/DD/YYYY date string | Matches date of first documented access failure in personal records |
| Wallet Label | First column of main data table on memo | Wallet type + last 4 of public address | Matches label used for this wallet in master crypto tax log |
| Units Shown Per Asset | Second column of main data table on memo | Numeric value + asset ticker | Aligns with block explorer balance dated within 7 days of loss date |
| Access Loss Cause | Notes section below main data table | 1-2 sentence description of loss event | No speculative or unsubstantiated claims of theft unless supported by police report |
| Preparer Signature (Digital or Physical) | Bottom left of memo | Full legal name + date of signature | Name matches legal name used on associated tax filings |
Date Entry Field Placement and Format Requirements
The confirmed access loss date must be placed in the top right corner of the memo, exactly 1 inch below the main header, with no other content in that 1-inch margin section to avoid misinterpretation. The only allowed format for this field is MM/DD/YYYY; no written month names, international date formats, or relative date entries (such as “last Tuesday”) are permitted for formal recordkeeping. The date entered must reflect the first date you confirmed you could not recover access to the wallet, not the date you drafted the memo. Illustrative example: if you confirmed you lost your seed phrase and exhausted all recovery options on 03/12/2024 but did not draft the memo until 03/18/2024, you enter 03/12/2024 in the date field. If access loss was gradual, such as forgetting a password over multiple weeks, use the date you exhausted all password recovery and account support options. For business-owned wallets, the date must be accompanied by the initials of the authorized finance team member responsible for digital asset records, placed directly next to the date entry. If you later file an amended tax return related to this lost wallet, cross-reference this date with the tax year you are amending to ensure alignment with reporting requirements.
Wallet Label Column Allowed Input Specifications
The wallet label column is reserved for standardized, verifiable identifiers that can be cross-referenced with your master crypto tax log, with no vague or generic entries permitted. Allowed input formats include: custodial wallet provider name + last 4 characters of the public wallet address, self-custody wallet hardware/software brand + last 4 characters of the public address, or multi-sig wallet designation + number of required signers + last 4 characters of the public address. Forbidden inputs include unidentifiable labels such as “my Bitcoin wallet”, “exchange funds”, or “crypto savings” that cannot be linked to a specific on-chain address or account. For multi-sig wallets controlled by a business, add the ID number of the multi-sig governance document outlining signer responsibilities in parentheses after the core label. Do not include full public addresses in the label field to avoid exposing sensitive wallet information in shared records; the last four characters are sufficient for cross-reference with your secure master log. If you have re-used a matching label for a different wallet in the past, add a numeric suffix corresponding to the creation year of the lost wallet, for example “Trezor Self-Custody – 3h7k (2022)” to distinguish it from a 2019 Trezor wallet with the same last four address characters.
Units Shown Box Required Verification Steps
The units shown box must reflect the exact balance of assets held in the wallet as of the confirmed access loss date, with no estimated values or fiat conversions included in this specific field. Follow these four mandatory verification steps before entering a value: first, pull the last public on-chain record of the wallet balance from a neutral block explorer dated no earlier than 7 days before your confirmed access loss date. Second, cross-reference that balance with the last transaction record you have on file for that wallet in your crypto tax records. Third, if there are pending transactions that were not confirmed before the access loss, note those transactions in the supporting notes section, do not adjust the units shown to include unconfirmed assets. Fourth, if the wallet holds multiple assets, list each asset’s units separately with its corresponding ticker, rather than combining all assets into a single entry. Illustrative example: if your lost wallet has 0.12 BTC and 2.4 ETH as of the access loss date, you enter 0.12 BTC in the units box for Bitcoin and 2.4 ETH in the units box for Ethereum, with no USD conversion listed in this field. If the wallet holds NFTs or other non-fungible digital assets, list each NFT by its token ID and collection name, and do not assign a fiat value to the NFT in this field. If you cannot confirm the exact balance due to a closed custodial platform or missing records, mark the field as “unverified” and add a note explaining the discrepancy in the supporting notes section.
Supporting Transaction Note Attachment Guidelines
All supporting documentation attached to the memo must be unedited, verifiable, and directly linked to the access loss event or wallet balance. Acceptable attachments include: uncropped block explorer screenshots with visible timestamps and wallet address information, screenshots of your last logged-in session to the wallet (if available), receipts for all transfers into the wallet that include transaction hashes and transfer dates, and copies of police reports if you believe the wallet was stolen or accessed without authorization. Unacceptable attachments include social media posts about losing access, text messages to personal contacts discussing the loss, uncorroborated balance estimates from unaffiliated third parties, and fiat price charts or value calculations for the lost assets. All attachments must be labeled with the same confirmed access loss date and wallet label as the main memo, and stored in the same subfolder of your crypto tax records as the completed memo. If attachments are larger than 10MB, save them to a password-protected cloud folder and add a secured link to the folder in the notes section of the memo, with access credentials stored in your separate secure master records folder. If you are attaching a police report, redact any sensitive personal information such as your home address or phone number before storing the report in shared folders.
Submitted Memo Form Filing Protocols
Once the memo is completed and signed, follow these mandatory filing protocols to ensure compliance with record retention requirements: first, make three identical copies of the completed memo: one for your personal crypto tax records folder, one for your licensed tax preparer (if you choose to share it), and one for your digital asset insurance provider (if applicable). Second, store the original digital copy of the memo in a password-protected folder separate from your active crypto wallet storage, to avoid permanent loss if your primary storage device is damaged or compromised. Third, if you regain access to the wallet at a later date, complete a supplementary addendum to the memo noting the date access was regained and any changes to the unit balance, and file the addendum alongside the original memo in all stored locations. Fourth, do not submit this memo directly to the IRS unless requested by a revenue agent as part of an audit, and always consult a licensed tax professional before submitting any crypto-related records to tax authorities. Retain both the original memo and any addenda for a minimum of 7 years, per federal tax record retention requirements. Field Ledger does not store any of your memo data, so all filing and retention responsibilities rest solely with the memo preparer.
Print a physical copy of your completed lost-access memo and store it in your locked physical tax records folder alongside your digital asset transaction receipts.