Accounts, holdings, and balances
Import holdings from a CSV file
Bring holdings from a supported statement export into one or more accounts without giving YARCalc ongoing access to the brokerage.
Import is a reviewed transfer, not a brokerage connection
The holdings importer reads a supported statement export and prepares proposed account and holding changes. It is intended to reduce manual entry while keeping you in control of where every security and balance goes. YARCalc does not sign in to the brokerage, maintain a live connection, or continue reading the account after the file is processed.
The preview is the important part of the workflow. A file can be structurally readable and still contain cash rows, unusual symbols, bonds, options, duplicate descriptions, missing basis, or account identifiers that require judgment. Nothing about recognizing the file proves that every row belongs in the plan as shown.
Stop when the preview does not tell a clear story
Use import when the source is a supported Fidelity, Schwab, or generic holdings export and the proposed destination accounts are unambiguous. Keep the original headers and structure; editing the file in a spreadsheet can change identifiers, dates, symbols, or numeric formats in ways that are hard to see.
If the importer cannot identify the source, an account maps to the wrong owner or tax type, totals do not reconcile, or warnings affect material holdings, stop. Correct the source or enter the information manually. Forcing an ambiguous file through is more work than reviewing a small number of accounts carefully.
Choose merge only when existing unmatched holdings should remain. Choose replacement only when the file represents the complete contents of the destination account on the statement date.
Review the proposed account changes before saving
Select the file and inspect the detected source. Map each source account to an existing YARCalc account or create the appropriate destination with the correct owner and tax treatment. Account numbers may help distinguish rows during import, but the import is not an authorization to retain or use brokerage credentials.
Review every security description, symbol, quantity, market value, cash position, destination account, and warning. Matching symbols may preserve YARCalc information not present in the file, such as an asset-class classification or dividend assumption. Confirm that preservation is appropriate rather than assuming the file overwrote everything.
Resolve material warnings and save once only after the preview reconciles with the statement. Repeatedly importing the same file without understanding merge or replacement behavior can create duplication or preserve stale rows.
Reconcile by account, not merely by grand total
Reopen Accounts & Holdings after saving. Compare each account’s holdings and total with the same source statement and date. A correct grand total can still hide a security assigned to the wrong account, a duplicated cash row, or an incorrect owner.
Review asset classes, basis, manually valued items, bonds, options, and unusual securities. The file may not carry enough information for YARCalc to classify or model them as you intend. Then open Update Balances and confirm quoted and manual values are distinguishable.
The imported starting point does not stay current automatically. Future values require supported price updates, another reviewed import, or manual maintenance.
A supported file format does not validate the investment data
YARCalc does not guarantee that every security, tax lot, option, bond cash flow, cost-basis field, cash-equivalent row, or proprietary brokerage symbol can be interpreted correctly. It does not execute trades or modify the brokerage account.
Retain the original statement as the source of truth. Do not upload a file when the preview exposes information you do not intend to use, and do not treat imported classifications as professional investment or tax advice.