Capture COS/WIP Activity ran in error for 7/1/22-7/6/22 when I meant to run 6/1/22-6/30/22. Now when I try to run 6/1/22-6/30/22, a message says that 6/1/22 is earlier than the last apply date of 7/1/22.
Earliest apply date is a form where you can set the earliest date people are allowed to post transactions to. Someone in your finance department would be setting this to 7/1 to close June to new transactions.
This setting can be changed back and forth as many times as you need to, so you should be able to change it to 6/1, post June’s COS/WIP, and then change it back to 7/1.
2 Likes
This now allows me to run 6/1/22-6/30/22 again. Thank you! No one manually changed this to 7/1, the system must have done it when I accidentally ran capture from 7/1-7/6/22.
I wonder now if I run capture from 6/1/22-6/30/22 will it include those July entries in June. Our IT says not to change it because “there was so much more to changing the earliest apply date that could impact financials”. Not sure what changing the earliest apply date to 6/1 could negatively impact June that we don’t want since we’re still closing it, but maybe not worth messing with it more.
Maybe a tangent, but you have the option in the capture screen to “capture outdated transactions” (aka before the month you are supposed to capture). It will post them in the month that all other transactions are posting.
Definite tangent - very sweet profile picture. 
1 Like
Running the capture for 6/1 - 6/30 should not capture any July transactions. Changing the earliest apply date will allow others to enter transactions (shipments, receipts, adjustments) for that earlier period, but you will need to change it if you want to post COS/WIP to June. That said, I would defer to your head of finance before changing the earliest apply date. There may be customized processes your company has in place that depend on the earliest apply date not going backwards.
2 Likes
Thank you for your reply. I do check this every time I run capture. I was worried the July transactions would post in June but that doesn’t seem to be the case.
You have been a life saver. Our company is still working on implementing clear procedures on closing modules and how this affects other processes, plus I’m new to Epicor.
So here is what happened, I accidentally ran capture from 7/1-7/6 (did not ck outdated transactions). This was a total fluke; don’t ask how it happened).
Then, when I went to run 6/1-6/30 correctly, it gave me the message that the earliest apply date was 7/1 (what??) I figured this happened because I had run capture for July in error. BUT this wasn’t the case. The earliest apply date, like you mentioned, was changed by the controller when I asked her to “lock inventory” because last period I had to reconcile the fixed asset account multiple times as transactions kept trickling in. She didn’t know she had to close it, or she normally closed it after we finished closing the month completely. So, now she agreed she would change the earliest apply date back to 6/1 to allow me to run capture thru June. I do not believe this will make the July transactions post in June as “outdated” transactions would be prior to June and I will run capture only thru 6/30. Anyway sorry for the long story, but wanted to close this thread and maybe help someone else who may make the same mistake. Thanks again everyone!
1 Like