Internal transfers to Nexo are not identified correctly

[RAS-2112]

Summary:
Nexo uses its own transaction ID in the exportable transactions CSV file that can be imported into Accointing. This ID is in the format NXTxxxxxxxxxx. When importing Nexo CSV files, this ID is used for the transaction ID in Accointing, which means that Accointing does not recognise internal transfers from other wallets correctly, as these usually use the transaction hash.

Desired Behaviour:
Accointing should suggest internal transfer for review if other rules listed here Internal Transactions - The Hub: Crypto and Bitcoin Tax Blog | ACCOINTING.com are satisfied, even if the transaction ID does not match.

User Impact:
User must manually change the transaction ID for the Nexo deposit, so the internal transfer is recognised.

Tested With
Binance account connected with API and Nexo transactions CSV imported manually.

[RAS-2112]

Just to add, manually editing transaction ID’s is less than ideal, as this makes it much harder to match the transaction between Accointing and Nexo. Maybe Accointing could add a new optional field for internal ID’s in these situations so the transaction hash can be kept separate from the vendor assigned ID?

[Matt]

We are aware of a bug with the Nexo CSV import error in our system and are working to fix it. Once that is fixed, I will reply here and ask if you are still experiencing this issue.

Also, consider our article on internals

Managing Your Internal Transactions

[RAS-2112]

Hi Matt, thanks for your quick response.

Glad to hear that you’re aware of the issue and are working on a fix