What is a difference in a connection?

The difference on a connection in CryptoBooks indicates a mismatch between the balance (quantity) and the sum of transactions made for that token. Under normal conditions, these two amounts should match; if they do not, an alert notifies the user that action is required to resolve the discrepancy.

This can only happen on automatic connections created via API or public address.

What causes differences?

Automatic connections to wallets (via public addresses) and exchanges (via API keys) depend on the accuracy and completeness of the data provided by these sources.

Each sourc, whether a wallet or an exchange, provides two types of data: the current balance and the list of transactions. When this data is accurate, the sum of all transactions should match the current balance.

However, there are cases where a wallet or exchange may not provide a complete transaction history. In such situations, the current balance does not match the sum of transactions, resulting in a discrepancy that needs to be resolved.

CryptoBooks automatically detects these differences in user connections and notifies users in real time, offering multiple solutions to address the issues and ensuring both the quality of accounting data and the accuracy of generated reports.

Why is it essential to fix differences?

Since the differences are caused by missing transactions, if not properly addressed, they can impact the accounting for the following reasons:

Tax accuracy
If the data is incorrect, the calculation of taxes owed or deductible losses will also be wrong, potentially leading to legal issues or penalties.
Incomplete or misleading reports
A report generated from incorrect data will not accurately reflect your financial and tax situation, compromising any analysis or declarations you intend to make.
Inability to generate certain reports
Some types of reports (e.g., tax revaluation, capital gains calculations) may not be available until the data is fully aligned.

How to fix differences

ℹ️ Important notice

Before proceeding to correct differences, users need to solve missing prices and negative balance first.

Click here to go to the missing prices resolution guide.

Click here to go to the negative balance resolution guide.

Choose your preferred resolution method

When starting the procedure to solve errors (missing prices, negative balance or differences), the software asks users to select which method to use.

By selecting Fix all automatically (fastest), the software will handle all the necessary fix, applying all the correction without any action required by the user.

If you would like to know more about the criteria used by the AI tool to solve differences, please read this article.

By selecting Manage manually, users can solve errors by applying manual fixes according to the following instructions (keep reading this guide).

The image below shows the four possible steps available in the guided procedure to fix differences. You will see the checked progression while you manage each step.

Step 1 - Upload a CSV (optional)

This step allows users to import the CSV file downloaded from the exchange in its native format, to retrieve missing transactions and solve the differences.

This option is only supported for some exchanges, in all the other cases it won't be suggested by the guided procedure.

click in the dedicated field to upload your CSV file, then click on xxxxxx
Otherwise click on Skip this step to move to the next one.
in the new modal confirm your choice by clicking on Proceed anyway

Step 2 - Fix spam tokens balance

This step allows users to solve differences for all the tokens labeled as spam. Given these tokens have no value, the software can automatically correct them adding fix transactions that won't have any impact on the gain/loss calculation.

click on the Fix all Spam balances button
confirm your choice by clicking on the Yes, proceed button

Step 3 - Fix rounding errors

This step allows users to handle rounding adjustments for tokens that show differences of just a few cents in fiat value.

click on the Apply roundings to all button to proceed, otherwise click on Skip this step to move to the next one.
in the new modal confirm your choice by clicking on Yes, proceed

Step 4 - Fix remaining token balances

In the final stesp of the guided procedure users can handle all the tokens that haven't been managed in the previous steps. Users have the options to solve manually by uploading a CSV file, or single manual transactions. Alternatively, they can rely on the automatic fix suggested by the software.

by clicking on View suggested fixes, users will be shown the fix transactions the software will add in order to solve differences
by clicking on Manual transaction, users will be able to add a single transaction at the time. To learn how to add a manual transaction read this guide.
by clicking on CSV file upload, users can add transactions in bulk instead of doing it one by one. Learn how to compile the CSV file in our format by reading the instructions here.

Cautious logic used for the automatic fix transactions

When you choose to resolve differences automatically, allowing the software to add the necessary placeholder transactions, these are inserted according to the logic described below.

Missing Deposit (negative amount mismatch):

In this case, a deposit transaction will be inserted with the following details:

Amount equal to the mismatch detected on the token
Acquisition price set to 0 (the least favorable condition for the user, but it safeguards against potential future audits)
Date matching the first transaction of that token on the given source (exchange or wallet)