[16.0] [FIX] account_reconcile_oca: Allow counterpart entries for invoice matching reconciliation models #711
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @etobella, |
ByteMeAsap
force-pushed
the
16.0-fix-account_reconcile_oca-invoice_matching_model
branch
9 times, most recently
from
f75805f
to
7d414c8
Compare
…tching reconciliation models Added Tests Updated test script
ByteMeAsap
force-pushed
the
16.0-fix-account_reconcile_oca-invoice_matching_model
branch
from
7d414c8
to
4915bf9
Compare
|
@etobella @ByteMeAsap This would be very usefull. In the Netherlands the 1 cent coin is not used anymore. Many businesses use 4,99 to soften the price of their products. When you pay with 5 euro's this 1 cent difference needs to be accounted for. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a problem with auto validation of invoices when we use the Payment Tolerance
Consider the following example:
Suppose the invoice matching model is setup with payment tolerance as shown in the picture:
The current module would generate entries as follows:
Expected Behaviour is it should generate entries as follows:
This PR would fix this scenario