Dario I have just created a Ticket, thank you.

Hello
Can someone advise why there are at least 3 different values for any crypto asset please.
For example as a test I have input the purchase of 10 ETH on 1st May 2020 at $300 AUD each, $3000 AUD total, no fees.
Then I run the reports and I get the following ETH values???

Closing Position Report from the Tax Report with year ending 30 06 2020
$3271.3

Balance by Exchange with year ending 30 06 2020
$3326.52

Total unrealized and realized Gain/Loss all currencies with year ending 30 06 2020
$3279.32

These multiple price values only serve to further make it more difficult that it already is?
They cannot ALL be right so why is this setup so confusingly incorrectly.
If I were to give all these or similar to my accountant to lodge with the ATO then I would be in trouble with many questions to ask.
I NEED TO BE 100% ACCURATE PLEASE.
Hopefully someone from CT will clear this up for the sake of clarity.
Thank you

Hello Cointracking Support

I do not know what the problem is but I am still waiting for an answer to my Ticket and email re the re importing of the backup files.
You acknowledged receiving the 2 files that I sent to you back on the 18th June saying

I have received the files and will look at them now.
Thank you!

I am still waiting!
I originally raised this problem back in May and now we are in July August??

I recently tried again to re import both the file of the Trade List Full View export and the Trade Table extended view export and both still give the wrong results following the completed re import. The problems are the same as  I have previously outlined to you.


I note that my Ticket that I submitted re this problem is still marked as ON HOLD with no solution forthcoming,,Why is this?

Could you please provide the answer and solution to this problem.

Thank you
Wayne

Hello Cointracking are you there???
This is exactly what I have posted about earlier, NO SUPPORT
What is a reasonable time to wait for a reply?
I am still waiting for the answer to my posts from a month ago and two weeks ago but all I hear is silence.
Plus the Ticket direct to Support at CT has been marked as on hold??
Could you please provide the answers to the queries?
Thank you
Wayne

Dominik
Thank you for responding at last.

I initially sent you an email raising a Ticket re the problems that I was experiencing with trying to re-import the files that I had exported from my Cointracking Practice account.

You asked me to send you my two actual sample files so that you can have a look at them and see what happens when you re-import them into my or your Practice account. I did this several times through the Ticket process and then by email.

So I did what you asked and sent them to you along with an explanation file as well to make it easy and obvious for you. This explanation file showed screenshots of the actual results from exporting the two different files to my laptop and then immediately re-importing them back into Cointracking using the Excel import facility as you advised.

Now the result of my efforts to fully explain to you the problems that I am experiencing re-importing into Cointracking is for you to completely ignore addressing the actual problem that I have raised. Your response here is to not even mention my files or my screenshot explanations which clearly show you the actual incorrect results of the re-importation of both the Trade Table and the Trades List files. 

Instead you attach two "canned" responses of unrelated simple examples of how and what the exported files should show.

I do not have a problem with the EXPORTING of the files from my Practice account. I have sent you these exported files (as you requested) for your inspection BUT I do have a problem with RE-IMPORTING those same files back into Cointracking. This is where the problem lies as is very clearly outlined in my communication and explanatory information that I sent you. Disappointingly this "smoke screen" approach is so very similar to the way that most of my earlier queries have been handled and only serves to obfuscate the truth with very few direct solutions to the actual problem being provided.

With regards to Bitcointalk being a public forum what better place to raise, discuss and solve problems and bugs so that everybody who wants to can access this information now and in the future and draw a benefit from it. This would surely save you a lot of time and effort in having to answer the same repetitive or similar questions posted to you directly via the Cointracking ticket process from many different users where nobody except the person who asks the question potentially benefits from any answers that you may provide.
The underlying strength of the crypto industry itself is that it is built firmly on the foundation of "Open source" and inclusiveness not exclusiveness. This approach welcomes input from interested parties who only add depth and knowledge to the understanding of the project which further serves to refine and improve the underlying asset or product. This is at complete odds to the approach that you are advocating here in carrying out discussions in private behind shuttered Ticketed doorways without the benefit of the broader community being informed collectively.

