Matched Not Received Quantity - Enhancement

ben-auer

Hey Everyone,

Currently Infor has no way of restricting the creation of matched not received (MNR) quantities. These MNR quantities build up in our system, typically when an invoice is matched above a receipt quantity. For example – Invoiced 4 and received 3. Infor still allows it to be matched. This leaves the PO line open and can skew reports and inventory re-ordering. Causing a big headache.  

We have opened multiple tickets to address this issue, we've been mainly told this is more of a training issue.  We have increased our training, this has helped.....somewhat.  There are still circumstances where this occurs though.  There is no warning that matching of an invoice using a specific set will create an MNR quantity.  There is also no way to restrict that.  A processor could go in and force match a100CA invoice against a receipt for 1CA.  

There needs to be controls for matched not received quantity.  Please endorse 

Our proposal in ER#99162 - https://icp.cloud.infor.com/infor/?LogicalId=lid://infor.generic37.1&Tab=ERS&ERId=99162 

1.) Enable an option to warn when attempting to match an invoice that an MNR Qty. will be created.

2.) Ability to turn on/off the ability to match an invoice with an MNR quantity. This should be configurable on the vendor level.

**None of this should affect invoices matched with Chargebacks due Invoice Qty. vs. Receipt Qty. The chargeback quantity would cancel out any MNR Quantity.

Thanks,

Ben

 

andy

Have you tried adding an Entrance Rule to the SmartReconInvoiceMatch action on the MatchReconQueue business class to warn/block when the set contains a quantity discrepancy?

There might be a little more fine tuning needed, e.g. more actions to configure, but I think you might be able to warn / block the force match in Recon by adding some action configurations in config console.