We have a finance related issue that I’m not sure how to fix because that side of Epicor is a relative mystery to me.
Our finance group tried to Capture December’s numbers and it wouldn’t post because the journal entry was out of balance.
I was able to identify the issue… We had a PO line item that somehow got tagged as Inspection Required. We don’t use Epicor’s inspection stuff so when our finance group saw the PUR-INS transaction, they had no idea what it was.
I cleared the item through the inspection queue, but the problem is, the items were received on 12/22/2025… (they tried to capture and resulted in a Received Not Invoiced record and an imbalance).
I cleared the part through inspection, but that was on 1/9/2026.
We’ve been looking at the Review Journal. But from what I’ve read, deleting the journal entry there doesn’t reverse any capturing (correct?). I could capture COS/WIP up through 1/9/2026 which would then capture the correcting transaction… but I assume I would then have (2) postings that would be out of balance.
I’m thinking I should make a manual entry in December, to get the period to balance. and Post it.
Then capture through 1/9/2026 (which again, would probably be unbalanced)… then make another manual entry to reverse the prior correction getting this second period to balance… and then Post that period.
At my job, we have certainly received a part in a prior month and inspected it in a later month. It has never caused a posting to be out of balance. Every transaction (like PUR-INS) should have a debit and a credit that balances.
To be technical, a single transaction (MFG-STK) might hit 3 debits and one credit or something, but point is that the left total equals the right total.
I was thinking the same thing… parts get received all the time… inspections get finalized later… this can’t be the issue.
I’m trying to see (since we don’t use epicor inspections) whether we never set up the other side of those transactions. So it is crediting one side but not entering a matching debit.
When this happens with us (usually from a weird situation like a new division code that was added but accounts never created), we:
Cancel the Review Journal. This reverses the single posting that was out of balance. This might be an entire day’s postings if you have your posting rule set to summarize.
Run the Inventory/WIP Reconciliation report for that period for Unposted transaction only. This lets us identify what the problem is.
Fix the problem: create the account, add the GL control, whatever it is.
Run the capture for that period again. If we were having trouble with a posting on 12/22/2025 we would run the capture through 12/31/2025. This will post for 12/1/2025 through 12/31/2025. If Finance/Accounting says 2025 is closed and no way can you post in December, even if the balances are wrong, then you can run the capture for some date in January and make sure “Capture Outdated transactions” is selected. This will “catch up” any missed transactions before January and post them on 1/1 (by default).
Don’t try to make any manual entries or anything…These transactions need to be captured by the WIP Capture process or they’ll always be out there as unposted.
If you know the date and the transaction type that is missing the account or control, you can enable the PE log and run the Inv/WIP Recon report for only that date and transaction type. It will make the log MUCH easier to parse through. Even a single day’s postings for all transaction types can be unwieldy to comb through.
If you have a Test/Third environment that is up-to-date enough to have this same issue, you can enable the PE Log in that environment so you don’t forget to disable it when you’re done.
In the PE Log Viewer screen, go to the Transaction Types tab/pane and you can enable the logger for certain transaction types and companies.
You’ll want to enable it for “COSAndWIP” in this case. Once it’s enabled, running the Inv/WIP Recon report or the COS/WIP Capture (after cancelling the Review Journal) will generate logs.
But cancelling the Review Journal isn’t going to back out any transactions, right? Or will it reset that process and I have to capture that time period again?
Looking through my notes from implementation.