I want to say something very clearly here and I would appreciate that you do not attempt to twist it around again.
I am on record here and elsewhere having said multiple times that In my opinion Cointracking has the potential to be the leading crypto record keeping software available.
This is providing that the bugs and problems that emerge are rectified in due course. Where Cointracking lacks very badly is in the support that is provided or really is not provided for issues that arise from time to time. And when this support does finally respond it is nearly always in an abstract way that does not address the actual problem at hand. An excellent example of this is your current response to this query of re-importing as I have addressed above. You only respond with a theoretical answer to how something should work on the exporting side but do not take in account the actual evidence placed in front of you that the problem lies in the re-importing side. This is where you then regularly use the "canned" responses to respond. So much so that I have previously asked you politely to stop sending me the same "canned" responses to various questions that I have raised and fully address the problem that has been identified.

So to reiterate for the sake of clarity "I LOVE COINTRACKING.INFO". I am one of it's greatest supporters and only want to see Cointracking improve and evolve on into the future.
So please listen to the genuine feedback and respond meaningfully to it with actual solutions that address the problems in a timely and concise manner and that way we can all benefit.
Cointracking.info can then assume and retain it's preeminent position at the top where it should be.

Thank you
Kind regards
Wayne

PS I have again tried to export and re-import the Trades List Full View and also the Trade Table with the same incorrect results as shown in the files that I have previously sent to you?
I attach those files to the email I have sent you as well as another screenshot explanation for you. Please accept that these problems are actually happening.

Also you advised previously
Attached you will find two sample files exported from the "Enter Coins" page.

The Trade List file that you sent me does not come from the Enter Coins page that I can see??   
Am I correct in my understanding of this or am I missing something ?

Dominik
I do not know what the problem is but I am still waiting for an answer to my ticket and email re the re importing of the backup files.
You acknowledged receiving the 2 files that I sent to you back on the 18th June saying

I have received the files and will look at them now.
Thank you!

I am still waiting!
I originally raised this problem back in May and now we are in July??

I recently tried again to re import both the file of the Trade List Full View export and the Trade Table extended view export and both still give the wrong results following the completed re import. The problems are the same as  I have previously outlined to you.

Do you think that it is possible that you could also answer my question or do you not have the answer to the problem?
Thank you

Dominik


As you are aware I have previously raised the same problem with you that CapitalConsortia has also now raised  quoted above re the re importing of previously exported backup files.
I am still waiting for an answer to my ticket and email re this exact same problem.
You acknowledged receiving the 2 files that I sent to you back on the 18th June saying

I have received the files and will look at them now.
Thank you!

I am still waiting??

I have again today tried to re import both the file of the Trade List Full View export and the Trade Table extended view export and both still give the wrong results following the successful re import. The problems are the same as  I have previously outlined to you.

Do you think that it is possible that you could also answer my question or do you not have the answer to the problem?
Thank you

Ok so I have decided to post this long piece that I wrote up a while back and never posted. I wrote it to crystallize my thoughts and also in the hope that it would help someone in the future that was going through what I was experiencing.
Please note that this is my personal experience and yours may be different so do not take this as the absolute gospel. Do your own research but hopefully this might assist some so here goes
Cointracking my experience with this software.
Guys I have decided to post this here and elsewhere in an effort to assist others who may travel along the same tortuous path as I have been on trying to get the Cointracking.info software to perform accurately and reliably.

Cointracking.info is potentially an absolutely superb program for the crypto investor BUT it has a host of annoying bugs and sometimes inexplicable and ultra annoying problems with how it handles some of the computations. I have learnt the long hard drawn out way that the Cointracking backup support is unbelievably poor, painfully slow and overall not at all very helpful. This sadly lets the Cointracking.info organisation down severely. The one person that I have been dealing with either does not care about servicing the customer who has paid to use the Cointracking program or he does not have a clue about the finer points of the program and its computations.  When he does deem it prudent to reply to one of the many Tickets that I have been forced to raise he just keeps cutting and pasting canned answers that do not really address the particular problem that I have requested assistance on. This is despite the screenshots and supporting files that I have included in the Ticket. I feel that he immediately adopts the attitude that the Cointracking program is infallible and that anyone questioning it does not know what they are talking about. This is the 180* wrong approach right from the start and is destined to end in failure with frustrated people on both sides.

