Invoices Go To URMTCH Status Instead Of TAXDIS
(Doc ID 2320271.1)
Last updated on MARCH 08, 2019
Applies to:Oracle Retail Invoice Matching - Version 16.0.1 and later
Information in this document applies to any platform.
Header level invoices with tax discrepancy are being updated to unresolved match instead of TAXDIS by the automatch batch program.
Steps to reproduce:
1 - The match strategy is the same as described in the issue:
a) Summary all to all
b) One to many - Regular
c) Detail - Regular
2 - Make sure that the automatch will use the above match strategy for the invoices that will be created.
3 - Create a PO
4 - Receive the PO in full
5 - Create a header level invoice where the totals (qty and cost) match the receipt but where the Tax is different to force the tax discrepancy scenario.
6 - Execute the Automatch batch program.
7 - Check that the invoice status is URMTCH instead of TAXDIS.
The following are examples of scenarios:
1. Set up a scenario with a header only invoice where the invoice matches to the receipt, but the taxes are discrepant.
2. When using a match strategy of (1 - Summary All to All; 2 - One to Many Regular; 3 Detail Regular)
a. The invoice comes back as unresolved match
3. When using a match strategy of (1 - Summary all to all; 2 - Summary one to Many Regular)
a. The Invoice comes back a Tax Discrepancy.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document