Labor Transactions Posted to GL without running Capture/Post

Our accounting team usually runs the capture COS/WIP process at the beginning of the month so that we are able to update labor records.

We are suddenly seeing where the majority of our labor transactions are showing posted, but the COS/WIP process has not been ran since 10/1.

Is there another process that someone may have ran that would cause these to post?

1 Like

Since no one has answered yet, I’ll just chime in with: no, not that I know of.

Interesting point - I don’t know of a way to find out what posted something. But AFAIK, everything has only one avenue anyway.

My tribal knowledge says:

  • Anything in PartTran (except ADJ-PUR?) is posted by Capture COS/WIP
  • Labor also posted with the Capture
  • Everything else is posted by the user with the “Post” button
    • AP anything (invoices, checks, etc.)
    • AR anything (invoices, cash receipts, etc.)
    • GL anything (Bank recon, manual journal entries, etc.)

Processing Project Revenue Recognition has an option to run Capture WIP/COS, but I can’t remember if running it through Revenue Rec. also updates the “Last Run” information shown in Capture COS/WIP’s screen.

LaborDtl has WIPPosted and PostedToGL fields. If you’re lucky and capturing change logs on those fields, you could see who and when the posting happened. You could also probably use Chart Tracker to find the GL postings and see if those have information about which user account posted the transactions.

1 Like

I believe they ran the capture project revenue recognition. We have the menu usage tracker extended solution and I had already looked at what screens the accounting team may have used recently and did notice one user opened the project revenue recognition screen multiple times.

Which would mean it does not update the last run field on the COS/WIP screen, because that still says it was last ran 10/1.

2 Likes

Didn’t have changelogs enabled for those columns, but I’ll look into turning them on.

I was able to check the SysTaskParam table that shows the Capture COS and WIP option was checked when they ran the process. Plus, the timing of when that process was run lines up with when I stop seeing posted laborDtl records.

1 Like

Glad you figured it out and nice detective work!

So are you seeing that revenue recognition captured ALL labor? Or just labor associated with Projects? (Or is there no difference where you work?)

We had a plant manager run the process once 6+ years ago with no Project ID filters and it posted all labor. At the time, we didn’t have any project jobs created.

1 Like

Looked back at the parameters that was used and they only selected a single project ID, but that project is only shown on about 5 open jobs. It definitely posted labor for other projects. Strangely it didn’t post all labordtl records though. I do have some on 10/9 and 10/10 that did not post.

1 Like