How to export your XXKK trade history (spot and futures) and turn it into a clean tax file

Tax time has a special talent for turning normal trading into a messy paper problem. You remember the big wins (and the painful liquidations), but the accountant wants rows: date, side, price, fees, IDs, and proof that it all matches your exchange. This guide explains how to do an XXKK trade history export for spot and futures, then reshape those exports into one clean CSV you can import into tax software or hand to your accountant. One quick warning in February 2026: there’s no widely indexed, official XXKK help page that shows the exact current export buttons and menu names, so the steps below are written as “UI-safe” click paths you can follow even if XXKK changes labels slightly. What a tax-ready XXKK export must include (and what people forget) A tax file is not only “spot trades”. It’s closer to a bank statement plus a trading ledger, and futures adds a second layer. For spot, you usually need: filled trades (each fill, not just the order), trading fees, and any conversions that look like swaps. Many traders export only “Orders” and later discover it contains cancels, edits, and unfilled orders, which has no tax meaning. You want fills, because cost basis is created at execution time, not when you placed the order. For futures, it’s even more picky. A futures “trade history” can show entries and exits, but your taxable result is often driven by: Realized PnL (profit or loss when you close, partially close, or get liquidated) Funding payments (paid or received on perpetuals, and it can be many small rows) Fees (open and close fees, sometimes separate from funding) Transfers between spot wallet and futures wallet (not taxable by itself, but it explains balance moves) Margin interest (if XXKK charges borrowing interest in isolated or cross margin setups) If you’ve seen how other exchanges phrase it, the pattern is similar: export a full transaction report, then reconcile. Binance.US, for example, separates exports and warns reports can take time to generate, see transaction history and tax report export steps. A practical rule: export by calendar year (or your local tax year), and also export a buffer of a few days before and after year-end. Those boundary trades are where timezone confusion quietly ruins the file. XXKK trade history export steps (web and mobile, spot and futures) Because XXKK UI wording can shift by region and app version, you’re aiming to locate three things: History, Filled/Trades, and Export/Download. If you can’t find “Export”, look for a download icon, “Generate report”, or an email-based report queue. Web (desktop browser) export path you can follow safely Log in to XXKK on the web, then open the top menu area for Orders or Trade (some UIs put it under Profile or Assets). Find Spot first, then open Order History or Trade History and switch the sub-tab to Filled, Executed, or Trades (avoid “Open Orders”). Set the date range (start with 1 month if you want to test, then do the whole tax year). If there’s a timezone selector, pick the one you will keep everywhere (UTC is simplest). Click Export or Download (CSV is preferred). If XXKK queues the file, wait for a notification, then download from the export center or messages area. Repeat the same for Futures (or Derivatives): look for Futures Trade History, plus separate pages for Realized PnL and Funding (if XXKK splits them). Also export Account Transactions (deposits, withdrawals, transfers) if the tax tool you use needs wallet flows to reconcile. If you’re unsure what you’re missing, compare the “what to export” categories with a well-documented exchange guide like KuCoin’s overview of taxes and history types. You’re not copying their file, you’re using the same mental checklist. Mobile app: when export exists, and when it doesn’t Many exchange apps show history but do not always support full CSV export. So the mobile goal is simple: confirm the data exists, then export from web if the button is missing. Open XXKK app, go to Orders (or History), then switch between Spot and Futures. Filter to Filled/Executed for spot, and for futures look for PnL, Funding, or Transaction History pages. If you see Export or a share icon, export CSV and save to Files/Drive (avoid sending it unencrypted in chat apps). If there’s no export option, use the web export flow in a mobile browser (or desktop). Screenshots are not a tax file, they’re just proof. Small tip that saves hours later: whatever device you use, export the same timezone each time, and write it down in the filename. Turn XXKK exports into one clean CSV your tax software accepts You usually end up with multiple files: spot fills, futures fills, realized PnL, funding, and maybe fees. The job is to normalize them into one schema your accountant can read without asking ten questions. Column mapping: from “exchange language” to “tax import language” Your XXKK CSV headers may differ, so use this mapping by meaning (left side shows common header variants you might see): XXKK column (common variants) Tax file field (common) Notes Time, Created Time, Executed At Date Keep one timezone (UTC preferred) Symbol, Pair, Market Base Asset, Quote Asset Split BTC/USDT into BTC and USDT Side, Type Type/Side Buy, Sell, Long, Short (futures may need translation) Price, Fill Price Price Use dot decimal if possible (10.25 not 10,25) Qty, Amount, Executed Qty Amount For sells, some tools want negative amount, be consistent Fee, Trading Fee Fee Keep as positive number, separate currency column Fee Asset, Fee Currency Fee Currency USDT, BNB, BTC, etc. Order ID, Trade ID, Deal ID Order ID/Trade ID Don’t delete, it helps dedupe merged fills Realized PnL, PnL Realized PnL Futures only, often in settlement currency Funding, Funding Fee Funding Can be income or expense, depends on sign Contract, Size, Position Contract/Instrument Needed if futures is inverse or coin-margined Now the “cleaning” part, where most bad imports are born: UTC vs local time: If spot is UTC and futures is local time, your merges will look wrong. Pick one timezone, convert the other (and keep a copy of originals). Comma decimal separators: Some exports use 1,234.56, others use 1.234,56. Import tools usually break on mixed formats. Normalize before upload. Merged fills and duplicates: Exchanges can export both “order” rows and “trade” rows. Prefer trades (fills). Keep IDs so you can remove duplicates instead of guessing. Negative quantities: Many tax tools accept sells as negative base amount, some want a side column instead. Don’t mix styles inside one file. Futures special rows: Funding and realized PnL are not “buy/sell spot trades”. If your tax software can’t ingest them as-is, keep them as separate transaction types (Funding, Fee, PnL) rather than forcing them into spot columns. If you’re using a tool that requires ordered uploads, the general rule is old to new. Cryptact mentions this clearly in its help docs, see upload exchange files from the oldest date. Privacy and security before you share files CSV exports can include account IDs, internal wallet addresses, and sometimes partial identifiers that you don’t want floating around. Keep these habits: Remove API keys from any notes you attach (API keys should never be inside a tax file anyway). Redact account UID, referral codes, and internal transfer IDs if your accountant doesn’t need them. Share using a secure method (encrypted drive link or your accountant’s portal), not email attachments if you can avoid it. Final checklist (do this once, save yourself the back-and-forth) You exported spot fills, not only open orders. You exported futures trades plus realized PnL plus funding (and interest if it exists). Timezone is consistent across every file. Fees have both fee amount and fee currency. Duplicates removed, IDs preserved. File opens cleanly in a spreadsheet without shifted columns. When your file passes that checklist, the tax work becomes boring again (which is the best outcome). The main idea is simple: export everything that changes value, then make the rows speak one language before you import.