Manufacturing Process

Some Products Must Be Made

The operations planner in our furnishing story has another supply question. Charles River buys finished merchandise, but it also manufactures selected products. Supplying those goods means arranging components, production work, and employee time.

The question is how materials become finished goods, and how accounting explains the cost of that change. Follow the work from planning to completion and close. When you investigate a work order, use its own material, production, and accounting records to build the explanation.

The purchasing chapter established how components arrive in inventory. Manufacturing begins with a plan for using those resources. It then records production activity and distinguishes physical completion from the accounting work needed to close the order.

Prepare the Product and the Work

A product needs a component recipe and a sequence of production steps. The recipe is the bill of material, commonly called a BOM. It identifies the components used to make the selected finished good.

The sequence of steps is the routing. Each step belongs to a work center, the location or resource where that production work is organized. These definitions describe how the item is intended to be made. They do not establish what happened on a particular production order.

Planning considers expected demand, inventory policy, and available supply. A recommendation to manufacture then provides support for a work order, the record organizing production of an item. The work order has its own operations and execution schedule.

A recommendation is therefore an expectation or proposed supply action. The work order moves the story into execution. Detailed capacity planning and daily operation schedules answer different questions and are retained in the optional reference.

The operations planner must also consider components. Purchasing can help supply raw materials and packaging, but buying a component and issuing it into production are separate events. The receipt belongs to P2P, while its subsequent use belongs to manufacturing.

Issue Materials into Production

Warehouse staff issue components to the work order. The material-issue record identifies the movement from available component inventory into production.

Accounting calls the accumulated value still in production work in process, or WIP. In this dataset, a material issue increases WIP and reduces materials and packaging inventory. The components are no longer available stock in the same sense as goods still on the shelf.

The work order gives this movement a purpose. To investigate consumption, identify the selected work order, its issued lines, and their quantities and dates. A company-wide purchasing total cannot by itself explain what one work order consumed.

The production recipe supplies a comparison point, while the material-issue records supply execution evidence. A difference needs interpretation: establish the scope, quantities, and timing before describing it as waste or an error.

Support Production with People's Work

Production staff perform the work-order operations. Approved attendance and labor allocations support the explanation of employee time used in production.

Those records explain hours and their allocation. Payroll records employee earnings and obligations through its own cycle. PayrollSummary posts capitalizable manufacturing labor and related burden directly to Manufacturing Cost Clearing (1090). Manufacturing payroll in months with no capitalizable direct labor is recorded in Manufacturing Variance (5080). Nonmanufacturing wages and burden remain period expense. Separate factory-overhead and depreciation journals provide other manufacturing cost support.

This means the labor-support records and the inventory valuation method are related but distinct. Charles River's dataset remains standard-cost based. Recording actual hours does not turn every finished item into an inventory value calculated from the complete actual cost of that individual order.

You will follow approved time and payroll in the next chapter. For now, keep the handoff in view: production needs supported labor, payroll establishes employee cost and liabilities, and accounting uses the relevant cost support.

Complete the Goods

Production completion records finished goods becoming available in inventory. This is the handoff that allows completed products to support later customer fulfillment.

The model values the completion at standard manufacturing cost. Its accounting increases finished-goods inventory and credits the relevant WIP and manufacturing-clearing amounts. Manufacturing clearing helps connect the standard conversion amounts with the manufacturing cost support recorded through other events.

The practical distinction comes first: goods can be physically complete and available even while their work order awaits accounting close. To explain availability, inspect the completion evidence. To explain whether costs and residual balances have been resolved, inspect the close evidence.

A completed quantity is also different from a customer's delivered quantity. Completion brings goods into inventory, and a later shipment takes them out through Order-to-Cash. Those events have their own documents and dates.

Close the Work Order

Cost accounting reviews the work-order amounts and closes residual WIP and manufacturing-clearing balances. The resulting difference is recorded as manufacturing variance.

Completion and close can occur on different dates. A work order can therefore be physically completed in one period and closed in another. Combining them into a single event would obscure both the availability of goods and the timing of the accounting resolution.

A variance is a result to explain. It does not prove waste, misconduct, or an approval failure. Identify the cost basis, supporting events, and close timing before deciding what further evidence or action is needed.

This is also where the controller's company-wide view matters. Payroll support, factory overhead, and equipment depreciation may contribute to manufacturing accounting without being another physical production step. Their detailed treatments remain in the reference below.

Bridge an Event to an Entry

Predict first: for Lesson 9's work order 1, which event makes finished goods available, and which event clears the remaining material difference? Explain why releasing the order alone does not move inventory value.

Compare the events with their accounting evidence

Keep the event dates separate as you explain what was complete at January 31 and what remained to be closed.

