-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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: Allocated Amount cannot be greater than outstanding amount #42062
Comments
this is a bug from the recent version update. We do not usually experience this one. |
Also Experiencing this also on latest version of version-15, message shows up on journal entry as references. |
This is still not resolved |
Any update on this? We cannot process payment entries due to the message :( |
any update on this? |
how can we add this when using frappecloud? looks like this bug is still not added to the latest version update |
Any update on this? |
@ruthra-kumar how can we fix the bug when using a frappecloud? |
@Ponyooooo If you are in FrappeCloud, would suggest you to raise a support ticket on this. |
Hi @szufisher how can we integrate your solution using client script or server script since frappecloud does not allow us to edit the backcodes of the erpnext. Our only way is to use client or server script only unless your solution will be included on the next version update. :( |
It looks like this issue is still not solved. Is this not impacting many people? How come it is not a P0 issue? |
Still no progress on this one |
Any progress? This is not possible to be added on the client script |
Information about bug
Payment entry shows pop up message for Allocated Amount cannot be greater than outstanding amount when creating payments for expense claim. Not yet tested if the pop up message also shows up for purchase order and purchase invoice.
Module
accounts
Version
ERPNext: v14.70.7 (HEAD)
Frappe Framework: v14.77.1 (HEAD)
Installation method
FrappeCloud
Relevant log output / Stack trace / Full Error Message.
The text was updated successfully, but these errors were encountered: