Preparing your own CSV columns for a portfolio

Your own CSV, with every column explicitly assigned

In Portfolio → Imports choose My CSV columns. Upload one file or paste comma-delimited text. This accepts bounded inert UTF-8 text, at most 500,000 bytes and 2,000 data records. A quoted multiline cell is one logical record; XLSX, ZIP, macros and formula execution are not used.

Original positions identify columns, so two equal headings remain distinguishable. Explicitly choose one universal field or Ignore for every column. No output field can be mapped twice. Economic time and the original supported event type are required. The account comes either from an explicitly mapped account_id column or from your chosen own account for the whole file.

Literal conversion without inferred economics

Mapping changes column arrangement and names. It guesses no date, time zone, decimal separator, sign, currency, event type or instrument. Date and numeric strings are copied literally; the existing universal kernel checks validity. A locale date, decimal comma or custom word for a purchase is not silently rewritten. Empty values, explicit zero and the text null are distinct.

Before preparing a server preview, compare original records with generated universal rows. Inspect explicitly ignored columns too. Changing the file, mapping or account invalidates the previous review. Two legitimate identical operations are not merged by conversion. A stable operation_id helps establish duplication; equal amounts and dates alone do not.

Retained lineage, preview and atomic confirmation

Server staging binds the original file, explicit mapping and generated universal CSV hash. Preview shows new, duplicate, conflicting, ignored and erroneous records and warnings. Only your separate confirmation of the whole acceptable group writes the ledger. Confirmation rechecks original lineage and conversion; upload or review alone posts nothing.

An uncertain outcome retains the original operation’s exact identity and content. Verification and retry are explicit; no different new request replaces the old one, and cancelling a wait cannot roll back an accepted write. Ordinary renewal of the portfolio’s short verification preserves drafted mapping. Account or portfolio changes and late responses are isolated.

Confirmed imports connect to existing history and supported import Undo; Undo uses opposite entries and has its own conditions. Mapping your columns establishes no history completeness, cost basis, market price or correct tax output. XTB, IBKR, Trading 212, DEGIRO, Fio and eToro still require genuine permitted anonymized samples and verification of each format. This is no automatic broker detection, AI mapping or broker connector.