Event and date	Evidence	Debit and credit effect	Remaining question
Release, January 5, 2024	WorkOrderID = 1	No direct ledger entry from the work-order record	Have components actually been issued?
Material issue, January 17	MaterialIssueID = 1, two lines	Debit 1046 WIP and credit 1045 materials, 754.29 each	How much issued material has standard-cost completion relieved?
Completion, January 25–26	ProductionCompletionID = 1 and 2	Debit 1040 finished goods 1,019.85; credit 1046 WIP 729.36 and 1090 manufacturing clearing 290.49	At January 31 the goods are completed; 24.93 selected WIP remains until close
Close, February 1	WorkOrderCloseID = 1	Debit 5080 manufacturing variance 743.16; credit 1046 24.93 and 1090 718.23	What supports the variance, and which conversion support is pooled rather than traceable to this order?

The issue, both completions, and close are complete event-voucher populations. The completion row combines the two completion vouchers. Follow the existing Lesson 9 evidence, then its optional reconciliation, to reproduce the amounts. Manufacturing clearing pools costs across work orders. The selected credits alone do not establish its company-wide balance or one order's actual overhead.

Follow the Manufacturing Responsibilities

How do Planning, Warehouse, Production, and Cost Accounting cooperate? Start with the supply need, follow release and execution, and then separate completion from close.

Expand the diagram for a larger view with zoom and pan controls.

Download editable Draw.io

Model scope: One work-order production and accounting-close pass; completion makes goods available before close.

Text description and database evidence

1. Planning reviews demand, supply, materials, and capacity support before a work order references its bill of material and routing.
2. Warehouse issues components into work in process. Production executes operations with recorded labor support.
3. Completion makes finished goods available at standard cost. Work-order cost close records a distinct accounting event.
4. A separate variance-review model proposes an analytical activity; it is not a gate that delays finished-goods availability.

Evidence tables: SupplyPlanRecommendation, WorkOrder, WorkOrderOperation, MaterialIssueLine, ProductionCompletionLine, WorkOrderClose, LaborTimeEntry, GLEntry.

Confirm keys and accounting sources in the Schema Reference and Posting Reference.

Planning rows do not prove authorization or execution. Labor analysis must distinguish operational support from payroll expense. Independent cost reconciliation and variance review are proposed controls rather than stored approvals.

Editable visual model in Draw.io XML; this is not executable BPMN XML. Notation and model library.

Read the model in three stages: prepare the work, make the goods, and resolve the accounting. The purchasing handoff supplies needed components, while the payroll connection supplies labor-cost support.

The model describes teaching responsibilities. Its lanes and recorded close fields do not establish an independently enforced release or variance-approval workflow.

Connect Production Events to Their Records

This map asks which records show that materials were used, goods were completed, and the order was closed.

Record and accounting evidence map

Expand the diagram for a larger view with zoom and pan controls.

Download editable Draw.io

Read the connectors and evidence boundaries

Planning supports a work order with separate material issue, operation, completion, and close branches. Labor entries support operations.

Line and path	Meaning	Evidence to check
r1 SupplyPlanRecommendation to WorkOrder	Stored FK path	WorkOrder.SupplyPlanRecommendationID → SupplyPlanRecommendation.SupplyPlanRecommendationID
r2 WorkOrder to MaterialIssue and lines	Stored FK path	MaterialIssue.WorkOrderID → WorkOrder.WorkOrderID
r3 WorkOrder to WorkOrderOperation	Stored FK path	WorkOrderOperation.WorkOrderID → WorkOrder.WorkOrderID
r4 LaborTimeEntry to WorkOrderOperation	Stored FK path	Labor support LaborTimeEntry.WorkOrderOperationID → WorkOrderOperation.WorkOrderOperationID
r5 WorkOrder to ProductionCompletion and lines	Stored FK path	ProductionCompletion.WorkOrderID → WorkOrder.WorkOrderID
r6 WorkOrder to WorkOrderClose	Stored FK path	WorkOrderClose.WorkOrderID → WorkOrder.WorkOrderID

Read each numbered connector with its evidence explanation. Reference paths are not a time sequence; analytical support and account effects do not create additional stored keys.

Each box identifies a record, source label, or interpretive context. Check dates and grouping before comparing operational support with postings.

Focused ER maps and table grains · Posting sources and account effects

Begin with the work order and follow each related event. The branches provide different kinds of evidence around the same order and cannot be treated as interchangeable measures of progress or cost.

Event	Accounting meaning in the published model
Planning recommendation and work-order setup	Support the intended work without directly posting its production cost
Material issue	Transfer component cost into WIP
Production completion	Recognize finished goods at standard cost
Manufacturing cost support	Connect labor and other manufacturing costs through their own postings
Work-order close	Resolve residual balances and recognize variance

Explain Completed Goods on an Open Order

Suppose the controller finds a completion dated before period end and a close dated afterward. Ask whether the finished-goods event was recorded and what remained unresolved in the work-order accounting.

