Warehouse Receiving Discrepancy Report: Record Imported Stock Variances at Receipt

Record the difference before the receipt is normalised

For an Australian importer, this record starts when a warehouse has a physical receipt event and the goods differ from the accepted expected record. Preserve that difference. A receiving discrepancy report should show what was expected, what was physically observed, how the observation was made, which evidence is attached, the warehouse-reported location and status of affected stock, and who owns the next decision.

Create one discrepancy item for each difference that needs a different owner or closure test. Do not overwrite the ASN, packing list, purchase order or warehouse receipt merely to make the numbers agree.

The minimum record connects:

• inbound and receipt references;
• receiving site, date, time and receiver;
• affected SKU, carton, pallet or other logistics-unit identity;
• expected value and its source;
• observed value and counting level;
• evidence such as scans, photos, count sheets or document extracts;
• current operational stock status;
• decision owner, next action and due time set by the organisation; and
• objective closure evidence.

Separate expected, observed, cause and disposition

A receiving report becomes unreliable when one note combines four different questions:

1. What did the controlled source say should arrive?
2. What did the warehouse actually observe at the defined checkpoint?
3. What caused the difference?
4. What is the authorised response?

Keep those answers in separate fields. The warehouse can record a physical difference without deciding whether it arose at packing, consolidation, carriage, delivery, counting or system entry. The importer can route an investigation without deciding liability or remedy.

The GS1 Logistics Interoperability Model describes an inbound receipt notification through which a logistics service provider informs the shipper of actual goods received compared with what was notified as sent. That expected-versus-received distinction is useful even where the operation uses a portal, spreadsheet or warehouse-management system instead of a GS1 message.

This article is not a legal acceptance, freight-claim or accounting guide. A signed receipt, photograph, ASN, packing list or WMS posting should be interpreted within its actual scope and the parties' approved procedures.

Anchor every discrepancy to the receiving event

Start from the exact inbound and physical event. Record:

• importer or inventory owner;
• warehouse account and site;
• inbound/ASN reference and version;
• purchase order and supplier packing-list reference;
• transport reference and delivery identifier;
• arrival and receipt timestamps, with site time zone;
• person or system recording the observation;
• SKU and product description;
• pallet, carton, label or barcode identifiers where available; and
• warehouse receipt or WMS transaction reference.

If the receiving team cannot map the physical goods to an expected inbound, classify them as unidentified stock under the warehouse's approved process. Do not force them onto the most plausible open order.

Microsoft's inbound ASN documentation illustrates why identity matters: its process carries source-system item references, quantities, units and packaging information, and can fail when external item mappings do not resolve. Your warehouse may use different technology, but it still needs an attributable mapping rather than a guess.

Link the source records rather than copying partial facts into an email. The commercial-invoice and packing-list reconciliation guide explains the earlier import-document comparison. The discrepancy report uses the warehouse's accepted expected basis and records how the physical receipt differs.

Use one minimum discrepancy record

The following schema is OPL analysis. It can sit in a controlled spreadsheet, 3PL portal, WMS exception or case-management tool.

Avoid a free-text report that says only quantity wrong or damaged on arrival. It hides the source, counting level, affected units, evidence and owner.

Count at the level the evidence supports

The statement one pallet received proves only that one pallet-shaped logistics unit was counted. It does not prove every expected carton, inner pack or sellable unit was inside it.

Distinguish pallet, carton, inner and unit counts

Record both the physical level and the conversion used:

• pallets observed;
• master cartons per pallet where verified;
• inner packs per master carton where verified;
• sellable units per inner or carton where verified; and
• total units counted or calculated.

If a master carton remains sealed and the warehouse procedure counts only cartons, say so. For example: 18 sealed master cartons observed; expected 18; internal unit count not performed. Do not convert that into 432 units physically counted simply because the ASN states 24 units per carton.

Where SSCCs, pallet IDs or carton labels are used, record the identifiers scanned and those missing or unexpected. The SSCC and logistics-label guide explains identifier design; the receiving report records what was actually present.

Record unknowns without inventing precision

If a mixed carton cannot be attributed to a SKU at the receiving checkpoint, record the carton ID, outer markings, observed condition and current location. Mark SKU and unit quantity as unresolved. An explicit unknown with an owner is more useful than an assumed match that corrupts inventory.

Do not apply a universal tolerance. A difference acceptable for one low-value, non-critical operation may be material for another product or customer commitment. Tolerances and authority must come from the organisation's approved procedures.

Classify the observation without deciding fault

Use a short, controlled classification list so trends can later be reviewed. Suitable observation classes include:

