For your users' next step: the ITD utility's CSV upload + import JSON rules, documented (MIT)

[mehulbhardwaj]

Hi — vestwise gets E*TRADE users to their STCG/LTCG and Schedule FA figures; the step after that is the ITD offline utility, whose CSV parser and import JSON are strict and undocumented. We spent a filing season deriving both and published the results (MIT, CivicTaxes):

• the CSV upload rules the utility actually accepts — 8 rules, each from a rejected upload (unquoted values, no trailing comma, CRLF, ASCII-only, enum codes not display text…)
• the import JSON contract — why a schema-valid JSON can still import blank

Feel free to link them for your users if useful. And thanks for encoding the BenefitHistory.xlsx format in the open — if we build an E*TRADE adapter for our broker-agnostic pipeline, yours and SeFA's format handling are what we'd follow, with credit.