Importing your history
Two routes in, and why Alltra stores fills rather than trades.
2 min read
A connected account syncs on its own, so new activity appears without you doing anything. Anything older than the connection comes in from a CSV.
Importing the same history twice does not double your P&L. Alltra reconciles on the fills themselves, so an overlapping CSV is safe to send.
Alltra stores fills, not trades
This is why the numbers can be trusted. Brokers each have their own idea of what counts as a "trade", and those definitions disagree — which is how the same activity ends up summarised three different ways in three different places.
Alltra stores the raw executions and builds trades from them. Every trade points back at the fills it was made of, so any figure on any page traces to the executions behind it. When a rule changes, trades are rebuilt from the same fills rather than edited in place.
What that buys you
- A broker changing its export format cannot quietly change your results.
- A partial fill, a scale-in and a scale-out are one position rather than three.
- Re-importing to fix a gap is safe, because the fills decide what is new.
Getting a usable CSV
- Export a CSV, not a PDF — a statement PDF cannot be read. Alltra takes both shapes brokers export — one row per fill, and one row per completed trade — so an orders export, an executions export and a performance report are all usable. Fills carry the most detail, so prefer them where the platform offers a choice.
- Take the widest date range — the whole account history if it will give it. Extra rows are free; missing ones need a second pass.
- Check the mapping, then a week you remember — the columns are matched for you and the screen shows what it matched them to. Fix anything it read wrong before you commit, then open a week you can check from memory.
Did this article answer your question?
Adding a trade by hand
The Add Trade drawer — typing one in, or uploading a file.
ReadGuide last updated