• shortage at the verified counting level;
• overage at the verified counting level;
• unexpected SKU or product;
• SKU, barcode or item-mapping mismatch;
• pallet/carton/inner-pack hierarchy mismatch;
• missing or unexpected logistics-unit identifier;
• visible packaging or product-condition issue;
• missing or conflicting receiving document; and
• unidentified stock.

Supplier error, carrier loss and warehouse miscount are not initial observation classes. They are possible findings after the evidence has been reviewed.

SAP's current ASN alert documentation includes a specific state for goods-receipt quantity differing from ASN quantity. The alert identifies a variance in that product; it does not establish who caused it or what commercial response follows.

If the physical observation is a product defect rather than a receipt-identity or count difference, link the supplier defect photo and measurement evidence pack. Do not force technical defect analysis into a general receiving discrepancy note.

If an observation may be safety-critical or involve regulated goods, stop the ordinary discrepancy workflow from making the disposition. Preserve the factual evidence and route the matter through the site's approved controls and qualified safety, regulatory or legal review as applicable.

Record location and case status without authorising stock movement

The report must preserve where the warehouse says the affected stock is and the status already applied under the site's approved process. It must not create a release, quarantine or movement authority. Keep the discrepancy-case state separate from the warehouse stock state.

Do not invent a quarantine label or release authority from this article. The incoming quality inspection guide describes a separate inspection-and-release process. Regulated or safety-sensitive goods require their own approved site controls and qualified review.

Route each discrepancy to the correct owner

The warehouse records the observation; it may not own the commercial, technical or inventory decision. Route by the question that must be answered:

• Receiving or data owner: Is the item mapping, counting unit, ASN or WMS receipt wrong?
• Procurement owner: Does the physical receipt differ from the controlled purchase and supplier packing evidence?
• Product or quality owner: Does observed condition or identity require inspection, defect evidence or technical disposition?
• Transport owner: Is carrier or delivery evidence needed to reconstruct a handoff?
• Inventory owner: Which system status may be changed, by whom and after what verification?

If the discrepancy changes the open purchase position, create or update a linked item in the open purchase-order exception board. Do not hide the receiving evidence inside a supplier follow-up email.

If repeated defects require supplier action, the supplier corrective-action plan owns root-cause correction and effectiveness evidence. The receiving record supplies an input; it does not prove root cause.

Close only against the stated evidence

Write the closure test when the discrepancy opens. Possible tests include:

• a recount at the agreed level confirms the corrected received quantity;
• an item-mapping error is corrected and the physical identifier is rescanned;
• an unidentified carton is matched to a controlled inbound and SKU;
• an authorised disposition is recorded and the WMS status is updated through the organisation's control;
• a linked product-quality or supplier exception reaches its own defined state; or
• the expected source is formally corrected and the receipt is reconciled to the authorised basis.

Closing the report should not erase the original observation. Retain expected value, observed value, investigation evidence, authorised outcome and any system adjustment reference.

This is operational closure, not a conclusion about liability, title, contractual notice, freight claim, refund, credit or accounting valuation. Those questions need the governing agreement, authorised finance process or qualified advice.

Worked example: three differences in one receipt

This example is hypothetical and does not represent an OPL client, warehouse, supplier or result.

Inbound INB-260914-07 arrives against accepted ASN version 3. The 3PL records one receipt event and three separate discrepancies because each has a different owner and closure test.

The warehouse should not collapse these into receipt short by one carton. RD-42 and RD-43 could exist even if the total carton count equals the ASN. Total quantity, identity and packaging hierarchy are different controls.

Preserve closed evidence for later analysis

Retain the original expectation, observation, evidence, authorised outcome, closure record and any linked system transaction. That history can support a separate, controlled defect or provider analysis later, but EVG-172 does not rank categories or calculate supplier performance.

Only verified closed outcomes should feed the supplier performance scorecard. Do not score a supplier from an open receiving observation whose cause is still unknown, and do not rewrite the original record when a later investigation reaches a different conclusion.

Start with the next warehouse receipt

For the next ordinary inbound:

1. identify the accepted ASN/pre-alert, PO and packing source;
2. define the counting level the warehouse will actually verify;
3. prepare one discrepancy ID for each different owner or closure test;
4. record expected and observed values without deciding cause;
5. attach evidence and preserve unknowns;
6. record the warehouse-reported location and current status, then assign the decision owner without authorising a status change;
7. link any PO, quality, transport or supplier-control follow-up; and
8. close only when the stated evidence and authorised disposition are complete.

The useful output is not a polished form. It is a receipt history that remains understandable after the truck has left, the stock has moved and the people involved are no longer reading the same email thread.

Sources

• GS1 Logistics Interoperability Model Application Standard 1.1.1
• SAP Help: Advanced Shipping Notification Alerts
• Microsoft Learn: Import inbound ASNs as despatch advice messages