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

Unallocated amount is inaccurate on multi-currency Payment Entry #29595

Closed
Archais opened this issue Feb 2, 2022 · 2 comments
Closed

Unallocated amount is inaccurate on multi-currency Payment Entry #29595

Archais opened this issue Feb 2, 2022 · 2 comments

Comments

@Archais
Copy link

Archais commented Feb 2, 2022

Information about bug

The issue is that when you are processing a payment entry in a currency other than base, the unallocated_amount can end up being inaccurate, especially with higher exchange rates, e.g. 210 : 1.

In my example of the issue we are running a base currency of USD and we are receipting payment in ZWL. The customer has paid us ZWL$1,160,250.00 at an exchange rate of 210:1 (represented in ERPNext as 0.004761905) which evaluates to USD$5,525.00. This part is accurate, however because ERPNext does the allocations in base currency then converts back to the selected currency to give you your unallocated_amount, we get a value of ZWL$1,160,249.94. So we are losing ZWL$0.06 on the transaction but there is no USD difference because when converted it is less than USD$0.01. Thus there is a loss in value of the customer's money without the value going anywhere.

Module

accounts

Version

Frappe version - 13.19.0
ERPNext version - 13.19.0

Installation method

manual install

Relevant log output / Stack trace / Full Error Message.

No response

@Archais Archais added the bug label Feb 2, 2022
@Archais Archais changed the title Unallocated amount is in accurate on multi-currency Payment Entry Unallocated amount is inaccurate on multi-currency Payment Entry Feb 7, 2022
@stale
Copy link

stale bot commented Apr 8, 2022

This issue has been automatically marked as inactive because it has not had recent activity and it wasn't validated by maintainer team. It will be closed within a week if no further activity occurs.

@fproldan
Copy link
Contributor

fproldan commented Sep 6, 2022

👍🏻

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants