How to Import Binance Spot Trading History into CoinTracking Without API

If you're managing crypto trades on Binance and need accurate tax reporting, you've probably run into import challenges. Many traders face frustrating roadblocks when trying to sync their transaction data with portfolio tracking tools—especially when they prefer not to use API connections for security reasons.

Let's walk through what's currently working (and what isn't) when importing Binance Spot trading history manually, plus some workarounds for common data errors.

The Problem: XLSX Files No Longer Accepted

For months, crypto traders could download their Binance Spot transaction history as Excel files and import them smoothly using the Legacy CSV Import feature. The process was straightforward:

1. Navigate to Orders → Spot Order → Trade History tab

2. Click "Export Trade History" in the upper right

3. Select "Within 6 Months" with your desired time range

4. Choose "Excel" format (only PDF and Excel were available)

5. Import the resulting XLSX file directly

This method worked flawlessly until recently. Now, attempting to upload an XLSX file triggers an error message: "*.xlsx is not allowed. Allowed extensions: csv, txt."

The file format from Binance hasn't changed—but the import restrictions have.

The Current Workaround (With Limitations)

There's an alternative export method that technically works, but it comes with significant drawbacks:

The "All Time" Export Method:

1. Go to Orders → Spot Order → Trade History

2. Click "Export Trade History"

3. Select "All Time" as the time period

4. Click "Generate" (limited to 5 exports per month)

5. Download the ZIP file containing CSV data

While these CSV files can be imported, they introduce data interpretation errors that could mess up your tax calculations. 👉 Track your crypto transactions accurately with professional portfolio management tools to avoid costly mistakes during tax season.

Specific Import Errors to Watch For

The CSV import method consistently mangles coin names in the fee column. Here are real examples from user reports:

Example 1: Wormhole (W) Transaction

Binance CSV line:

2024-04-04 16:43:04,"WUSDT","BUY","1.203","24.9W","29.9547USDT","0.0249W"

Imported result:

• Coin name correctly converted from "W" to "W2"

• Fee column error: Shows "0.02000000 49W" instead of proper W2 designation

• Decimal places incorrectly merged into the coin name

Example 2: CYBER Token

Binance CSV line:

2024-03-10 07:24:11,"CYBERUSDT","BUY","11.341","1.65CYBER","18.71265USDT","0.00165CYBER"

Imported result:

• Fee shows as "0.00165000 YBER" (first letter dropped)

• Creates duplicate entries that don't match previously imported XLSX data

Other affected altcoins include API3, MANTA, and MATIC. The first character gets stripped from fee currency names, creating mismatched records across your portfolio history.

Why This Matters for Tax Reporting

These seemingly small errors compound over time. When fee currencies are mislabeled:

• Your cost basis calculations become inaccurate

• Duplicate entries inflate your transaction count

• Tax reports show discrepancies between different import periods

• Reconciling with exchange records becomes nearly impossible

For anyone serious about crypto tax compliance, data accuracy isn't optional—it's essential. 👉 Automate your crypto tax reporting with dedicated tracking solutions that handle complex transaction histories across multiple exchanges.

What's Being Done

The development team has acknowledged these issues. Since Legacy Importers are no longer being updated, the recommendation is to either:

• Switch to newer file format importers

• Submit a support ticket with original files and screenshots showing where you obtained the data

For users experiencing these problems, contacting support directly with sample files helps prioritize fixes.

Temporary Solutions While Waiting for Fixes

Until the import issues are resolved, consider these approaches:

Manual verification: Cross-reference imported transactions against your Binance records, paying special attention to fee calculations for the affected altcoins.

Batch imports carefully: Since the "All Time" export is limited to 5 times monthly, plan your imports strategically rather than exporting repeatedly.

Document discrepancies: Keep notes on which transactions show errors so you can correct them later when proper import functionality is restored.

Use shorter time periods: Smaller data sets are easier to verify manually and reduce the impact of any single import error.

The good news is that Binance's export format itself hasn't changed—meaning once the import compatibility is fixed, historical data should process correctly.

Managing crypto portfolios across multiple exchanges and hundreds of transactions isn't simple, but having reliable tools makes tax season significantly less stressful. The key is catching data errors early before they cascade through your entire transaction history.