How Long Month End Close Takes Across Plant Operations and What the Benchmarks Show

A supervisor on second shift holds four operators over to finish a run that fell behind after a changeover. The hours are real, the output is real, and the line hits its number. What does not happen is anyone attaching a reason to those hours, so three weeks later a cost center shows labor variance that nobody on the floor can explain from memory, and finance keeps the period open while two people rebuild a Thursday night from punch records and a production log. Nothing failed in the plant. The close failed instead, and it failed for a reason that was created during the period rather than after it.

Month end close gets treated as a finance calendar item, which is why the fix is usually looked for in accounting workflow. The duration, though, is largely set by how quickly plant operations can hand over labor actuals and production totals that hold up under review. The benchmark ranges below are useful mainly as a diagnostic: if your close sits in the long half of the distribution, the reason is almost always identifiable at the shift level, and it repeats every month until someone changes how labor data gets captured while the work is happening.

What Month End Close Requires from Plant Operations

The plant's contribution to close is narrow but unforgiving. Finance needs labor actuals allocated to the right cost centers, output totals by line and product, and overtime charges that carry an explanation, and it needs all three to agree with each other before anything can be posted. Everything else in the close depends on those inputs being settled.

The sequence is straightforward on paper. Raw punches come out of the time clocks, supervisors reconcile them against the schedule that was actually run rather than the one that was published, cost center owners sign off on hours and premium pay, and finance posts. In practice the second step carries the weight, because the schedule that was published on Friday is rarely the schedule that ran on Tuesday. Absences get covered, a qualified operator gets moved to a different line for half a shift, a maintenance window slides, and each of those adjustments changes where hours belong.

Any gap in that chain pushes the close window out rather than absorbing it. When labor hours are missing a cost center, when overtime appears without a documented cause, or when output totals do not tie to the hours charged against them, finance cannot resolve the discrepancy from its own systems. It has to send the question back to the plant, wait for someone who was there to answer it, and hold the period open in the meantime. A single unexplained cost center can carry the same delay cost as a dozen of them, because the review cycle, not the volume of errors, sets the clock.

Benchmark Ranges for Month End Close Duration

APQC's cross-industry benchmarking of roughly 2,300 organizations puts the median monthly close at 6.4 calendar days, measured from running the trial balance to completing the consolidated financial statements. The top quartile finishes in 4.8 days or less, and the bottom quartile needs 10 days or more. Those figures span industries rather than isolating manufacturing, so treat them as a reference point instead of a plant-specific target. The spread matters more than the median: two plants running comparable product with comparable headcount can sit a full week apart on close duration without either of them being badly managed.

What separates the halves of that range is not accounting sophistication. Plants in the longer half are almost always collecting labor data manually after the fact, pulling punch detail into offline workbooks, comparing it by hand against production records, and rebuilding the story of the period from documents that were never designed to agree with each other. Every one of those steps is serial, every one requires a person who remembers the shift, and every one is a place where the close stops while somebody waits for an answer.

The single best predictor of where a plant falls is how quickly it can deliver confirmed labor and production actuals. Confirmed is the operative word. Plants that can produce hours by cost center, overtime with attached causes, and output totals that already reconcile tend to close in days; plants that produce those numbers only after a reconciliation project tend to close in weeks. Treat the top quartile figure as evidence that a fast close is achievable rather than as a target to impose on a plant whose data collection has not changed, since compressing the finance calendar without changing what arrives from the floor just moves the pressure onto supervisors during the busiest week of the month.

Where Plant Operations Loses Days During Close

Three failure modes account for most of the lost time, and they are specific enough to check against your own last close. 

The first is overtime that was never captured at the shift level. When hours are approved verbally on the floor and only appear later as a payroll total, someone has to reconstruct which line, which cost center, and which cause produced them, and that reconstruction routinely adds one to two days to the close. The reconstruction is also expensive in a way that rarely shows up anywhere: the only people who can do it are supervisors and senior operators, so the hours spent on that archaeology come out of the most experienced time in the building.

The second is a mismatch between MES counts and what the floor recorded. Once the two disagree, finance cannot post either number, and the plant enters a reconciliation loop where operations verifies counts, finance re-checks the variance, and both sides wait on the other. Facilities have gotten substantially better at instrumenting equipment, which makes the asymmetry sharper: machine data is often current to the minute while the labor charged against that machine is still being assembled by hand.

The third is labor hours that split across cost centers mid-shift. Time clock systems record when someone worked, not which product line absorbed the cost after they were moved at 2 p.m. to cover a short crew, so the reallocation is manual by default, and it depends on someone recalling a decision made under pressure three weeks earlier.

