Shop floor time tracking in Microsoft Dynamics 365 Business Central means recording the setup and run time an operator spends on each production order operation, so that capacity ledger entries, production costs and payroll hours all come from the same captured record. Business Central provides the journals to post that time. What it does not provide is a fast way to capture it at the machine, which is why many shops still key hours in from paper travelers. This article covers where time lands in Business Central, why late keyboard entry produces poor data, what barcode capture at the work center changes, and how captured time compares against routing estimates.
Where does operation time live in standard Business Central?
Operation time in Business Central becomes a capacity ledger entry, posted through the Production Journal, the Output Journal or the Capacity Journal. Microsoft Learn describes the first of these plainly: “The Production Journal page provides a single place to record the components used, quantities produced, scrap, and operation time for a released production order.” When you post it, “time spent posts as capacity ledger entries,” as the Microsoft Learn page on registering consumption and output puts it.
The estimate side comes from the routing. Each routing operation carries four time fields, and Microsoft Learn notes that “Setup time is calculated per production order, whereas run time is calculated per produced item” on the routing creation page. Those fields, multiplied by the work center or machine center cost rate, produce the expected capacity cost on the production order.
The Capacity Journal handles time that belongs to a work center but not to an order. Microsoft Learn gives the example that “maintenance work must be assigned to capacity, but not to a production order” on the post capacities page. Either way, the Capacity Ledger Entries page is where every recorded minute ends up.
Routing supplies the estimate, capacity ledger entries supply the actual, and the two can be compared. The weak point is how the actual gets there.
Why does keying shop floor time after the fact fail?
Keyed time entry fails because the person typing was not the person working, and the data arrives hours or days after the event. Operators write start and stop times on a paper traveler, a clerk enters them into the Output Journal at the end of the week, and the numbers are rounded to the nearest quarter hour because nobody remembers otherwise. Three problems follow.
- Rework and non-productive time disappear. An operator who hands a part back to a colleague for a fix rarely writes that down. The rework hour lands inside the run time of whichever operation was open, and the root cause is never recorded.
- Overlapping work is impossible to represent honestly. One operator running a laser cutter and a saw at the same time, or a paint booth full of parts from six production orders, cannot be typed into a journal as one line per operation without inventing a split.
- Payroll and production drift apart. Hours for payroll come from a time clock; hours for costing come from the journal. When the two disagree, nobody trusts either.
The result is a variance nobody can act on, because the actual figure is itself an estimate. The post on barcoded time tracking pros and cons covers the fuller argument.
What changes when time is captured by barcode at the work center?
Barcode time capture changes the record from a recollection into an event log: the operator scans a badge, scans the operation barcode on the traveler, works, and scans the next thing. Shop Floor Insight, the Insight Works manufacturing execution system, works exactly this way. Each new scan closes the previous activity automatically, so there is no separate clock-out step to forget. Setup time and run time have their own barcodes, which keeps the two figures apart in the capacity ledger entry.
The operator does the same thing at the start of every activity, and the timestamp is recorded as it happens rather than reconstructed later. The shop floor time tracking for Business Central page describes the full terminal workflow; the points below matter most for time quality.
Can one operator run several jobs at once?
Yes. Shop Floor Insight supports one operator on several activities at the same time, and several operators on one activity. For batch processes such as paint booths, dip tanks, laser cutters and saws, an operator clocks onto several production order operations together, and on clock-off the captured time is split by quantity, by capacity (the routing’s expected time), equally, or applied in total to each order. The Auto-Split Behavior is set on the Shop Floor Work Center, and the automatic time splitting scenarios article in the knowledge base shows the configuration for each rule. Time splitting applies to time recorded against production orders.
The split method is a real decision. Applying the total time to each order is right only when the machine genuinely runs each order for the whole duration.
How are breaks, rework and non-productive time recorded?
Breaks are deducted automatically according to the shift pattern, and rounding of start, stop, run and setup times is configurable per shift. Non-productive activities such as cleanup, first aid, toolbox meetings and waiting on material get customer-defined codes, so they appear as their own lines rather than inflating an operation. Rework is captured with a rework code plus a root cause code, and the time lands on the correct production order and operation flagged as exception time.
That root cause field is where the value sits for a production manager. Once rework time is separated and tagged, the question of whether the cause is drawings, sales promises, material or equipment has data behind it. Midnight-crossing shifts and early clock-ins are also handled.
How do captured hours reach payroll and the general ledger?
Captured time reaches payroll through an approval worksheet in Business Central, then a configurable CSV export; it reaches costing through normal posting of the time card lines. The shop floor client itself cannot post. The knowledge base puts it this way: “use the Business Central interface with a full license to approve and post time, consumption, and output.” The Time Card Approval worksheet validates as soon as it opens, highlights cards and lines with problems in red, and lets the approver correct time in place, re-validate, and approve. The time card approval article walks through that page and the optional Shop Floor Insight Approver role center.
Overtime is calculated daily and weekly through a suggest, accept and carry-out sequence, and the adjustments are written as separate double-entry lines that never alter the original captured record. The daily time report for the payroll administrator is an Excel-friendly summary by employee group and pay code, and the CSV export carries approved hours to the payroll system.
One configuration edge case is worth knowing before rollout. A supervisor who should see only the time cards of their own employees cannot hold the Post permission in Shop Floor Insight. With Post on, the supervisor sees every employee’s time cards, although the approval worksheet offers an Only Show Managed Employees filter. The supervisor time card visibility article explains the Reports To and Manages setup, and notes that posting is normally an accounting or payroll role rather than a supervisor’s. Plan the approval chain around that split.
How does actual time compare against the routing estimate?
Once time is captured at the work center, the comparison becomes a query against real data instead of an argument. The production order carries the expected capacity cost from the routing; the capacity ledger entries carry what happened. Business Central’s Production Order Statistics report shows expected and actual cost side by side with a deviation percentage, and it can be run on released orders before they finish.
Shop Floor Insight adds two things. On the terminal, work instructions show estimated, actual and current time and quantity, so the operator sees the gap while the operation is still open. In Business Central, every time card line, posted or unposted, sits in one table readable through analysis mode, Excel or Power BI. For a review of operation times across finished production orders, including standard deviation per operation, the routing analysis for Business Central app reads the same captured data.
| Aspect | Keyed entry from paper travelers | Barcode capture at the work center |
|---|---|---|
| Timestamp source | Operator memory, transcribed later | Scan event as it happens |
| Setup vs run | Often blended | Separate barcodes |
| Several jobs at once | Manual split, if any | Rule-based split by quantity, expected time or evenly |
| Rework time | Usually hidden in run time | Rework code plus root cause code |
| Breaks | Estimated | Deducted by shift pattern |
| Payroll hours | Separate time clock | Same captured lines, approved and exported |
| Variance analysis | Estimate against estimate | Estimate against recorded actual |
What does Shop Floor Insight require to run?
Shop Floor Insight has two parts, and one of them lives on your network even when Business Central runs in the cloud. The knowledge base is direct about it: “Shop Floor Insight has a Business Central app component and a separate installer for an on-premise component for barcode scanning.” That component is a Windows service; the shop floor service installation article walks through downloading the installer from the Shop Floor Setup page, running it on a dedicated Windows server, and binding the production and sandbox service ports. Terminals talk to that service over the local network rather than to Business Central directly. How many service instances a multi-company or multi-time-zone site needs is a question to settle with your partner during install planning.
Terminals run in Chrome or Edge on Windows, Android or Chrome OS devices; the before you begin article states that “iOS is NOT supported, including Apple computers and iPads.” Production order time capture needs Business Central Premium, while job and job task time capture does not. Microsoft licensing is separate: a Business Central device license can cover a scanning station, and the app page lists Device, Essential, Premium and Team Member as compatible license types. Insight Works licenses the app per employee tracking time, not per terminal. For the broader framing, see why Shop Floor Insight fits as an MES.
FAQ
Can one operator run several jobs at once in Shop Floor Insight? Yes. An operator can be clocked onto several activities at the same time, and several production orders can be scanned into one batch activity with the time split by quantity, by expected time, evenly, or applied in full to each order.
How do I compare estimated vs actual run times gathered from routings and shop floor capture? Run the Production Order Statistics report in Business Central for the expected against actual cost with a deviation percentage, or query the capacity ledger entries directly. Shop Floor Insight shows estimated, actual and current time on the terminal, and Routing Analysis reviews operation times across finished orders.
Does the shop floor terminal post time directly to Business Central? No. Captured lines wait in an approval worksheet, and a user with a full Business Central license approves and posts time, consumption and output.
Which Business Central license do I need for production time capture? Production orders require Business Central Premium. Time against jobs and job tasks does not. A Business Central device license can cover a scanning station, and approving and posting needs a full license in Business Central.