Stock ledger: reconcile movements to the closing balance

A closing quantity can agree while transfers or reversals are missing. Preserve movement identity and check each location before accepting the total.

Kartik Deshpande··7 min read

Yesterday’s closing quantity does not match today’s opening balance, even though the warehouse has not started picking. Reconstruct the stock ledger from a supported opening balance and every posted movement affecting the same item and location. Add signed receipts and issues in source order, retain the document behind each line, and compare the result with the closing balance at the same cutoff. A matching total needs a separate completeness check because missing movements can cancel each other.

Use this process when you need the movement history across receipts, consumption, transfers, returns, and corrections. The inventory adjustment report narrows the review to posted corrections and their reasons. Here, the question is broader: which entries explain every change between the opening and closing quantities?

Fix the balance scope before exporting movements

Choose the company, item, warehouse, and location level you need to reconcile. Retain lot, serial, ownership, or stock-status dimensions wherever they separate balances in the source. A bin-level balance cannot be checked against warehouse-level movements without a documented rollup. Keep a missing location in an exception queue instead of assigning it to the warehouse with the largest balance.

Record the opening cutoff, closing cutoff, time zone, and extraction time. State whether the report follows physical stock postings or another source-defined date. Microsoft’s inventory transaction documentation distinguishes physical dates from financial dates and distinguishes receipt and issue statuses. A quantity report based on physical postings needs those dates and statuses to avoid mixing an expected receipt with stock already received.

Export an opening balance immediately before the movement window. If the export includes an opening row, identify it as a balance carried forward (not a receipt inside the window) so it is not added twice. Preserve the export filters with the file. When the prior close and the new opening disagree, compare their dimensions and extraction times before treating the difference as warehouse activity.

Give every stock movement its own identity

Use the source’s stable stock-entry ID as the movement key, namespaced by source and company. Keep the document number and line reference beside it. Microsoft documents that partial updates and inventory dimensions can split one order line into several inventory transactions in its posting-profile explanation. Deduplicating by order line alone could remove valid split movements.

Retain the item and location dimensions, source quantity and unit, normalized signed quantity, movement type, effective posting time, and entry timestamp where available. Add transfer references and original-entry references for reversals. Keep the original unit beside any conversion factor: a case-to-each conversion needs the pack size that applied to that movement, not an unexplained current default.

ERPNext’s Stock Ledger Report documentation describes item and warehouse movement history with quantity and value, and links the voucher number to the originating document. Preserve that route back to evidence when combining exports. Join attachments and comments after calculating movement totals, since several attachments for one entry must not create several copies of its quantity.

For each item and location, calculate opening quantity plus the cumulative signed movement quantity. Sort by the source’s posting sequence, retaining its stable tie-breaker when timestamps match. If the export lacks that sequence, reconcile the closing quantity but mark any reconstructed within-timestamp order as uncertain. Sorting identical timestamps by document name does not establish which movement the ERP processed first.

Reconcile a transfer, returns, and a reversed issue

The following is a synthetic quantity example, not product performance. Assume one company, one SKU, warehouses A and B, quantities in eaches, and no lot or ownership splits. The opening balances are A = 100 and B = 20. All subsequent rows are physically posted within the same window, appear in source sequence, and have the unique stock-entry IDs shown.

Entry / eventWarehouseSigned quantityBalance in that warehouse
Opening balanceACarried forward100
Opening balanceBCarried forward20
L101 / purchase receiptA+40140
L102 / production issueA-30110
L103 / transfer T17 outA-2585
L104 / transfer T17 inB+2545
L105 / customer return receivedA+590
L106 / supplier return shippedB-441
L107 / erroneous issueA-882
L108 / reversal of L107A+890
L109 / corrected issueA-387

Warehouse A closes at 87: 100 + 40 - 30 - 25 + 5 - 8 + 8 - 3. Warehouse B closes at 41: 20 + 25 - 4. Across both warehouses, opening stock of 120 plus net movement of 8 equals closing stock of 128. The transfer changes location without changing the combined quantity. The erroneous issue and reversal net to zero, leaving the corrected issue’s three-unit reduction.

Check the gross movements as well: nine unique stock entries, positive quantities totaling 78, and negative quantities totaling -70. Exclude the two opening-balance rows from that entry count. If both transfer entries disappear, the combined close remains 128 but A and B are wrong. If both L107 and L108 disappear, the closing quantities still agree, but the report has lost the correction history. Neither omission can be detected from the final total alone.

The transfer here is immediate. Microsoft’s inventory-journal documentation says a transfer journal creates an issue at the source and a receipt at the destination, while a transfer order supports in-transit inventory. For a shipment received after the cutoff, reconcile the source-defined transit balance and open transfer status. Do not create a destination receipt just to make the warehouse totals agree.