Use the reporting date to explain both positions. The later close can explain the resolution of residual balances without implying that the goods were unavailable before it.

Likewise, a weekly capacity signal does not establish the date an operation actually ran. Use the record appropriate to the question: planning pressure, execution timing, goods availability, or accounting close.

Check Your Understanding

Must goods wait for work-order close before becoming finished-goods inventory?

No. Production completion establishes the finished-goods event at standard cost. Work-order close subsequently resolves residual WIP and manufacturing-clearing balances and records variance.

Does having actual labor-hour records make this a full actual-cost inventory system?

No. Actual labor support helps explain production and payroll-supported costing, while completion remains standard-cost based. State which cost basis you are using before comparing amounts.

Next Steps

Continue the company story: the production story depends on people's work. Continue to Payroll to follow that work from attendance and approval into employee pay and later liability settlement.

Investigate this process: complete Lesson 1, Lesson 2, and Lesson 3, plus the Excel or SQL setup, before the manufacturing cost-flow exercise. It follows one work order through its accounting events, with an optional account reconciliation extending that example.

Find analytical evidence. Browse Production and Planning queries and related reports. Use the Schema Reference for join keys and the Posting Reference for accounting effects.

Optional Reference

Return to these sections when you have a specific question or an assignment that uses the data. The chapter above can be read without opening a file.

Look up documents, accounting entries, and traceability fields

Core Tables and What They Represent

Process stage	Main tables	Grain or event represented	Why students use them
Planning and replenishment pressure	DemandForecast, InventoryPolicy, SupplyPlanRecommendation, MaterialRequirementPlan, RoughCutCapacityPlan	Weekly forecast, policy, replenishment signal, exploded component demand, and weekly load-versus-capacity tieout	Explain why manufacturing demand existed before any work order was released
Standard manufacturing design	Item, BillOfMaterial, BillOfMaterialLine, Routing, RoutingOperation, WorkCenter, WorkCenterCalendar	Product recipe, operation sequence, and available work-center capacity	Understand how an item is supposed to be built
Work-order release and schedule	WorkOrder, WorkOrderOperation, WorkOrderOperationSchedule	One production order, its operation sequence, and its daily scheduled hours	Review finite scheduling, execution timing, and open production activity
Component support and issue	PurchaseRequisition, PurchaseOrder, GoodsReceipt, MaterialIssue, MaterialIssueLine	Purchased support for missing components and the physical issue of material into WIP	Trace whether materials were available and when they were consumed
Labor support and cost traceability	EmployeeShiftRoster, TimeClockEntry, LaborTimeEntry, PayrollRegister, PayrollRegisterLine, GLEntry, JournalEntry	Approved attendance, labor allocation, summarized payroll recognition, and separate overhead and depreciation journals	Compare operational labor support with manufacturing accounting at its actual grain
Completion and close	ProductionCompletion, ProductionCompletionLine, WorkOrderClose	Finished-goods completion event and final variance close	Separate physical completion from accounting close and variance analysis

When Accounting Happens

Event	Business meaning	Accounting effect
Material issue	Components are moved from stock into work in process	Debit 1046 Inventory - Work in Process and credit 1045 Inventory - Materials and Packaging
Production completion	Finished goods are completed from WIP at standard manufacturing cost	Debit 1040 Inventory - Finished Goods, credit 1046 Inventory - Work in Process, and credit 1090 Manufacturing Cost Clearing
Work-order close	Accounting clears residual WIP and clearing balances and recognizes manufacturing variance	Debit or credit 5080 Manufacturing Variance with the offset to unresolved WIP or clearing balances
Manufacturing payroll recognition	Payroll recognizes qualifying manufacturing wages and related burden by period and cost center	PayrollSummary debits 1090 directly, or 5080 in months with no capitalizable direct labor, and credits payroll liabilities
Factory overhead	A separate journal records other factory costs	Debit 1090, or 5080 in months with no capitalizable direct labor, and credit cash
Manufacturing equipment depreciation	Monthly fixed-asset depreciation is recorded for plant equipment tied to manufacturing work centers	Debit 1090 Manufacturing Cost Clearing and credit 1186 Accumulated Depreciation - Manufacturing Equipment

Key Traceability and Data Notes

• SupplyPlanRecommendation is the planning bridge into both WorkOrder and purchased replenishment support.
• MaterialRequirementPlan is the component-demand explosion tied back to one manufacturing recommendation.
• RoughCutCapacityPlan is a weekly planning tieout and should not be used as the daily execution schedule.
• WorkOrderOperationSchedule is the daily schedule for operation-timing and capacity-use questions.
• LaborTimeEntry is the bridge from approved time into manufacturing cost traceability, especially when linked to WorkOrderOperationID.
• WorkOrderClose is the accounting close event, not the physical production event.
• FixedAsset.BehaviorGroup, WorkCenterID, and DepreciationDebitAccountID explain why plant equipment depreciation flows into 1090, while warehouse equipment still remains outside product cost.
• Manufacturing stays standard-cost based even though payroll and time provide operational labor support beneath that costing layer.

