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

Vendor invoice : Invalid Remaining unpaid #19631

Open
seblu opened this issue Dec 15, 2021 · 5 comments
Open

Vendor invoice : Invalid Remaining unpaid #19631

seblu opened this issue Dec 15, 2021 · 5 comments
Labels
Bug This is a bug (something does not work as expected)

Comments

@seblu
Copy link
Contributor

seblu commented Dec 15, 2021

Bug

In the Vendor invoice module (/fourn/facture/card.php), the computed value of Remaining unpaid is incorrect. The value is not the difference between the billed value and the amount value. This difference is the value of the credit note.

Screenshot_20211215_165331

Environment

  • Version: 14.0.4
  • OS: Ubuntu 20.04
  • Web server: apache 2.4
  • PHP: 7.4
  • Database: mariadb 10.3

Expected and actual behavior

  • Remaining unpaid should be the difference between billed and amount. 0 is our case.
@seblu seblu added the Bug This is a bug (something does not work as expected) label Dec 15, 2021
@seblu
Copy link
Contributor Author

seblu commented Dec 15, 2021

Remaining unpaid is also incorrect without credit note but when the Recalculate feature is used to compute another tax rounding.

Screenshot_20211215_235626

Screenshot_20211216_001107

@seblu
Copy link
Contributor Author

seblu commented Dec 15, 2021

Please note, when Classify automatically all standard, down payment or replacement invoices as "Paid" when payment is done entirely is checked in the payment form (/fourn/facture/paiement.php), the Remaining Unpaid is correctly set to 0 and the invoice is closed as paid.

@seblu seblu changed the title Vendor invoice : Invalid Remaining unpaid when credit note Vendor invoice : Invalid Remaining unpaid Dec 15, 2021
@github-actions github-actions bot added the Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open label Dec 16, 2022
@seblu
Copy link
Contributor Author

seblu commented Dec 22, 2022

I confirm it is still present on latest stable version

@github-actions github-actions bot removed the Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open label Dec 22, 2022
@ksar-ksar
Copy link
Contributor

Hello,

Is it still the case on V18 ?

@michalhana99
Copy link

unfortunately even in version 18.0.3 this problem persists, when will this error be fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This is a bug (something does not work as expected)
Projects
None yet
Development

No branches or pull requests

3 participants