- Feature
- Prevent shop-floor registrations after daily calculation
- Availability
- Generally available in Supply Chain Management 10.0.49 (enhancement)
- Industry focus
- Unionized manufacturing plants
In a unionized plant, time and attendance data is more than an operational record. It feeds pay, overtime, premiums and allowances agreed in collective agreements, and it is one of the first things workers and their representatives check when something looks wrong. Accuracy and fairness in that data are central to good industrial relations.
The industry challenge
Dynamics 365 supports shop-floor time and attendance, with workers registering clock-ins, job starts and stops through the production floor execution interface. Each day, a calculation step processes those registrations into pay-relevant time, which supervisors review and approve before it flows towards payroll.
The weak point has been registrations made after that calculation has run. If a worker or terminal records time for a day that has already been calculated, the calculated result and the raw registrations no longer agree. The late registration may be missed, double-counted or require manual correction. Each correction is a potential pay error, and pay errors in a unionized environment quickly become grievances.
What Microsoft delivered in Supply Chain Management 10.0.49
Supply Chain Management 10.0.49 prevents shop-floor registrations for a day after the daily calculation for that day has run. If a registration genuinely needs to be added, a supervisor can choose Undo calculation for today, add or allow the registration, and then recalculate.
The calculation stays consistent with the registrations behind it, and late changes go through a deliberate supervisor action.
Where the value shows up
| Business area | Impact |
|---|---|
| Pay accuracy | Calculated time always reflects the registrations behind it |
| Industrial relations | Fewer pay discrepancies that could lead to grievances |
| Supervisor control | Late changes require an explicit undo and recalculation |
| Payroll | Cleaner data flowing to payroll, with fewer manual adjustments |
| Audit trail | A clearer record of when and why calculations were reopened |
A worked scenario
(An illustrative example.) A metal fabrication plant runs three shifts under a collective agreement with overtime and night-shift premiums. The day shift supervisor runs the daily calculation at the end of the shift and approves the results.
Later that evening, a worker who forgot to clock off a job tries to correct it from a terminal. Previously, that registration would have been accepted, leaving the approved calculation out of step, and the payroll team would only have spotted the discrepancy after the pay run. Now, the registration is blocked. The next morning, the supervisor reviews the request, undoes the calculation for that day, adds the correction and recalculates, so the worker is paid correctly and the change is visible.
Adoption considerations
- Agree the timing. Decide when the daily calculation runs relative to shift ends so genuine registrations are not blocked.
- Define a correction process. Set clear rules on who can undo calculations and how requests are made.
- Brief workers and representatives. Explain the change and the correction route to avoid confusion.
- Check terminal messages. Make sure workers see a clear message when a registration is blocked.
- Monitor undo frequency. Frequent undos may signal a timing or training problem.
The bottom line
In unionized manufacturing, pay accuracy underpins trust. Blocking registrations after the daily calculation, with a controlled supervisor override, keeps calculated time consistent with what was registered and makes late changes deliberate and visible. It is a small enhancement with a real effect on payroll integrity and industrial relations. An experienced Dynamics 365 manufacturing adviser can help you align it with your shift patterns and agreements.
Source: Microsoft: What's new or changed in Dynamics 365 Supply Chain Management 10.0.49