Explore detailed process and analysis paths

Analytical Subsections

Planning, MRP, and Rough-Cut Capacity

Why was manufacture recommended? Follow weekly planning into component requirements and rough-cut capacity. These records describe expected demand and load before detailed production execution.

Record and accounting evidence map

Expand the diagram for a larger view with zoom and pan controls.

Download editable Draw.io

Read the connectors and evidence boundaries

Demand forecasts and inventory policies support supply recommendations, which feed material requirements and rough-cut capacity planning.

Line and path	Meaning	Evidence to check
r1 DemandForecast to SupplyPlanRecommendation	Analytical match or aggregation	Item and warehouse; relevant weekly bucket
r2 InventoryPolicy to SupplyPlanRecommendation	Analytical match or aggregation	Item and warehouse; active policy and driver
r3 SupplyPlanRecommendation to MaterialRequirementPlan	Stored FK path	MaterialRequirementPlan.SupplyPlanRecommendationID → SupplyPlanRecommendation.SupplyPlanRecommendationID
r4 SupplyPlanRecommendation to RoughCutCapacityPlan	Stored FK path	RoughCutCapacityPlan.SupplyPlanRecommendationID → SupplyPlanRecommendation.SupplyPlanRecommendationID

Keep the record grains separate. Foreign-key paths, analytical matches, and business context answer different questions; read the numbered evidence table before joining.

Each box identifies a record, source label, or interpretive context. Check dates and grouping before comparing operational support with postings.

Focused ER maps and table grains · Posting sources and account effects

Tables involved

Table	Role in the flow
DemandForecast	Shows the weekly demand signal behind planned replenishment
InventoryPolicy	Shows safety stock, reorder logic, and lead-time assumptions
SupplyPlanRecommendation	Shows the planned manufacture signal by week, item, and warehouse
MaterialRequirementPlan	Shows exploded component demand created from the planned manufacture signal
RoughCutCapacityPlan	Shows weekly planned load versus available work-center hours

warning

RoughCutCapacityPlan is a weekly planning tieout, not the same thing as WorkOrderOperationSchedule. Use rough-cut rows for planning pressure and WorkOrderOperationSchedule for daily execution timing.

Starter analytical question: Which manufactured recommendations created both component pressure and rough-cut capacity pressure before execution began?

Analytical plan

• Objective: Link manufactured recommendations to component demand and weekly capacity pressure.
• Evidence path: SupplyPlanRecommendation -> MaterialRequirementPlan and RoughCutCapacityPlan.
• Comparison: Group by item, work center, warehouse, or bucket week.

Standard Recipe, Routing, and Work Centers

What recipe and production steps define the item? Follow its bill of material into component requirements and its routing into work-center operations. This is the standard design against which execution can be compared.

Record and accounting evidence map

Expand the diagram for a larger view with zoom and pan controls.

Download editable Draw.io

Read the connectors and evidence boundaries

An item links to its bill of material and routing. Routing operations identify work centers, whose calendars provide daily capacity.

Line and path	Meaning	Evidence to check
r1 Item to BillOfMaterial	Business context or account effect	Business context; no direct foreign key is depicted
r2 Item to Routing	Stored FK path	Item.RoutingID → Routing.RoutingID
r3 Routing to RoutingOperation	Stored FK path	RoutingOperation.RoutingID → Routing.RoutingID
r4 RoutingOperation to WorkCenter	Stored FK path	RoutingOperation.WorkCenterID → WorkCenter.WorkCenterID
r5 WorkCenter to WorkCenterCalendar	Stored FK path	WorkCenterCalendar.WorkCenterID → WorkCenter.WorkCenterID
r6 BillOfMaterial to BillOfMaterialLine	Stored FK path	BOMID BillOfMaterialLine.BOMID → BillOfMaterial.BOMID

Keep the record grains separate. Foreign-key paths, analytical matches, and business context answer different questions; read the numbered evidence table before joining.

Each box identifies a record, source label, or interpretive context. Check dates and grouping before comparing operational support with postings.

Focused ER maps and table grains · Posting sources and account effects

Tables involved

Table	Role in the flow
Item	Identifies which products are manufactured and stores standard cost components
BillOfMaterial, BillOfMaterialLine	Define the component recipe for the finished good
Routing, RoutingOperation	Define the ordered operation path through the factory
WorkCenter, WorkCenterCalendar	Define where the work happens and how much daily time is available

Starter analytical question: Which manufactured item groups use the most complex routing or the heaviest component structure?

