Goods receipts

Route: /org/inventory/procurement · Module: org_inv_procurement — 4 permissions Permission to view: View Inventory Procurements

1. What a goods receipt is

The record that stock arrived from a vendor. One receipt is a batch — many lines posted together under one reference number, typically one delivery or one invoice.

The Goods Receipts list showing four batches with date, a Raw Material or Finished Good type pill, reference numbers GRN-2607-118 to 121, item counts, total costs and remarks — Figure 1 — Four receipt batches. The type pill distinguishes raw materials from finished goods.

	Raw material receipt	Finished goods receipt
You are	Buying inputs to make things	Buying ready-made products to resell
Lines key on	`raw_material_id`	`variation_id`
Typical for	A manufacturer	A trader
The chooser calls it	Default	The alternative

2. How a receipt moves through the module

3. Step by step

Step 1 · Choose what you are receiving

A dialog headed 'What are you receiving?' with the subtitle 'Pick the type of inbound stock for this batch', offering two cards — Raw Materials, badged Default, described as 'Increment stock for materials used in production. Default for manufacturers.' and Finished Goods, 'Buy ready-made products to resell. Use this when trading rather than manufacturing.' — Figure 2 — The type chooser.

Add Receipt Batch does not open the entry form. It asks a question first.

Raw Materials carries a Default badge and is described as the manufacturer's path.

Finished Goods is for buying products you resell without making.

The choice decides which master the lines are drawn from, and it cannot be changed once you are in the grid — go back and start again.

Step 2 · Fill the grid

The Add Raw Material Receipt screen with Reference / Invoice # and Remarks fields, a filter box reading '0 of 160 filled', and a table of every raw material with columns MATERIAL, UOM, CURRENT, LAST COST, QTY, UNIT COST, BATCH # and EXPIRY — Figure 3 — The entry grid. Every material is listed; a line counts only once you type a quantity.

The grid lists every material — 160 on this tenant — and the counter reads 0 of 160 filled. A row becomes part of the receipt only when it has a quantity.

Column	Notes
Material	Read-only
UOM	From the material. Not editable here
Current	The material's `current_stock` today
Last cost	`last_purchase_price`
Qty *	Required per filled line. Must be > 0
Unit cost *	Required. Pre-filled from Last cost; may be 0 but not negative
Batch #	Optional. A vendor lot number
Expiry	Optional date

Above the grid, Reference / Invoice # and Remarks apply to the whole batch.

Step 3 · Save

Save Receipt posts one PURCHASE ledger row per filled line, all sharing a generated batch id and your reference number.

Saving a receipt does not change the Current column

Every line writes a ledger row. Nothing writes current_stock. Come back to this screen after saving and the Current column reads exactly what it did before.

This is the module's most confusing behaviour and it is not a bug you can configure away. See How stock is counted.

4. Validation — the exact strings

Condition	Message
No line has a quantity	`Add a quantity to at least one item`
A filled line has qty ≤ 0, or a negative/non-numeric unit cost	`Each filled line needs a positive quantity and non-negative unit cost`
Save succeeds	`Receipt saved — N items`
Save fails	`Failed to save receipt batch`

5. Permissions — and a gap

Action	Permission	Enforced?
See the screen	`procurement.view`	✅
Menu entry	`procurement.menu`	✅
Post a receipt	`procurement.create`	✅ at the API
Approve a receipt	`procurement.approve`	❌ never checked anywhere

procurement.approve does nothing, and the buttons are not hidden

There is no approval step in the product. The permission exists, can be granted, and is read by no route and no component.

Worse, this screen performs no permission checks in the UI at all — Add Receipt Batch renders for anyone holding procurement.view. A user without procurement.create can fill in a whole batch and only discover the problem when Save fails. See Permissions.

6. The admin contract

Must be true	Or else
A project is selected	The list is empty
Raw materials (or products) exist	The grid has no rows to fill
`last_purchase_price` is set	Unit cost pre-fills as 0

7. Downstream

Effect	Where
One `PURCHASE` row per line	Ledger
Batch grouping	The list view groups by batch id
Cost captured	The row's `unit_cost`, used for valuation
`current_stock`	Unchanged

8. Troubleshooting

Symptom	Cause
Add Receipt Batch opens a dialog, not a form	Correct — the type chooser comes first
Unit cost pre-fills as 0	The material's `last_purchase_price` is 0
Save refused with a validation toast	A filled line has qty ≤ 0 or a negative unit cost
Stock did not go up	Expected. Receipts write the ledger only — see §3
A colleague can open the form but not save	They hold `procurement.view` but not `.create`; the UI does not hide the button

1. What a goods receipt is​

2. How a receipt moves through the module​

3. Step by step​

Step 1 · Choose what you are receiving​

Step 2 · Fill the grid​

Step 3 · Save​

4. Validation — the exact strings​

5. Permissions — and a gap​

6. The admin contract​

7. Downstream​

8. Troubleshooting​