Treat returns according to the posted stock effect. L105 increases A because the customer return was received there; L106 reduces B because the supplier return shipped from there. Preserve the return document and its original receipt or shipment reference where available. A credit document without a stock movement cannot supply a missing physical receipt.

Match evidence at the level where omissions hide
ControlEvidence
MovementEntry and document
LocationTransfer and balance
HistoryOriginal and reversal
A company-wide net can agree even when location balances or the correction trail are incomplete.

Keep backdated restatements separate from saved snapshots

Suppose a six-unit receipt into A is entered after this report was saved but carries an effective date before its opening cutoff. A restated report would begin A at 106 and close A at 93, with B unchanged at 41. The combined closing quantity would be 134. Keep the original snapshot at 128 with its extraction time, and label the new version as restated. Moving the late receipt into the current movement window would explain the wrong period.

ERPNext’s immutable-ledger documentation describes controlled reposting for permitted backdated stock transactions and notes that later valuations can change. Check the installed release, period restrictions, and repost status before using a refreshed export. A permitted backdated entry does not establish that all downstream calculations have completed.

Retain the effective date and the time the entry became available to the report. Those fields answer different questions: what the ledger now says happened by a cutoff, and what the reviewer could see when the original report ran. If entry timestamps are unavailable, preserve successive extracts and report that limitation instead of claiming to reproduce a prior as-known view.

Prove source coverage before accepting the close

Compare against an independent source report or export manifest using identical filters. A total calculated twice from the same incomplete file proves arithmetic, not extraction coverage. Retain source row counts and extract completion evidence, then check the following differences before handing off the report.

  • Compare unique stock-entry counts and signed receipt and issue totals by item, location, and unit; a net-only check misses offsetting omissions.
  • Match transfer references across source, destination, and any transit stage; retain open legs supported by status instead of manufacturing a matching row.
  • Verify reversal-to-original links and report filters that hide canceled entries; a balanced correction pair still belongs in the evidence trail.
  • Reconcile extraction pages and filters to the manifest, then confirm the latest included posting and any unfinished source recalculation; a recent file timestamp does not prove complete coverage.

Assign unresolved differences to the source owner with the affected movement IDs and cutoff. Use inventory reconciliation when the remaining issue is a disagreement between the recorded balance and a physical observation. The ledger can explain recorded activity while an unrecorded receipt or issue still requires warehouse investigation.

Where Permute fits in movement reconciliation

Permute sells connected business data, custom applications, and governed analysis. For this workflow, we can combine permitted movement extracts with item and location mappings while preserving the source stock-entry IDs. An ambiguous location or unmatched reversal stays visible for review instead of being absorbed into a balancing adjustment.

We can apply your declared units, date basis, and stock dimensions across repeated analyses. An inventory operations lead can ask which entries explain a location’s change and inspect the underlying references their permissions allow. The same governed data can support questions in Claude, ChatGPT, or Copilot, without making a chat answer the system that posts stock.

Bring a movement extract into the review

Start with permitted stock entries and the opening and closing balance exports for the same scope.

Leave stock posting and cost treatment with their owners

This workflow reads source records for reconciliation. It does not promise an ERP stock adjustment, a reversal, or a backdated posting through Permute. Any proposed external action needs a supported provider/action scope, current permissions, and approval. Your inventory owner remains responsible for correcting source records.

A quantity tie-out also leaves a separate value question. Microsoft documents that financial updates and inventory close can affect transaction costs in its inventory transaction fields. Preserve source values and currencies if you need them, and use the inventory valuation methods comparison for cost-layer questions. We do not choose accounting treatments or replace general-ledger reconciliation.

Resolve the opening-balance mismatch with the same stock dimensions, cutoff, and source evidence used to reconstruct the closing balance. Keep each signed movement and its stable identity, even when a transfer or reversal nets to zero. Accept the close after the location balances and source-coverage checks agree. Preserve a separate restatement when late entries change history so the next reviewer can explain the difference.

Review the gaps between stock sources

Bring the ERP exports, location mappings, and unresolved movement references to a scoped review.

Questions about stock movement history

When is a stock balance report enough?

Use a balance report when you need quantities at a defined cutoff and have no unresolved movement question. When an opening or closing quantity changes between extracts, keep the balance report as the comparison point and inspect the movement history behind the difference.

What if movements share the same posting timestamp?

Use the source’s transaction sequence or other documented ordering field. Without one, you can reconcile the closing total, but label the intermediate sequence as uncertain. Do not infer the source order from alphabetical document numbers.

Does a stock ledger replace the general ledger?

The operating ledger reconstructs stock movements and balances by item and location. Accounting entries also depend on the ERP’s posting and costing rules, so a quantity agreement does not establish that inventory values or general-ledger accounts reconcile. Keep those reviews linked through source references and owned by the responsible teams.