Straight into the service manual page
WrenchQuarry
More

3 quantities to record when parts arrive on site

WrenchQuarry Editorial Team · Published · 13 min read · How these guides are written

Record three quantities for every delivery: the quantity ordered, the quantity that actually arrived, and the quantity accepted into usable stock. In the ERPNext documentation example, 200 USB-C adapters were ordered and 200 were counted at the loading bay, but only 195 were accepted and 5 damaged units were kept separately.

Net takeaways

  • Record three quantities for each delivery: ordered, arrived and accepted.
  • Treat an order as a request, not proof that parts arrived.
  • Add only accepted units to van stock, and keep rejected units in a separate location.
  • Submit the goods-in document after the count is finished, because submission is what updates stock.
  • Check the system figure against the physical count before a dispatcher assigns the job.

The three quantities and the answer

The three quantities are the order, the arrival and the acceptance. The ordered quantity is what the buyer asked for. The arrived quantity is what the delivery actually contained when someone counted it. The accepted quantity is what you are willing to place on the shelf as usable stock. Each one answers a different question. Mixing them up can leave a van carrying fewer parts than the system says.

That sentence names two quantities, arrived and accepted, and gives each outcome its own location. Rejected goods are not quietly subtracted and forgotten. They are placed somewhere specific so they can be found and handled.

For a van-based operation, the translation is direct. The order is the parts list on the purchase order or job ticket. The arrived count is what the supplier or depot hands over, counted line by line. The accepted count is what goes into the van stock record as available for scheduled work. A missing, wrong or damaged item becomes its own line, not a silent gap between the order and the shelf.

Consider what happens without this split. A job needs eight fittings, and the system shows eight because the order was entered as stock. The technician arrives and finds six usable fittings, two were damaged, and the dispatcher learns about it only on site. Recording arrived and accepted separately makes that gap visible before the van leaves the depot.

Start from the order, then prove arrival

The order is the reference point, but it is not evidence. The ERPNext example states the problem plainly: The buying team ordered 200 USB-C adapters from Keystone Cables, but an order alone does not prove that the goods arrived. A purchase order records what was requested and promised. It cannot tell you what is in the box on the loading bay.

So the workflow starts from the order and then requires proof of arrival. The order gives the expected quantity for each part. The count taken at the loading bay gives the arrived quantity for that same delivery. Comparing the two shows whether the supplier shipped in full, short, or with extra units. The figures in the example are shown below.

MeasureFigure in the exampleWhat the figure represents
Ordered200USB-C adapters requested from Keystone Cables
Counted at the loading bay200Units physically counted when the delivery arrived
Accepted195Units placed into usable stock
Rejected (damaged)5Units kept apart from usable stock

The count matched the order in this example, yet only 195 units were usable. A match between order and count does not mean every unit is stock. Acceptance is a separate step and needs its own number.

Dispatchers should never treat the purchase order as the stock figure. The order shows what was requested.

Ordered, arrived and accepted side by side

Placing the three quantities next to each other shows why only one of them should feed the van stock record. In the ERPNext example, the same delivery gives two different numbers: 200 ordered and counted, and 195 accepted. The receiving step sets out the sequence: When the delivery reaches the loading bay, you count 200 units, accept 195, and keep 5 damaged units separately. The count comes first, then acceptance, then separation of the rejected units.

The table below compares two ways of reading the same delivery. The order-based view counts what was requested. The acceptance-based view counts what went into usable stock. Both use the example figures, so the difference is exactly the rejected units.

Measure comparedOrder-based viewAcceptance-based view
Quantity treated as stock200195
Units left out of stock05
Basis for the figurePurchase orderCount at the loading bay plus acceptance
Suitable for job assignmentNoYes

The order-based view overstates usable stock by 5 units in this example. The acceptance-based view matches what the van can carry. A dispatcher who assigns jobs from the order-based figure will plan work the van cannot finish.

The practical rule is simple. Record the count first, decide acceptance second, and let only the accepted figure reach the van stock. The ordered figure stays on the purchase order, where it belongs.

Where accepted and rejected units belong

