Skip to main content

Automatic Merging to Label "Transfer"

Updated over a month ago

Auto-Merging Feature (full-automatic linking of transactions to Transfers)

Auto Merging enables the linking of two related transactions (withdrawal + deposit) between two integrations to Transfers. The detection of these so-called Transfers is fully automated using certain merging parameters, which are described in more detail in this article.

If you prefer to deactivate the feature, you can now opt-out. The opt-out can be found in the Account Settings and allows you to switch to purely manual merging.

Transfer of acquisition costs between integrations via label "Transfer"

The transfer of acquisition costs is particularly important for the later calculation of your actual profits or losses. The starting point for the transfer of acquisition costs between two integrations is always a matching Unlabeled Withdrawal from integration B and, as counterpart, a matching Unlabeled Deposit into integration A.

✅ Once you have created all your integrations and uploaded your transactions, transfers between your integrations will be automatically identified by Blockpit.

💡 This is done by matching related Withdrawals and Deposits (Unlabeled Transactions) based on certain rules (parameters) and linking them directly to the Transfers. This is called "merging", because two transactions become one.


Rules for Auto-Merging to Label "Transfer"

The algorithm for automatic merging to Transfers works in a simplified way as follows:

  1. Ensuring that incoming and outgoing transactions are not in the same integration

  2. Matching of transaction IDs (transaction hash)

  3. Matching of asset IDs

  4. Check if timestamp of incoming transaction is ≥ timestamp of outgoing transaction

  5. Checking whether (timestamp of incoming transaction - timestamp of outgoing transaction) is ≤ (2 hours)

  6. Check whether incoming asset quantity ≤ outgoing asset quantity

  7. Check whether (incoming asset quantity / outgoing asset quantity) ≥ 0.9

  8. Merge to Transfer if all conditions from step 1-7 apply and at a maximum only one incoming and one outgoing transaction was found

  9. If all conditions from step 1-7 apply and multiple incoming and outgoing transactions are found (duplicates), those transfers whose timestamps are closest are merged to Transfer first

All steps are gone through after each import of a new transaction.

So, the Auto-Merging of transactions happens...

  • ...after each Exchange API import

  • ...after each Exchange CSV import

  • ...after each Wallet import

  • ...after each Excel import

  • ...after each manual creation of an incoming/outgoing transaction via the user interface

Auto-Merging does NOT work for transactions that have previously been split using “split transaction” feature.

Did this answer your question?