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 edge case - 1 payment with valid settlement AND open balance #80

Open
thelontx opened this issue May 12, 2022 · 0 comments
Open
Labels
bug Something isn't working

Comments

@thelontx
Copy link
Collaborator

Edge case: When a single WA payment has a valid settlement to an Invoice AND has a remaining unsettled amount, the Unsettled amount of this payment does not show up inside QBO. A single WA payment that is completely unsettled, does show up correctly inside QBO as an unsettled payment.

Current v0.7 QBWA relies on Payment allocations to drive bundles and proper linkage of payments to invoices. This approach is needed for a single payment that settles to multiple invoices.

An "empty" allocation bundle is created for an unsettled payment because no WA Allocation exists. When looking up the Invoice for an empty Allocation bundle, logic in QBWA exists to recognize there is no Invoice and to treat the Payment as Unsettled.

A payment with valid settlement produces an allocation bundle for that related invoice. However, if that Payment has an additional unsettled amount, there is no logic to create a "fake" partial empty allocation bundle. i.e. There is no logic to check that the summed allocation "amounts" equal to the total paid "amount".

This will likely require inserting an iterator and/or aggregator to check the summed amounts and create a "fake" bundle. This may require significant rework of the Core scenario. Leaving this as a known bug for the moment.

@thelontx thelontx added the bug Something isn't working label May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant