I am working with a scenario where a PO referenced Vendor Invoice is evaluated by workflow and automatically rejects it if the invoice price/amount is outside of the defined variance tolerances. If the invoice price/amount is outside of these tolerances the business requirement calls for a user to update to Purchase Order to fall within the tolerance threshold so that the invoice will pass matching. While one may disagree with modifying the PO in this situation versus posting to PPV accounts to capture the variance, the business requirement calls for this process.
The issue I am encountering is that (1) once the PO is modified to satisfy the invoice matching rules and confirmed, and (2) the vendor invoice is resubmitted to workflow, the vendor invoice matching logic is not reprocessed to determine if the variances are now acceptable. It seems to retain a snap shot of the original matching results and the only way to get the system to reprocess the matching logic is to perform a "fake" line-level edit on the vendor invoice before submitting to workflow.
Question:
1) Have you ever encountered this before or have a solution to triggering the invoice matching logic in workflow without a code change?