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

[16.0][FIX] account_payment_line - wrong compute #721

Closed

Conversation

kittiu
Copy link
Member

@kittiu kittiu commented Mar 18, 2024

Note: This module extend this #666

Before this fix, things (sign + or -) seem to go wrong on Supplier Payment side, especially when use together with write off.

For example,

  1. When click Propose Payment Distribution, the allocation amount is (+), while I think this should be (-) as other columns (otherwise it is very confusing)

image

  1. Then I click on Full Paid the writeoff amount become -200

image

  1. Or I choose to allocate only partial 90 out of 100, and tick Full Paid again, I would expect to write off = -10, but it is -190

image

  1. Or I redo again, 1) Amount 190, 2) system allocate, tick full paid 3) click Confirm

image

I also wonder why there are so much bugs here. But I think the previous author focus on testing for the Customer Payment side, which seem to be OK.

So, this PR is trying to make it works on both side.

@kittiu
Copy link
Member Author

kittiu commented Mar 18, 2024

@ChrisOForgeFlow as maintainer of this module, can you help check if I am not misunderstanding your design intention and the fix is valid.

Thanks!

@kittiu kittiu changed the title [16.0][FIX] account_payment_line [16.0][FIX] account_payment_line - wrong compute Mar 18, 2024
@ChrisOForgeFlow
Copy link
Contributor

@ChrisOForgeFlow as maintainer of this module, can you help check if I am not misunderstanding your design intention and the fix is valid.

Thanks!

Just like you say, my principal focus was on customer side, I added some supplier test, but I think is good to add your fixes in main version, and maybe we can add a backport

Copy link

github-actions bot commented Aug 4, 2024

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 4, 2024
@github-actions github-actions bot closed this Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants