WIP Reconciliation and Ageing Reports for Apparel Production

When the WIP report and the floor disagree

A sewing line reports 572 garments in progress. The floor count finds 560. Planning wants to release another bundle. The supervisor thinks twelve garments are missing. Before anyone changes the stock figure, a handler checks a trolley beside inspection. It holds the twelve pieces. The ledger was right; the count missed a location.

This is a hypothetical example, but it shows what a useful WIP report must do. It should explain where unfinished work sits, how it arrived there, and what must happen next. A single input-minus-output figure cannot answer all three questions.

Work in progress, also called work in process or WIP, changes as garments move through cutting, sewing, washing and finishing. Some units wait for a machine. Others need repair, approval or transport. They still belong in the report even when no one is working on them.

The purpose of reconciliation is to connect those physical units to a clear record. Once the quantities agree, an ageing report can help the team find stalled work. An unreliable balance can hide losses. It may also prompt the team to release work that the next stage cannot use.

Define what the report counts

Start with the process boundary. One report may begin when complete cut sets enter production. Another may start when fabric enters cutting, so their balances will differ. Both can be useful if the heading and units make the boundary clear.

The Lean Enterprise Institute’s inventory definitions classify stock by where it sits and why it is there. In-process stock includes units needed within the process, including those in machines. Applying that idea to apparel means looking beyond the bundles waiting between departments.

In the worked examples below, complete cut garment sets mark the start of WIP. Each set is ready for sewing. It ends when packed goods pass the required checks and enter finished-goods stock. Washing includes the associated outward and return transport. All quantities are hypothetical.

This boundary excludes uncut fabric and unfinished component sets. Those items still form part of the factory’s inventory and need their own records. The chosen report simply cannot add metres of fabric, loose panels and garments into one meaningful piece total.

A bundle is a container, not a fixed unit

A bundle ticket may state twenty garments, but a split bundle may now contain seven. Counting tickets and multiplying by twenty creates stock that does not exist. Record the actual remaining quantity whenever work splits, combines or moves.

The same care applies to component counts. Forty sleeves are not forty shirts. Even twenty matching sleeve pairs cannot become twenty complete shirt sets if the fronts or backs are missing. Keep counts for each part until the garment set is complete. Each part must stay linked to its intended order.

If an operation processes garment parts in separate streams, retain their shared set identity. Count each garment once in the factory total. Counting it in both the sleeve and body streams would double the stock. A routing record can show work in several places while the unit ledger counts each garment only once.

Use a balance equation that includes every valid movement

For a defined stage and reporting period, use:

Closing WIP = opening WIP + accepted inputs + returns in − transfers out − scrap removed ± approved corrections.

The words around the formula matter. “Opening” means the agreed closing balance from the prior period. “Accepted inputs” means goods received under the agreed handover rule. They have crossed into the reporting area. “Scrap removed” means a recorded disposition, not any item that has failed inspection.

An item awaiting a decision remains in a hold or rejected status within WIP. It leaves WIP only through an authorised transaction that moves it outside this process or into a non-WIP status. Microsoft’s scrap-posting guidance makes this clear. Scrap has its own record and does not increase good output.

Approved corrections should remain visible. A missing transfer, wrong unit conversion and physical shortage have different causes. Posting all three as “adjustment” may make the totals agree while leaving the same faults ready to recur.

A complete four-stage reconciliation

Consider one order at a daily cutoff. Each row uses the same garment-unit basis. Each receiving stage has accepted its ordinary transfers before cutoff.

Sewing's 1,020 inputs comprise 1,000 normal transfers from cutting and twenty returns from finishing. No other stage receives a return in this example.

Finishing transfers out 1,140 garments. Of these, 1,120 enter finished goods after acceptance; twenty return to sewing. The twenty appear as returns into sewing, so they do not create extra factory WIP.

The sewing calculation is:

640 + 1,000 + 20 − 1,080 − 8 = 572 garments.

The whole-boundary check removes internal transfers. Each one leaves one stage and enters another, so they cancel out. Opening stock is 1,840 garments. New complete cut sets add 1,200, packed output removes 1,120, and recorded scrap removes 27.

Factory process balance = 1,840 + 1,200 − 1,120 − 27 = 1,893 garments.

This agrees with the four closing balances. If it did not, the team would first inspect transfer pairs, cutoff treatment and unit definitions. Adding more columns would not repair a broken movement record.

Keep rework from creating phantom production

A garment can pass through an operation twice without becoming two garments. This is the most useful rule when designing rework records.

Suppose thirty pieces within sewing move to a repair table. Twenty-four are repaired and six remain on hold. If that table sits within the sewing boundary, none of these moves changes total sewing WIP. They change the location, status and work required.

Recording the thirty as fresh sewing input would overstate receipts. The twenty-four repairs may already have an output record. Counting them as new output could count the same garments twice. A repair transaction should link back to the original units or traceable bundle.

Cross-stage rework is different. The twenty garments returned from finishing in the worked example cross a stage boundary. They therefore need a matched transfer out of finishing and return into sewing. The factory total remains unchanged, while each stage’s responsibility changes.