Analytical plan

• Objective: Compare recipe complexity and routing complexity across manufactured items.
• Evidence path: Item -> BillOfMaterial -> BillOfMaterialLine and Item -> Routing -> RoutingOperation.
• Comparison: Group by item group, collection, or work center.

Work Order Release and Operation Scheduling

How was the recommendation put into production? Follow the released work order into its operations and daily schedule. Compare release, due, scheduled, and actual dates when explaining the progress of the work.

Record and accounting evidence map

Expand the diagram for a larger view with zoom and pan controls.

Download editable Draw.io

Read the connectors and evidence boundaries

A supply recommendation supports a work order and its operations. Daily schedules match work-center calendar records on both center and date.

Line and path	Meaning	Evidence to check
r1 SupplyPlanRecommendation to WorkOrder	Stored FK path	WorkOrder.SupplyPlanRecommendationID → SupplyPlanRecommendation.SupplyPlanRecommendationID
r2 WorkOrder to WorkOrderOperation	Stored FK path	WorkOrderOperation.WorkOrderID → WorkOrder.WorkOrderID
r3 WorkOrderOperation to WorkOrderOperationSchedule	Stored FK path	WorkOrderOperationSchedule.WorkOrderOperationID → WorkOrderOperation.WorkOrderOperationID
r4 WorkCenterCalendar to WorkOrderOperationSchedule	Analytical match or aggregation	WorkCenterID and CalendarDate equals ScheduleDate

Keep the record grains separate. Foreign-key paths, analytical matches, and business context answer different questions; read the numbered evidence table before joining.

Each box identifies a record, source label, or interpretive context. Check dates and grouping before comparing operational support with postings.

Focused ER maps and table grains · Posting sources and account effects

Tables involved

Table	Role in the flow
SupplyPlanRecommendation	Shows the planning row that supported the work-order release
WorkOrder	Shows the released production order
WorkOrderOperation	Shows the operation-level execution plan and actual progression
WorkOrderOperationSchedule	Shows the daily scheduled hours for each operation
WorkCenterCalendar	Shows the daily capacity that the schedule was placed against

Key joins

• WorkOrder.SupplyPlanRecommendationID -> SupplyPlanRecommendation.SupplyPlanRecommendationID
• WorkOrderOperation.WorkOrderID -> WorkOrder.WorkOrderID
• WorkOrderOperationSchedule.WorkOrderOperationID -> WorkOrderOperation.WorkOrderOperationID
• Match WorkOrderOperationSchedule.WorkCenterID = WorkCenterCalendar.WorkCenterID and WorkOrderOperationSchedule.ScheduleDate = WorkCenterCalendar.CalendarDate together.

Work center alone is not a daily key. Schedule 5 is center 4 on January 19, 2024, with 0.42 scheduled hours. Adding the date reduces a center-only calendar join from 1,180 matches to one, as the following queries show.

SELECT s.WorkOrderOperationScheduleID, s.WorkCenterID, s.ScheduleDate,
       s.ScheduledHours, c.AvailableHours
FROM WorkOrderOperationSchedule AS s
JOIN WorkCenterCalendar AS c
  ON c.WorkCenterID = s.WorkCenterID
 AND c.CalendarDate = s.ScheduleDate
WHERE s.WorkOrderOperationScheduleID = 5;

Even the correct two-column join repeats capacity if several operations share a center/day. Aggregate scheduled hours independently to center/day before comparing with the one daily calendar row. The existing daily load query uses this pattern:

WITH scheduled_load AS (
    SELECT WorkCenterID, ScheduleDate, COUNT(*) AS ScheduleRows,
           ROUND(SUM(ScheduledHours), 2) AS ScheduledHours
    FROM WorkOrderOperationSchedule
    GROUP BY WorkCenterID, ScheduleDate
)
SELECT c.WorkCenterID, c.CalendarDate, s.ScheduleRows,
       s.ScheduledHours, c.AvailableHours
FROM WorkCenterCalendar AS c
JOIN scheduled_load AS s
  ON s.WorkCenterID = c.WorkCenterID
 AND s.ScheduleDate = c.CalendarDate
WHERE c.WorkCenterID = 1 AND c.CalendarDate = '2024-01-22';

For this center/day, four schedule rows total 6.45 hours against 101.76 available hours. Summing calendar capacity after joining all four operation rows would incorrectly report 407.04. For a month, sum the resulting daily rows once each, retaining dates without scheduled work when measuring the full month's available capacity.

Analytical plan

• Objective: Trace one released work order from planning support into operation-level daily schedule rows.
• Evidence path: SupplyPlanRecommendation -> WorkOrder -> WorkOrderOperation -> WorkOrderOperationSchedule.
• Comparison: Compare release date, due date, schedule date, and actual operation timing.

