Reviewing and importing a broker statement
Start with the actual file. Before writing, review every record, account, instrument and time zone.
Multiple statements in one confirmed import
In Portfolio → Import, open Combined broker files (2–6). Add original XML, CSV or XLSX and select the exact supported profile for each file. Every file keeps its own account and asset mappings, time and fee choices. Prepare each conversion, then the combined preview. Switching between files retains unfinished forms.
Choose 2–6 different files, up to 500 kB each, 2 MB in total and 2,000 source records. Review new, duplicate, conflicting and excluded records across all files. Supported stable operation IDs are evaluated together; matching dates or amounts alone do not establish a duplicate. Any conflict or unresolved record blocks the whole bundle. Only separate confirmation writes all new events together.
If a reply is uncertain, explicitly check the original state or retry the exact original operation first. Cancelling a wait does not undo a confirmed write. After success, open saved history and original recipes; supported Undo has its own preview and conditions. Confirmed original files are not archived on the server. Unfinished forms and exact recovery live in open-page memory, not a backup after reload.
Supported file
In Portfolio, open Import → Brokers. Choose Interactive Brokers Activity Flex XML, XTB Cash Operations CSV, Trading 212 History CSV, DEGIRO Account CSV, Fio e-Broker CSV or eToro Account Activity CSV/XLSX up to 500 kB. The first four profiles use UTF-8; for Fio, explicitly select UTF-8 or Windows-1250. eToro reads original XLSX or a UTF-8 CSV of the specific Account Activity worksheet. These are bounded formats and operations; they do not establish full support for every broker statement.
No broker credentials are requested. Select your own file; no demo trade is added to your portfolio. Loading and local review do not write to the journal.
XTB: currency and manually verified costs
For dividend income from a supported Cash Operations CSV, select the XTB History and dividends (v2) scope. First explicitly choose the account currency from the actual statement. Map each dividend to an asset and confirm that its original Amount is gross dividend cash. Amount, currency and gross meaning are not inferred from a comment or ticker.
Manually allocate original negative Withholding tax records with the same account, ticker and exact UTC clock. A tax row can belong to only one dividend and is not counted twice. If withholding is actually zero, explicitly confirm that fact; a missing row does not establish zero. Separately provide the evidenced UTC entitlement instant. Cash posting time does not automatically replace it.
Before confirmation, compare original dividend and tax rows with the one prepared dividend and its net amount. Previously supported trades and funding retain their identities across the profile change. The same choices work in Combined broker files and remain in confirmed history. This does not support interest, unclear FX/Category, unproven NET meanings or native Full Report XLSX.
Save the Cash Operations section as semicolon-separated CSV. The adapter recognizes two exact layouts of 8 or 10 columns with the original account number and UTC window. This does not support native XLSX Full Report, arbitrary CSV exports or changed headers. Encoding is not guessed.
Explicitly choose the source account currency. For every stock trade, provide the actual quoted-price currency, fee currency and amount, and the reason or evidence for this addition. A blank fee is not zero; enter zero only when you have verified it. These are your additions, not facts found in the CSV. The confirmed private recipe retains them.
The first version requires matching currencies and an exact reconciliation of quantity × price and fee with the original cash movement. An unexplained difference, FX or rounding blocks conversion. A Total summary is not an extra transaction and may be explicitly excluded with a reason. Dividends, withholding, internal transfers, CFDs and corporate actions remain unresolved until supported or explicitly excluded.
Trading 212: statement version, time and total costs
Two evidenced older History CSV layouts with 15 or 19 columns and a Time field are supported. Choose the time zone from your original statement; the field alone does not prove UTC. Newer exports with Time (UTC), Gross/Net, CFD and other headers must not automatically be presented as supported.
The file contains no source account number. My Trading 212 statement is a local key; select your own Portfolio account. Explicitly assign instruments. The price and its currency remain from the CSV. For each trade, provide the actual total fee, its currency and the evidence used to verify it. Zero is allowed only as your explicit verified input.
A stated conversion component in the second layout must neither be counted twice nor hidden: it must be included in the verified total fee. The first adapter requires matching price, Total and fee currencies with exact cash reconciliation. Different currencies, an unclear exchange rate, ambiguous IDs and other operations remain unresolved. Dividends and interest are not converted into deposits.
For dividends, select Trading 212 · history and dividends under Trading 212 statement scope. The original v1 trade-history option remains separate. Changing scope clears the loaded file and choices, not a retained unresolved server command. The new option uses the same exact older 15/19-column layouts with Time; it does not support arbitrary newer exports.
For a positive Dividend (Ordinary), explicitly confirm under Dividend evidence that the original Total is gross cash before separate withholding. Its amount is not overwritten. Manually select each corresponding negative Dividend (Dividend tax); the original Time, ISIN and currency must match. Similarity or an offered candidate does not automatically pair records. One withholding record cannot be assigned to two dividends. Explicitly confirm evidenced zero withholding separately; an absent row does not prove zero.
Enter Evidenced entitlement date · UTC and Evidenced entitlement time · UTC from your own records with an explanation. They start blank; the cash-payment time is not copied into them. Entitlement cannot follow payment, and the statement time zone does not shift these explicitly entered UTC values. Conversion creates one dividend event with gross amount and withholding; cash is their net difference. The allocated tax record remains in the audit map without being posted again as another outflow.
Inspect the complete preview, including links and new, duplicate and unresolved records. Back to editing confirms nothing; only the separate confirmation writes to the ledger. Original operation IDs share the namespace used by the v1 trade profile: identical previously stored operations are not added again, while changed content is a conflict. History and its separately confirmed Undo use the events actually added. After confirmation, the original file hash, recipe including dividend links and record map remain, not the original CSV or a restorable copy.
An already net Total, unclear gross amount, missing entitlement evidence, FX and unsupported actions are not guessed. In a supported statement, resolve the record or explicitly exclude it with a reason. New Time (UTC) and Gross/Net headers remain unsupported. This bounded conversion does not establish completeness of an actual broker statement and is not a tax calculation.
DEGIRO: source records, minutes and allocated fees
For income from the supported Account CSV, choose DEGIRO · history and dividends (v2). The profile recognizes the exact original descriptions Dividende and Impôts sur dividende. For each positive dividend, explicitly evidence Change amount as gross cash in its original Change currency, rather than an already net amount. Negative dividend corrections, interest and unclear FX remain unresolved; they do not become inferred deposits.
Select tax records individually from your evidence. Product, ISIN, Change currency, Date, Time and Value date must match; withholding is deducted once and a row cannot belong to two dividends. Without a tax row, separately evidence and confirm zero. Enter entitlement independently in UTC; neither payment time nor Value date supplies it. The same choices remain in combined files and the private history recipe. After confirmation, open the dividend report for that portfolio.
The supported Account CSV has an exact twelve-column header and French decimal-comma cash amounts without thousands separators. Two amount cells have no header of their own, so the adapter preserves their original positions. Transaction CSV, a Portfolio snapshot and native XLSX are different formats. My DEGIRO statement is a local key; this source does not establish a broker account number.
Choose the actual statement time zone and explicitly confirm the number format and use of the recorded minute start for accounting order. The source has HH:mm without seconds; 00 is not an evidenced execution second. Order IDs may be repeated or empty. The wizard uses the original file and row position: it protects exact retries, while changed or overlapping files need your review and explicit exclusion of already posted records. Equal amounts are not automatically merged.
A trade shows its original quantity, price and currency. Verify exact agreement with the cash movement before fees. Supply the evidenced total fee and reason; if it is reported separately, explicitly allocate its original record to the correct trade. Allocated amounts must sum exactly in the same currency and time. A record is included once in the trade and is not posted again separately. Unallocated brokerage commission stays unresolved; exchange connection expenses may be separate fees.
A cash-price difference is not converted into an invented fee or replacement price. Dividends/withholding remain unsupported in the original v1 profile. FX, sweeps, internal flatex transfers and unknown operations stay visibly unresolved or require reasoned exclusion. The adapter does not create missing acquisition history; journal validation blocks a sale without established holdings.
Fio: Czech encoding, source records and net amounts
Upload the original file and choose its actual encoding. SHA-256 identifies the original bytes, not re-encoded text. The wizard displays decoded records and retains the encoding choice in the audit. After changing encoding, select the file again; the wizard does not silently try another decoder.
The exact Czech fourteen-column semicolon Trades header is supported, or an explicitly configured fifteenth Trh column. This does not certify every default Fio export. Preamble records are retained and need reviewed exclusion with a reason. Money pages and balances are not automatically deposit events.
Choose the actual time zone and acknowledge decimal commas and recorded minute starts for accounting order. Settlement date does not replace trade time. Map the account and instrument using symbol, currency and evidenced market. Original-file-and-record identity protects exact retries; changed overlaps need review of the original history and explicit exclusion of already posted records.
Buys and sells must exactly match the original net cash amount in one currency, including fees. A reported fee is preserved; a blank fee needs an evidenced manual value and reason and is never automatically changed to zero. Amounts in different currencies are not added together. Explicit cash-desk transfers additionally require external-flow review with a reason. Unknown operations, FX, dividends and unestablished transfers remain unresolved.
eToro: original XLSX, Amount meaning and actual stocks
Explicitly choose original XLSX or a CSV of the Account Activity worksheet. SHA-256 belongs to the original selected file bytes. XLSX is actually unpacked and its named worksheets, relationships and text/numeric cells are read; financial values are not rounded through ordinary binary numbers. A decoded row in the wizard is not the original binary file. Encrypted files, macros, formulas, external links and unsupported structures are rejected. Legacy binary XLS is not XLSX.
Account Activity has a specific eleven-column header with Units or Units / Contracts. Other worksheets, their rows and preambles remain visible. You prepare only supported Account Activity operations; other records need reviewed exclusion with a reason. Closed Positions does not establish complete opening history, and Summary balances are not deposits.
Choose the actual time zone and account currency, and acknowledge decimal points and weak file-and-record identity. Position ID may repeat across opens, partial closes and fees; it is not an individual execution identity. Equal positions are not merged. Changed or overlapping files need your review of previously posted history.
For a Stocks trade, explicitly attest an actually owned, long, unleveraged position. Supply an evidenced unit price, its currency, aggregate fee and supporting reason. Source quantity remains unchanged. Review Amount meaning separately: gross value must exactly equal quantity × price; on a close, original position capital can be explicitly evidenced without treating it as proceeds. Price and proceeds are not derived from Amount / Units, profit, Realized Equity or Balance. This adapter does not support CFDs or short/leveraged positions.
If an aggregate fee includes a separate SDRT record, explicitly allocate it. Position, time, description and exact sum must agree, producing one cost. Other supported standalone fees require confirmation that they are not included in a trade, plus a reason. A missing fee is never changed to zero. Withdraw Request does not confirm a settled withdrawal; dividends, refunds and unclear cash/FX operations remain unresolved.
Accounts, instruments and original values
Map every source account to a named account in your portfolio. Map each instrument to the correct existing identity or explicitly choose the separate identity offered from its IBKR Conid/ISIN. A similar ticker does not prove the same listing. A new broker identity does not itself provide a market price.
Choose the time zone from your statement settings. An unspecified clock is not converted to assumed UTC. A missing time of day or an ambiguous daylight-saving clock blocks conversion. Review original attributes and the prepared event; an original settlement day is not presented as a verified exact settlement instant.
Unresolved and excluded records
Unsupported or contradictory events stay visible. Correct the choices or explicitly exclude a record with a specific reason. Excluded records are not posted and the resulting portfolio may be incomplete. The reason and original-record-to-row link remain in the private audit.
The adapter does not invent a missing price, withholding or fee. The same date and amount alone do not establish a duplicate. Separate evidenced execution identifiers are preserved; an Order ID is not always such an identifier. DEGIRO here uses explicitly reviewed file-and-record identity.
Preview, confirmation and history
After local review, explicitly prepare the server preview. It compares events with the current journal and separates new, duplicate and conflicting rows. Review the summary and confirm that exact preview. If the journal changed meanwhile, prepare a new preview.
After an uncertain outcome, verify the same account and original request state; do not create a replacement import. Confirmation retains a receipt, history and, where eligible, controlled Undo import. The original file and preview are purged; the confirmed recipe, exclusions, row links and hashes remain private. A hash alone cannot restore the file.
This is a guide to Datisto. Private features require sign-in and access to your own data. Personal models use your assumptions; availability and permitted use of source data are checked with the particular result. This is not investment advice.