Stock mismatch is a difference between a physical inventory count and the recorded balance for the same item, location, batch, unit and time. Reconciliation establishes the difference; investigation explains its cause.
Quick answer: To fix stock mismatch in a Delhi factory, compare physical stock with the stock ledger at the same cut-off time, item, location, batch and unit of measure. Trace receipts, production issues, returns, transfers, scrap and dispatches before approving adjustments. Choose inventory software or ERP around the movement that repeatedly goes unrecorded.
A storekeeper says material is available, production says it was consumed, and accounts shows a third figure. Buying another dashboard will not resolve that disagreement unless every team is recording the same events. This guide helps factory owners and operations managers diagnose the gap before choosing technology.
Prepared by Dork Industry · Updated 30 September 2026. Examples below are illustrative, not customer results or promised savings.
What causes stock mismatch in manufacturing?
Stock differs when the physical movement and its recorded transaction disagree. Common causes include delayed material issues, incorrect units, duplicate receipts, unrecorded scrap, transfers posted to the wrong location and returns left outside the ledger. A difference is a signal to investigate; it does not establish theft or prove that your software needs replacing.
Separate raw material, work in progress (WIP), finished goods, rejected stock and material held by a job-worker. A bag moved from stores to the shop floor has not necessarily been consumed. A completed batch awaiting inspection may not yet be available for dispatch. Mixing those states produces misleading totals even when nobody has lost material.
| Symptom | What to investigate | Evidence to compare |
|---|---|---|
| System stock exceeds physical stock | Unposted issue, dispatch, scrap or wrong receipt | Issue slips, dispatch records, scrap approvals and receipt quantities |
| Physical stock exceeds system stock | Unposted receipt or return; duplicate consumption | Goods receipts, unused-material returns and production postings |
| Company total matches, location does not | Missing or misdirected transfer | Source issue, in-transit record and destination receipt |
| Quantity matches, value does not | Valuation, costing or posting-date issue | Costing method and financial reconciliation reviewed with accounts |
| Differences repeat for one material | Unit conversion, weighing or batch-identification issue | Item master, pack size, calibrated measurements and batch labels |
How do you fix stock mismatch in 8 practical steps?
Reconcile one item-location-batch combination at a defined cut-off time. Record the physical quantity independently, export the ledger balance for that time and trace every intervening movement. Recount unexplained differences before correcting records. Keep the original discrepancy, reason, supporting documents and approval so the next review can distinguish a genuine fix from another adjustment.
- Set a counting boundary. Choose one store, material group or line. Define what is included and who owns the count.
- Control movements. Pause movements where practical. Otherwise log every receipt and issue during the count, with times, so both balances refer to the same instant.
- Confirm item identity. Check SKU, batch, location and units. Do not compare kilograms with bags until the conversion is verified.
- Count without copying the expected balance. Use an independent recount for material differences and follow your safety procedures for handling stock.
- Trace the ledger. Check opening balance, receipts, production issues, returns, transfers, dispatches and approved write-offs.
- Document the explanation. Assign a reason code and owner. Do not label an unexplained discrepancy as normal wastage.
- Approve the correction. Apply your authorization controls and accounting policy; preserve the audit trail.
- Test the next cycle. Confirm that the same root cause does not recur after the workflow changes.
ERPNext’s official stock reconciliation documentation describes comparing physical and system balances and supports item/warehouse reconciliation. That is a software mechanism; your team still needs a reliable count and an explanation for the difference.
What should a stock reconciliation worksheet contain?
A useful worksheet records identity, time, quantities and the explanation for any difference. Include the item code, location, batch, unit, cut-off time, ledger balance, physical count, signed variance, reason code, evidence and reviewer. Keep unresolved cases visible rather than overwriting them with a corrected total that hides the underlying operational problem.
Illustrative stores-only example: A resin store begins with 1,000 kg, receives 500 kg, issues 800 kg to production and receives 50 kg of unused material back. With no other movements, its expected closing balance is 750 kg. A physical count of 710 kg creates a signed variance of −40 kg.
Expected closing stock = opening + receipts + returns + transfers in − issues − dispatches − transfers out − approved write-offs. Adapt the movement categories to your system. Do not subtract production consumption a second time if the same quantity was already removed by a stores issue.
| Worksheet field | Example | Purpose |
|---|---|---|
| Item / location / unit | RESIN-A / Stores-01 / kg | Ensures like-for-like comparison |
| Cut-off | Shift-end timestamp | Aligns count with ledger snapshot |
| Expected / actual | 750 / 710 kg | Records the original discrepancy |
| Signed variance | 710 − 750 = −40 kg | Shows direction and quantity |
| Reason / document / owner | Pending investigation | Prevents invented explanations |
| Approval / next check | Assigned reviewer and date | Closes the loop with accountability |
Do not assume the 40 kg was stolen or scrapped. Check an unposted issue, a timing difference, weighing error, incorrect opening balance and material in another location first. The example is arithmetic, not a benchmark for acceptable factory loss.
Do you need inventory software, ERP, barcodes or IoT?
Choose technology according to the failed workflow. Inventory software can handle location-level movements and counts; ERP connects those movements to purchasing, production and finance. Barcodes help identify items when operators scan correctly. IoT may help capture suitable equipment measurements. None automatically repairs inaccurate master data, skipped transactions or unclear responsibility for recording material.
| Option | Best-fit problem | What to verify |
|---|---|---|
| Controlled spreadsheet | Limited movements with one accountable owner | Version control, permissions and reconciliation discipline |
| Inventory management system | Multiple bins, batches, counts and transfers | Location ledger, scanning, returns and adjustment approvals |
| Manufacturing ERP | Purchasing, BOM, production, WIP and finance are disconnected | Material issue/return logic and actual versus planned consumption |
| Barcode layer | Wrong item or location identification | Labels, device usability and correction workflow |
| IoT or connected scales | A suitable physical measurement needs automated capture | Calibration, integration, ownership and exception handling |
| Custom integration | Existing tools are useful but exchange unreliable movement data | Duplicate prevention, retries and reconciliation reports |
For broader context, read our guide to manufacturing visibility in Delhi NCR and explore Dork Industry’s manufacturing technology solutions. This article focuses specifically on stock discrepancies, rather than general factory management.
What should Delhi manufacturers test in a software demo?
Ask vendors to demonstrate your material journey, not only their dashboard. For a Delhi operation with a separate warehouse, shop floor or job-worker, the demo should preserve location, ownership and material state through each handover. Use representative data and require the system to explain a discrepancy without deleting history or relying on manual spreadsheet reconciliation.
If your operation spans industrial locations such as Bawana, Narela, Okhla or Naraina, test the actual transfers and user roles involved. These are planning scenarios, not claims that Dork has a customer or branch at each location. Geography matters when handovers, connectivity, training or support affect how promptly movements are recorded.
- Receive material into inspection, then release accepted quantity to usable stock.
- Issue part of a batch to a work order and return unused material.
- Record a transfer with an in-transit state and destination confirmation.
- Track material sent to a job-worker separately from material consumed.
- Record scrap with a reason and an approval trail.
- Retry the same integration message and confirm it does not duplicate stock.
- Recount one item and show the authorized adjustment and original evidence.
- Export balances and movement history so you can verify them independently.
Acceptance criterion: opening balance plus the demonstrated movements must equal the closing balance for each item and location, with every transaction traceable to its source. Agree response times, data ownership, backup recovery and support scope in the proposal. Delivery dates and costs depend on the verified requirements.
How do you know the fix is working?
Measure repeat discrepancies, posting delay and unresolved exceptions against a documented baseline. Use the same counting scope, frequency and tolerance before and after the change. A cleaner dashboard is not proof of better inventory accuracy. The useful result is fewer repeated causes, faster investigation and more dependable purchasing, production and dispatch decisions.
- Exact-match rate: item-location-batch records matching physical counts ÷ records counted × 100. If using a tolerance, state it separately.
- Absolute variance: total absolute quantity difference within a comparable unit or item group. Do not add kilograms and pieces.
- Posting delay: elapsed time from physical movement to ledger posting.
- Exception age: time an unresolved discrepancy remains open.
- Recurrence: repeat discrepancies attributed to the same validated cause.
Start with a scoped pilot. Clean item codes and units, agree movement ownership, reconcile opening balances, train users and test real transactions. Expand to another location only after the pilot’s balances and exception process are trustworthy. AI can help prioritize anomalies later; it is not a substitute for a reliable stock ledger.
How do you prevent stock mismatch from returning?
Prevent stock mismatch by recording each material movement once, at the point it occurs, with a clear item, location, quantity and owner. Validate units and batch identity before posting. Give supervisors an exception queue for missing or rejected transactions, then review repeat causes instead of making recurring adjustments that hide the workflow failure.
Separate recording from approval
A stores operator may record an issue, while a supervisor approves exceptional adjustments. Define who can create an item, change a conversion, backdate a movement or authorize a write-off. Keep an audit trail showing the original transaction and any correction. This makes a stock mismatch investigation reproducible without requiring the business owner to reconstruct conversations.
Make delayed and failed entries visible
If a handheld device loses connectivity, an offline capture workflow should retain the transaction safely and show whether it has synchronized. A failed integration should create a visible exception with a source identifier, retry status and responsible person. Repeated delivery of the same movement must not create repeated stock entries. Test these situations before rolling out devices across a factory.
Schedule risk based cycle counts
Count a selected set of items between full stocktakes. Prioritize materials that repeatedly differ, stop production when unavailable, have high value or move frequently. Choose counting frequency from your operational risk and capacity rather than copying a universal target. Preserve the count scope so an apparent improvement is not simply the result of checking easier items.
How should a factory handle WIP and job work?
Track work in progress and externally held material separately from available stores stock. A transfer to production changes location or state; it is not automatically final consumption. Record material sent to a job-worker, returned finished goods, unused material and approved scrap against the same job so the balance can be explained without mixing unlike units.
For example, a Delhi factory might send material to an external processor while retaining ownership. The stock record needs to show where it is held and whether it is available for another order. Do not remove it from company-owned stock merely because it left the premises, or include it in usable stores stock merely because it remains company-owned.
Where material changes form, distinguish the input quantity from output units. A job using kilograms of material to produce pieces needs a defined yield or conversion model and separate scrap records. A stock mismatch caused by comparing input kilograms directly with finished pieces is a measurement-design issue, not proof of a missing consignment. Validate the process with production and accounts before configuration.
What information should you bring to an inventory consultation?
Bring a recent stock mismatch, its count sheet and movement records for the same item and period. Include item units, locations, production or job-work references, the current software and the people recording each handover. Remove unnecessary personal or confidential data from samples. A concrete exception helps distinguish process changes from configuration, integration or custom-development requirements.
- A sample receipt, production issue, unused-material return and dispatch record.
- The item master and verified unit conversion for the affected material.
- One count-to-ledger comparison with its exact cut-off time.
- A list of stores, production locations and external processors involved.
- The rules for approvals, stock adjustments and posting-date changes.
- Your baseline for recurring differences, investigation time and delayed entries.
Ask for a written scope stating which stock mismatch causes the project addresses, which remain process responsibilities and how success will be tested. Start with a demonstration using representative transactions. Review migration, device compatibility, training, data export and support alongside software features; each can affect whether the records stay dependable after launch.
How can Dork Industry help?
Dork Industry’s manufacturing offering connects software, ERP, industrial IoT and operational reporting. Bring a recent stock discrepancy, a sample movement ledger and your current process to a discovery discussion. The first decision is whether better controls, configuration or integration can resolve the problem before a larger development project is justified.
Discuss your factory’s inventory mismatch with Dork Industry. Tell us which material differs, where the discrepancy appears, which systems you use and how many locations are involved. Call +91 82107 92477. Dork Industry is based in Rohini, Delhi.
Frequently asked questions
Can inventory software eliminate stock mismatch completely?
No system can guarantee that. Software can validate movements and preserve history, but accurate counts, correct item masters, disciplined entry and clear ownership remain essential. Evaluate results against your baseline.
Can we keep our accounting software?
Possibly. Test whether an integration can exchange approved movements without duplicates, timing gaps or conflicting item codes. Retaining a useful accounting system may be more practical than replacing every application.
Should we adjust stock every time a difference appears?
Investigate and recount first. Approved adjustments correct balances; they do not fix recurring causes. Retain the reason, evidence and authorization, and consult accounts about valuation effects.
How much does a manufacturing inventory project cost?
Cost depends on locations, users, workflows, hardware, migration, integrations, training and support. Request a scoped proposal after demonstrating representative transactions; a generic price is not a reliable project estimate.
Do we need AI to improve stock accuracy?
Usually the first requirements are dependable movement records and controls. Consider AI only when reliable data and a specific anomaly-detection or forecasting use case justify it.
Sources and methodology
This guide combines a Dork Industry diagnostic framework with the ERPNext stock reconciliation documentation and the capabilities described on Dork Industry’s manufacturing page. The worksheet, demo checklist and numerical example are editorial tools, not a verified customer case study. Images are AI-generated illustrations. No search-volume estimate, competitor performance figure or savings guarantee is claimed.