Supplier Despatch vs Receipt Lens™

Upload your own XLSX or CSV files, apply controlled matching rules, review exceptions and export clean outputs. Nothing is submitted to a server.

Local processingdata stays inside the browser session

Exception firstfocus on records that require a decision

local://Supplier_Despatch_vs_Receipt_Lens.html

Processing files…

Everything remains local

Supplier Despatch vs Receipt Lens™

Local working demo · v1.1

1 Upload2 Map & Validate3 Review Exceptions4 Export

1 · Supplier Despatch File

XLSX / CSVChoose a file—

2 · Receipt History

XLSX / CSVChoose a file—

Date tolerance days

Automatic mapping will recognise common names such as PO Number, Purchase Order, PO Ref, Material, Part Number, Qty and GR Date.

Matched—ready records

Missing—no receipt found

Variance—quantity or date

Review Required—decision needed

Ready to Export—clean output

How to read this comparisonSupplier Qty comes from the despatch file.Receipt Qty comes from a matched receipt record.No receipt found means no matching record exists — it does not mean zero units were physically received.

Choose both files or load the included sample data.

The Lens will validate, match and classify every supplier despatch line.

Included logic

Exact PO + line + item matching, fallback mismatch detection, duplicate checks, quantity validation, date tolerance and UOM review.

Demo limitations

This showcase uses generic rules. A production Lens is configured around your actual files, tolerances, business decisions and required outputs.

Privacy

The tool reads files inside the browser. Closing or refreshing the page clears the working session.