Quick Answer: If a tax-software import does not reflect your margin trading result, do not add a guessed profit or loss to make the total match. Confirm the export's period, account scope, and included transaction types; obtain the relevant margin or contract records separately where needed; then compare transactions, fees, funding, transfers, and realized PnL in a dated reconciliation sheet. Phemex's Help Center has warned that a CSV import may omit Margin PnL, but export features can change. Verify the current files and have a qualified tax professional decide how the reconciled records should be reported in your jurisdiction.
Why can a tax import and trading history disagree?
A tax-software dashboard is a calculation based on imported records and its own classification rules. It is not a direct copy of every balance and result displayed inside a trading account. If a source file omits a transaction type, uses a different date range, or is imported twice, the software's total can differ from the platform's account history even when neither system has a simple arithmetic error.
Phemex's basic trade-history guide explains how to download a CSV and import it into a partner tool. The account-statement Help Center page adds a specific caution that the Phemex CSV import does not include Margin PnL data in the workflow it describes and points readers to a separate report. Because that help article is older than some current product pages, it should prompt a check of today's export rather than an unqualified claim that every present-day CSV always has the same gap.
There can be several records for one economic position. A trade execution, fee, funding payment, collateral transfer, and realized result may appear in different files or account sections. Import software may label them differently. The purpose of reconciliation is to identify what happened and how it is represented, before asking a tax engine to calculate a jurisdiction-specific result.
Step 1: define the period and accounts
Write down the tax period you need to review, its timezone, and the accounts involved. Include sub-accounts if they traded. An export that starts one day late or excludes a sub-account can create a difference that looks like a missing trade. A position opened before the period and closed inside it may also require earlier acquisition or opening records for the software's calculation.
Open the Phemex Tax Reporting page and inspect the current export options. The page describes downloading transaction history including main and sub-accounts and then selecting a tax partner. Do not assume the default period matches your filing year. Save the export request settings and file name alongside the generated file so you can reproduce the import if a question arises later.
The file's date and creation time matter. If you export before a late adjustment, correction, or transaction has posted, the report may not match a later screen. Compare like with like: the same period, account set, and as-of time. If an import was performed weeks ago, rerun it using a documented fresh export only after checking that doing so will not duplicate existing records in the software.
Step 2: inventory the source records
List the categories you expect to see: spot trades, margin trades if applicable, contract trades, deposits, withdrawals, internal transfers, funding payments, interest or borrowing charges, trading fees, and realized PnL. You may not have all categories. The point is to know which ones could affect the discrepancy rather than searching only for a single missing row.
The Help Center's report instructions describe separate paths for Contract Trade Accounts, Spot Account, Spot Trade History, Investment Account, and withdrawals. The interface and report names may have changed, so use the current account page as the operational source. Export each relevant category for the same date range. Keep original files unchanged and work from copies for sorting and notes.
Distinguish “Margin PnL” as a label in a product report from a general reference to any leveraged trading. A margin account, a futures account, and an external tax tool may use different terminology. A user should inspect the actual source field and account type before claiming a particular futures result is missing because a Help Center note mentions Margin PnL. If the missing record concerns a different product, the appropriate report may also differ.
Step 3: compare records, not headline totals
Begin with a transaction-level match. For each source record, capture its timestamp, account, instrument, type, asset, amount, fee, and unique identifier if available. Then locate the corresponding imported entry. A spreadsheet can help, but keep amounts in their native asset and record any valuation currency separately. A fee of 2 USDT and a transfer of 0.01 BTC should not be collapsed into a single number without a defined conversion method.
A practical reconciliation table has these columns: source file, source row or transaction ID, timestamp and timezone, account, transaction type, asset, signed amount, fee, imported-software ID, classification, and status. Status can be “matched,” “missing from import,” “duplicate,” or “needs review.” This is a working checklist, not a substitute for the final tax calculation.
Consider a hypothetical case. A user closes a margin position and sees a realized result in an account report, but the imported tax file shows only two trade executions and a collateral transfer. The first question is whether the result is represented through those executions under the software's method or whether a separate PnL event is genuinely absent. Adding the visible PnL as a new transaction without checking could double count it. The example illustrates the review logic; it does not assert that any particular Phemex report uses that structure for every margin product.
Step 4: separate transfers from disposals and costs
Moving collateral between a user's own accounts can change balances without being an external purchase or sale. An import tool that treats the outgoing side as an unexplained withdrawal and the incoming side as new income may distort its totals. Match both sides using time, amount, asset, and account identifiers. If one side is missing, investigate the transfer before assigning a tax category.
Fees and funding are separate from the movement of collateral. They can explain why a platform balance changed more than a simple entry-to-exit price calculation suggests. Export the records and reconcile them, but do not claim a uniform tax treatment. Jurisdictions differ, and the treatment can depend on the product and circumstances. The task of this article is to preserve accurate evidence for that decision.
Unrealized PnL is another source of confusion. A dashboard may show an open position's current estimate, while a tax tool may focus on realized transactions or use another reporting rule. Compare the status of the position and the meaning of each figure. Do not create a taxable event from a mark-to-market display unless the applicable rules and professional advice require that treatment.
Step 5: resolve duplicates and missing entries
If the same source row appears twice in the tax software, check whether you imported overlapping files or used both an automatic connection and a manual CSV. Remove or exclude duplicates according to the tool's documented workflow. Keep a note of what you changed and why. Deleting a row solely to force a target total can conceal a separate missing entry.
If an entry is missing, determine whether it is absent from the Phemex export or present in the export but not accepted by the tax tool. For the first case, obtain the correct account history or contact Phemex support with the account type, period, and report name. For the second, inspect the software's import warnings, field mapping, and supported transaction types. A row rejected because its timestamp or type was not parsed is a different problem from a source report that never contained it.
Where manual entry is necessary, preserve the original source record and link it to the added entry. Label the manual adjustment so a later re-import does not silently duplicate it. The amount, timestamp, asset, and reason should be traceable. A manual correction should solve an identified gap, not be used as a balancing plug.
When is the reconciliation complete?
Completion means material source records have been matched, explained as excluded under a documented rule, or flagged for professional review. The trading-account balance, the sum of imported transactions, and the tax-software gain figure do not have to be identical because they answer different questions. What matters is being able to explain the bridge between them.
Save the original exports, the tax tool's import log, your reconciliation sheet, the source documents for manual adjustments, and the versions or dates of the software used. Record any unresolved item and its potential effect rather than hiding it in a rounded total. If the discrepancy spans large positions, several account types, or multiple jurisdictions, consult a tax professional before filing or amending a return.
The Phemex Tax Reporting page can start the export process. It is a product route, not a promise that one file contains every record needed for every tax situation. The user's own transaction history and applicable local law remain necessary inputs.
FAQ
Does the Phemex CSV always omit Margin PnL?
An older Phemex Help Center workflow warns about a Margin PnL omission and points to a separate report. Product exports can change, so inspect the current file and documentation before making a general claim. The correct next step depends on the account type and report being used.
Should I enter the PnL displayed on my trading screen manually?
Not until you determine whether the imported trades or another report already represent that result. A direct entry without reconciliation may double count it. Preserve source records and follow the tax software's supported adjustment process.
Why do my balances match but my tax-software result does not?
Balances and tax results are different calculations. Transfers, fees, funding, opening positions, missing acquisition data, classification rules, and valuation methods can affect the software's figure even when the account balance is correct.
Can Phemex tell me the tax treatment of a transaction?
Phemex provides account records and a tax-reporting route, while tax treatment depends on the jurisdiction and personal circumstances. A qualified local adviser should resolve classification and filing questions using the reconciled records.