These do not stay in their lanes. A period with heavy overtime is usually a period with unplanned shift changes, and unplanned shift changes are exactly what create mid-shift cost center splits and count discrepancies, so a plant that had a hard month gets all three failure modes at once. The months when the close matters most to the business are the months when the close takes longest.

How Capturing Labor Actuals During the Period Affects Close Speed

The useful way to think about close duration is that it measures how much of the period has to be reconstructed. A plant that tracks labor actuals against plan as the shifts run has already answered the questions finance is going to ask, because the delta between planned and actual hours was visible the day it happened and was explained while the reason was still fresh. A plant working from disconnected systems has to rebuild that same delta retroactively, and the rebuild is where the days go. The accounting steps themselves are not slow. Labor is the cost line with the most transactions behind it in most plants, and it is the one most often reconstructed after the fact rather than captured as it occurs.

Reducing the reconstruction comes down to capture: hours, coverage decisions, and overtime causes recorded where the decision is made instead of inferred later. Unplanned overtime matters most here, because it is the input that generates the most allocation work at close. Jetson connects operational performance to financial outcomes, reconciling labor actuals against plan as the shifts run and attributing hours and overtime to the right cost center and cause while the reason is still fresh. Because the delta between planned and actual is captured and explained during the period, finance is validating at close rather than reconstructing, and fewer premium hours arrive unexplained.

None of that requires replacing the systems of record. Jetson integrates with the HRIS, time clocks, ERP, and MES a plant already runs, which is the relevant point for close speed: the time clock remains the source of hours and the MES remains the source of counts, while Jetson keeps plan and actuals reconciled against them during the period rather than after it. Jetson's implementation team gets customers live in about four weeks, though how quickly the numbers tie out depends on how clean the underlying data already is.

Industry Differences That Shift the Benchmark

Comparing your close to a benchmark only works if you compare against a similar operating model, because several structural factors move the range independent of how well the plant is run.

Shift structure is the largest. Continuous production operations carry high shift change frequency, and every handoff is a transaction that has to be attributed to a cost center, so a 24/7 plant generates several times the reconciliation volume of a single shift discrete manufacturer running the same headcount. The discrete plant may look like a strong close performer when what it really has is fewer boundaries to reconcile.

Regulated process industries add a verification step that does not exist elsewhere. Where labor hour tracking is subject to regulatory requirements, the plant has to confirm compliance before finance signs off, and that confirmation sits in sequence rather than in parallel, so a close that is otherwise fast still carries the extra day.

Union environments add a different kind of work. Contract classifications and premium pay rules mean that overtime crossing a classification boundary is not a single rate calculation but a reconciliation question, and it has to be resolved correctly the first time because the consequences of getting it wrong extend past the ledger. Plants with multiple classifications on the same line should expect their realistic floor to sit above the top quartile figure, and should measure improvement against their own trend rather than against a benchmark drawn from operations with simpler pay structures.

KPIs Plant Operations Should Confirm Before Handing Off to Finance

The fastest available improvement in most plants is not a new system but a stricter handoff. Confirming four numbers, each with a documented source, pre-answers most of what finance would otherwise send back:

• Total labor hours by cost center, reconciled to time clock records for the full period including mid-shift moves.
• Overtime hours with a reason code attached to each block, not a period total.
• Output totals that already tie between the MES and what the floor recorded, with any remaining variance explained rather than left open.
• Labor hours tied to downtime events, which is the metric most often missing at handoff and the one most likely to generate a question days later.

Overtime without reason codes is the reliable trigger for rework, because finance cannot classify the cost and operations is the only place the answer exists. A handoff that arrives with reason codes already attached shortens the finance review cycle directly, since the review becomes verification rather than investigation.

Questions Plant and Finance Leaders Can Ask After Reviewing the Benchmarks

Take the last close and work backward through these together, since the answers point at specific system and process decisions rather than at effort:

• Where did the close first stop, and which data source was it waiting on?
• Was overtime captured at the shift with a cause attached, or reconstructed after the period ended?
• How many hours of supervisor time went into reconciliation, and what did those hours produce that a system could not?
• Do the schedule and time clock data connect automatically, or does someone move them by hand?

The last question tends to be the structural one, since top quartile closes usually belong to the plants where plan and actuals were already connected during the period. If the answers point to the same delay you saw last month, that is the place to start before the next close. Request a demo to walk through how your labor and production actuals would reconcile during the period.