Oracle’s rejected-quantity workflow provides a useful software example. Rejected work can return to a ready state for repair or move to scrap. Its reasons and history remain in the record. That distinction helps avoid treating every reject as a permanent loss.

The report should also distinguish repair workload from repair stock. Six held garments may need several operations. Those operations need labour, but the physical count remains six. ApparelDiary’s guide to rework and inspection capacity helps plan that extra work.

Make handover and cutoff rules explicit

Two departments may both have correct local records and still produce a wrong combined report. This happens when they use different handover times.

Imagine a twelve-piece transfer dispatched at 17:58 and received at 18:06. The report closes at 18:00. The sender may remove it at dispatch, while the receiver adds it on receipt. Without an in-transit balance, the pieces vanish for eight minutes.

There are two workable approaches. The sender can keep responsibility until the receiver accepts the goods. A dispatched status shows where they are. Another approach moves the goods into a named transit account at dispatch. That account clears on confirmed receipt. Choose one approach for the movement and apply it consistently.

The truck driver or handler does not become the legal owner of the garments. Operational responsibility, physical custody and legal ownership are different fields. The reporting design should state which one each balance represents.

A transfer record needs the order, actual quantity and unit. Add the source, destination, event time and a unique reference. It also needs the person or system confirming receipt. The GS1 traceability framework separates tracking events from the data describing them. That is a useful basis for deciding what a handover must record.

Use event time for the physical movement and retain posting time separately. A late entry made the next morning should not silently appear to be a new physical movement. If it changes an earlier report, retain the original snapshot and explain the correction.

Preserve identity when bundles split

Suppose bundle B17 contains 24 garment sets. Eighteen move to the next operation and six remain on hold. Create linked child records, or reduce the original quantity and record the separate movement. Either design must leave 24 active units in total.

If both child records are created while B17 remains active at 24, the report now shows 48 units. Nothing physical has doubled; the data has counted the parent and its children together. Retire or close the parent record when its quantity has been fully allocated.

Keep order, size and colour identity through the split. A correct overall total can still hide a shortage in one size and an excess in another. A repair return may cover only part of a bundle. Its reference should identify that part, leaving the other garments closed.

Reconcile work held outside the factory

Sending garments to a washing contractor does not make them irrelevant to production control. The report needs to show both the outstanding quantity and its last confirmed location.

In the worked example, the washing balance is 476 garments:

400 opening + 1,080 sent in − 1,000 accepted back − 4 recorded scrap = 476.

The washing coordinator then reconciles that balance to custody records.

These categories are mutually exclusive at the cutoff. A garment on the return vehicle is not also counted as waiting at the contractor. The transport document and supplier record should carry the same lot reference, even when the shipment has been split.

A supplier’s “completed” figure is not always the factory’s “received” figure. The difference may be goods awaiting dispatch, goods in transit or a disputed count. Ask which event the number represents before calling it a shortage.

For a partial receipt, preserve the original dispatch quantity and record each return against it. Keep the dispatch line intact. Replacing it with the latest balance removes evidence needed to investigate an old difference. Keep authorised losses and accepted returns separate, with supporting records for both.

Close an order without forcing its WIP to zero

An order can meet its shipped quantity while extra units remain in production. It can also show a zero balance because someone removed unresolved stock during administrative closure. Neither situation proves that all materials and garments have been accounted for.

Before closing the ledger, account for the authorised cut quantity. Match it to accepted finished output, recorded scrap, returned material and units still held. Explain any extra cut allowance through actual records. The allowance is a planning quantity; it does not authorise unexplained loss.

Consider an order with 2,040 complete cut sets admitted to the process. Its final records show 2,000 accepted garments, eighteen scrapped units and twenty-two units still on hold. The quantities reconcile, but production closure is incomplete. The twenty-two units need an approved decision about their future. Keep their location on record until that decision is carried out.

An approved transfer to another order must preserve the original reference and confirm that the new use is permitted. The garments may look suitable for reuse, yet the rules may prevent it. Check label changes, customer limits and material ownership. The production team should not solve a reporting problem by assigning goods to an unrelated order.

After closure, block routine entries against the old order. Any reopening or correction needs approval. Keep the closing reconciliation. A later return, supplier claim or count finding can then link back to the same evidence.

Investigate a difference without hiding it

A physical check should cover every location within the boundary. Include machines, tables and trolleys, plus repair areas, quality holds and dispatch lanes. It should also identify goods belonging to another order or stage.

In the opening example, expected sewing WIP is 572 and the first count is 560. The apparent variance is:

Count variance = physical count − book balance = 560 − 572 = −12.

Finding twelve garments on the omitted trolley brings the count to 572. There is no reason to post an inventory gain or loss. The corrective action concerns the count map and handover routine.

Another case may end differently. A repeated count could confirm that twelve units are absent, with no supported movement explaining them. That difference needs investigation and the required approval before a stock adjustment. A convenient matching number on an unrelated order is not evidence of a transfer.

Useful checks follow the evidence trail. Start with the last agreed balance and movement references. Check bundle splits, scrap records and receipts still due. Look for duplicate scans as well as missing scans. An interface may retry a transaction that already succeeded. If the system counts it again, WIP becomes too high.