Purchased Component Support and Material Issue

How did purchased components support production? Inspect the purchasing and receiving evidence alongside the later material issue to the work order. Receipt brings components into stock, while issue moves their cost into WIP.

Record and accounting evidence map

Expand the diagram for a larger view with zoom and pan controls.

Download editable Draw.io

Read the connectors and evidence boundaries

Purchasing and receiving support component availability. A separate work-order material issue records components moving into production.

Line and path	Meaning	Evidence to check
r1 Supply Plan Recommendation to Purchase Requisition	Stored FK path	PurchaseRequisition.SupplyPlanRecommendationID → SupplyPlanRecommendation.SupplyPlanRecommendationID
r2 Purchase Requisition to PurchaseOrderLine	Stored FK path	PurchaseOrderLine.RequisitionID → PurchaseRequisition.RequisitionID
r3 PurchaseOrderLine to GoodsReceiptLine	Stored FK path	GoodsReceiptLine.POLineID → PurchaseOrderLine.POLineID
r4 Work Order to Material Issue	Stored FK path	MaterialIssue.WorkOrderID → WorkOrder.WorkOrderID
r5 GoodsReceiptLine to Material Issue	Analytical match or aggregation	Item warehouse and timing support only

Read each numbered connector with its evidence explanation. Reference paths are not a time sequence; analytical support and account effects do not create additional stored keys.

Each box identifies a record, source label, or interpretive context. Check dates and grouping before comparing operational support with postings.

Focused ER maps and table grains · Posting sources and account effects

Tables involved

Table	Role in the flow
PurchaseRequisition, PurchaseOrder, GoodsReceipt	Show how P2P supports missing materials and packaging
WorkOrder	Anchors the production order that consumes the components
MaterialIssue, MaterialIssueLine	Show when material actually moved into WIP

Starter analytical question: Which work orders depended on purchased component support before material could be issued into production?

Analytical plan

• Objective: Compare upstream purchased support to the later physical issue of components into WIP.
• Evidence path: SupplyPlanRecommendation -> PurchaseRequisition and WorkOrder -> MaterialIssue -> MaterialIssueLine.
• Comparison: Compare receipt timing, issue timing, and work-order release timing.

Labor Capture, Payroll Bridge, and Manufacturing Cost

Which approved work supports the operation's labor explanation? Follow TimeClockEntry into LaborTimeEntry and the work-order operation. PayrollSummary recognizes qualifying manufacturing payroll directly in clearing. Factory overhead and depreciation use separate journals. These accounting sources do not allocate every pooled cost to an individual work order.

Record and accounting evidence map

Expand the diagram for a larger view with zoom and pan controls.

Download editable Draw.io

Read the connectors and evidence boundaries

Labeled solid arrows identify stored keys. Dashed arrows identify aggregation or analytical support. PayrollSummary posts directly to the ledger. Factory overhead and depreciation have separate journal routes.

Line and path	Meaning	Evidence to check
r1 TimeClockEntry to LaborTimeEntry	Stored FK path	TimeClockEntryID LaborTimeEntry.TimeClockEntryID → TimeClockEntry.TimeClockEntryID
r2 LaborTimeEntry to WorkOrderOperation	Stored FK path	WorkOrderOperationID LaborTimeEntry.WorkOrderOperationID → WorkOrderOperation.WorkOrderOperationID
r3 LaborTimeEntry to PayrollRegisterLine	Stored FK path	LaborTimeEntryID PayrollRegisterLine.LaborTimeEntryID → LaborTimeEntry.LaborTimeEntryID
r4 PayrollRegisterLine to PayrollRegister	Stored FK path	PayrollRegisterID PayrollRegisterLine.PayrollRegisterID → PayrollRegister.PayrollRegisterID
r5 PayrollRegister to PayrollSummary source label	Analytical match or aggregation	Aggregate by period cost center and account
r6 PayrollSummary source label to GLEntry	Type-qualified ledger source	GLEntry source type PayrollSummary and source ID
r7 JournalEntry factory overhead and depreciation to GLEntry	Type-qualified ledger source	GLEntry source type JournalEntry and source ID

Read each numbered connector with its evidence explanation. Reference paths are not a time sequence; analytical support and account effects do not create additional stored keys.

Each box identifies a record, source label, or interpretive context. PayrollSummary is a constructed posting identifier rather than a physical table. Check dates and grouping before comparing operational support with postings.

Focused ER maps and table grains · Posting sources and account effects

Tables involved

Table	Role in the flow
EmployeeShiftRoster, TimeClockEntry	Show planned and approved labor support beneath payroll
LaborTimeEntry	Shows the costing bridge from approved time into production analysis
WorkOrderOperation	Shows which operation consumed the direct labor support
PayrollRegister, PayrollRegisterLine	Provide employee facts summarized into PayrollSummary postings
JournalEntry, GLEntry	Show separate factory-overhead and depreciation entries alongside summarized payroll recognition

