Importing an investment statement (CSV)
Varuno can import investment activity from a CSV your provider exports. This is the only statement import that exists — there is no bank or credit-card statement import for transactions, and no PDF import.
File requirements
- CSV or plain text
- UTF-8 encoded
- At most 10 MB and 10,000 rows
If a file is rejected for format, size or encoding, re-export it from your provider as CSV (UTF-8).
The flow
- Insights → Investments → Import, and choose the destination investment account.
- Pick the file.
- Map the columns — tell Varuno which columns hold dates, amounts and references.
- Review the rows. Each row can be toggled on or off before committing.
- Tap Import N rows. The commit is atomic — all selected rows or none.
The file is read locally on your device; its contents are not uploaded.
Duplicate protection
Imports are idempotent through four independent layers, from file hashes down to per-row fingerprints:
- Re-importing the same file shows all rows as “Already imported” with 0 ready — that is working as intended, not an error.
- “Conflicts with an imported row” means a row has the same provider reference as an existing record but a different amount. The commit is blocked for that row: uncheck it, then verify the correct figure with your provider. If conflicts recur, contact support with the reference id — never the amounts.
- Rows you edited after a previous import are never overwritten by a re-import.
Asking for help
If a provider’s CSV that should work keeps failing, report it with the provider’s name and the header row only — no amounts, no balances.