This article explains how to import Exchange-Native Trading Bots Data (e.g. Pionex, BingX and others) into Blockpit meaning bot products that are directly offered and executed by exchanges (e.g. Grid Bots, DCA Bots, Futures Bots, etc.). It does not cover external third-party trading bots that connect to exchanges via API as these may already be included in the respective API/CSV import scope.

Exchange-Native Trading Bots can look similar in the exchange UI, but they don’t all produce the same kind of data. Some bots generate normal spot buys and sells, others use borrowed funds (margin), and some trade futures/perpetuals/options and output profit/loss plus funding and fees.

Before importing anything, clarify which type of bot you are dealing with.

Once you identify this structure, importing the data into Blockpit becomes much clearer.

Spot bots (e.g. grid bots, DCA strategies, rebalancing bots) execute regular buy and sell transactions on the spot market. From a reporting perspective, nothing special happens, the bot simply generates normal spot trades.

Used Blockpit Label:

If your exchange provides a full trade history via API or CSV, you can import it like any other exchange activity. No PnL calculation is required because spot taxation is based on individual buy and sell events.

Spot margin bots combine spot trades with borrowed funds. The activity usually consists of:

In Blockpit, this must be reflected correctly.

Used Blockpit Labels:

Margin trading does not require derivative PnL labels. However, missing loan or repayment entries are one of the most common reasons for balance mismatches.

Derivatives bots trade contracts instead of spot assets. Typical UI elements include:

Tax reporting for these bots is based on realized profit or loss.

Used Blockpit Labels:

Spot trade entries alone are not sufficient.

Whenever possible, use API or official CSV exports.

For spot bots, the trade history is usually enough.
​For margin bots, ensure that trade history and margin ledger (borrow/repay) are included.
​For derivatives bots, check that realized PnL and funding/fee data are available.

Some exchanges split the data across multiple exports, for example or even provide the data via a sub-account API key.

Make sure all relevant files are included before uploading.

If the data already contains full underlying activity, you can upload it directly or migrate it into the Blockpit Excel Template.

📌 Blockpit Excel Template – Manual Import Guide
📌 How to Import PnL Manually
📌 Understanding Transaction Labels in Blockpit

If no suitable export is available, use the official Blockpit Excel Template and enter/migrate your data manually.

Enter each buy and sell individually as:

Include fees as provided.

You must enter:

Include fees as provided. If loan entries are missing, balances will not match.

For derivatives activity, enter:

Some exchanges do not provide granular transaction exports. Instead, they only display a final strategy result such as total profit or net PnL inside the dashboard.

If detailed history is not accessible, you can abstract the result into Blockpit.

Used Blockpit Labels:

In this UI-only scenario, it is generally consistent to assign the result to the tax year in which the bot was closed and the profit or loss was realized.

Mismatched Balances often result from incomplete exports, for example:

Blockpit offers an auto-balancing feature that can generate corrective transactions if historical data is missing. These transactions should always be reviewed carefully and adjusted if necessary (for example relabeled as Non-Taxable Deposits if they correct missing starting balances).

In many cases, manually completing the missing history (loans, funding, transfers) provides the most accurate and audit-proof result.