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 structured comparison table maps aligned data points between lightning payment logs and official on-chain disposal documentation. It is designed for use in cryptocurrency tax record folders to simplify cross-referencing between off-chain transaction records and permanently recorded on-chain activity. You can use this structure alongside your existing tax preparer checklists to reduce reconciliation delays and eliminate mismatches between off-chain activity and reported disposal events. All entries should be verified against your own wallet records and exchange-issued tax forms before submission to any tax authority.
Log Entry Column Values For Verified Lightning Payment Records
Every valid lightning payment log entry used for tax record keeping must include standardized, verifiable column values to ensure alignment with on-chain disposal records. Required columns include: exact settled payment timestamp (UTC, rounded to the nearest second), unique payment hash, unique pre-image hash for settled payments, sender public key, recipient public key, list of routed channel IDs for payments that pass through intermediate nodes, total satoshi amount transferred to the recipient, total lightning routing fees paid to node operators, user-assigned transaction category (e.g., business operating expense, personal consumer purchase, crypto-to-fiat disposal), and a unique internal log entry ID for cross-referencing. Only payments marked as fully settled with a confirmed pre-image are eligible for matching to on-chain disposal events; pending, failed, or canceled lightning payments cannot be counted as reportable disposals. You should attach a timestamped screenshot of the payment confirmation from your lightning wallet to each log entry in your tax folder, labeled with the corresponding internal log entry ID for fast lookup. You may use the Field Ledger template for lightning payment logs to standardize these columns across all your off-chain records. This document is for educational purposes only, and cannot be used to file a tax return or validate a disposal event for official purposes. Always consult a licensed tax professional before submitting any cryptocurrency tax documentation to a government authority.
Disposal Form Box Entries For On-Chain Transaction Disposal Confirmations
On-chain disposal confirmation forms, whether submitted as part of your personal or business tax filing, require specific box entries that correspond to immutable on-chain transaction data. Required box entries include: transaction date (UTC, matching the block timestamp for the transaction), unique on-chain transaction hash, sender wallet address linked to the disposal, recipient wallet address receiving the disposed crypto, total amount of cryptocurrency disposed (denominated in the native token of the chain, e.g., BTC for Bitcoin blockchain transactions), total on-chain network fees paid for the transaction, fair market value of the disposed cryptocurrency at the exact time of the block confirmation, and disposal type classification aligned with your local tax authority’s guidelines (e.g., sale for fiat currency, exchange for goods or services, gift to a third party, loss due to theft or hardware failure). All entries must match the public record for the transaction hash as shown on a reputable block explorer, and you should save a PDF copy of the block explorer page for the transaction in your tax folder alongside the completed disposal form. Do not adjust on-chain transaction values to match lightning log entries without written documentation of the linkage, approved by your tax preparer.
Cross-Reference Folder Contents For Matched Lightning and On-Chain Entries
When a lightning payment is settled off-chain and later recorded on-chain as part of a channel closure, batch settlement, or other on-chain disposal event, you must group all associated records in a dedicated cross-referenced subfolder in your main cryptocurrency tax records. The table below outlines aligned data points, match requirements, and storage locations for these matched records:
| Lightning Log Field | On-Chain Disposal Form Field | Reconciliation Match Requirement | Folder Storage Location |
|---|---|---|---|
| Settled Payment Timestamp (UTC to second) | Block Transaction Timestamp (UTC to minute) | Timestamps must align within a 10-minute window for channel closure batch disposals | Log tab 2, Form section 3, Block explorer PDF tab 7 |
| Total Satoshi Amount Transferred | Total Crypto Disposed Amount (converted to BTC) | Values must match within 0.00000001 BTC (1 satoshi) margin of error | Log tab 2, Form section 4, Wallet export CSV tab 5 |
| Lightning Network Fee Paid | On-Chain Network Fee Paid | Sum of lightning routing fees plus on-chain channel closure fee must match form entry | Log tab 3, Form section 4, Channel closure receipt tab 6 |
| Payment Pre-Image Hash | Associated Channel Closure Transaction Hash | Pre-image must be linked to the channel ID included in the on-chain closure transaction metadata | Log tab 2, Channel closure receipt tab 6, Block explorer PDF tab 7 |
| Transaction Category (e.g., business software purchase) | Disposal Type (e.g., exchange for property/services) | Category and disposal type must align for consistent tax classification | Log tab 4, Form section 5, Vendor purchase receipt tab 8 |
| Unique Internal Log Entry ID | Cross-Reference ID Field | Log entry ID must be entered in the form’s designated cross-reference field for easy audit lookup | Log tab 1, Form section 1, Folder cover index tab 1 |
Each matched subfolder should be labeled with the unique cross-reference ID from the table, and should include all supporting documentation for the underlying transaction, such as vendor invoices, payment receipts, or channel closure confirmations from your lightning wallet provider. You should update your main folder index each time you add a new matched subfolder, to avoid missing entries during end-of-year tax reconciliation.
Reconciliation Note Fields For Unmatched Lightning Log Disposal Exceptions
In some cases, lightning payment log entries will not have a corresponding one-to-one match with an on-chain disposal entry, and these exceptions require documented notes to be retained in your tax folder. Common reasons for mismatches include: multiple lightning payments batched into a single on-chain channel closure transaction, lightning payments settled in one tax year that are batched for on-chain processing in a subsequent tax year, data entry errors in either the lightning log or on-chain disposal form, or pending channel closures that have not yet been confirmed on-chain. All exception notes must include the following standardized fields: unique exception ID, date of reconciliation, detailed reason for the mismatch, list of all associated lightning log entry IDs and on-chain disposal transaction hashes, estimated resolution date for the mismatch (if applicable), and a signature or initial field for the record keeper or assigned tax preparer. Illustrative example: A freelance graphic designer who received 18 small lightning payments from clients in December 2023 that were batched into a single on-chain channel closure transaction in January 2024 would list all 18 lightning log entry IDs in the exception note, link them to the single January 2024 on-chain disposal transaction hash, and note cross-year batch processing as the mismatch reason. You should never discard or ignore unmatched entries, and should consult your tax preparer to determine the appropriate tax treatment for any exception before filing your return.
Archival Schedule Timelines For Retained Lightning and On-Chain Disposal Records
Retention periods for cryptocurrency tax records vary by jurisdiction and transaction type, so you should always confirm the applicable timeline with your local tax authority and licensed tax professional before discarding any records. For US personal taxpayers, the general guidance is to retain all cryptocurrency tax records, including lightning payment logs, on-chain disposal confirmations, cross-reference subfolders, and exception notes, for a minimum of 3 years from the date you file your associated tax return, or 7 years if you reported capital losses that are carried forward to future tax years. For business taxpayers using cryptocurrency for operational transactions, retain all records for a minimum of 7 years from the date of the transaction, even if the associated tax return was filed and processed years earlier. All records should be stored in at least two separate locations: one encrypted digital copy stored on a password-protected external hard drive or end-to-end encrypted cloud storage service, and one physical printed copy stored in a secure filing cabinet, to avoid loss due to hardware failure, data breach, or natural disaster. You may use the Field Ledger archival checklist to track when records are eligible for secure disposal once the applicable retention period expires. Never discard records before the end of the required retention period, even if you no longer use the associated wallet or lightning node.
Pull your most recent 3 months of lightning payment logs and corresponding on-chain disposal records this week to cross-reference entries using the table above, and flag any mismatches to share with your tax preparer at your next scheduled check-in.