Starter analytical question: Which work centers or work orders show the highest approved labor support relative to planned operation timing?

Analytical plan

• Connect approved factory time to work-order operations, then compare payroll support with its summarized recognition.
• Follow TimeClockEntry and LaborTimeEntry through stored keys. Compare PayrollRegister totals independently with PayrollSummary at period/cost-center grain using the Posting Reference.
• Group operational support by work center, work order, or labor type. Preserve period/cost-center grain for the payroll-to-ledger comparison.

Production Completion, Close, and Finished-Goods Availability

When were goods available, and when was their order closed? Compare ProductionCompletion and WorkOrderClose separately. Completion recognizes finished goods at standard cost, while close resolves the remaining variance and balances.

Record and accounting evidence map

Expand the diagram for a larger view with zoom and pan controls.

Download editable Draw.io

Read the connectors and evidence boundaries

A work order links separately to material issues, labor, production completion lines, and accounting close. Completion makes finished goods available before close.

Line and path	Meaning	Evidence to check
r1 Work Order to Material Issue	Stored FK path	MaterialIssue.WorkOrderID → WorkOrder.WorkOrderID
r2 Work Order to Labor Time Entry	Stored FK path	LaborTimeEntry.WorkOrderID → WorkOrder.WorkOrderID
r3 Work Order to Production Completion	Stored FK path	ProductionCompletion.WorkOrderID → WorkOrder.WorkOrderID
r4 Production Completion to Production Completion Line	Stored FK path	ProductionCompletionLine.ProductionCompletionID → ProductionCompletion.ProductionCompletionID
r5 Production Completion to Finished goods available to O2C	Business context or account effect	Conceptual support; consult the detailed keys before joining
r6 Work Order to WorkOrderClose	Stored FK path	WorkOrderClose.WorkOrderID → WorkOrder.WorkOrderID

Read each numbered connector with its evidence explanation. Reference paths are not a time sequence; analytical support and account effects do not create additional stored keys.

Each box identifies a record, source label, or interpretive context. Check dates and grouping before comparing operational support with postings.

Focused ER maps and table grains · Posting sources and account effects

Tables involved

Table	Role in the flow
MaterialIssue	Shows material already consumed into WIP before completion
LaborTimeEntry	Shows labor support that contributes to cost traceability
ProductionCompletion, ProductionCompletionLine	Show the physical completion event and standard finished-goods cost detail
WorkOrderClose	Shows the final close and manufacturing variance event

Starter analytical question: Which work orders were physically completed in one period but not closed until a later period?

Analytical plan

• Objective: Separate physical completion from accounting close and finished-goods availability.
• Evidence paths: WorkOrder -> ProductionCompletion -> ProductionCompletionLine, and separately WorkOrder -> WorkOrderClose. WorkOrderClose.WorkOrderID connects close to the order without a ProductionCompletionLineID foreign key.
• Comparison: Compare completion date, close date, quantity completed, and variance amount by month.

Aggregate each branch before joining at WorkOrderID. Otherwise, two completion lines can repeat the same close amount. This worked comparison retains the two different event dates:

WITH completion_totals AS (
    SELECT p.WorkOrderID, COUNT(*) AS CompletionLines,
           MAX(p.CompletionDate) AS LastCompletionDate,
           ROUND(SUM(l.QuantityCompleted), 2) AS CompletedQuantity,
           ROUND(SUM(l.ExtendedStandardTotalCost), 2) AS StandardCompletedCost
    FROM ProductionCompletion AS p
    JOIN ProductionCompletionLine AS l
      ON l.ProductionCompletionID = p.ProductionCompletionID
    GROUP BY p.WorkOrderID
), close_totals AS (
    SELECT WorkOrderID, COUNT(*) AS CloseRows, MAX(CloseDate) AS LastCloseDate,
           ROUND(SUM(TotalVarianceAmount), 2) AS TotalVariance
    FROM WorkOrderClose
    GROUP BY WorkOrderID
)
SELECT w.WorkOrderID, p.CompletionLines, p.LastCompletionDate,
       p.CompletedQuantity, p.StandardCompletedCost,
       c.CloseRows, c.LastCloseDate, c.TotalVariance
FROM WorkOrder AS w
LEFT JOIN completion_totals AS p ON p.WorkOrderID = w.WorkOrderID
LEFT JOIN close_totals AS c ON c.WorkOrderID = w.WorkOrderID
WHERE w.WorkOrderID = 1;

Work order 1 has two completion lines, last completed January 26, 2024, totaling 7.03 units and 1,019.85 standard cost. Its one close is dated February 1, with 743.16 total variance. A missing close stays null in this comparison rather than becoming a zero recorded variance.