Keep a discrepancy log with the amount, suspected cause, owner and resolution. If the cause remains unknown at the reporting deadline, show the unresolved quantity separately. A total is less useful when it hides an unknown quantity. Show what is confirmed and what still needs checking.

Add age only after the quantity makes sense

Ageing asks how long the remaining work has been in a defined condition. It needs a clock with a named starting event.

Three clocks answer different questions. Total process age begins when the garment first enters the report boundary. Stage age begins when the current stage accepts it. Hold age begins when a specific block prevents progress. A transfer to another rack should not reset all three.

For the 572 garments remaining in sewing, assume the following stage-age distribution at cutoff:

The quantity aged at least 48 hours is 142 garments, or 142 ÷ 572 × 100 = 24.8%. The buckets are chosen for this example; they are not industry limits or proof that any particular garment is late.

Use calendar hours when the question concerns elapsed customer lead time. Use a stated working calendar when the question concerns available production time. A weekend changes the interpretation, so the report must not switch between these clocks without warning.

Understand how the software assigns age

A system may assign age from transaction layers rather than the physical history of each garment. Microsoft’s inventory-ageing guide gives one example. Its report places receipts in time periods and deducts issues using FIFO logic. Its examples also show how warehouse grouping affects the displayed distribution.

That method is valid for its stated purpose. It does not prove how long a particular garment has waited. Test the report with a small known movement history before using it to chase individual bundles.

Where physical age matters, retain original lot dates through splits and transfers. If lots with different ages are merged, preserve their sublot quantities or state the allocation rule. An average date can conceal a small quantity that has been waiting much longer than the rest.

Turn old stock into specific actions

An ageing report should lead to a question that someone can resolve. “Reduce old WIP” is too broad to direct work on the floor.

Suppose the oldest 52 sewing garments await approval for a label change. Another 200 garments are younger but must clear sewing today to meet an agreed washing slot. Age alone cannot choose the sequence. The team needs the block reason, approved due date, available capacity and consequences of delay.

For the label hold, the next action is to obtain a valid decision and record its scope. Moving the bundle to another table improves neither readiness nor age. For the washing slot, planning must check the time left for sewing and quality checks. The plan must allow all required controls.

Assign an owner to the next decision, not just to the department where the stock sits. A sewing supervisor cannot resolve a buyer approval that no one has requested. The buyer’s answer must also apply to the correct units and specification. The factory checks this before clearing the hold.

Reducing WIP then becomes a controlled operating change. ApparelDiary’s Kanban cutting-to-sewing guide addresses release limits. Reconciliation gives those limits a reliable stock basis. Further checks are needed to decide whether the current limit is right.

Keep the quantity report separate from inventory valuation

Two groups of garments can have the same quantity and different costs because they have reached different stages. A physical WIP balance is therefore an input to valuation, not a finished accounting calculation.

Where IFRS applies, IAS 2 addresses inventory cost and measurement at the lower of cost and net realisable value. Its cost guidance includes purchase and conversion costs. A piece-count report does not establish which costs are eligible, how they are allocated, or whether a write-down is needed.

Give finance the reconciled counts and evidence of each stage reached. Add ownership details and known quality holds. Identify customer-owned material and subcontract custody separately. Finance can then apply the entity’s accounting policies without treating every garment as fully complete.

The same restraint applies to delivery forecasts. Dividing one day’s closing WIP by one day’s output gives a rough snapshot ratio. It does not reveal the remaining work, bottleneck capacity or time needed for a held lot. Use the actual route and readiness conditions when promising completion.

A daily report people can rely on

The final report should show its cutoff, boundary and units before the stage balances. Each balance should start from an agreed figure and explain the recorded movements. It should match a defined set of physical locations.

Before replacing an existing report, run a small trial with one order and a known opening count. Include a normal transfer, a split bundle, a cross-stage repair, a scrap decision and a movement across the cutoff. Compare the expected result with the software or spreadsheet output after each event.

This trial tests the rules that matter. A report that adds clean rows correctly may still mishandle a reversed movement or a duplicate upload. Confirm that a correction leaves an audit trail and that reloading the same event does not add its quantity again. The trial should also show whether users can find held work without reading every transaction.

Alongside the balances, show old stock and goods on hold. Add unmatched transfers and count differences that still need checking. The action list can then focus on the few decisions that prevent work from progressing. The detailed transaction history remains available for investigation without overwhelming the daily meeting.

At the next cutoff, compare the result with the promised action. Did the held garments move after approval? Did the contractor return the agreed quantity? Did the same transfer gap recur? These checks make reconciliation a working control. The aim is to account for the goods and move them through production with clear decisions.

References

1. Lean Enterprise Institute. Inventory: position, purpose and work in process.

2. GS1. What is the GS1 Traceability Standard?.

3. Microsoft Learn. Post scrap manually in Business Central.

4. Oracle. Disposition of rejected quantities for a work-order operation.

5. Microsoft Learn. Inventory ageing report examples and logic.

6. IFRS Foundation. IAS 2 Inventories.