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

Bug Report: Paid Amount Not Updating Automatically in Payment Entry (Internal Transfer with Different Currencies) #45543

Open
Awey01 opened this issue Jan 27, 2025 · 1 comment
Assignees
Labels

Comments

@Awey01
Copy link

Awey01 commented Jan 27, 2025

Information about bug

Steps to Reproduce:

Create a Payment Entry of type Internal Transfer, where the accounts involved use two different currencies.
Change the Received Amount.
Expected Behavior:

The Paid Amount should update automatically based on the exchange rate whenever the Received Amount is modified.
Actual Behavior:

The Paid Amount does not update automatically when the Received Amount is changed.
The Paid Amount only updates when the Target Exchange Rate is changed to a different value.
For example, if the current Target Exchange Rate is 1.05, and you delete and re-enter 1.05, nothing happens.
However, if you change the rate to another value (e.g., 1.04), the Paid Amount updates.
After this, if you revert the Target Exchange Rate back to 1.05, the Paid Amount updates again.
The exchange rate must first be changed to a different value before reverting to the original rate to trigger the recalculation.

Module

accounts

Version

ERPNext: v15.48.4 (version-15)
Frappe Framework: v15.52.0 (version-15)

And also in

Frappe 16

Installation method

manual install

Relevant log output / Stack trace / Full Error Message.

@Awey01
Copy link
Author

Awey01 commented Jan 31, 2025

Same bug with Received Amount - Received Amount does not update automatically when the Paid Amount is changed.

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