Follow specialized process branches

Expand the diagram for a larger view with zoom and pan controls.

Download editable Draw.io

Model scope: One proposed classroom review of selected work-order cost-close evidence.

Text description and database evidence

1. A student selects a recorded work-order close and defines the reporting boundary.
2. The proposed analyst role collects material, completion, labor, and close evidence, then reconciles recorded cost support.
3. The proposed reviewer evaluates whether the evidence explains the difference. A supported explanation is documented; otherwise targeted follow-up identifies missing evidence.
4. The activity ends with a student conclusion or an unresolved evidence request. It does not prescribe a favorable or unfavorable answer.

Evidence tables: WorkOrder, MaterialIssue, ProductionCompletion, LaborTimeEntry, WorkOrderClose, GLEntry.

Confirm keys and accounting sources in the Schema Reference and Posting Reference.

Every analyst/reviewer task is a proposed classroom activity. The database does not implement this independent review, its sign-off, or a finished-goods hold. Submit a risk/control matrix rather than assuming control operation.

Editable visual model in Draw.io XML; this is not executable BPMN XML. Notation and model library.

Read completion, cost support, and WorkOrderClose as distinct evidence. A recorded variance is an accounting result to interpret, not proof of waste, an unauthorized transaction, or a separate approval workflow.

Evaluate controls and try the optional AIS activity

Risks, Controls, and Evidence

Risk and control objective	Evidence available	Teaching boundary
Unsupported production: connect execution to a documented plan	SupplyPlanRecommendation, WorkOrder.SupplyPlanRecommendationID, release and employee fields	A planning link supports traceability; it does not prove that a separate release-approval control operated
Incorrect consumption or labor allocation: support the work-order cost trail	MaterialIssueLine, LaborTimeEntry, WorkOrderOperation	Compare records at their own grain; an independent consumption reconciliation is a proposed teaching control
Incomplete close: explain residual balances and variance	ProductionCompletionLine, WorkOrderClose, GLEntry	ClosedByEmployeeID identifies recorded responsibility; an independent variance sign-off is a proposed teaching control, not a stored approval chain

Optional AIS Activity: Evaluate a Conversion Handoff

Context and objective: an operations and finance review needs to explain how a work order moved from planned demand to finished goods and accounting close. Use the BPMN responsibilities to identify a risk without confusing standard-cost accounting with operational actual labor support.

Prerequisites, tools, and sources: complete the manufacturing cost-flow exercise linked above and review WIP, manufacturing clearing, and variance. Use a SQL tool with the published SQLite file, or Excel with filters and lookups, plus a copy of the editable Draw.io model. Sources are SupplyPlanRecommendation, WorkOrder, WorkOrderOperation, WorkOrderOperationSchedule, MaterialIssueLine, MaterialIssue, LaborTimeEntry, ProductionCompletion, ProductionCompletionLine, WorkOrderClose, and GLEntry.

1. Record the source file, chosen work order, scope, and reporting date. Mark its planning, execution, completion, and close evidence on the model.
2. Compare the event dates and distinguish an open work order from completed goods awaiting accounting close. Retain document grain and state the cost basis of every amount.
3. Propose one review of consumption, labor support, or close. Label it a proposed teaching control and specify its risk, objective, owner, evidence, test, and limitation using the workshop matrix.

Assessed deliverable: submit the annotated process model, a reproducible event and cost schedule, and the matrix row. Explain what evidence would change a production or accounting decision. The records do not establish a complete actual-cost inventory system, every shop-floor action, or the effectiveness of an unrecorded control. Extend the investigation through the existing manufacturing case and operations reports below.

Choose a further investigation

Questions for Further Investigation

• Which products are manufactured and which are purchased?

• Which manufactured recommendations created the most component demand or rough-cut capacity pressure?

• Which items use the most complex BOM or routing structure?

• Which work centers look busiest by week or month?

• Which work orders remained open at period end?

• Which work orders had schedule pressure before actual execution began?

• Which work orders depended on purchased component support before material issue?

• How much direct labor is tied to each work order and operation?

• Which work orders were completed but not yet closed?

• How much manufacturing variance was posted by month, work center, or item group?

• Read Production and Planning to compare utilization, forecasts, and capacity, and add Purchasing and Inventory for supply reliability and coverage.

• Read Manufacturing Labor Case when you want a guided walkthrough from production support into costing and close.

• Read Explain Profit, Cash, and the Year-End Close when you want to add plant-equipment depreciation and note-financed equipment into the manufacturing-cost story.

• Read P2P to see how raw materials and packaging are replenished when manufacturing needs purchased support.

• Read Payroll for approved attendance support and Manufacturing Payroll and Cost Support for direct payroll recognition and the separate cost-support sources.

• Read GLEntry Posting Reference and Schema Reference when you need the detailed posting or join logic.