GRN vs MRN: Difference, Full Form, Workflow & Practical Examples

GRN and MRN in simple terms

GRN usually means Goods Receipt Note. It is created when material or goods are physically received and checked. A GRN gives the business evidence of the received quantity, the accepted quantity, shortages, damage or rejection and the purchase order or delivery reference.

In many construction and project businesses, MRN means Material Requisition Note. It is used when a site, department or user requests material from a store or warehouse. After approval, the requested quantity may be issued and the stock balance should be reduced accordingly.

There is one important terminology warning: some organizations use MRN to mean Material Receipt Note. That can make MRN function very similarly to a GRN. The safest approach is to define the abbreviation clearly in your procurement SOP and software so users never have to guess what the document represents.

GRN vs MRN comparison

A controlled GRN workflow

A reliable receiving process should begin with an approved purchase order. When a supplier reaches the site or warehouse, the receiver checks the delivery document, PO reference, material description, unit, quantity and condition. The accepted quantity is then recorded in the GRN instead of assuming that the supplier invoice or challan is correct.

• Confirm the purchase order and vendor.
• Check delivered quantity against ordered and pending quantity.
• Record shortages, excess delivery, visible damage and rejected quantity.
• Capture delivery challan, invoice or transport references where applicable.
• Identify the project, site, warehouse and receiving user.
• Post only the accepted quantity into available stock.
• Keep an approval and edit history for audit purposes.

This is where a digital workflow becomes valuable. A manual GRN in a spreadsheet can record a number, but it often does not automatically prevent over-receipt, show remaining PO quantity or connect the receipt with the later invoice.

A controlled MRN workflow

For a Material Requisition Note, the requirement begins inside the organization. A site engineer, supervisor or department requests a defined material quantity for a project or activity. The request can then follow approval rules before the store issues material.

For example, a site engineer may request 100 bags of cement for Block A. The system should show the store balance, approved quantity, issued quantity, issue date and receiving person. If only 60 bags are issued, the remaining requirement should stay visible instead of forcing the team to create disconnected records.

Well-designed MRN controls are especially useful for multi-site businesses because the same item may be available in another store. Before placing another purchase order, procurement can see whether an internal transfer is possible.

How GRN, MRN, PO and invoices connect

The strongest workflow is not a collection of independent forms. It is a connected record chain. A purchase requirement can move to RFQ and approval, then to a PO. The vendor delivery creates a GRN. Accepted material becomes available stock. A site requirement creates an MRN and the approved issue becomes project consumption. The supplier invoice can then be checked against the PO and accepted receipt before payment approval.

This connected chain makes it easier to answer practical questions: How much did we order? How much is still pending? How much was received? Which site consumed it? Was the invoice quantity actually accepted? Who approved an exception?

Explore EzyProcure's purchase order workflow, vendor management and procurement automation capabilities for the wider process.

Common GRN and MRN mistakes

• Creating a GRN without a PO or authorized exception reference.
• Recording invoice quantity instead of physically accepted quantity.
• Allowing users to edit posted receipts without an audit trail.
• Using the same MRN abbreviation for different processes without defining it.
• Issuing stock without linking the transaction to a site, project or department.
• Keeping procurement, stores and accounts in separate spreadsheets with no shared document references.

Removing these gaps is less about adding paperwork and more about making each transaction traceable from requirement to payment and consumption.

What to look for in GRN and MRN software

For construction, infrastructure and other material-driven businesses, useful controls include role-based access, multi-site inventory, PO balance checks, partial receipts, rejection tracking, attachments, approval rules, project tagging, stock transfers, mobile-friendly site entry and an immutable activity history.

EzyProcure is designed around connected procurement and site workflows rather than isolated documents. If your team currently manages PO, GRN, MRN, vendors and inventory across spreadsheets or multiple tools, a structured demo can be mapped to your actual approval and site process.