Below is a list of the reasons that could cause an unmatched trade. Read through them, and if you answer yes to a question, expand it, so you can see how to correct that specific reason. Your account may have unmatched trades caused by multiple reasons, so work your way through the list until all unmatched trades in your account are fixed.
Most common reasons
Did you receive/purchase crypto in a previous year?
If you received/bought crypto in a previous tax year, the software will not automatically add it to the current tax year when you import your current year trades. You will need to change the tax year in the top left to the corresponding tax year of when you received/bought the crypto, and import the trades for that tax year. Once you have done that, and calculated the trades for that year, the software will automatically add the closing positions from that year to the Opening tab of the following year.
For example if you received 4 BTC in 2015, and sold 2 of those BTC this year, you would need to:
change the tax year in the top left to 2015, enter the 4 BTC there, and then calculate 2015, and each following tax year, so the software can automatically place the 4 BTC in the Opening tab of the current tax year.
You can enter the data manually to the current year's Opening Tab, but we would advise against relying on this method.
Did you forget to add every single trade you made this year?
Bitcoin.tax can not automatically find missing information for you. If you do not tell the software about a trade you made, then it has no idea the trade happened.
For example if you purchased 3 LTC from exchange A and immediately transferred those 3 LTC to exchange B, because that is where you do most of your trading. Then later in the year you sold those 3 LTC through exchange B, and imported all your trades from Exchange B in to Bitcoin.tax, because Bitcoin.tax has an integration with exchange B, and all of your other trades happened in exchange B, you would still see an unmatched trades for those 3 LTC, because you did not tell the software where you originally purchased them from.
You need to make sure you import all your crypto trades, even if it is from exchanges that you used once earlier in the year, and forgot about.
Did you receive any crypto as payment or as a gift?
If you received crypto as a payment in any way, or as a gift, you need to add that information to the Income tab. That way if you ever sell/spend that crypto, the software will know where it originally came from, and will be able to match it with the sell/spend trade.
Was some of your trade information imported wrong?
There are times where a CSV file has incorrect/out of order information, or an API request does not import the information correctly. To figure out if this is the reason for your unmatched trades, you will need to compare the information in Bitcoin.tax with the information in your exchanges.
You can then try reimporting your information, or you can manually edit/delete the trades to fix the wrong information.
The most common situation is when a sell of crypto gets placed before the buy of that crypto. It is usually easy to find this in Bitcoin.tax because there will be a sell of a specific number of crypto, and shortly after there will be a buy for that exact same amount of crypto. For example
2-3-2018 1200 SELL 1.002 BTC
2-3-2018 1201 BUY 1.002 BTC
That specific example would be a great one to edit, and simply place the buy before the sell.
Less common reasons
Did you receive forked income this year?
If you received coins from a crypto fork (such as the BTC/BCH fork), you'll need to enter them into your Income Tab. The date of the entry should be the date that you acquired the new coins.
Keep in mind, not all crypto forks create new coins. So for those type of forks, you would not need to enter anything.
Did you use Binance to convert Dust to BNB?
If you converted dust (a tiny amount of crypto) to BNB on Binance, you'll need to import this data into your Bitcoin.tax Trading Tab. You can do this by manually importing the transactions, or by creating and importing a standard CSV.
You can treat the Dust to BNB conversions as trades. For example, if you've converted .599 TRX to .00253543 BNB, you can add it as a sale of TRX for BNB.
Did crypto you owned, split, or do a token swap?
When recording a split you will want to add the new crypto to the Income tab, and can usually use the date of the split as the date you acquired the token, although this may vary per split. You can either set your own cost basis, or allow us to pull the price from historical data by leaving the value blank.
Swaps can currently be entered by following the instructions outlined in the VEN/VET swap article. Keep in mind, the instructions are specific to VEN/VET in terms of ratios and dates - please be sure to change these according to the swapped coin you are entering.
Did you enter data in your Spending tab?
If there is data in your Spending tab, it may have been mis-categorized, and you will need to manually fix the category of the trade.
For example: When using API import for on the Spending Tab for Coinbase, the import will pick up transfers and categorize them as Spends. Transfers need to be categorized as transfers, or they will potentially cause unmatched trades.
Did you import any trades using the standard CSV option?
If you have added data from an unsupported exchange, using our standard CSV option, be sure to double check that data, and correct any information that is wrong.
For example: Make sure the price you enter for the "price" column is the price per coin and not the total cost of the trade.