Purchase Price Variance - AP Qty does not match Receipt Quantity

Hello All,

I have two different receipts and for those two different receipts I have separate invoices.

Both invoices have an invoice quantity higher than what the receipt quantity and it’s paid and posted.

Both unit prices match the receipt unit price, which matched the standard cost, so there’s not unit price difference.

It’s a quantity variance.

The odd thing is, one invoice generated a variance that got posted to the PPV GL and the other did not. The only true difference I can find is that the invoice that posted the variance to the GL was marked as “final invoice” and the other was not. Is that it? Is that why?

I’m deep in the PPV weeds here and about to hop in a test environment to test that hypothesis. It’s documented nowhere in the transaction posting guide.

From what I have seen you are correct. You have the allow multiple invoice per receipt set at the company level, so if final is not checked it does not know what the variance would be yet.

2 Likes

Are you using DocStar?

1 Like

Yeah, why?

Okay thank you Greg, I was about to test it this morning, still will just to confirm.

It’s wild that none of the documentation mentions that.

Are you seeing an issue here?

It doesn’t matter if Final is checked or not, it will still allow for a quantity on the Invoice that is greater the Receipt Quantity. There are ways you can help prevent it from the DocStar side…I’m going to login and look to see what I’ve done.

I think it could be coming from your select auto-match solution.

1 Like

Go to your Auto-Match Step.
Can you show a screenshot of your Search Task? (I’ve seen strange behavior when there are extra spaces in the output for _packSlipsWIP.)
What do your Auto-Match Settings look like? And what thresholds do you have? (Screenshots?)

1 Like

The thing is though the base application also allows you to modify the quantity and from what I am finding it does matter, but I can’t seem to uncheck it… so it’s obviously something in ECM that’s doing things differently than the base screen that’s unchecking that check box.

1 Like