A goods received note (GRN) is a control point between an approved purchase order and the materials recorded for a construction project or store. For UAE contractors, reviewing the GRN before downstream accounting or store activity can help teams confirm that the receipt matches the approved order and that quantity and cost information is traceable.
What a construction GRN should confirm
BlueberryERP’s documented GRN rules require a GRN to be linked to an approved LPO. Supported LPO types include Project, Store, Asset and Other. The LPO type determines whether the related Store or Project field is shown. This gives the receiving team a defined reference before recording goods received.
| Review stage | Evidence to check | Control question |
|---|---|---|
| 1. Purchase reference | Approved LPO and LPO type | Is the GRN linked to an approved LPO? |
| 2. Quantity receipt | Received quantity and remaining LPO balance | Does each received quantity stay within the remaining LPO quantity? |
| 3. Downstream use | Purchase invoice and Store Issue Voucher status | Is the GRN still editable, or has it already been used downstream? |
Three GRN purchase-control checks
1. Match the GRN to an approved LPO
A GRN cannot be created without an LPO in the documented workflow. The receiving team should therefore confirm the approved LPO reference and its type before accepting the receipt. For project materials, the project context matters; for store materials, the store context is relevant. This check helps separate goods received against an approved purchasing decision from an unreferenced delivery.
2. Check the remaining quantity
BlueberryERP does not allow the quantity received for an item to exceed the remaining balance on the LPO. The practical review is to compare the delivery quantity with the quantity still available on the purchase order. If the receipt would exceed that balance, the team should resolve the discrepancy before treating the delivery as a valid GRN receipt.
3. Understand when editing is blocked
A GRN cannot be edited after it has been used to create a purchase invoice or after a Store Issue Voucher has been created from it. Editing is also blocked if the linked LPO has been cancelled. This makes the timing of review important: receiving and finance teams should investigate quantity or reference issues before downstream documents depend on the GRN.
How GRN controls support better project records
Purchase expenses are distributed proportionally to each item’s gross amount in the documented GRN workflow. The allocated expense is added to the item’s total cost, increasing its average cost. For that reason, a GRN review should include both the item quantities and the purchase context that supports the recorded cost.
These checks are useful for project managers, store teams and finance reviewers who need a shared view of what was ordered, what was received and whether the receipt has already moved into invoice or store-issue processing. BlueberryERP can help contractors keep these checks within an ERP workflow grounded in the underlying purchasing records.
For more information about Blueberry ERP for construction companies, visit Blueberry Software.
