Skip to content
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

Invoice items price gets multiplied when currency accuracy is changed #3120

Closed
vitis586 opened this issue Dec 28, 2023 · 1 comment
Closed
Labels
Milestone

Comments

@vitis586
Copy link

Akaunting version

3.1.5

PHP version

Cloud Trial

Operating system

Cloud Trial

Steps to reproduce

  1. Start trial company with CZK as base currency
  2. Create invoice with a customer and a single item with price 250,00 Kč
  3. Go to currencies - edit Czech Koruna
  4. Change precision from 2 to 0 (or 1 - that also works)
  5. Go to your invoice concept and edit it
  6. Notice that the prices got multiplied by 100 (or 10 - if you chose precision 1)

Expected result

I would expect that the prices would not get changed at all. Only the number of decimals should change.

Actual result

Prices get changed every time I edit an invoice.

Additional comments

This applies to all currencies actually. I also tried it with USD. Invoices work well only if you do not change the currency precision. Otherwise the item pricing changes every time the invoice is open for editing.

This applies to selfhosted and cloud Akaunting. The error is present for a while, but I have not been using invoice that much before. Now when I use them more it gets a bit annoying.

Relevant log output

No response

@cuneytsenturk cuneytsenturk added this to the 3.1.6 milestone Feb 12, 2024
@vitis586
Copy link
Author

Hello @cuneytsenturk, first of all - thank you for all the fixes! I am playing with a testing instance of the new 3.1.6 and everything works well!

However the currency conversion in the invoice still shows remains of this error. This is the invoice with 0 decimals precision CZK currency.
image

The same screenshot with 1 decimal precision.
image

The same screenshot with 2 decimals precision. It shows correctly the number.
image

I believe that the intention here is to have the number same as the total shown above. Do you mind having a look into that one too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants