Module
Goods Receipt
What actually arrived, matched against what was ordered and what was billed.
Watch demo
The bill is for a hundred. Sixty arrived. Nobody put the two documents side by side.
The running product, filmed as it works — every number on screen was computed live while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.
What it produces
- A receipt document per delivery — date, quantity, who signed for it — posted or reversed, never edited
- Three-way match: purchase order against receipt against supplier invoice, line by line
- The difference named as ahead of the goods, over the agreed price, or inside a tolerance you stated
- A rejection counted inside the delivery, so a defect does not read as a short shipment
A worked example
100 bearings ordered at ₹250 · 60 received · billed for 100
acceptable = received 60 − rejected 0 = 60
quantity variance = invoiced 100 − acceptable 60 = 40 ahead of the goods
verdict: QUANTITY_OVER — the line is held and the receipts behind it are named
price variance = (250 − 250) × 100 = ₹0, so the rate is not the question
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
A purchase order line here already records what arrived and what was rejected on inspection, so the quantity is known. But a running total is not a receipt, and a three-way match compares three dated documents — order, receipt, bill — to find which of the three disagrees. Without the receipt document there is nothing to match against, and an invoice gets approved on somebody's memory of a delivery. This is the closest of the unbuilt modules to being possible, because the hard part is already recorded.
Opened by WAREHOUSE_MANAGER and the procurement lead — what each of them sees first.
Said before you ask
What we don’t do.
SIAARU decides from your records and nothing else. It carries no copy of the world’s data, states no number your systems have not, and acts in nobody’s name. Where your data does not support an answer, it says so by name rather than producing a confident one — which is the whole reason a decision taken on it holds up later.
Released, and three things it deliberately does not do. It does not approve a bill: the match produces the verdict and approving an invoice for payment stays a person's act with their name on it. It does not post to a ledger. And receipts are entered against an order rather than imported in bulk — a bulk path lands when a tenant asks for one, through the same refusals. Batches are held by Quality and are not yet joined to the receipt line.
Where this sits
One of 36 modules, on one engine.
Goods Receipt reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 35 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.