Goods Receipt and GRN OCR Parser

A record made at the receiving location confirming what was physically delivered, counted and inspected. It records the delivered quantity, what was accepted, what was rejected or damaged and why, and it carries the signatures and timestamps that make it evidence. It is the third leg of a three-way match and the primary evidence in a cargo claim.

The receipt number and date, receiving location and personnel, the purchase order and delivery references, the supplier, and per line the item, unit of measure, quantity delivered, quantity accepted, quantity rejected and the rejection reason — plus condition notes, seal condition and signature evidence.

Because they drive different actions. The accepted quantity is what should be paid; the rejected quantity is what should be claimed or credited. A receipt recording only a single 'received' figure loses that distinction and pushes the problem into a later dispute with weaker evidence.

It should not. Where a required evidence role is missing, the match reports as incomplete rather than approving by default — because the whole purpose of the receipt is to confirm that what is being paid for actually arrived. An approval issued without it is an assumption, not a control.

Yes, as text alongside the quantity they relate to. A rejected quantity with no stated reason is flagged, because it cannot be actioned: whether three cartons were short-delivered, crushed in transit or wrong-item determines who the claim goes to and under which process.

Where the receipt records it, yes — and where the transport document also carries a seal number, the two are compared. A seal number at delivery that differs from the number recorded at stuffing is a cargo security event, and it is the first thing an adjuster will ask about in a loss claim.

Yes. The PO reference is matched to an existing order record, and line-level comparison of item, quantity and unit follows. Where the supplier uses different item codes, matching uses several signals rather than a single key, and genuinely ambiguous lines are surfaced for a human rather than paired on weak similarity.

Over-delivery is flagged rather than silently accepted, because accepting it may create an obligation to pay for goods nobody ordered. Confirm whether the over-delivery was authorised — some contracts allow a tolerance — before accepting or paying, and record the decision against the shipment.

Yes. Proof-of-delivery notes, warehouse receipts and signed delivery notes carry the same essential evidence — what arrived, in what condition, when, and who acknowledged it — and extract into the same field model. Signature and timestamp evidence is captured as present or absent rather than interpreted.

They are common at loading docks and are handled, though results depend on legibility. Handwritten quantities and annotations are extracted where readable and flagged for review where they are not, rather than being guessed. Given that these documents become claims evidence, a field marked uncertain is more useful than a field filled in confidently and wrongly.

Yes. Reviewed data exports to Excel, CSV or structured JSON with line rows preserved, and connector payloads are available for pushing receipts into a downstream system so the goods-receipt posting does not have to be re-keyed.

It establishes the condition of the goods at the moment custody transferred, with a signature and a time against it. Damage recorded at receipt, with the delivering driver's acknowledgement and photographs referenced, is materially stronger evidence than damage discovered during unpacking a day later — and adjusters treat the two very differently.

No automatic approval is issued when a required evidence role is missing. The result remains incomplete.

Yes. Rejected and damaged quantities and notes are retained separately from accepted quantity.