Periodic Posting Process entry missing in WIP/Recon report

Epicor ERP 10
1

I have a Periodic Posting entry in the GL, that won’t show it’s details in the WIP/Recon report

Here’s a snap shot of the GL report

image
image815×194 27.8 KB

If I run WIP recon for Inv Jrnl 326 it gives me the “No records” error. Yet doing the same for Jrnl Numbers 323 or 372 work fine.

I did some snooping around, and found that the Invoice I expected to be referenced in the WIP/Recon of Jrn;Num 326, is referenced by more than one TranGLC entries.

image
image855×202 3.17 KB

Invoice (key1) 61767 was created and posted back in 2018. That shows for JrnlNum 326 (highlighted above).

Then something happened that caused the other lines to post on 12-01-2019 (JrnlNum 1014)

Invoice 61767 was a cancellation invoice, if that matters.

Shouldn’t Periodic posting entires be visible in WIP Recon? Or am I chasing a Red Herring?

2

To add to the confusion … When I use AR Invoice Tracker to view Invoice 61767, I see GL Trans with an entirely different Jrnl Num

image
image450×536 6.37 KB

3

Cancellation invoices are a little tricky and are treated like sales returns. We discovered that recently when our sales return accounts were analysed. The cancellation invoices are posted according to the GL accounts defined for sales returns in the AR GL Control code.

4

It’s not about the GL accts being hit. We’ve set up our Sales GLC’s such that each one has the same GL account for its Sales and Returns contexts.

I can’t figure out why TranGLC entries were created on 12-01-2019, referncing an invoice that was posted back in 2018.

Perhaps I’ve misinterpreted the meaning of fields “Key1” in the TranGLC table, for RelatedToFile = InvcDtl

5

Calvin,
Did you check the box for Capture outdated transactions when you ran C&P for December? It will post the outdated transactions to the first day of the month of the capture period.

6

I’m sure that has something to do with it. Especially since 12/1/2019 is a Sunday, and we were closed (so no transactions were created for that date.

But we regularly use the captured outdated transaction function. So I thought something related to such an old original invoice would have been captured.

Maybe since it was a cancellation invoice, it used the apply dates of the original invoice, and that this cancellation invoice was actually posted after 12/1. So it created back dated transactions.

What lead me away from thinking that, is the Invoice number for the cancellation invoice is from around the same number range as the invoice it canceled.

It can’t be that the cancelation invoice was created way back in 2018, and just finally posted in mid Dec 2019. Because the Invoice Tracker for the cancellation invoice shows GL Trans dated (actually happened, not just the Apply date) 2018.