OKAY this is looking promising!. One thing I note straight away though is that the CSV files have all the data in one column rather than separated into columns so I will need to go through and clean it up before checking
Ok can see collums in google spread sheets.
Looks like we are unable to export a custom date range? In UK taxes run from 5 April - 5 April
In the raw and Koinly reports we cant see the send and receive wallets?
This is a common frustration with excel when opening CSV. It tends to handle CSV better when you create a new file and import the csv from the data tab.
The underlying reason for this is the inconsistency in delimiters in the CSV file format, sometimes it’s ; and other times , or something else altogether.
In exports date range for UK is 5 April - 5 April.
But sync was limited to prev year, now there is no limit, please try “Resync all” and then export again(select year 2025 for 2025/26).
If you add an address - it will appear in transactions. Are you sure you need it, if that is not your address? What is the use case?
AI says that’s not necessary for the tax authority.
So in the Uk at least it is needed as part of record keeping, we are supposed to know where transactions have come from.Also It helps work out what the transaction are actually for when there is some doubt.
Also its proof of sending between wallets you own which is not a taxable event
Nice tool, would be useful to be able to mark a specific or all transactions from an address like for instance CEX address as not income. That should significantly improve reporting accuracy.
Would be nice to have an option to exclude certain wallets form the export. For example a wallet my be for an app you are creating and need the transactions to be separately accounted for.
