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

[14.0] [purchase_advance_payment] wrong residual amount when reconciling credit note with invoice #1855

Closed
ygol opened this issue Apr 25, 2023 · 7 comments
Labels

Comments

@ygol
Copy link

ygol commented Apr 25, 2023

Module

purchase_advance_payment

Describe the bug

When reconciling an bill with a vendor credit note, the residual amount is false. As the vendor credit note amount is subtracted twice.

To Reproduce

tested 14.0

Steps to reproduce the behavior:

  1. create a PO, confirm + create an invoice
  2. edit the above PO and add a new line with negative amount, confirm + create bill
  3. reconcile the available vendor credit note amount on the vendor bill
  4. Get wrong residual amount = 360000
    image

Expected behavior
Residual amount to be 480000

image
Additional context
Add any other context about the problem here. (e.g. OS, Python version, ...)

@ygol ygol added the bug label Apr 25, 2023
@ygol
Copy link
Author

ygol commented Apr 26, 2023

the problem is that the PO total amount has already discounted the value of the credit note and when we reconcile the credit note with the invoice it is thus deducted a 2nd time when

invoice_paid_amount += inv.amount_total - inv.amount_residual

@HviorForgeFlow
Copy link
Member

ping @MateuGForgeFlow

@HviorForgeFlow
Copy link
Member

@ygol We will be more than excited to review your fix proposal

@djtao1
Copy link

djtao1 commented Jun 11, 2023

I am also very troubled by this issue. Is there a plan or possibility to fix this issue? thanks for support!

@rvalyi
Copy link
Member

rvalyi commented Jun 11, 2023

cc @clementmbr @PierrickBrun @NathanQj

@djtao1
Copy link

djtao1 commented Jun 20, 2023

I have tested the latest version and it appears to be functioning correctly. but how to correct the erroneous entry caused by this issue earlier. They don't seem to have been automatically corrected.

@ygol
Copy link
Author

ygol commented Jun 20, 2023

I have tested the latest version and it appears to be functioning correctly. but how to correct the erroneous entry caused by this issue earlier. They don't seem to have been automatically corrected.

hi @djtao1 working on a solution in #1862

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

4 participants