Skip to main content

Updates on old Connections (October 6th, 2025)

Descubre qué hicimos y por qué

Updated over a week ago

ℹ️ Connection involved in the update

The following procedure impacts only Connections created before 06 October 2025. Connections created from 06 October 2025 and onwards are not impacted by this update.

On October 6, 2025, we implemented a significant update to user connections in CryptoBooks accounts to resolve longstanding balance issues.

Previously, when an outgoing transaction created a negative balance, you would receive a yellow warning notification indicating the missing amount would be considered at zero cost basis. This required either manual intervention or acceptance of adjusted capital gains. Our new update provides an automated solution that addresses these issues at their source.

This update achieves two main goals:

  1. Improves Portfolio analysis accuracy by automatically fixing negative balances that previously caused false readings in stock values

  2. Enhances Tax Strategy Tools by ensuring all Connections maintain accurate balances, leading to more reliable tax calculations


What did we do?

Our approach was comprehensive:

  1. Implemented an intelligent "Negative Balances" detection system that identifies discrepancies across all Connections and Tokens

  2. Developed a sophisticated "Differences" correction algorithm that automatically resolves balance issues while preserving transaction integrity

These processes were executed by our advanced CryptoBooks AI, ensuring consistent application across all accounts while maintaining your transaction history intact.


What to do next?

If you want to learn more about these fixes and how they were performed, you can:

  • check this article to understand the logic behind the Negative Balance Fix

  • check this article to understand the logic behind the Differences Fix

  • please reach out to customer.support@cryptobooks.tax if you need more information on this topic, or would like to request the deletion of transactions created with this automatic update

Did this answer your question?