Having said that the most important part of the process is to make sure the data that is loaded into the web based program is 100% correct. You will need to check and double triple check and compare the various results of the individual reports against each other plus any other records that you may have such as notes and or the actual raw data from the exchanges that you may have downloaded. This is so critical to achieving accurate end results in the reports and I cannot stress this enough. The current situation is that Cointracking.info is very time consuming and demands a lot of manual tweaking and checking to ever hope to get accurate results. Hopefully this will improve with time as the many bugs are sorted and rectified, hopefully.

The easiest way to import is by API but Coinspot does not have a working API at the moment so the .csv import has to be used which is nowhere as good or as detailed in the information contained as when using an API.

I describe what I did personally to try and get accurate end results using .csv imports from Coinspot and API imports from Cryptopia. I also had to add in manual transactions to and from offline wallets etc. This is my experience and your experience may differ so please keep this in mind.

So the process goes like this.
Download your OrderHistory.csv from Coinspot and then load it up into the online converter ‘Coinspot to Cointracking converter’. https://cr.ypto.co/cs2ct/ This nifty little tool will save you a lot of heartbreak if you are using Coinspot and converts the raw Coinspot data into a suitable template that Cointracking can recognise and import. (Thanks go to the developer of this tool and the provision of it’s use for others)
(Be sure to follow the instructions on the converter webpage).

Next attempt to import the resultant report into your Cointracking account and you may have a whole lot of problems and warning messages that the transaction dates cannot be recognised and therefore this record will not be fully imported. You will just have to persevere with it as it is too involved to try and fully explain everything I tried to get it to work. Best advice is to keep trying different date formats and tweaking some of the existing standard date formulas including the English (US) date formats. Try and make these date format changes in the raw data .csv from Coinspot and or in the saved report from the Converter process. If you are unfamiliar with Excel or Libre Calc then let Google be your best friend as there is help available but you have to find it. The very short description of how to try this is to highlight the column that you can see has the date information in by clicking on the Column letter at the top then right click and select Date then you may have to try different date formats until you find one that Cointracking will accept. Sometimes the problem can be that some or all of the date strings have been imported / converted with
an apostrophe ‘ preceding the date string and these strings will not convert to an acceptable date format for Cointracking to accept when importing.  So after a lot of trial and error and angst I discovered that the way to remove these apostrophes ‘ from the first character of the date string is to do the following. Click on the Column header letter usually A that obviously contains the string of numbers that looks like a date format and once the column is highlighted go to the Toolbar above and click on ‘Data’ in Libre Office Calc then select ‘Text to Column’ in the dropdown. This will then present you with some choices so then select ‘Separated By’ and ‘Other’ then insert ‘ into the little white box to the right. Next hit the OK button and just like magic the apostrophes ‘ will disappear and your date strings will then be able to be easily converted into any date format you desire. Once this is done Cointracking should accept the Import by .csv or Excel import if that is your file type. Good luck but do keep trying. This process is a little different if you are using Excel but essentially it is to add a new column to the right of the date column then select all the dates in the other original column then Copy and Paste into the first cell of the newly created blank column by selecting 123 from the Paste Options and this will remove the apostrophes ‘ for you as above and the selection of any Date format will then be possible.
Once the data import has finally been accepted into Cointracking and it shows without any error flags you will need to Recalculate. 
When you see the red box to Recalculate being offered, click this box to commence the recalculation. If the Recalculate box is not presented then you can click on Enter Coins then select Overview and Manual Import in the dropdown box and this will cause the Recalcute box to appear provided that recalculation is required.
At this point your basic raw data is visible in the Cointracking software and that is where the real work starts.

