Header and column count
The bundled 1099-DA template contains 71 columns. Verify the names and order, not just the number of columns.
Free 1099-DA IRIS troubleshooting guide
1099-DA CSV Errors: Fix IRIS Formatting & Upload Problems
If a 1099-DA CSV is rejected by a pre-check, looks wrong after spreadsheet export, or produces an IRIS upload problem, start with the file structure before rebuilding the data. This guide is tailored to digital asset broker transaction reporting and the bundled 1099-DA CSV layout.
✓ Validator runs locally in your browserStart with the structure
Three checks solve many 1099-DA CSV problems quickly.
A file can look correct in Excel and still contain a changed header, shifted row, or converted value. Check the raw CSV structure first.
Row width and quoting
Every data row should stay aligned with the header. A stray comma, quote, or missing delimiter can shift the rest of a row.
Spreadsheet conversions
Review TINs, dates, amounts, codes, and indicators after export. Excel can change values without making the change obvious.
Why 1099-DA needs a form-specific check
Digital Asset Proceeds From Broker Transactions
Digital asset reporting uses a wide template with broker/customer identity data, asset transaction details, dates, proceeds, basis-related fields, transfer information, and state reporting. It deserves a form-specific preflight rather than a generic CSV check.
The safest troubleshooting approach is to compare the exported CSV against the exact current template, inspect the form-specific fields that carry the filing information, and then use the general IRIS troubleshooter only after the file itself is structurally clean.
1099-DA file snapshot
71columns in bundled CSV layout
6form-specific fields highlighted below
Localbrowser validator processing
Freetemplate and pre-check tools
Inspect these columns first
Important 1099-DA fields to review after export
These fields come directly from the bundled 1099-DA template. They are useful checkpoints because they contain digital asset broker transaction reporting data rather than only generic contact information.
Box 1a - Code for digital asset
This is a coded field. Compare the value with the current form/IRIS instructions instead of entering a descriptive phrase.
Box 1b - Name of digital asset
Compare this field with the current form-specific template and confirm the value stayed in the correct column after export.
Box 1c - Number of units
Preserve identifiers as text when leading zeroes or long values matter, and verify the value did not change during spreadsheet import/export.
Box 1d - Date acquired
Treat this as a date/year field, not display text. Check that Excel has not converted it to a localized or unexpected format before saving the CSV.
Box 1e - Date sold or disposed
Treat this as a date/year field, not display text. Check that Excel has not converted it to a localized or unexpected format before saving the CSV.
Box 1f - Proceeds
Keep the underlying value plain and consistent. Before export, remove display-only currency symbols, thousands separators, or formulas that could change the CSV value.
Common CSV trouble spots
What to check when a 1099-DA CSV looks right but still has problems
These are pre-upload troubleshooting checks, not promises about IRS acceptance. Use them to find spreadsheet and CSV problems before you spend time retrying the portal.
Dates changed by the spreadsheet
A date that looked correct in the workbook can be exported in a different display format. Review date columns as raw CSV values, especially Box 1a - Code for digital asset, Box 1b - Name of digital asset.
Currency or number formatting leaked into the CSV
Currency signs, comma separators, formulas, or accounting-style cells can turn a plain value into text or change how it is exported. Inspect the raw values in amount-related columns.
A code field contains descriptive text
Code fields should be checked against the current instructions. A readable phrase in Excel is not necessarily the value expected in the CSV template.
Checkbox or indicator values are inconsistent
Checkbox-style fields need consistent accepted values. Do not mix TRUE/FALSE, X, Yes/No, and numeric indicators unless the current template specifically allows them.
A TIN lost leading zeroes or became scientific notation
TINs and other identifiers should be preserved as text in the source spreadsheet. Open the exported CSV in a text editor or validator rather than trusting the spreadsheet display alone.
A comma or quote created an extra column
Names, descriptions, or other text can contain punctuation. Proper CSV quoting keeps the row width stable; hand-editing with commas can break the structure.
Recommended repair workflow
Fix the source file, then export again.
- Start with the current 1099-DA template. Do not recreate the header from memory.
- Run the 1099-DA validator. Fix header, row-width, TIN, tax-year, duplicate-record, and spreadsheet-format warnings first.
- Inspect the form-specific fields. Pay special attention to Box 1a - Code for digital asset and other amount, date, code, or indicator columns.
- Correct the source workbook or export process. Avoid hand-editing only the final CSV if the source will be used again.
- Save a fresh CSV and validate it again. Confirm the warning count falls to zero or only expected review items remain.
- Then retry IRIS. If the structurally clean file still has a portal problem, use the general IRIS error troubleshooter and current IRS guidance.
Related form guides
Other CSV error guides you may need
If your filing workflow includes more than one information return, keep each form in its own exact template and validate each file separately.
1099-DA CSV FAQs
Questions about 1099-DA CSV errors and IRIS uploads
Why can a 1099-DA CSV fail a pre-upload check?
A 1099-DA file can have a header mismatch, a row with the wrong number of columns, spreadsheet-converted identifiers, unexpected date or amount formatting, or a form-specific field that needs review. This guide focuses on those pre-upload checks; the IRS makes the final acceptance decision.
How many columns are in the bundled 1099-DA CSV template?
The bundled 1099-DA CSV template used by this site contains 71 columns. The free validator compares the uploaded header and row width with that layout.
Which 1099-DA fields should I inspect first?
Begin with the identity fields, Tax Year, and form-specific fields such as Box 1a - Code for digital asset, Box 1b - Name of digital asset, and Box 1c - Number of units. Then review every warning from the form-specific validator.
Does the 1099-DA CSV validator guarantee IRS acceptance?
No. The validator is a local structural and formatting pre-check. Current IRS processing-year specifications, business rules, and portal validation determine final acceptance.
Where can I get the 1099-DA CSV template?
Use the free 1099-DA template link on this page or the site-wide IRIS CSV and Excel Template Library. Start with the current layout instead of building a header from memory.
Use this page as a troubleshooting aid, not as a substitute for the current IRS instructions. IRIS templates and processing-year rules can change.
Already filed?
CSV repair and IRS correction are different steps.
If the 1099-DA return was accepted and the reported information is wrong, review the form-specific correction workflow.
TIN or name mismatch?
Use the 1099-DA TIN guide for pre-filing cleanup, CP2100/CP2100A, B Notices, backup withholding, and TIN Matching notes.
Need the full desktop workflow?
Prepare 1099-DA records before the portal.
1099ERICH imports structured data, validates records, prints recipient copies where applicable, and prepares IRIS-ready filing files on Windows.
Free tool → complete workflow
Prepare Form 1099-DA in the full 1099ERICH desktop workflow.
The free 1099-DA resources help with individual checks. 1099ERICH handles the repeatable workflow: import CSV or Excel data, validate and re-import, print recipient copies, and create IRIS-ready CSV files.
Windows desktopCSV + Excel importRecipient copiesIRIS-ready CSV$299