GRN and MRN are often used interchangeably, but many organizations use them for different control points. The exact naming can vary by company, yet the operational purpose is consistent: record what material physically arrived, compare it with what was ordered and create evidence for inventory, project and accounts teams.
Updated 6 September 2026 · Practical guide for procurement teams
GRN commonly means Goods Receipt Note. It confirms that goods have been received against a purchase order or delivery. A GRN normally records supplier, PO reference, item, quantity received, date, location, accepted quantity and sometimes inspection status. Accounts may use the GRN as one part of invoice verification.
MRN is commonly used as Material Receipt Note in construction, engineering and warehouse environments. It may record the same type of physical receipt as a GRN, but some companies use MRN specifically for site materials while GRN is used in a central warehouse or ERP. The company procedure should define the term clearly so teams do not create duplicate receipt documents.
The important difference is not the acronym; it is the control design. If both documents exist, each should have a distinct purpose. For example, the site may prepare an MRN when material reaches the project and the warehouse or system may generate a GRN after verification. If there is no distinct control need, one standardized receipt process is usually simpler.
Without a reliable receipt record, accounts cannot easily know whether an invoice represents material actually delivered. A three-way check between PO, receipt and invoice helps identify quantity differences, unauthorized rates and duplicate billing. Receipt quality therefore affects both inventory accuracy and payment control.
A digital workflow can allow site or warehouse users to select the PO, record delivered quantities, upload photos or delivery challans and flag shortages. Procurement sees supplier delivery performance, accounts sees payment evidence and management gets a clearer picture of open commitments versus received value.
Suppose a purchase order is issued for 1,000 units. The supplier delivers 950, but inspection rejects 30. The receipt process should not simply mark the PO as delivered. A proper GRN or MRN records 950 physically received, 920 accepted, 30 rejected and 50 still outstanding. Procurement can then follow up on the balance and replacement quantity, stores can record only usable stock and accounts can avoid paying for material that was not accepted.
At minimum, the document should identify the supplier, PO, delivery document, receiving location, item, ordered quantity, delivered quantity, accepted quantity, rejected quantity and receipt date. Depending on the industry, it may also capture batch number, test certificate, vehicle details, photographs or inspection result. The point is not to collect unnecessary fields; it is to capture enough evidence for the next teams to trust the transaction.
If the receiving team records the full PO quantity even when material is missing, inventory becomes overstated and accounts may release excess payment. If users delay receipt entry, procurement reports may show overdue deliveries even though material is already on site. If the same delivery is recorded twice, stock and invoice matching can both be distorted. Clear user responsibility and simple mobile receipt entry reduce these errors.
Some companies maintain both MRN and GRN because different systems or departments evolved separately. That can be valid if each document represents a distinct control point. But if both records duplicate the same physical receipt, users may enter conflicting quantities and dates. Review whether one standardized digital receipt can satisfy site, warehouse, procurement and accounts requirements. Simplifying duplicated controls often improves data quality more than adding another approval.
