Blockpit highlights Tips related to your asset balance and your transactions.
Tips provide information about mismatched asset balances in your Dashboard and insufficient transaction details in your Transactions list. These are usually related to missing transaction histories, undefined transaction labels or missing asset values.
If you resolve tips, it will have an impact on your tax report.
Make sure to always synchronize all your integrations first using "Sync all" and then start a recalculation of your transaction data using "Recalculate" before reviewing tips.
Use the available Filter Options in your Dashboard or in your Transactions list to display all tips:
Dashbaord:
Transactions:
> How to use Filter Options?
Before you work on particular Tips try the following steps:
Step 1: Initially, focus on single integrations in your Dashboard and always read the import scopes descriptions of our automatic Exchange- and Wallet Integrations as guidelines when trying to resolve tips!
Step 2: Create a temporary secondary integration to compare your new and old integration. Then delete the integration that you do not want to keep.
Step 3 (optional): Re-synchronize missing/incorrectly imported transactions, taking all precuationary measures into account (please read to avoid currupting existing transaction histories and duplicate transactions).
Step 4: If your problem still persists, please follow the continuing instructions below.
How to solve particular Tips?
Select the corresponding Tip from the following list for further guidance:
-
Transactions that have not yet been labeled are displayed as "Unlabeled":
Labels are used to classify transactions.
Exchange and Wallet Integrations already identify many Labels such as Trade, Transfer, Staking, Lending, Airdrop and many more fully automatically.
In some cases, however, no unique label can be assigned to your transaction. Such transactions will be displayed as "Unlabeled Deposit" (Incoming) or "Unlabeled Withdrawal" (Outgoing) and will appear as such in your transaction list.
Please also use additional articles for the correct Labeling or merging of Unlabeled Transactions:
> Basics on Labeling and Merging of Transactions
> Automatic & manual Merging to Label "Transfer"The most common causes of the "Unlabeled" Transactions are Fiat Bank Deposits/Withdrawals. These can be labeled as "Non-Taxable".
> Transaction-Label "Non-Taxable"
Other common causes are not yet directly determinable reward inflows (Airdrop, Bounty, Lending, Mining, etc.), incompletely recognized Trades/Transfers, or inflows/outflows from undetermined smart contracts (fallbacks) e.g. free NFT Mints (fallback_claim).
If your Integration is not yet supported, and you want to link/merge a Transfer to an existing integration, you can first create a Manual Integration (e.g. "IOTA Wallet Manual") and then edit the existing Unlabaled Transaction into a Transfer.
> How do I create a trade or transfer if only one side of the transaction exists?
Example: Labeling of multiple Fiat Bank Deposits to Non-Taxable
-
The Tip "Mismatched Balance" indicates that there are differences between the balances reported by the data source and the calculated ones based on your transactions in Blockpit. This may be caused by missing or incorrect transactions received via APIs.
> What is the difference between Synced Balance and Calculated Balance?
Important
The Synced Balance of every automatic Exchange or Wallet Integration will always be registered/imported a bit earlier than your latest transactions. Therefore, always wait until your most recent transactions have been imported.
Please also note that the Synced Balance itself can sometimes be the cause of a Mismatched Balance (E.g. Bybit Funding Account). Therefor, make sure to use the import scopes descriptions of our automatic Exchange- and Wallet Integrations as guidelines.
Before you fix "Mismatched Balance" Tips, you must always fix "Missing History" Tip first.Consider the following steps:
-
-
Make sure you have imported all transactions from your sources (wallets, exchanges, services) across all years into Blockpit.
-
Check your transaction history (imported via API, Chain or CSV) and identify any missing transactions by comparison. You can add missing transactions manually or by migrating your CSV data into our Excel template.
If there are any "Missing History" Tips in your transaction list, these should be fixed first.Hint: Always use the import scopes descriptions of our automatic Exchange- and Wallet Integrations as guidelines!
-
If you could not find the cause of the Mismatched Balance you can manually add a matching transaction with the Non-Taxable label at a suitable time or let Blockpit reconcile the mismatch for you.
This feature can be used to reconcile either single balances or multiple balances at once.
We will then create Auto-Balancing deposits or withdrawals on the current day, depending on the difference
> More information about the Label "Auto-Balancing"
> More information about the Blockpit Dashboard in full detail
-
-
-
The Tip "Missing History" indicates that assets have been withdrawn which were not present according to your transaction list and calculated balance.
In such cases, for example, a Trade or other outflow Labels reveals that the Calculated Balance of the asset in question has fallen below 0. Depending on the Transaction Label of this outflow, in the case of a sale of missing assets due to unknown acquisition costs, the full disposal value of the missing asset is imputed as a gain and thus potentially interpreted unfavorably from a tax point of view.
Tips are only displayed if the transaction value is above 1€/$.
To solve this Tip, you need to check if all Transactions of the affected Asset in your Integration have actually been imported correctly or if you have manual Transaction duplicates.
Use the Ledger Mode feature to help you compare your transaction histories and balances.-
-
Examine the transaction history of your Exchange or Wallet and focus your search on the asset that triggered the Tip. Start with the oldest Tip per affected asset, as this usually triggers all other subsequent Tips.
-
Pay attention to the Integration Type that is affected (Manual Integration, Exchange Integration, Wallet Integration) and use all available filter options in your transaction history to compare your Blockpit transactions.
Hint: Always use the import scopes descriptions of our automatic Exchange- and Wallet Integrations as guidelines!
-
Once you have identified missing, duplicate, or incorrect transactions, you can fix them as follows, depending on the type of integration:
Exchange & Wallet Integration
Missing transactions can be added manually
Duplicate transactions can be excluded manually
Incomplete or incorrect can be edited manually or reported to our support.Manual Integration
Missing transactions must be added manually.
Double transactions must be deleted manually.
Incomplete or incorrect transactions must be edited manually.
> You can also try to re-synchronize missing/incorrectly imported transactions by taking all precuationary measures into account. (Please read to avoid currupting existing transaction histories and duplicate transactions).
> How to report "Missing Assets" to our support-team? What evidence base does our support-team need to implement missing, duplicate, or incorrectly imported Exchange or Wallet products (transactions)
- If you could not find the cause of the Missing History, you can manually add a matching transaction with the Non-Taxable label at a suitable time or let Blockpit reconcile the data for you. Based on the missing amount, we will then create an Auto-Balancing deposit just before the corresponding Tip/Transaction.
To do this, simply click on the Tip indicator on the transaction and then Reconcile History.
The Auto-Balancing transaction created in this way can then be found and recalled again using the Label: Auto-Balancing (incoming) filter.
> More information about the Label "Auto-Balancing"
-
Examine the transaction history of your Exchange or Wallet and focus your search on the asset that triggered the Tip. Start with the oldest Tip per affected asset, as this usually triggers all other subsequent Tips.
-
-
If no fiat value can be determined for your Asset at the time of the transaction, Asset Values can be added to affected transactions by the user to resolve the Tip.
Use the Filter Option: Tip > Missing Value in the transaction list to find the corresponding transaction(s). Now click on the three dots as shown in the image below and select Update Asset Value.
In the follow-up menu (sidebar) you can now enter either the Price per Unit (currency rate of your asset at the time of the transaction) or the Total Value of the transaction. Confirm your input with the "Save Changes" button.
The Asset Value should always reflect the market price at the time of the transaction. Blockpit uses Coinmarketcap, Coingecko or other available price data sources. If asset values are missing, you can use other price aggregators, in the best case, get values directly from the transaction history of your exchange.If the Tip is not resolved, Blockpit automatically assumes 0 Euro as asset value. (Fallback)
Merged Deposits and Withdrawals (Transfers, Trades) or labeled Airdrops do not require currency rates.
Merging transactions or labeling them as Airdrops thus solves the problem of a Missing Fiat Values.
If transactions (Trades) are settled directly against fiat or other assets whose price data are known, no additional price source/rate is required due to the direct valuation. -
This Tip refers to incorrectly linked transactions. Please unlink all affected transactions and link them manually afterward.
Pay special attention to the timestamps of your transactions to avoid re-linking loops.
If the time stamps of several affected Unlabaled Deposits and Unlabaled Withdrawals are identical to the second, they should be manually reprocessed so that a unique or unmistakable chronological order of your transactions is created. -
The Tip is triggered if the hard fork base asset within the integration is missing at the actual hard fork time/date.
Causes for missing assets are mostly missing, double or incorrect transactions for the affected base asset. To solve the Tip please follow the steps in "Missing History" above. -
The asset did not have a hard fork at the specified time or the hard fork has not yet been registered in our database.
Please note that your hard fork transaction must be created after the official hard fork date.
If the Tip still occurs, please contact our support and provide all necessary information about this hard fork for our support team so that we can analyze and fix the Tip for you as fast as possible. -
This Tip refers to an unsupported label regarding the regulatory framework of your tax country, which means that the label you would like to apply is not available for the asset types involved in the transaction. Therefore, the label should be changed.
-
Undefined Tip can occur as a result of faulty transaction data calculations on blockpit side. Therefore, you may not be able to fix this Tip yourself.
Please contact our support team and provide all necessary information so that we can analyze and fix the Tip for you as fast as possible.