Invoice is Going to Matched Status After Tax Discrepancy Resolution Eventhough It has Cost and Quantity Discrepancy Also
(Doc ID 2335886.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Retail Invoice Matching - Version 14.0.2 and later
Information in this document applies to any platform.
An invoice is created in Tax Discrepancy (TAXDIS) status.The invoice is having the quantity and cost discrepancy also.
Once the tax discrepancy is resolved by using system tax is correct the invoice is going to Matched (MTCH) status instead of Ready For Match (RMTCH) status. Why?
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