Next have a look around the data and various reports and see if it makes sense. Then open the Enter Coins page select Edit for any coin then the Edit Transaction box will open. Select Edit Asset within the Trade Value box if it is offered otherwise the two ‘Value’ boxes will already have been opened and will be visible. Then check that the AUD value of the trade is the same on both sides of the trade ie; Purchase Value and Sale Value. My experience shows that the correct AUD amount will have populated to the Sale Value side only and there will be another incorrect AUD amount showing in the Purchase Value side that has been inserted by Cointracking? The Sale Value amount should be correct as it appears to be drawn from the supplied Coinspot OrderHistory.csv records of the transaction. Next copy the correct AUD amount over from the Sale Value box and paste it over the incorrect amount showing in the Purchase Value side so that both boxes are identical then click Update.
Unfortunately this will have to be done for each and every Trade entry that is loaded. Leave the Recalculate red box until you have fixed a batch lot of coin entries and this will then recalculate all your changes in one go.
The OrderHistory.csv import only loads the Trades and not the Deposits, Withdrawals, Sends or Receives and generally speaking does not include airdropped bonus or forked coins(unless the exchange has supported the fork or airdrop).
All of these Trades, Deposits, Withdrawals, Sends or Receives have to be manually added into the Cointracking software. You can download .csv reports from Coinspot of the AUD Deposits that were made into your Coinspot account through your bank or finance institution. These will have to be manually entered for the time being until the API is fixed and usable. Coinspot seem to have been sitting on this API repair for more than 6 months for whatever reason so don’t hold your breath.

The only way to find the other information is unfortunately to open every individual coin Wallet in your Coinspot account that you remember or suspect that there have been some transactions during the year such as Send or Receive including bonus forked airdropped coins if applicable. This is very much a hit or miss scenario and could lead to non discovery and or non declaration of what could be a substantial transaction so be diligent.
An important point to remember is that all airdropped bonus coins from a fork or bonus scheme need to be designated as a Gift/Tip when inputting the information on the Enter Coins page in Cointracking. In my case I have chosen to assign a nil value at the point of receiving them as in a lot of cases there is no immediate ready market for these fledgling coins to arrive at an honest and realistic value. I will ultimately report them in the Tax Report and then pay Capital Gains tax on the increase above my cost base of zero.(Check your local country requirements as tax laws differ vastly around the world and I am awaiting confirmation from my accountant and the ATO in Australia that this is the correct approach).

At anytime after data input and after having updated via the red box that pops up offering to Recalculate you can check the status of each entry by opening the Trade Prices report and viewing the ‘Spread ‘ column. This ‘Spread’ column will show 0.00% when both sides of each of the individual trades are equal. (Caution that they could both be equal but also that they could both be wrong yet still equal if the wrong information is input).
If there are any numbers at all showing in the ‘Spread’ column as a percentage then that means that both sides of the trade (Sale and Purchase Values) are not the same and should be investigated by going back to the Enter Coins page and selecting the particular trade as identified in the ‘Spread’ column of the Trade Prices report. Then to correct this you will have to go through the same editing as discussed above.
Recheck back in this Trade Prices Report to see that your progress of eliminating all the non equal values is proceeding to completion. What you want to achieve is that the percentage is showing 0.00% against all entries then you will know that both Value amounts are equal which is how you want it to be.
AUD or fiat purchases of crypto are way less problematic than crypto to crypto trades but they still need a lot of work to achieve accurate results in the various reports.


With crypto to crypto trades such as those that are imported via an active API from Cryptopia there are even more steps in the process to achieve results that are accurate enough that you could submit to the ATO for taxation purposes.
When the import from Cryptopia and probably many other similar exchanges are done these  exchanges do not convert or show the crypto trades with a fiat AUD equivalent alongside.
So Cointracking generates it’s own conversion in AUD or chosen fiat currency and populates the Sale and Purchase Value boxes previously talked about with their own Cointracking amounts apparently based on historical sales data. These are invariably very wrong and are always different on both sides of the trade which is just weird to my thinking. So after the import from Cryptopia run the Recalucate red box process and reopen the Trade Prices Report looking at the ‘Spread’ column again and you will see which entries are showing as not equal by the entry showing the % with a number in front which is the percentage of differentiation between the two uneven cost basis Values of Sale and Purchase as discussed earlier. These are the entries that one must now concentrate on and individually edit these incorrect value that are showing. But be aware that there is an extra step to be added into the crypto to crypto trades that have no exchange generated fiat value included in the API import.

