Importing a supported Fidelity or Schwab transaction-history export gives an account a trade ledger, cost basis, realized gains, income, and daily value history. CSV support follows the explicit broker format, not a custom institution name.
- Export the right date range. Before a file is chosen, the drawer says where this account's history ends and which date to export from: a week before that end, or earlier. A trade is recorded on the day it settles, which can be days after the date the broker lists it under, and a broker filters its export by that listed date, so starting the day after the last recorded transaction could miss whatever happened in between. A week covers ordinary settlement. A new-issue CD or Treasury purchase that settles more than a week after it was placed, or a transaction you typed in with a future date, can still put the suggested date after the day your last export ended; if you know when that export was taken, start from that day instead. Overlap is harmless: rows already in the account are recognised and skipped. A complete-history account begins at an explicit
$0opening date; a later file into it is checked against the whole ledger, so a sale of shares an earlier file bought is not read as a deficit, and neither is cash that dips below zero for a few days while the money-fund sale paying for a purchase settles, even in a file exported before that sale posted (money in transit). An opening-statement account names the first newer-transaction date; rows on or before its prior-day observation are skipped so the sources cannot double-count. Rows dated before the account's own starting point are left out for the same reason, and the import result says how many. A file whose first new row falls long after the account's last recorded transaction warns before import; a file that overlaps the ledger never does. - Confirm the file. On Accounts, open the account's Import CSV action and choose the file. A broker export carries no account identity inside it, so the drawer reads two other things. First the file's rows against the account's ledger: rows already stored in this account are near-proof the file is this account's, and the next step opens at once under one green line, File confirmed (with a Not this file? way back); rows inside the ledger's date range that match nothing and name securities the account has never held are refused as another account's export (a file with no securities, such as a cash-only Schwab export, is asked about instead). The facts behind a confirmed file sit under Details: how many of the file's rows the account already holds, how many of its securities the account has ever held (a security new to the account is ordinary and is named), for a Fidelity export whether its cash balance matches, and the file-name match. A warning is never folded away: a sale of a security the account has never held (the wrong account, or missing history) or a cash difference shows beneath the line, and inside the question when the drawer has to ask. Second the account number brokers put in the file name (Schwab's
XXX242, Fidelity'sHistory_for_Account_…) against every file already imported: a number this account's earlier imports carried also skips the question, and a Fidelity number only ever imported into a different account is refused, as is a file in another broker's format. Schwab's name carries just the last three digits, which two accounts can share: an account with no Schwab ending on record yet is asked, and the question names the other account, while an account that already has its own Schwab ending refuses a different one. When neither can tell, the drawer shows the file's format and date range and asks Is this the right file for this account?, with a caution if the account has activity in the file's range that the file does not contain. Choose another file picks again. - Read what the import will add. One section, titled with the count of transactions the account does not have yet (the only ones the import adds), their date range and types, lists exactly those rows; beneath it, how many rows are already in the account, fall before its starting point, or could not be read. The Import button carries the same count. A file whose every row is already stored says Nothing new to import and cannot be imported; neither can a completed import be run a second time. Unknown tickers among the new rows are stubbed rather than dropped.
- Review every core-cash change. A candidate requires opposing same-day, equal-value legs between two money-market vehicles. Confirm change makes the pair traceable, zero-value internal movement and records the dated cash-vehicle lineage. Not a core change imports the rows ordinarily and leaves lineage unchanged. The former fund's own start is dated at the first row the import can see. Once the account's history shows a fund in use earlier, any later import, whatever it contains, says so beforehand (X was the core cash fund before its recorded start) and moves that start back to the fund's own first activity, so the account's cash history (checkpoints, the register's cash balance) counts the earlier activity too. It never moves it onto days the fund before it was still in use, or into a stretch you dated as regular cash or an unknown vehicle. A start you set or edited yourself is never moved. Whatever the import can't cover, the review warns about, and the fix is the account's Cash vehicle history on Account details.
- Resolve the current answer. If the newest confirmed change conflicts with setup, choose the imported vehicle, keep setup with a later effective date, or leave it unresolved. History still imports; the choice controls today's grouping.
- Read the cash result. A broker checkpoint that matches is the evidence block's green Cash line; one that does not produces a card with the exact difference. Import with warning preserves that discrepancy; it never labels the account reconciled. The card offers only the reviews that can explain it: the cash-vehicle changes when the file has one, and the opening data when nothing vouches for the earlier history. If the account's last checked import matched the broker, the card names that date and amount instead, because the difference then lies after it: in a row this import adds, or in a transaction already in the register that the broker's file does not show. An export that carries no checkpoint, as Schwab's never do, shows no cash card at all. The checkpoint compared is the balance after the newest row in the file that carries a readable cash balance (normally its first record, since exports list newest first), never the row with the latest date. A broker's running balance follows the file's order, and a trade is dated by its settlement, so on an exchange day a trade can carry a later date than the dividends listed above it; each row from this file therefore counts by its place in the file, not by its date. A row the file does not report (an earlier import's, or one you entered) counts when it is dated on or before the latest date the counted file rows reach.
- Review opening observations and compare with the broker. Missing opening positions or cash remain findable from the Overview and Accounts until resolved. Reconcile shares and the one logical cash pool against the broker.
Confirmed old-to-new transfer legs contribute no deposit, withdrawal, purchase, sale, income, lot, or performance flow. Later dividends or corrections from a former vehicle still enter cash without making it current again.
T-bills, Treasury notes and bonds, and CDs in the file are recovered as instruments and appear on Fixed Income. A Treasury security (a CUSIP beginning 912) counts as a bill unless its rows show a coupon, an interest payment or a term longer than a year; a stated 0% coupon (a STRIP) keeps it one. A later file never takes back what an earlier one proved about an instrument: a coupon row the broker rewrote after maturity does not date the maturity, and a coupon schedule is read from every coupon imported so far, not from one file. See The Fixed Income page.
An imported row is recognised by the broker line it came from: the security, type, amount and the broker's own description, as the import read them. A note you add to it in the register, or a date or amount you correct there, does not stop the next overlapping export from recognising it, so it is never added a second time. Rows imported before this version learn that identity the first time a file matches them. One whose note you had already edited before then, or whose description the broker has since re-worded, cannot be recognised for certain, because its stored text no longer matches any line. When lines of the file agree with it in date, security, type and amount, the drawer lists the stored transaction under Is this a transaction you already have? with its Stored description/note (your note, or the broker's older wording) and every line it could be, the likeliest first, and asks which one it is. Picking a line skips that line, keeps your transaction and remembers the answer, so it is not asked again; every other line imports. None of these lines imports them all. Nothing is skipped or added until you answer. After None of these lines, your stored transaction still matches no line of later exports, so those imports may list it under the warning below; if it really is separate, that warning can be left as it is.
An earlier version could book a row a second time: one whose note you had edited, when an overlapping export came in, or a purchase (often a Treasury bill) that two exports dated a few days apart. When a file matches one copy of such a pair and nothing in it stands behind the other, the drawer says the transaction may already be in the account twice. This keeps being said after later imports have recognised each copy, until one is removed. It deletes nothing, because two genuine transactions look exactly the same (two equal purchases of one security a few days apart, one of them just outside the file, also raise it): open the account's register, and if they are the same, delete one. An earlier version also suggested starting the next export the day after the last recorded transaction, which could miss activity listed on those days. If a broker checkpoint or a position count disagrees after such an import, export again from a week before the last import's end; rows already here are skipped and the missing ones are added.
A purchase whose settlement date the broker leaves blank, as Fidelity does on Treasury bills until settlement posts months later, is dated instead by the core-cash movement that paid for it. Exporting the same period again once that date has filled in gives the same purchase a different date, and the import recognises it as the row you already have rather than adding it a second time. One catch applies to a ledger imported before this version: it holds no record of which of its dates were derived that way. Import the original export once more first. It adds nothing, and the later one then reconciles against it.
Any line the file contains but the import cannot use is listed by reason and line number before you import, including the export's own header and disclaimer text. A file that yields nothing therefore says why instead of reporting a clean import of no rows, and a file with a header and no transactions says This file has no transactions rather than claiming they are all already stored.
A Fidelity export can include activity the broker has not posted yet, such as a scheduled transfer: the line shows Processing where the cash balance would be, and may carry a date still ahead. Those lines are not imported. They are listed as Not yet posted at the broker, and the transaction arrives with the next export you import after it posts. Importing one early would book it twice, because Fidelity can re-word the line when it posts.
The columns are found by their header names, not their positions, so an export that reorders them (Quantity before Price, say) or spells Price ($) either way reads the same. A header missing a column the format needs, such as Amount, is refused by name rather than guessed at. Files saved with old Mac (carriage return only) line endings read like any other.
A Schwab maturity arrives as two lines: the quantity leg posts as a sale at par, and the cash leg is listed as Cash leg of a maturity, already posted by its quantity leg. That is deliberate, since posting both would count the maturity twice, and it raises no warning. Any other action the importer does not recognise that carried a dollar amount (a dividend or interest under a name it does not know, a foreign tax charge) raises Some activity in this file will not be posted, with the total and the action names. Nothing is guessed: that money is not in the account until you enter it by hand, so its cash will differ from the broker's.
Previous imports, collapsed beneath the CSV flow in the account's Import drawer with its run count, undoes one run, removing the rows only that import stands behind. Rows a later, overlapping import also reported are kept and handed to that import; the Undo count is what will actually be deleted. Import-owned cash periods go with their run unless surviving rows still rest on them, and a start the import moved back stays with the import that first recorded it. A cash period you manually edited is detached from that disposable import provenance and always survives.