Same-Day Buy and Sell Left as Two Separate Rows

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.

The same-day two-row card logs separate buy and sell transaction entries for official crypto trade record submissions. This document standardizes entry placement for transactions executed within the same UTC calendar day to eliminate misclassification by tax processing software. It is designed for use with your existing crypto tax records folder, and all guidance aligns with standard record-keeping requirements for self-filers and professional preparers. You should cross-reference all entries with original exchange confirmations before submitting any documentation to a regulatory body, and consult a licensed tax professional with questions specific to your filing jurisdiction. This page cannot file a return on your behalf, and all guidance is for educational purposes only.

Buy Transaction Row Label Placement

The buy row always appears as the top row of the two-row set, with no blank rows, comments, or unrelated entries placed between the buy and corresponding sell row. The mandatory label “SAME-DAY BUY” must be left-aligned in the first column of the buy row, formatted in bold for digital spreadsheets or all capital letters for handwritten logs to avoid confusion with regular non-same-day buy entries. You may not merge any cells across the buy and sell rows, as merged cells often cause import errors in popular crypto tax processing tools. All required fields for the buy entry must be included in the corresponding columns: asset ticker, quantity purchased, gross cost in your filing fiat currency, total transaction fees, exchange or platform name, and unique buy confirmation ID. If you are logging multiple same-day buy-sell pairs for the same asset in a single log, each pair gets its own discrete two-row set, with no grouping of multiple pairs into a single block of rows. Field Ledger templates include a dedicated first column for these labels to reduce formatting errors for users compiling their own records. You should never place a sell row above a buy row for a same-day pair, even if the position is a short sale, as tax processing systems default to first-in-first-out cost basis ordering, and misaligned rows will lead to incorrect calculation of gains or losses.

Sell Entry Column Spacing Standards

The corresponding sell entry appears directly below the buy row, with consistent column spacing that matches the rest of your crypto trade log exactly. You may not adjust column widths for just the two-row set, as inconsistent width can cause OCR scanning errors for physical logs and import failures for digital spreadsheets. For digital logs, set all columns to a minimum width of 12 characters and lock the column width for the entire log before entering same-day pairs to prevent accidental auto-adjustment. For handwritten logs, leave a minimum of 0.25 inches of blank space between each column to avoid bleed-through or misreading of adjacent values. The sell row label “SAME-DAY SELL” must appear in the same first column as the buy label, using identical formatting (bold for digital, all caps for handwritten) to maintain consistency. Align the fiat proceeds column for the sell entry vertically with the gross cost column for the buy entry, so preparers can quickly calculate gross gain or loss without cross-referencing across columns. Illustrative example: If your gross cost field is located in column F of your log, your sell proceeds field must also be in column F for the corresponding sell row, with no shifting to column G or any other adjacent column.

Timestamp Verification Box Requirements

A dedicated timestamp verification box must be placed to the right of each two-row set, spanning the full height of both rows but not overlapping with any entry columns to avoid obscuring trade data. The box must include four mandatory elements: the full UTC timestamp of the buy execution as listed on your exchange confirmation, the full UTC timestamp of the sell execution as listed on your exchange confirmation, a check box to confirm both timestamps fall within the same UTC calendar day, and a signature or digital initial line for the record keeper along with the date the entry was verified. You may not use local time zones for timestamps in this box, as exchange records universally use UTC, and time zone discrepancies are a common trigger for audit inquiries. If the two transactions fall on separate UTC calendar days, you cannot use this two-row format, and must log the buy and sell as separate unrelated entries in your main trade log. Illustrative example: If your buy is timestamped 23:47 UTC on 10/14/2023 and your sell is timestamped 00:12 UTC on 10/15/2023, they fall on different UTC days and are ineligible for this formatting. For physical logs, fill out the verification box in non-erasable blue or black ink, with no pencil or white-out permitted. If you make an error when entering the pair, cross out the entire two-row set with a single diagonal line, write “VOID” across the verification box, and create a new two-row set on the next available line of your log.

Trade Reference Note Positioning Rules

All trade reference notes for the two-row set must be placed directly below the sell row, with no notes placed between the buy and sell row. For handwritten logs, indent the note 0.5 inches from the left margin to clearly distinguish it from formal entry rows. For digital logs, place the note in a dedicated “Trade Reference” column that spans the full width of all entry columns for the row directly below the sell entry, or use a threaded comment attached to the sell row label to keep references linked to the correct pair. Reference notes may only include factual, verifiable information: the unique combined trade ID if your exchange assigns one for same-day round trips, a note of any related wallet transfers that funded the buy or received the sell proceeds, and a cross-reference to the page number or file name of the original exchange confirmation stored in your supporting documents folder. Do not include extraneous information like personal opinions on the trade, market conditions at the time of execution, or planned future trades in the reference note, as these details are irrelevant for tax record purposes. If you have multiple reference details for a single pair, list them sequentially with numbered bullet points to avoid truncation or misreading.

Filing Folder Tab Naming Conventions

All completed same-day two-row entry logs must be stored in a dedicated subfolder of your main crypto tax records folder, with standardized tab naming to ensure quick retrieval during preparation or audit. The main folder tab must follow the exact format: [4-Digit Tax Year] – SAME-DAY CRYPTO TRADES – [Last 4 Digits of SSN or EIN]. Do not use abbreviated tax years (e.g. use 2023, not 23) or informal labels like “quick trades” on the folder tab, as informal labels can delay processing if your records are requested by a tax authority. If you have more than 50 two-row sets for a single tax year, split the entries into quarterly subfolders labeled Q1, Q2, Q3, and Q4, placed inside the main same-day trades folder, with each quarterly folder containing a table of contents listing all included pairs by date. Store both a digital copy of the entry log and scanned copies of all corresponding exchange confirmations in the folder, with all scanned files named using the confirmation ID of the associated trade. For physical folders, place the tab on the right side of the folder in the third cut position, so it is visible when stored in a standard filing cabinet alongside your other tax records. Retain these folders for a minimum of 7 years per standard federal tax record retention guidelines, and consult your tax preparer for jurisdiction-specific retention requirements.

Same-Day Two-Row Card Entry Standard

Before logging your next same-day crypto buy-sell pair, cross-verify both transaction timestamps against your exchange’s official UTC confirmation to confirm eligibility for the two-row format.