Factory GRN Automation: Resolve Short and Excess Receipts

Putting this workflow into practice? Explore Automation Systems Architecture for implementation scope, controls, and next steps.

A factory goods-receipt workflow should tell procurement what arrived, quality what needs inspection and accounts which supplier bill can be reviewed. Those are connected decisions, but recording a delivery does not complete all three. A useful GRN automation keeps the differences visible until the correct owner resolves them.

Consider an illustrative order for 100 components where 90 arrive and five need inspection. The physical receipt, accepted quantity, purchase-order balance and invoice proposal describe different facts. A single “received” checkbox cannot explain which quantity production may use or which amount finance should approve.

Start with the order line and delivery evidence

Use a stable purchase-order line identifier, supplier reference, item, expected unit and destination location. Preserve the supplier's delivery reference separately. One truck can deliver several orders, and one order can arrive across several trucks; a header-level link alone can leave individual quantities unexplained.

At receipt, capture the observed quantity and evidence used by the stores team. If the supplier's item description differs from the internal item, require a maintained mapping or a reviewer decision. Do not let an operator choose a vaguely similar item merely to finish the entry.

Keep native records and workflow decisions distinct

Tally's purchase-order and receipt-note guidance documents the relationship between orders, receipts and purchases. The purchase-process overview also describes different recording sequences. Confirm the factory's chosen sequence before adding an external GRN queue.

The additional design here covers operational evidence, discrepancy ownership and release decisions. A receipt record may be a valid input without proving that inspection, a supplier amendment or payment review has finished. Show those separate states beside the linked references.

Classify the difference before assigning it

A short receipt needs a different action from a wrong item or an invoice that exceeds accepted quantities. Store the reason and next owner explicitly. Keep the original observed quantity so a later correction does not erase what the receipt team first reported.

Avoid using an automatic tolerance as a substitute for acceptance. A permitted rounding difference in a calculation does not authorise the factory to accept a different material or quantity. Agree each tolerance with its process owner and record the reason for any override.

Support partial delivery without closing the order early

Connect each receipt allocation to its order line. Show cumulative received, accepted, returned and still expected quantities using the appropriate units. If the business cancels an outstanding balance, record who approved the cancellation and why.

Test a delivery that serves two order lines for the same item. The operator should see the allocation rather than the system assigning the whole quantity to whichever order it encounters first. When an earlier receipt is corrected, recalculate the affected balances from linked events.

Hand accounts a comparison they can review

The invoice review should identify the order agreement, receipt evidence and any accepted changes. Keep price, quantity, charges and tax review questions distinct. A three-way comparison can prepare evidence, but the finance team must decide the accounting and tax treatment appropriate to the business.

Mark disputed or incomplete items with a reason and a next action date. Do not label a supplier bill approved merely because its total matches an order. The relevant goods may still be on hold, returned or assigned to a different receipt.

Design the correction path before the import

A receiving error is inevitable. Define how an authorised operator corrects an item, quantity or allocation and how downstream users learn about the change. A corrected receipt may affect inventory availability, supplier follow-up and a payment pack already under review.

Where the process writes to Tally, use stable external references and verify the destination result. A timeout after submission needs a result check before retry. The Tally duplicate-prevention guide explains the transaction-identity issue that also matters in receiving integrations.

Validate the receiving review in a pilot

Use an ordinary receipt, a split delivery, an excess quantity and a supplier bill arriving before inspection is complete. Ask stores and accounts to review each example using only the linked records. The test should reveal whether either team still needs a private spreadsheet to understand the open decision.

Also test an incorrect receipt that has already been used by a later process. The resolution must identify that dependency and route the correction through the authorised source workflow. Deleting the receipt to make the exception disappear would remove the evidence needed by the next reviewer.

Retain the expected quantity, actual observation and final accepted quantity separately in the pilot evidence. A successful review explains why these figures differ. Measure unresolved receipt age and repeated exception causes so the owner can improve purchasing instructions or receiving practice, rather than simply increasing reminders.

Implementation work to scope

1. Map order, delivery, receipt and invoice references at line level.
2. Define physical, accepted, held and returned quantities with unit rules.
3. Build a discrepancy queue with procurement, quality and accounts ownership.
4. Add correction, partial receipt and cancellation evidence.
5. Reconcile a pilot order from receipt through supplier-bill review.

The acceptance pack should include a short delivery, an excess delivery, a wrong item, a partial release and a corrected receipt. Ask each department to reconstruct its decision from the same linked evidence. Measure unresolved discrepancies and time awaiting action rather than counting generated GRNs as success.

Connect receiving to the production decision

Once accepted material is available, the next question is whether it can satisfy a production job. Carry the relevant lot, location and reservation information into that decision. The factory material-readiness guide covers the release boundary.

To scope the receiving and review handoffs around your existing tools, explore automation systems or share one purchase-to-receipt cycle. Start with a representative order and its exceptions so the project proves a complete workflow.

Raghav Mittal

Founder, The Night Marketer (Shopify Select Partner). 12+ years of experience and 450+ brands served since 2015.