So the next step then is to open the ‘Cointracking Coin Price Calculator’ in another window and the Enter Coins page in the other window. Select the particular trade in the Enter Coins page that has Cointracking supplied fiat values is wrongly inserted. Then copy the figure showing in ‘Amount’ and then paste this figure into the Coin Price Calculator in the ‘Amount’ box then select your crypto currency that you are converting so say ETH then the fiat type you are converting to so in this case AUD and finally the transaction date for the value on that day.
Then hit enter to see the result of the conversion on the right hand side of the Coin Price Calculator window. Next step is to copy this resultant AUD figure and go back to the Enter Coins page in which the Edit box should still be open and paste this figure into both sides of the trade ie Sale Value and Purchase Value then hit ‘Update’. Doing it this way one has to accept the accuracy of this Cointracking Coin Price Calculator conversion data as being right but the alternative way of achieving this result is not worth contemplating especially if you have a lot of trades to edit.
This will have to be done for each and every entry that you have imported. This can be a very long and arduous task unfortunately but it has to be done in an effort to achieve accurate results.

The API imports generally include within the transaction values the deposit and withdrawal transactions unlike the earlier .csv reports downloaded from Coinspot which don’t include this data and then have to be input as a separate process. Also if airdropped coins have been supported by the particular exchange and have been received into your account due to holding the qualifying coin on the particular exchange then unlike the .csv imports of Coinspot and other similar exchanges these should be shown in the Deposit part of the transactions imported. Withdrawals such as sending to your offline wallet for safety are also generally included in the API import as well. Note that you will have to create a manual corresponding Deposit entry for each of the withdrawal transactions from the exchange into your chosen wallets that match your exchange withdrawals. If you are able to use the Cointracking Wallet import interface then you will not have to do this manually.
Good luck to alll

CapitalConsortia
Yes the tax report situation is not as it should be. One should be able to rerun the report after adding extra trades or transactions but as you say a NEW report has to be created? Strange!

With regards to the csv and xls reports I am still waiting for the answer and the advice from the Cointracking support on how to stop this happening as it is a major problem that needs to be fixed. We need to be able to export and reimport without a problem but so far CT support does not believe me that this is actually happening despite me sending them the files for evaluation. "Must be a step I am doing wrong"

Despite the serious problems with parts of Cointracking I agree that it is a powerful piece of software. It is just such a shame that the product support is so dreadful and not in keeping with the quality of the software.

Mr Bee
Thank you for taking the time to respond with your thoughtful advice.
I have tried exporting via the Trades List and also via the Trade Table and then re importing the same unedited file back into Cointracking.
Both ways introduce different mistakes and differing results due to the multiple values CT applies.
I am still waiting on a response from CT support after supplying them with all the files and detailed info so will let you know the outcome.

Creating a backup only saves the data into CT and not on my laptop unfortunately. I would like to remove all backups to my local hard drive so that when and if the online security at CT is breached then my records should be safe as they will not be stored on their servers.

I now have a pretty good understanding of the date format problems having spent countless hours on understanding and solving various date problems to be able to import and make sense of my records. It seems to work in various date formats not just the one which is as it should be to cater for different formats used around the world.

The learning curve as you mention is steep beyond belief. I acknowledge that what CT is attempting to do is very complicated and convoluted and has so many parameters to consider in arriving at meaningful results BUT it introduces multiple values  for each transaction as outlined in my earlier post on the 2nd March re the hypothetical purchase of 1 BTC example. This where a lot of the incorrect results stem from and CT support still refuses to supply a detailed explanation of why it does this?

I do agree that CT is the potential leader in the field of crypto record keeping and it is such a shame that they do not put a greater effort into providing support to their customers when those customers identify problems that are occurring within the way that CT works. I still do not have a detailed answer to my post of 2nd March despite their protestations that they have answered each of these queries which they certainly have not. Just imagine how much better CT would be if they actually learned from their customers reports of the problems that they experience instead of blindly believing that CT is PERFECT and that customers reports are always customer error. I acknowledge that due to the complexities involved with CT some but not all customer complaints are customer error but...

