help wanted: mining costs about bittytax

[nanonano]

@chamsters thanks for the kind words :) be sure to spread the word if you know anyone else who would find BittyTax useful?!

Re: Crypto.com, do they provide a CSV export? If you are happy to share an example data file (email me privately), I can look at integrating it?

[chamsters]

@chamsters thanks for the kind words :) be sure to spread the word if you know anyone else who would find BittyTax useful?!

Re: Crypto.com, do they provide a CSV export? If you are happy to share an example data file (email me privately), I can look at integrating it?

I've just emailed you a sample CSV export! Will likely need a few iterations as there are a lot of transaction types there, but presumably easily mapped to one of your transaction types. Happy to be a guinea pig for any testing purposes with actual data files and sharing errors / new mappings as required!

[nanonano]

Hi @chamsters, you will need to work out your profit and loss with income less expenditure in your own spreadsheet. You can take the income figures for the year from the BittyTax report, and then include your expenses for electricity, etc.

This article has some useful info https://bettingbitcoin.io/cryptocurrency-uk-tax-treatments/#mining

If you need more help you're best to speak to an accountant.

[chamsters]

Hi @chamsters, you will need to work out your profit and loss with income less expenditure in your own spreadsheet. You can take the income figures for the year from the BittyTax report, and then include your expenses for electricity, etc.

This article has some useful info https://bettingbitcoin.io/cryptocurrency-uk-tax-treatments/#mining

If you need more help you're best to speak to an accountant.

Got it - thank you 👍

This tool really is incredible, thank you for building it! I hope you soon integrate crypto.com into the tool too! I was able to manually categorise the extract, but would really be less of a headache having it built in.

[nanonano]

@chamsters got your email, thanks for the export!

[nanonano]

@chamsters please see #30, date format was wrong in Crypto.com parser, please check your data.