Have you looked at the actual punches in Job Tracker or LaborDtl table? Maybe the employee had a $0 rate? That should not affect the hours, but maybe? I think you need to look at the details to figure this one out. Just looking at summaries is not going to get you there.
The production labor rate is only used for quoting and estimating. When an employee logs into an operation, their labor rate from their employee record is used.
If I follow correctly, the actual Labor Detail records (BAQ) total the 94.4 hours as do the records that appear on the Job Activity screen. What do they show on the Production Detail Report? Is the Job Closing screen the only location where they aren’t 94.4?
It looks like the Production Detail hours is also showing the burden hours in place of the Total Production Hours. It is showing 20.78 instead of 94.64.
I’m not clear on why it actually captures burden hours / how it is calculating these hours. We don’t have burden rates set in the system and do not actively record burden hours when clocking onto operations.
The reason for the difference between burden and labor is that multiple people are clocking into the same operation. If you look at the top four labor transactions in your image, they add up to four hours for burden and each one of labor entries is four hours.
If the burden and labor hours should be the same change it on the resource group setting to Burden=Labor.
You can use your test environment to test what those do and print the production detail report and/or close the job and capture WIP to see what it does.