You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Second issue, linked to #692 I guess :
It may be solved with a change on the linked issue, I post it to record it so we can check this case easily then.
Here is the use case (I'll join a shell script at the end allowing to reproduce the issue from a demo database with only account_reconcile_oca installed).
Set up (you can run the shell script)
Active CNY currency
Create a bank journal in a foreign currency (CNY) (set the currency on the journal)
Create a rate for the CNY currency : 0.125989013758 USD per unit for 2024-09-10 and 0.126225969731 USD per unit for 2024-09-09
Create a statement line on this CNY bank journal with amount 259200
Create a customer invoice, with currency CNY, and total amount 259200
Then, go to the bank statement reconciliation, and you have this :
The suspense line does not have any currency visible, like in first issue. I think it is confusing already because we are in a account in CNY and the suspense line should reflect the bank line.
Then when I choose the invoice :
The currency amount appear now, but it is not the right amount (259199.98 instead of 259200). I guess there is some kind of conversion toward usd and then backtoward CNY.
Therefor the amount is strikethrough which is also confusing because the amount is of the invoice is the same as the amount received.
And it let me think that the reconciliation will be partial
Once validated, I check the accounting entry :
I see that the counterpart is not in CNY currency, it has been switched to a full USD line. I expect to have a amount currency of -259200 for the line with account 121000. (same as first linked issue)
Finally on the reconciled invoice :
I see a payment of 0.02 cny which I don't want.
Like I said it may be solved or partially solved by link issue, I still post it now to show all the problems I found for now.
And once again, thanks for the job on the matter!
Well, it seems to be a rounding issue indeed, but I can't get why we would have to round anything in this case.
We have an amount (259200) and it has to be converted in the company currency using the rate. But the inverse conversion is not needed IMHO, that is why I think there is an issue. As if the CNY amount is converted in euro (with rounding then) and the amount in euro is converted back to CNY (once again, with rounding).
Hello @etobella
Second issue, linked to #692 I guess :
It may be solved with a change on the linked issue, I post it to record it so we can check this case easily then.
Here is the use case (I'll join a shell script at the end allowing to reproduce the issue from a demo database with only account_reconcile_oca installed).
Set up (you can run the shell script)
Then, go to the bank statement reconciliation, and you have this :
The suspense line does not have any currency visible, like in first issue. I think it is confusing already because we are in a account in CNY and the suspense line should reflect the bank line.
Then when I choose the invoice :
The currency amount appear now, but it is not the right amount (259199.98 instead of 259200). I guess there is some kind of conversion toward usd and then backtoward CNY.
Therefor the amount is strikethrough which is also confusing because the amount is of the invoice is the same as the amount received.
And it let me think that the reconciliation will be partial
Once validated, I check the accounting entry :
I see that the counterpart is not in CNY currency, it has been switched to a full USD line. I expect to have a amount currency of -259200 for the line with account 121000. (same as first linked issue)
Finally on the reconciled invoice :
I see a payment of 0.02 cny which I don't want.
Like I said it may be solved or partially solved by link issue, I still post it now to show all the problems I found for now.
And once again, thanks for the job on the matter!
Shell script :
The text was updated successfully, but these errors were encountered: