Goods Received Note | Optiwise
Learn what a Goods Received Note is, why GRN matters in purchasing and inventory control, what details it should include, and how ERP helps manufacturers avoid stock and billing errors.
Goods Received Note: The Small Document That Protects Purchase, Inventory, And Accounts
A Goods Received Note, often called GRN, is created when a business receives material from a supplier and records what actually arrived.
It sounds like a simple receiving document. In practice, it is one of the most important control points in a manufacturing business.
A GRN answers a basic question: did the supplier deliver what the business ordered, in the right quantity and acceptable condition?
If the answer is recorded properly, inventory becomes accurate, accounts can verify supplier bills, purchase can track pending quantities, and production can plan with confidence. If the GRN is skipped or loosely maintained, the business starts depending on assumptions.
For manufacturers, AICAN Optiwise treats GRN as more than a form. It is the moment where purchase data becomes real stock.
What Is A Goods Received Note?
A Goods Received Note is an internal document prepared by the buyer when goods are received from a supplier. It records the material received, quantity, condition, supplier details, purchase order reference, delivery challan or invoice reference, date of receipt, and inspection status where applicable.
The GRN is usually prepared by the stores or receiving team after checking the supplier delivery.
In a manufacturing business, a GRN may be created for:
- Raw material
- Packaging material
- Bought-out components
- Spare parts
- Consumables
- Tools and fixtures
- Finished goods received from subcontractors
- Any other purchased goods entering the business
The GRN becomes evidence that goods physically entered the company premises.
Why GRN Matters So Much
A factory may place a purchase order for 1,000 kg of raw material. The supplier may send 950 kg. The delivery challan may show 1,000 kg. The invoice may later arrive for 1,000 kg. If the receiving team does not create a proper GRN, accounts may pay for more than what was received.
That is one simple example. The real risk is larger.
Without GRN discipline:
- Stock may be updated incorrectly
- Purchase order pending quantity may remain wrong
- Supplier bills may be approved without verification
- Rejections may not be tracked
- Production may plan with material that is not usable
- Short receipts may go unnoticed
- Duplicate or excess deliveries may become hard to identify
A GRN protects the business because it creates a factual receiving record.
GRN In The Purchase-To-Pay Flow
GRN sits between purchase order and supplier billing.
A typical process looks like this:
- The business raises a purchase requirement.
- Purchase creates a purchase order.
- Supplier dispatches goods.
- Stores receives the material.
- Stores checks the material against PO and supplier document.
- GRN is created for the quantity actually received.
- Quality team inspects material if required.
- Accepted quantity moves to usable stock.
- Accounts matches supplier invoice against PO and GRN.
- Payment is processed after verification.
This is why GRN is central to internal control. It connects purchase commitment, physical receipt, inventory update, quality approval, and financial liability.
What Details Should A GRN Include?
A useful GRN should be clear enough that a person can understand the receipt even months later.
Common GRN details include:
- GRN number
- GRN date
- Supplier name
- Supplier GSTIN if relevant
- Purchase order number
- Delivery challan number
- Supplier invoice number if available
- Item code and item name
- Item description or specification
- Ordered quantity
- Received quantity
- Accepted quantity
- Rejected quantity
- Unit of measurement
- Batch number or lot number where applicable
- Warehouse or location
- Vehicle or transport reference where needed
- Inspection status
- Remarks about shortage, damage, or mismatch
- Prepared by and approved by details
In ERP, many of these fields can be pulled from the purchase order. That reduces manual entry and helps avoid spelling or item-code mistakes.
GRN And Inventory Accuracy
The inventory impact of GRN depends on the company’s control process.
In some businesses, stock is updated immediately after GRN. In others, material first goes into inspection stock, and only accepted quantity moves into available stock after quality approval.
Both approaches can work if the rules are clear. The mistake is treating all received material as usable before it is checked.
For example, if 500 units arrive and 50 are damaged, ERP should show the difference between received, accepted, rejected, and pending supplier action. Otherwise, production may believe 500 units are available even though only 450 can be used.
This is where a connected ERP system becomes valuable. Optiwise by AICAN can help manufacturers connect GRN with purchase orders, inventory, quality, and supplier follow-up so material status does not remain hidden in someone’s notebook.
GRN And Supplier Bill Checking
Accounts should not approve supplier invoices only because an invoice has been received. The invoice should be checked against purchase order and GRN.
This is often called three-way matching:
- Purchase order: What did we agree to buy?
- GRN: What did we actually receive?
- Supplier invoice: What is the supplier asking us to pay?
If all three match, the bill is easier to approve. If there is a difference, the business can investigate before payment.
Common mismatches include:
- Invoice quantity higher than received quantity
- Rate different from purchase order
- Tax calculation mismatch
- Material received against wrong PO
- Short delivery not adjusted
- Rejected material still billed
GRN gives accounts a practical checkpoint instead of forcing them to rely on verbal confirmation.
GRN And Quality Control
For manufacturing companies, receiving material is not enough. The material must also be usable.
A GRN process can include quality inspection. Some items may need visual checks, dimensional checks, lab testing, certificate verification, or batch approval.
A good ERP process should let the business track:
- Material awaiting inspection
- Accepted quantity
- Rejected quantity
- Rework or sorting requirement
- Supplier replacement pending
- Debit note or credit note requirement
This is especially important for businesses supplying to larger customers, regulated sectors, or quality-sensitive products.
Manual GRN Vs ERP-Based GRN
A manual GRN can work for a very small business, but it becomes difficult when volumes grow.
Manual GRN problems usually include:
- Duplicate GRN numbers
- Missing purchase order references
- Incorrect item names
- Delayed stock update
- No easy link to supplier bill
- No visibility of rejected quantity
- Difficulty finding old records
- Weak audit trail
ERP-based GRN improves control because it connects the receipt to existing purchase data. The receiving team can select the purchase order, enter actual received quantity, record shortage or excess, route material to inspection, and update inventory according to approval rules.
That is why GRN should not be seen as clerical work. It is one of the control points that keeps purchase, stores, quality, and accounts aligned.
Practical Example
A fabrication unit orders 200 sheets of a specific grade of metal. The supplier sends 200 sheets, but stores finds that 12 sheets are visibly damaged. The delivery challan shows full quantity.
If stores simply accepts the delivery and updates stock as 200 sheets, production may issue all 200. The damaged sheets may be discovered later, causing delay and confusion.
With a proper GRN:
- 200 sheets are recorded as received
- 188 are accepted
- 12 are marked rejected or under review
- Purchase is notified for supplier replacement or commercial adjustment
- Accounts sees the mismatch before payment
- Production sees only usable stock
This is the kind of operational discipline that prevents small errors from becoming expensive ones.
Where AICAN Optiwise Fits
AICAN helps manufacturers move from disconnected spreadsheets to connected operational workflows. In AICAN Optiwise, GRN can become part of a larger purchase and inventory flow: purchase order, material receipt, quality check, stock update, supplier bill verification, and reporting.
The result is not just better documentation. It is better control over material and money.
Founder’s Note
In many factories, the receiving gate is where control either begins or quietly fails. If the business records material correctly at the time of receipt, many later problems disappear. If it does not, everyone spends time correcting avoidable confusion.
Our belief at AICAN is that ERP should make these routine control points easy enough that teams actually follow them. A good GRN process is not bureaucracy. It is protection.
FAQs
What is a Goods Received Note?
A Goods Received Note is an internal record created when a company receives goods from a supplier. It captures what arrived, in what quantity, and in what condition.
Who prepares the GRN?
The stores, warehouse, or receiving team usually prepares the GRN after checking the supplier delivery against purchase order and delivery documents.
Is GRN the same as an invoice?
No. A GRN is created by the buyer to record receipt of goods. An invoice is issued by the supplier to request payment.
Why is GRN important in manufacturing?
GRN helps maintain accurate stock, supports quality checks, verifies supplier invoices, and gives purchase teams visibility into pending or short deliveries.
Can ERP generate GRN automatically?
ERP can help generate a GRN from purchase order data, but the receiving team still needs to confirm actual quantity, condition, and acceptance status.
Related Posts
Kanban System | Optiwise
Learn how a Kanban system works in manufacturing, where it helps, where it fails, and how Optiwise connects Kanban signals with inventory, purchase, and production planning.
Erp In Operations Management | Optiwise
Learn how ERP improves operations management by connecting planning, inventory, purchase, production, quality, dispatch, finance, and reporting.
ERP for FMCG Companies in India
A practical guide to ERP for FMCG companies in India, covering distributor orders, batch tracking, expiry, inventory, production, schemes, costing, and reporting.
What's the Difference Between Odoo, Acumatica, and Dynamics 365 for Small Businesses?
Compare Odoo, Acumatica, and Microsoft Dynamics 365 for small businesses across flexibility, cost, implementation, manufacturing fit, ecosystem, and support considerations.

