fix: difference amount calculation logic in Payment Entry UI #36899
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ruthra-kumar
added a commit
that referenced
this pull request
Sep 1, 2023
…-36899 fix: difference amount calculation logic in Payment Entry UI (backport #36899)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When adding references in Payment Entry, use Payment Entries exchange rate to calculate
base_total_allocated_amount. This is to avoid difference amount being generated and submitted by Payment Entry. Said difference amount will be calculated and posted by Journals by an internal logicbefore:
before_exc.mp4
after:
after_exc.mp4
part of: #36873
fixes: #36873 (comment)