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

Payment Entry : Exchange Gain or Loss #40472

Closed
Bknjogu opened this issue Mar 15, 2024 · 2 comments · Fixed by #40511
Closed

Payment Entry : Exchange Gain or Loss #40472

Bknjogu opened this issue Mar 15, 2024 · 2 comments · Fixed by #40511
Labels

Comments

@Bknjogu
Copy link

Bknjogu commented Mar 15, 2024

Information about bug

I'm encountering an issue during payment reconciliation in the system, specifically related to the generation of journals for exchange gain or loss with abnormal figures.
When conducting payment reconciliation involving multiple currency transactions, the system generates journals to account for exchange gain or loss. However, I have observed that the figures in these journals are abnormal, deviating significantly from the expected values.

There's a Customer with Currency in Company Default
Have allowed multi-currency invoices against single party account.

Have a stand lone Payment Entry. When receiving Payment the Exchange Rate from USD to KES was 140.5.

frappe1

Against the same customer I created an Invoice in USD, at the point of invoicing the Exchange Rate USD to KES was 160.00

frappe3

When I do Payment Reconciliation to allocate the Payment, reconciliation is successful and a journal is booked to register the Exchange Gain or loss, and rightly so. However, the figures in these journals are abnormal, deviating significantly from the expected values.

frappe2 image image

Module

accounts

Version

ERPNext: v14.65.3 (HEAD)
Frappe Framework: v14.67.1 (HEAD)
Frappe HR: v14.23.0 (HEAD)
Payments: v0.0.1 (HEAD)

Installation method

FrappeCloud

Relevant log output / Stack trace / Full Error Message.

No response

@Bknjogu Bknjogu added the bug label Mar 15, 2024
@albertfns
Copy link

Same problem in version 15.17.1

@ruthra-kumar
Copy link
Member

caused by a regression in #40149

#40511 will fix it.

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

Successfully merging a pull request may close this issue.

3 participants