I do thank you for your positive encouragement and I will not be giving up as I can see the potential of the power of the CT program:)
Hopefully these blemishes can be straightened out and in time CT can assume the mantle of the worlds leading crypto accounting software.
Wayne

Dominik
I have just tried this all again.

Which step?
There are a total of 2 steps
Step 1. Export .csv report to hard drive and save
Step 2. Import .csv report to Cointracking
All completed within 2 minutes.
Same problems as reported to you before so which step is wrong???

I exported the report in CSV Extended view to my laptop.
I then re imported the same file into my Practice account via the Enter Coins page CSV and Excel import tools and compared the resultant entries with the original entries still in my Personal account and the bad news is that they are not identical.

The re import transfers all the correct existing data from the Comments column into the Group column, inserts a random date into the Comments column, deletes all the listings of exchanges under the Exchange column and removes all the entries under both the Fee and Currency columns?
You can see this for yourself in my Practice account.
Why is this happening when it is the same file(s) re imported that was exported moments earlier?
Obviously this messes all reports up and is useless to rely on for backup locally.
Please advise on how to fix this here openly on this forum as from experience things seem to get lost in the Help Desk.
Thank you

Dominik
I note that you are answering other questions but are not providing answers to my questions such as the one below.
Why are you choosing to just ignore my important questions?
I need an answer to this problem with the backup please.(see below)



Thank you for your advice re the Trade List Full View which I followed.
I exported the report in in CSV and also in XLSX and also saved a copy in XLS to my laptop.
I then re imported into my Practice account via the Enter Coins page CSV and Excel import tools and compared the resultant entries with the original entries still in my Personal account and the bad news is that they are not identical. I tried re importing with all 3 versions of the exported data and all have the same problem.
The re import transfers all the correct existing data from the Comments column into the Group column, inserts a random date into the Comments column, deletes all the listings of exchanges under the Exchange column and removes all the entries under both the Fee and Currency columns?
You can see this for yourself in my Practice account.
Why is this happening when it is the same file(s) re imported that was exported moments earlier?Huh
Obviously this messes all reports up and is useless to rely on for backup locally.
Please advise on how to fix this.

Thank you

Dominik
Thank you for your advice re the Trade List Full View which I followed.
I exported the report in in CSV and also in XLSX and also saved a copy in XLS to my laptop.
I then re imported into my Practice account via the Enter Coins page CSV and Excel import tools and compared the resultant entries with the original entries still in my Personal account and the bad news is that they are not identical. I tried re importing with all 3 versions of the exported data and all have the same problem.
The re import transfers all the correct existing data from the Comments column into the Group column, inserts a random date into the Comments column, deletes all the listings of exchanges under the Exchange column and removes all the entries under both the Fee and Currency columns?
You can see this for yourself in my Practice account.
Why is this happening when it is the same file(s) re imported that was exported moments earlier?
Obviously this messes all reports up and is useless to rely on for backup locally.
Please advise on how to fix this.


With regards to the second question you have never answered these series of questions once let alone several times.
If I had the answers do you really think that I would waste my time re asking the same questions over and over. I have much more to do than that.
Please take the time to have a close look at the individual points and values that I outlined and provide a detailed explanation of each here so that all can have the benefit of this knowledge on how and why Cointracking does what it does with all these multiple values and more importantly how to stop Cointracking from continuing to propagate false values.
I am sure that it would benefit all users as identifying and subsequently correcting all of these introduced mistakes consumes so much time and energy to get Cointracking to produce reliable results.
Thank you

Hello Cointracking
I originally posted the following questions here some 59 days ago seeking clarification and advice re the following simple basic transaction so that I (and others) might better achieve an understanding of how Cointracking values and handles each transaction that is inserted. 
At this stage I am still waiting for a proper response to these very important questions that I have been asking for some time.

Understanding of this very basic principle of varying values within the software would certainly be advantageous to all concerned as we would be better equipped to locate, identify and correct these wrong values that are automatically inserted by Cointracking.
Obviously it would be far more professional if these incorrect values were not introduced in the first place.

