1. Export
Export trades or executions from Quantower.
Import
Quantower trading journal
Quantower is Beta. The preview looks for date, symbol, side, quantity, price, and connection. Map the columns yourself, and do not treat the import as a finished parser.
Beta, via CSV export. Not a supported format yet. No auto-sync.
Export, then preview
2. Set the fee
Import the CSV and read the preview, including any skipped rows.
3. Read the preview
If the detection misses, use the column mapper for time, symbol, side, quantity, and price.
4. Tie the session
Supported means the parser is finished. Quantower stays on the mapper until it is listed as supported.
Map the columns once, and leave it Beta
Quantower is Beta. Supported would mean a finished parser with a known header. Quantower uses the column mapper until that is true. Export trades or executions, import the CSV, and read every skipped row. If detection misses, map time, symbol, side, quantity, and price yourself. Fees then come from the file or from the account preset. There is no Quantower auto-sync.
Do not confirm a Beta preview and treat the net as the statement. The reconcile screen will show the gap, which is useful, and it will also show a wrong gap if the mapper attached the wrong price column. Check one row against Quantower’s grid before you confirm the batch.
| What the preview looks for | Why |
|---|---|
| Date | The session needs a time. |
| Symbol | The contract. |
| Side | Buy or sell. |
| Quantity and price | The fill. |
| Connection | Which route the row came from, when the file has it. |
What the preview looks forDate
WhyThe session needs a time.
What the preview looks forSymbol
WhyThe contract.
What the preview looks forSide
WhyBuy or sell.
What the preview looks forQuantity and price
WhyThe fill.
What the preview looks forConnection
WhyWhich route the row came from, when the file has it.
A single mapped fill
Suppose the export calls the price column “Fill price” and the time column “Date/Time”. Point the mapper at those names. The preview should then show the same price you see in Quantower. If it shows a zero, you mapped the wrong column. Cancel and map again. Nothing is stored before confirm.
After a clean preview, the journal can group the fills by Chicago session and show fees. That is the same book as a supported import. The label on the format stays Beta so the next file is not assumed to match. When a real Quantower header is checked and the parser is finished, the status on this page changes. Until then it does not.
Quantower can connect to more than one route, which is why the preview looks for a connection column when the file has one. The connection does not change the tick. It tells you which account the row belonged to before you drop two routes into one book by mistake. Split the file, or confirm only the rows for the account you meant. A mixed preview is a mixed journal, and the statement tie will fail for a reason that looks like a fee error. Read the connection before you press confirm.
Questions
Is Quantower supported?
No. It is Beta. Supported means a finished parser. Quantower uses the column mapper.
Is there Quantower auto-sync?
No.
Can I reuse the mapping?
Map the columns on the file in front of you. A later export that renames a column needs another look.
Where do fees come from?
The file, if a fee column was mapped or detected. Otherwise the account preset, which you should match to the statement.
Start the 7-day trial. No card.
The preview names every skipped row before a fill is saved.