ATHughes
(Aled Hughes)
October 7, 2024, 1:08pm
1
Bit of an interesting question.
We’re using the Purchase Ordering aspect of Epicor, with all parts set up as Non-Stock-Item.
We end up having a lot of receipts done incorrectly through user error, which is something that’s actively being addressed.
What’s throwing us for a loop is how to rectify these mistakes correctly.
Up until now, if the receipt is wrong, we’ve just deleted the receipt, had the necessary corrections done, and then the receipt re input.
What we have noticed though, is that this is creating some havoc in accounts.
Some analysis shows the following:
If I delete a receipt, correct and re-receipt within the same period, the GL reflects the following:
The reversal of the receipt, therefore a credit
The new receipt, therefore a debit.
What the GL doesn’t show after a receipt is deleted, is the original receipt. So the credit isn’t being offset against anything.
Is there a way of doing this that we’re unaware of?
Ernie
(Ernie Lowell)
October 7, 2024, 5:05pm
2
Why are you using the “Non-Stock” for all your purchased parts? This may not be the functionality you are looking for.
When you physically Delete a Receipt transaction, it is gone as if it never existed. Using this approach means the offset has no transaction to show.
1 Like
ATHughes
(Aled Hughes)
October 8, 2024, 10:49am
4
Ah worked it out. If you un-receive a Receipt, but leave it in place, it removes the cost whilst leaving a record, which is what we wanted.
2 Likes
If you are just unchecking the Received checkbox this could result in Arrived Receipt records sticking around, which Epicor considers supply.
1 Like
ATHughes
(Aled Hughes)
October 8, 2024, 12:34pm
6
Considering how basic our usage is, I don’t think it’s going to adversely affect us from testing.
Only thing we’d need to do by the looks of it, is once the period is closed, used the GRNI to cleanse the data afterwards. For what we’re doing at the moment, that seems sufficient.
1 Like