Export a transaction-history CSV from OANDA HUB
The OANDA HUB transaction history guide describes this workflow: sign in to HUB, open Reports → Transaction History, choose the account and start/end dates, set the timezone, show the transactions, and select Export to csv. OANDA services differ by legal entity and region, so menu labels or available reports may vary.
Use the help pages for the OANDA division that holds your account if your dashboard looks different.
The report’s timezone matters. OANDA notes that timestamps use the selected timezone and that the default can be GMT−12 in the referenced HUB workflow. Choose the timezone you want before exporting, and record it with the file. A trade that appears on one calendar date in OANDA can fall on the previous or next date in Edgelog if the report timezone is misunderstood.
Select trade rows, not every account event
Transaction history may include more than completed trades. Before importing, inspect the CSV headings and several rows. Identify the records that represent closed trade results. Deposits, withdrawals, financing, account adjustments and open-position activity should not be mapped to P&L as if they were closed trades.
If the report separates trade execution from related cash entries, select a trade-focused report or export when your OANDA platform provides one.
Edgelog requires symbol or instrument, buy/sell side, entry price, trade volume or quantity, and realized profit or loss. Optional close price, fees and dates improve the journal record when available. If the export reports units rather than lots, make sure the quantity is understood before mapping it; a number being numeric does not mean it is in the right unit.
Import the OANDA CSV into Edgelog
- Open the CSV import flow in Edgelog and create or select the CSV account representing the OANDA account. Do not combine two OANDA accounts into one Edgelog account if you need their performance kept separate.
- Upload the file and inspect Edgelog’s suggested column mapping. Confirm the fields manually when headers are ambiguous.
- Check direction, sign and units on representative rows. A profitable sell must remain a sell; a loss must remain negative; quantity must mean position size.
- Compare a few trade timestamps to the same OANDA records, accounting for the timezone selected during export.
- Compare the imported trade count and net realized P&L with OANDA for the same account and period before accepting the result.
Avoid common date and P&L mistakes
Do not assume the export uses your computer’s local timezone. Keep the selected timezone consistent across monthly exports so one account’s history does not switch conventions midway through. If the CSV includes gross profit, financing, commission and net P&L separately, choose the field that represents the result you want to track and avoid mapping both gross and net values into the same field.
Edgelog’s fee field is optional; its meaning should match the broker report’s sign convention.
If one OANDA position was closed in several parts, check whether the report shows one final position result or multiple realized transactions. Use the representation you want to journal consistently, and do not mix position-level rows from one export with execution-level rows from another. A stable row definition makes comparisons across weeks and accounts more meaningful.
Refresh older data without duplicating it
When downloading another date range, select the existing OANDA CSV account if the import flow offers it. Use adjacent date ranges with clear start and end boundaries, and avoid overlapping exports unless you have reviewed duplicate behavior. Keep a simple note of the dates already imported.
If the broker offers a current CSV covering all history, compare its first and last trade dates with Edgelog before importing it over an existing account.
For a general checklist, see the broker CSV import hub. If a heading is not recognized, follow column mapping guidance; if dates, quantities or P&L look wrong, use CSV import troubleshooting.