Inventory Discrepancy Report Template: Record Variance, Evidence and Resolution

An inventory discrepancy report template turns a count difference into a traceable control record. It should show what was expected, what was physically verified, what evidence was checked, who authorized any correction and how recurrence will be reduced.

The report does not prove theft, error or system failure by itself. Preserve facts, separate hypotheses from findings and follow the organization’s inventory, finance, security and regulated-goods procedures.

Define when a discrepancy report is required

Set triggers before a variance occurs. They may include quantity or value thresholds, repeated differences, negative stock, serial or lot mismatch, missing controlled items, damaged goods, unexplained location moves or a failed reconciliation. A small variance can still require escalation when the item is sensitive or the pattern repeats.

Name the process owner, adjustment authority, escalation route and required separation of duties. The person who counted can provide evidence, but should not silently change the system record. Use the warehouse shift handover checklist when an open discrepancy crosses shifts.

Copy this inventory discrepancy report template

INVENTORY DISCREPANCY REPORT

Report ID / date / status:
Site / zone / bin:
Item / SKU / description:
Lot, batch or serial identifiers:
Unit of measure:

EXPECTED AND VERIFIED POSITION
System quantity / timestamp / source:
First count / counter / method:
Independent recount / counter / method:
Confirmed variance:
Authorized valuation basis, if needed:

EVIDENCE
Photos, labels, scan or transaction references:
Receiving, transfer, pick, return or disposal records checked:
Related reports or system events:

INVESTIGATION
Facts established:
Possible causes still unverified:
Operational, customer, financial or security impact:

RESOLUTION
Containment action / owner / time:
Approved stock correction / approver / time:
Root-cause action / owner / due date:
Verification and closure approval:

Use one report ID across attachments and system notes. Do not paste personal or commercially sensitive information where a restricted reference will do.

Freeze a reliable count position

Record the system quantity with a timestamp and source before investigating. If operations continue, define a temporary movement hold or a clear transaction cut-off so the physical count and ledger refer to the same moment. Otherwise, legitimate picks or receipts can appear as variance.

Verify item, location, unit of measure, pack size, lot and serial identifiers. Count unopened and open containers according to the approved method. Record who counted, what equipment was used and whether the area was accessible during the count. For material discrepancies, use an independent recount without revealing the first result when policy requires it.

Control the count sheet itself. Number pages, identify voided entries, retain original marks and make corrections with a visible reason, author and time. If scanners are used offline, confirm when their transactions synchronize. Also inspect adjacent bins, overflow locations, staging areas and quarantine zones under the approved search procedure; a misplaced item should be transferred through the system rather than informally carried back to the expected bin.

Calculate variance without hiding units

Show expected quantity, verified quantity and arithmetic variance in the same unit. If stock is stored in cases but issued as units, document the conversion rather than mixing measures. Keep quantity variance separate from value impact.

Finance should define the valid valuation basis. Do not infer margin, loss or accounting treatment from a warehouse count alone.

Attach evidence and preserve traceability

Evidence may include count sheets, barcode scans, timestamped photographs, label details, receiving records, transfer confirmations, pick history, returns, quarantine records and approved disposal documents. Reference controlled records rather than duplicating them unnecessarily.

Record both supporting and contradictory evidence. A photograph of an empty bin proves its visible state at a time; it does not establish why stock is absent. Keep original files, access controls and retention rules intact. The quality inspection report template is useful when condition, damage or conformance must be assessed separately.

Investigate the transaction trail

Work backward and forward from the last known reliable balance. Check receipts, put-away, relocations, picks, packing, dispatch, returns, consumption, adjustments and cancellations. Look for duplicate scans, delayed postings, wrong locations, unit conversions, substituted SKUs and cut-off timing.

Classify statements clearly:

• Fact: supported by a named record or verified observation.
• Hypothesis: plausible but not yet demonstrated.
• Finding: conclusion accepted through the defined review process.
• Unknown: evidence is missing or conflicting.

Do not name an individual as the cause without adequate evidence and the appropriate investigation route. Security, misconduct or fraud concerns require restricted handling, not speculation in a general report.

Contain risk before correcting records

Containment prevents further confusion while the investigation continues. Options may include pausing movements, quarantining a lot, restricting a bin, checking adjacent locations, notifying dispatch or preserving system logs. Assign one owner and a review time to every containment action.

Avoid correcting the ledger merely to make it match the first count. The decision log template can preserve a material adjustment decision, authority and rationale. Emergency operational actions should still be documented and retrospectively reviewed under the approved process.

Approve and post the resolution

The resolution should identify the authorized quantity change, reason code, approver, posting reference and effective time. Where the physical stock is right but master data is wrong, correct the responsible source rather than repeatedly adjusting quantities. Where evidence remains incomplete, record that uncertainty.

Separate immediate correction from preventive action. Fixing a balance restores the record; it does not address a broken label, confusing bin layout, delayed interface or training gap. Confirm downstream effects on orders, replenishment, customer commitments and financial reporting with the responsible owners.

Where several systems hold inventory, identify the system of record and reconcile interfaces in sequence. A warehouse platform, enterprise ledger and marketplace feed may update at different times. Record which balance was corrected, which downstream update is expected and how successful propagation will be verified. Never repeat an adjustment in multiple systems merely because the first change is not yet visible.

Turn causes into preventive actions

Use a cause method proportionate to the issue. Repeated discrepancies may justify trend review by item, location, transaction type, shift or process step. Avoid forcing every event into one root cause when evidence supports several contributing factors.

Write actions so completion can be verified: change a scan rule, relabel a location, amend a work instruction, repair an interface, retrain named roles or add a targeted count. Give each action one owner, due date and evidence of completion. Vendor-control gaps can be routed through the vendor due diligence checklist where appropriate.

Capture review conversations responsibly

Discrepancy reviews can include staff information, security concerns and commercially sensitive stock data. Record only when authorized and necessary, provide clear notice and obtain agreement where required. Limit access and retention to the approved purpose.

For an authorized discrepancy review with visible, consented capture, Kuno can help create draft notes and actions for human verification. It does not determine fault, approve adjustments or replace inventory and finance controls. Explore Kuno

Check any AI-assisted draft against original count sheets and system records. A fluent summary can still transpose a SKU, sign, unit or time.

Close only after verification

Closure means more than posting an adjustment. Confirm that the authorized correction reached the intended system, containment was removed safely, affected orders were reviewed, actions have evidence and recurring patterns have an owner. Use meeting follow-up practices to distribute the reviewed outcome and corrections.

Final QA checklist:

• The report ID, item, location, units and timestamps are unambiguous.
• System quantity and physical counts refer to a controlled cut-off.
• Independent recount requirements were followed.
• Evidence is referenced, preserved and access-controlled.
• Facts, hypotheses, findings and unknowns are distinct.
• Quantity and value impacts use authorized methods.
• Containment, correction and prevention have named owners.
• The correct authority approved every stock adjustment.
• Downstream operational and financial effects were checked.
• Closure includes verification, not merely a status change.

Turn authorized review discussions into a traceable draft, then verify every field. Kuno supports consented capture and structured follow-up; accountable people retain judgment over evidence, adjustments and closure. See Kuno