Post of the 2nd March below
Hello
I have been trying to get Cointracking to function accurately since December with very mixed results unfortunately.
So I thought I would go back to basics and start again in trying to understand the workings of this mysterious software.
To this end I set up a new empty account and have been trying some dummy entries to try and understand how this software works but I am even more confused now.
Does anyone have any valid explanation as to why there are 4 different values that appear when I simply enter a sample buy transaction of 
1 BTC as shown below?

Interestingly and very confusingly Cointracking provides 4 differing values for the 1 BTC purchase on the nominated date and time which just serves to muddy the waters and potentially produce reports that are wrong. Check it out yourself but in my example below this is what I found for the 

1 BTC dummy purchase on 24 /02 /2019, I Entered $5898 as the Cost and $898 as the Fee and Home as the Exchange

$5898    The actual fiat cost value entered into the Enter Coins page (from LiveCoinWatch), Populates to the 'Sales Value' box✔

$5870    Cointracking automatically inserted this figure in the 'Purchase Value' box disagreeing with the above Sales Value box? Why ❓
$5535    The Cointracking Coin Calculator for 1 BTC on the purchase date value showed this figure when I checked out of interest. Why
               (Somewhat explained but your explanation should be noted on the Coin Calculator webpage  as it was not at the time. Alternatively why cannot the Calculators resultant values be the same data set as the 'Sales Value" makes sense to me and removes one of the discrepancies) 
$5875    Showed as the current value of 1 BTC in the Summary box on the Enter Coins page at the exact  time of the purchase entry? Why❓
               

Next I checked the Total Realised and Unrealised Gains Report and this report uses the incorrect $5870 that Cointracking inserted automatically as a Purchase Cost Value to do the calculation which can then only ever be wrong!.❓
This is further complicated and messed up beyond comprehension when I check the Tax Report / Closing Position Report which shows a 5th differing Cost value now inserted for this one simple purchase transaction of $5786. ❓

Is there any wonder that confusion reigns supreme within this software when you have now 5 differing values for 1 BTC at the same date and time. Every transaction entered for every coin will be likewise affected so it would be required to be be very careful and triple check everything as there are potentially so many mistakes.   

The only factual amount was the $5898 that I theoretically paid to buy the 1 BTC and believe it or not the Cointracking software totally ignores the one and only cost value that matters. How could this software ever be relied on to produce correct reports when it uses so many differing values for the same coin?
There has got to be a better more realiable way to manage crypto surely.
I have applied extensive manual editing to correct these mistakes this but it is so labour intensive to make it not really worth the time especially when Cointracking could and should correct their introduced problems so that all of this manual editing is not required.

Maybe I am missing something here so I am open to any advice as to why there should be any more than the one and only correct cost value used for all calculations, especially fiat based transactions.

Hopefully someone very knowledgeable from Cointracking will chime in here and explain this for all of us.
Thank you

Hello Cointracking
I have previously posted this and have not received an answer to the following. Could someone please advise re this question. Thank you

I would like to be able to run a  'Trades Backup" with the asset values and IDs that saves to my laptop and not your server for security purposes. This way if and when Cointracking is hacked I will not have my records visible to the bad guys as my account will be empty of all records and the Trades Backup will reside on my laptop and not the Cointracking server. 
When I need to do the next years Tax Return I will simply reload the previous years records from my laptop backup with all the assets values correctly retained and then enter the current transactions for that year.
How do I achieve this please?
Thank you
Wayne

Twintalk
I have the iOS app and it syncs and works fine.

Hello Cointracking
I originally posted the following questions here some 23 days ago seeking clarification and advice re the following simple basic transaction so that I (and others) might better achieve an understanding of how Cointracking values and handles each transaction that is inserted.
At this stage I am still waiting for a proper response to these very important questions that I have been asking for some time.

Understanding of this very basic principle of varying values within the software would certainly be advantageous to all concerned as we would be better equipped to locate, identify and correct these wrong values that are automatically inserted by Cointracking.
Obviously it would be far more professional if these incorrect values were not introduced in the first place.

Post of the 2nd March below
Hello
I have been trying to get Cointracking to function accurately since December with very mixed results unfortunately.
So I thought I would go back to basics and start again in trying to understand the workings of this mysterious software.
To this end I set up a new empty account and have been trying some dummy entries to try and understand how this software works but I am even more confused now.
Does anyone have any valid explanation as to why there are 4 different values that appear when I simply enter a sample buy transaction of
1 BTC as shown below?

Interestingly and very confusingly Cointracking provides 4 differing values for the 1 BTC purchase on the nominated date and time which just serves to muddy the waters and potentially produce reports that are wrong. Check it out yourself but in my example below this is what I found for the

1 BTC dummy purchase on 24 /02 /2019, I Entered $5898 as the Cost and $898 as the Fee and Home as the Exchange

$5898    The actual fiat cost value entered into the Enter Coins page (from LiveCoinWatch), Populates to the 'Sales Value' box✔

$5870    Cointracking automatically inserted this figure in the 'Purchase Value' box disagreeing with the above Sales Value box? Why ❓
$5535    The Cointracking Coin Calculator for 1 BTC on the purchase date value showed this figure when I checked out of interest. Why
               (Somewhat explained but your explanation should be noted on the Coin Calculator webpage  as it was not at the time. Alternatively
            why cannot the Calculators resultant values be the same as the 'Sales Value" makes sense to me and removes one of the discrepancies)
$5875    Showed as the current value of 1 BTC in the Summary box on the Enter Coins page at the exact  time of the purchase entry? Why❓
              

Next I checked the Total Realised and Unrealised Gains Report and this report uses the incorrect $5870 that Cointracking inserted automatically as a Purchase Cost Value to do the calculation which can then only ever be wrong!.❓
This is further complicated and messed up beyond comprehension when I check the Tax Report / Closing Position Report which shows a 5th differing Cost value now inserted for this one simple purchase transaction of $5786. ❓

Is there any wonder that confusion reigns supreme within this software when you have now 5 differing values for 1 BTC at the same date and time. Every transaction entered for every coin will be likewise affected so it would be required to be be very careful and triple check everything as there are potentially so many mistakes.  

The only factual amount was the $5898 that I theoretically paid to buy the 1 BTC and believe it or not the Cointracking software totally ignores the one and only cost value that matters. How could this software ever be relied on to produce correct reports when it uses so many differing values for the same coin?
There has got to be a better more realiable way to manage crypto surely.
I have applied extensive manual editing to correct these mistakes this but it is so labour intensive to make it not really worth the time especially when Cointracking could and should correct their introduced problems so that all of this manual editing is not required.

Maybe I am missing something here so I am open to any advice as to why there should be any more than the one and only correct cost value used for all calculations, especially fiat based transactions.

Hopefully someone very knowledgeable from Cointracking will chime in here and explain this for all of us.
Thank you

Dominik
I would like to be able to run a  'Trades Backup" with the asset values and IDs that saves to my laptop and not your server for security purposes. This way if and when Cointracking is hacked I will not have my records visible to the bad guys as my account will be empty of all records.
When I need to do the next years Tax Return I will simply reload the previous years records with all the assets values correctly retained and enter the current transactions.
How do I achieve this please?
Thank you
Wayne

Sam I agree also that this is a strange way to put the offers together. It is my understanding that the 3500 is a total limit of transactions within your account at any given time whether it takes one year, two years or a lifetime to reach the cap. I think that you can delete or remove some of the older years transactions if you are getting close to the 3500 limit but it is very strange the way they have constructed these offers.
If you are lucky maybe somebody of authority can chime in here and confirm for you.

I am not sure that I have an answer for this situation other than your workaround.

Although you might try selecting Transfer (last one in the dropdown) to solve your problem?
This creates two entries one in and one out which is what you have with a refund. Just use the same name for the in and the out exchange so in this case Customer 1 and Customer 1 (or any defining name) Just add the notes in the Comments column for future reference.
Check the result in the Balance by Exchange Report and it will be nil balance.
Good luck with it all.
Regards
Wayne