Replies: 1 comment 3 replies
-
No problem, although I would still get an email if you posted on the discussion page for that package. I am fairly sure the code is still up to date. The only changes I had to make (post converting to python3*) were little tweaks to cope with the fact IB changes the format of their XML reports. These are easy to spot, since everything just breaks when it tries to read the data in. The actual logic hasn't changed in some time. Having said that, I've been working off my local branch rather than the head, if it doesn't work let me know and I will check to see if there was some local changes I hadn't made. If CGTcalc is False, then you won't be calculating CGT anymore - you will be doing income tax without all the matching rules! So it might be 'safer' but HMRC won't be happy. I have done ocasional tests to see if, for example, using CGT =True I end up with left over trades when my position should be completely closed. And I haven't seen any issues, so I think it works. (Actually I haven't run the code with this flag set False for a long time) |
Beta Was this translation helpful? Give feedback.
-
Hi Rob,
Apologies to use this forum for the question, I believe it is monitored by you more frequently.
I am using your python-uk-trading-tax-calculator script to calculate capital gains tax. First of I wanted to ask you whether the github code is still up-to-date or whether you have made any changes not checked-in?
Second I noticed that the CGTCalc parameter can have a huge difference on profit and loss, and when set to True, I also noticed that in certain cases trades are not matched with opening/closing trades therefore not included in the overall calculation. I was wondering whether you have noticed this behaviour, it seems safer to run this parameter as False.
Best,
Emre
Beta Was this translation helpful? Give feedback.
All reactions