Accepted and rejected units must not share a location. The ERPNext example shows the split in concrete terms: The warehouse accepts 195 into Receiving Warehouse and places 5 damaged units in Returns Warehouse. The two groups leave the dock in different places, and the system records them under different locations.

This separation protects van stock from contamination. If damaged units sit in the same bin as good ones, a technician may pick them for a job and discover the fault on site. A separate return location keeps the damaged units visible, countable and out of the available figure until they are repaired, returned to the supplier or written off.

The table below sets out the three figures that matter for location, with each count tied to where it belongs.

GroupCountLocation
Accepted, usable stock195Receiving Warehouse
Rejected, damaged units5Returns Warehouse
Total counted at the loading bay200Both locations combined

The total row is the check. The accepted and rejected groups must add back to the count taken at the loading bay. If they do not, a unit has gone missing between the dock and the shelf, and the goods-in document should not be finished until the difference is explained.

For team leads, the rule is to give rejected units a fixed home, label them as not available for jobs, and keep their count visible. The dispatcher then sees the true available figure every time.

Submitting the goods-in document updates stock

Submission is the moment the record changes the stock. The ERPNext manual states the effect directly: Submitting it updates stock and the received quantity on the linked Purchase Order. Until the goods-in document is submitted, the van stock figure should not reflect the delivery, even if the parts are already sitting in the van.

Timing matters here. If the goods-in document is submitted before the count is complete, the stock figure will show units that were never checked. If it is submitted after a partial count, the total will be wrong, and the purchase order will show a received quantity that does not match the delivery. Both errors then flow into job planning. The safe sequence is to finish the count, record the acceptance and rejection split, confirm the total, and only then submit.

Submitting also updates the received quantity on the linked purchase order, so the order becomes a record of what has actually arrived. A purchase order that shows full delivery while parts are still missing points to a document split incorrectly or one submitted before the count was final, and it should be corrected at once.

Once a goods-in document is submitted, the figures it creates are the figures the team plans against. Submit only when the count, the acceptance and the location split agree with each other and with the delivery in front of you.

Why counts must match the physical shelf

The system figure is only useful if it agrees with the shelf. The OpenStax accounting text describes the same logic for periodic inventory: As you’ve learned, the periodic inventory system is updated at the end of the period to adjust inventory numbers to match the physical count and provide accurate merchandise inventory values for the balance sheet. The recorded figure is adjusted to the physical count, and the physical count is treated as the authority.

For a van, the same principle applies on a shorter cycle. The record exists to describe what is on the shelf or in the van. When the two disagree, the record is corrected, not the shelf. A dispatcher who trusts a figure that no count has confirmed is trusting an estimate.

This is why the physical count belongs at the point of delivery and again at the point of loading. Counting only when the delivery arrives leaves room for losses between the depot and the van. Counting at loading catches the difference before a technician finds it at a customer's door.

A simple practice follows. Before a job is assigned, compare the system figure for each part with a quick physical check of the van or bin. Where the two match, the job can go ahead. Where they differ, correct the record first, and only then plan the job. The goal is a stock figure a technician could verify by looking.

What the period-end adjustment leaves on hand

The OpenStax text describes the periodic method, where the inventory record is brought into line at the end of a period. Its key sentence is this: The adjustment ensures that only the inventory costs that remain on hand are recorded, and the remainder of the goods available for sale are expensed on the income statement as cost of goods sold.

That idea carries over to a van. Only goods still on hand should appear as remaining stock. Anything that was available but has left the van, because it went onto a completed job or was otherwise used, is no longer on hand and should not be counted as available. A count at the end of a working period tells you what really remains.

The scope needs care. The OpenStax passage is about accounting for inventory over a period, not about van dispatch, and it does not say how often a van should be counted. What it supports is the logic: the figure left on hand is the one that matters, and it must be set by counting what remains. A dispatcher planning tomorrow's jobs should use that remaining count, not a total that assumes parts already used are still there.

How FIFO assigns cost to each delivery

Microsoft's Business Central documentation makes the link between deliveries and cost explicit: An item's unit cost is the actual value of any receiving the item, selected by the FIFO rule. Cost belongs to deliveries, and the FIFO rule decides which delivery's value is selected.

FIFO stands for first in, first out. Picture a fitting that arrived in two deliveries. Each delivery is its own entry with its own value, and the rule determines which entry's value applies when a unit is costed. The delivery you record is therefore the record that carries the cost.

This is why the accepted figure matters for cost as well as availability. If a damaged unit were received as usable, its cost would attach to stock that is not on the shelf.

The source does not give a worked FIFO calculation, so this post does not supply one. It confirms the principle: the delivery is the unit of cost, and FIFO selects among deliveries.

Weighted-average or FIFO: which one should you pick?

The sources show two options, and they are different kinds of evidence. The table sets out what each one shows.

OptionWhat the source showsFigure given
Weighted-average periodicGross margin results from weighted-average periodic cost allocations$8,283

The sources do not say which method a business should choose, and this post will not choose on its behalf. The OpenStax example reports a gross margin of $8283 from the weighted-average periodic allocations. That tells you what the method produces, not that it is better. The FIFO description tells you cost follows each delivery.

A practical way to decide is to match the method to how you record deliveries. If the value of each delivery matters and you want cost tied to each entry, the FIFO description fits. If you run periodic counts and want a single averaged cost, the weighted-average example fits. Whichever you choose, apply it consistently to each item so figures can be compared from one period to the next.

Cost of goods sold figures compared

The OpenStax example reports two results that both read $8,283: a gross margin under weighted-average periodic allocation, and a cost of goods sold recorded as an expense. The table keeps them apart.

MeasureFigureTreatment in the source
Gross margin, weighted-average periodic allocations$8,283Result of the allocations
Cost of goods sold$8,283Recorded as an expense

The two figures sit side by side in the example, but they are different measures. Gross margin is what the allocations produce, while cost of goods sold was calculated to be $8,283, which should be recorded as an expense.

Dispatchers do not usually handle expense accounts, but the chain behind these figures matters to them. An error in the quantity recorded as received carries through to the cost reported later. Getting the count and acceptance right at the dock is the first step toward getting cost right.

Common gaps between order and van stock

The clearest example of a gap is the ERPNext walk-through: When the delivery reaches the loading bay, you count 200 units, accept 195, and keep 5 damaged units separately. The count matches the order, yet usable stock is 195. Several common gaps follow from that pattern:

  • Treating the order as the count. The purchase order records what was asked for, not what arrived.
  • Counting the arrival but not the acceptance. A matching count does not confirm usable stock.
  • Leaving damaged units in the same bin. A technician may pick a unit that was never acceptable.
  • Submitting before the split is complete. The stock figure then reflects a decision not yet made.
  • Skipping a check at loading. Parts can go missing between the depot and the van, and a goods-in figure alone will not catch that.

Each gap has the same fix: keep the three quantities separate, and compare them before the van leaves.

Related guides: Credit sale dates: 2 dates to record for each job · Crew break rules away from the job site: 3 states · 3 eye protection rules for field techs on the job site.

Reader questions

Should the physical count override the system figure? Yes. The OpenStax text describes the periodic system being updated to adjust inventory numbers to match the physical count. The count is the authority, so correct the record to match the shelf.

What happens to damaged units? They are kept apart from usable stock. In the ERPNext example, the warehouse places 5 damaged units in Returns Warehouse while 195 go into Receiving Warehouse. Keep damaged units in their own location and out of the available figure.

What is FIFO? It is the rule Microsoft describes for selecting unit cost. Each delivery carries its own value, and first in, first out decides which one applies. It is a method for assigning cost to records, not a counting rule.

Do the sources say which costing method to use? No. They describe a FIFO rule and a weighted-average example with a gross margin of $8283, but they do not rank the two. Choose one and apply it consistently.

What does the period-end adjustment mean for stock? Only the costs of goods still on hand remain on the balance, and the rest is expensed. Use the count of what remains as your stock figure.

What is cost of goods sold in this example? The OpenStax example records $8,283 as an expense. It is a cost figure, not a sales figure.

Sources

More field guides