Buyers and category managers
Compare suppliers, quotations, prices and commercial terms.
Warehouse Operations Tools
Receiving Discrepancy Checker Online Free
Compare purchase-order quantities with physical receipts and identify shortages, overages and damaged stock before put-away or invoice approval.
Receiving Discrepancy Checker
Compare expected and received quantities to identify shortages, overages, damage and receipt exceptions before put-away. Supported files are processed locally in your browser.
Upload a CSV or Excel file to begin.
Business context
The business problem this tool helps solve
Receiving discrepancies occur when delivered quantity, accepted quantity or condition does not match the purchase order. Detecting the exception before put-away protects inventory accuracy, supplier claims and invoice approval.
What can happen when the issue is ignored
- • Shortages hidden after put-away
- • Damaged stock entered as available
- • Over-receipts accepted without approval
- • Invoice paid for quantities not accepted
Who should use this tool?
This guidance is designed for people who need to use receiving discrepancy checker results in a real approval, planning or operational workflow.
Operations managers
Balance price, service, quality and continuity of supply.
Small-business owners
Make repeatable purchasing decisions without a complex ERP report.
Input guide
Prepare the inputs before calculation
| Column | Purpose | Example |
|---|---|---|
| PO Number * | Purchase order connected to the receipt. | PO-10872 |
| Item or SKU * | Delivered product or material. | PK-220 |
| Expected Quantity * | Quantity due according to the purchase order or ASN. | 500 |
| Received Quantity * | Physical quantity delivered before damage adjustment. | 492 |
| Damaged Quantity * | Quantity quarantined or rejected due to condition. | 4 |
| Supplier * | Vendor responsible for the delivery. | Northstar Packaging |
Mapping note: Use consistent dates, currencies, units and definitions. A correct calculation based on inconsistent inputs can still lead to a poor decision.
From raw data to a business decision
Use the analysis as a controlled decision-support step: prepare reliable data, review the exceptions, verify the cause and document the action taken.
- STEP 1
Prepare
Clean the source data and confirm the required fields and reporting period.
- STEP 2
Analyse
Run the tool and prioritise the most important receiving discrepancy results.
- STEP 3
Investigate
Validate the cause with contracts, transactions and operational evidence.
- STEP 4
Act and review
Assign actions, export the report and measure improvement in the next cycle.
Decision support
Recommended next actions
These actions are practical review priorities. Apply your organisation's approval limits, tolerance rules and contractual requirements.
- 1
Immediate
Review the material receiving discrepancy exceptions
Start with records that have the greatest financial, service or operational effect. Confirm the source data before taking action.
- 2
Next
Identify the business cause
Separate genuine performance or demand movement from data quality, timing, unit, currency and process issues.
- 3
Monitor
Create a repeatable review
Run the analysis on a consistent schedule, record decisions and compare whether corrective actions improve the next period.
Practical review tips
- • Use one reporting period and consistent definitions.
- • Review high-value exceptions before low-value noise.
- • Keep operational context with the analysis.
Common mistakes
- • Using incomplete or stale records.
- • Mixing units, currencies or reporting periods.
- • Taking action without checking the underlying transaction.
Good control practices
- • Define thresholds before reviewing results.
- • Assign each action to an owner and due date.
- • Retain the exported report with management decisions.
Practical examples
How teams use this analysis
The same result can require a different response depending on product criticality, shelf life, contract terms, service impact and available alternatives.
Restaurant supply
A chilled delivery arrives short and two cartons are damaged.
Expected outcome: Accepted quantity is recorded correctly and the supplier claim is raised before invoice approval.
Manufacturing
A supplier sends more material than the approved PO quantity.
Expected outcome: The excess is held pending buyer approval rather than automatically received.
About this warehouse tool
This tool creates an exception report from receipt data. It supports receiving control but does not replace physical inspection, quality checks, supplier claims or authorised receipt tolerances.
How to use it
- Upload a PO and receipt comparison file.
- Map PO, item, expected, received, damaged and supplier columns.
- Run the discrepancy check.
- Quarantine, query or approve each exception before completing the workflow.
Related Warehouse Operations Tools
Frequently asked questions
How is accepted quantity calculated?
The analysis subtracts damaged quantity from received quantity. Confirm whether your process uses additional rejected or quarantined statuses.
Can an over-receipt be accepted?
Only according to your purchase-order tolerance, contract and authorised approval process.