Perpetual inventory system: keep movements and balances aligned

A running stock balance depends on capturing receipts, issues, and transfers at the right event, then checking it against physical stock.

Kartik Deshpande··5 min read

Your warehouse receives a shipment while production consumes material and the order desk checks stock. A perpetual inventory system updates recorded quantities as inventory transactions post, so each decision can use a running balance. The balance is only as complete as the movements captured: an unrecorded issue leaves the screen overstating what remains.

Oracle NetSuite’s perpetual inventory explanation distinguishes transaction-by-transaction updates from a periodic system’s end-of-period inventory determination. Choose the operating model around the decisions that need current records, then design the event capture and physical checks that support those decisions. A frequently refreshed report cannot compensate for stock movements that never reached the record.

Decide which events change each balance

Set the record grain before connecting scanners or importing transactions. Item, warehouse, bin, lot, stock status, owner, and unit can all change which quantity a user means by on hand. Use the dimensions needed by the decision, while preserving the source identifier that separates one movement from another. A lot on quality hold may be physically present but excluded from usable stock.

Write a movement rule for receipts, production issues, finished output, shipments, returns, and transfers. Name the event that changes quantity in the inventory system. A purchase order requests stock; a receipt establishes a received quantity under the warehouse process. Counting both as additions would overstate stock before any supplier short-ships.

Keep reservations distinct from physical movements. Reserving an order can reduce availability without reducing physical on hand, while shipment changes the physical balance. Inspect the source export’s definition before subtracting reserved units again. The available to promise article addresses the dated commitment decision built on those balances.

Separate quantity maintenance from valuation. A running unit balance does not select a cost formula, establish ownership, or decide when an accounting entry should post. Have finance approve valuation and posting rules, then link the relevant transactions to those rules. The inventory valuation methods article covers that separate accounting choice.

Follow a running balance through a transfer

Assume a hypothetical item measured in pieces, no quality holds, no reservations, and two warehouses. Warehouse A opens with 100 pieces and B with 20. A receives 40, issues 25 to production, and ships 30 to customers. A then dispatches 15 pieces to B, which receives them later that day. There are no other movements.

EventWarehouse AIn transitWarehouse B
Opening balance100020
Receipt into A140020
Production issue from A115020
Customer shipment from A85020
Transfer dispatch701520
Transfer receipt70035

The final network balance is 105 pieces: 120 opening plus 40 received minus 25 consumed minus 30 shipped. The internal transfer changes location, not the network total. During transit, a warehouse-only sum shows 90, so retain the 15-piece transit balance if the intended network scope includes company-controlled stock between facilities. Use the transfer reference to connect dispatch and receipt without treating them as unrelated adjustments.

Now assume the transfer receipt arrives twice through an import retry. If both copies add stock, B displays 50 and the network displays 120. Require a stable source movement key and a rule for repeated deliveries so the retry does not become another physical receipt. Preserve the rejected duplicate as processing evidence; a user should be able to distinguish a replay from a genuine second delivery.

Separate movement, location, and availability
Physical movement
Receipt, issue, or shipment
Location change
Dispatch, transit, receipt
Availability
Usable stock less commitments
A transfer can preserve the network total while changing which warehouse can fulfill an order.

Inspect the movements behind one stock balance

Bring a permitted inventory movement extract into Permute and check the item, location, and transaction identifiers.

Design capture and recovery around missing events

Assign ownership at the point where a physical event becomes a record. Receiving owns quantity accepted against the delivery; production owns material consumption and output; shipping owns the dispatched quantity. If a scanner is offline, define how its unposted events remain visible and how a supervisor confirms the backlog has cleared. Show both the event time (when the movement occurred) and posting time when the source supplies them.

Treat a failed transaction feed as an exception in freshness. The last successful balance may still answer a historical question, but it cannot support an unqualified claim about current stock. Display the extraction cutoff and affected location beside the number. A successful refresh of other warehouses should not hide a missing feed from the warehouse supplying the order.

Handle reversals as linked movements. If a receiver corrects an accepted quantity, retain the original event, reversal, and replacement where the source supports that history. Overwriting the current balance without an explanation prevents a later reviewer from reconstructing the sequence. Use the source’s correction process and authorization before accepting the amended balance into reporting.

Use physical checks to test the recorded model

Oracle’s cycle counting documentation describes counting stock on a cyclic schedule. Use a count as an independent observation of physical quantity, then compare it with records at a common cutoff. Continuous transaction recording does not observe theft, an unscanned issue, or stock left in the wrong bin.

If operations continue during a count, retain the movements between observation and comparison. A count of 70 pieces at noon and an ERP balance of 65 after a five-piece shipment can agree once the cutoff is aligned. The inventory reconciliation article covers that investigation. Keep the count observation separate from any approved adjustment so the evidence survives the correction.

Before accepting a new workflow, replay a receipt that was short, a transfer still in transit, and a production issue entered after its physical event. For each case, ask the owner to reproduce the opening balance, signed movements, and ending balance at the same cutoff. Record any source history the test cannot recover instead of labeling the workflow complete.

Where Permute connects transaction evidence

Permute is the context layer we sell between business data and the AI tools people already use. We connect permitted ERP and spreadsheet records, then match item, location, and movement identifiers across them. That lets the inventory owner inspect which recorded events support a reported quantity.

We can reuse declared unit conversions, stock-status definitions, and reporting cutoffs across reports and scoped questions. An inventory controller can ask why a warehouse balance changed and examine the supporting records within their permissions. Keep unmatched movements and stale sources visible so an answer does not imply coverage the inputs lack.

Keep stock posting and accounting under their owners

We read from connected systems in this workflow and do not write stock movements or count adjustments back to the system of record. We are not a warehouse execution system or a forecasting engine. Warehouse staff own physical capture and finance owns accounting treatment; missing scans and inaccessible source history remain limitations on the analysis.

Trust the recorded sequence and verify the stock

A perpetual inventory system maintains a running balance through posted stock movements. Define which event changes each quantity, preserve transfers in transit, and keep availability separate from physical stock. Repeated imports and late events need explicit handling because both can distort the sequence. Compare the resulting record with physical observations at the same cutoff before approving a correction.

Review a balance that cannot be reconstructed

Bring one item’s opening quantity, movement history, and count observation to identify the missing evidence.

Questions about perpetual inventory system

When can a periodic system be enough?

Consider it when decisions can wait for the chosen count and reporting cycle and transaction capture would cost more than the resulting visibility is worth. State that lag to users. Reassess if production or order commitments start depending on a balance the process cannot keep current.

What does a negative recorded balance mean?

It means recorded deductions exceed recorded additions within the selected scope. Investigate receipt timing, duplicate issues, units, and location selection before interpreting it as a physical quantity. Keep the exception visible until the source owner explains it.

Are barcodes required?

Barcodes are one way to capture item and movement identifiers. A process can use other controls, but each relevant movement still needs a reliable record. Choose the method around the volume, physical workflow, and error checks required.