-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export Account Transactions has wrong tax #141
Comments
Hi, you can change pytr's csv locale using the export_transactions --lang argument. Excel should also be able to parse semicolumn separated csvs. Furthermore, could you share the (redacted) json entry of the event with the erroneous tax (all_events.json)? |
In account_transactions.csv I also get wrong or malformatted tax: snippet from all_events.json: |
I have the same situation: the values in the JSON look correct (as with @msdn65) |
I see and yes, this event is not yet supported. To add support and for validating potential changes, please share the full json event entry with unaltered keys, nesting, and value formatting. |
chnaging the language does not change the outcome, only the format ... tax is wrong
80.35 would by correct BUT I digged deeper: all_events.json: in locale "en"
is parsed here (I think) in /pytr/event.py in locale "de":
BUT "text": "€80.35", is not in locale "de" its 80.35 so cls._parse_float_from_detail(taxes_dict, "en") will fix it? |
…g#141) It seems the "Steuer" value can either be represented as "€11.14" or as "11,14 €" string. The "€11.14" representation was misinterpreted as 1114.
Hi,
I am a beginner in Python programming and managed to get this (great) program running under a virtual Python 3.9 on my new Mac mini.
While exporting the transactions
dl_docs
, I noticed that the taxes were incorrectly displayed.Output: 2024-11-01;Interest;187.16;Zinsen;;;;-6,704
The real value is: 187,16€ and 67,04€ tax (instead of 6704€).
Additionally, I have the problem of importing .csv files into Excel on my Mac (German locale)
(comma/period and UTF-8 -> Mac-Roman).
Would it make sense to offer a specific option for this?
Additional question: Does it make sense to get this app running under Python 3.12 as well? (As mentioned, I’m new to Python).
Thanks
Ralf
The text was updated successfully, but these errors were encountered: