Skip to main content
GullySystem
Other industries

Goods Receipt (GRN) for Milk collection centres

Record what physically arrives against a supplier order.

Procurement

Does this function belong in your operation?

Use when purchased physical goods need quantity and acceptance checks on arrival.

Purchased goods arrive at a receiving location.

Every can is weighed at the platform and entered with the supplier number, the shift and the net litres. Sour cans are rejected at the door. The morning total tallies with the cooler.

Bring the records the workflow depends on.

  • Purchase order
  • Delivery note
  • Acceptance and storage rules

Outputs to check

  • Numbered receipt and inspection record
  • Accepted and rejected quantity statement
  • Purchase-order balance and bill-match inputs

Follow the goods receipt (grn) workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Identify the delivery

    Match the supplier and delivery note to the order or approved exception.

  2. 2. Count the goods

    Record actual quantities separately from the supplier's stated quantities.

  3. 3. Inspect and classify

    Distinguish accepted, held, damaged and rejected goods.

  4. 4. Post accepted receipt

    Update the appropriate location only for the authorised quantity.

  5. 5. Handover for matching

    Pass receipt evidence to purchasing and accounts while leaving undelivered balances open.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Storekeeper

Counts, enters and keeps the delivery note. The entry made at the dock is what moves stock.

Accounts assistant

Passes bills only against what was received, and holds the rest for purchase to settle.

Purchase executive

Sees which orders are part-delivered and which vendor keeps sending short.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Excess delivery

Record the excess separately and obtain the purchasing decision before accepting it.

Damage at unloading

Capture condition and hold or reject the affected quantity.

Receipt without PO

Route the exception for authorisation and establish a valid purchasing reference before bill approval.

Can this work independently?

Goods receipt needs item and supplier references; a purchase order is preferred or an explicitly approved unplanned receipt is required. Stock posting, quality release and invoice approval are separate handoffs. Receiving a delivery note does not prove that the stated goods were counted or accepted.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Stock: Item-location quantities and authorised stock movements.
  • Vendor bills: Supplier invoice lines and authorised posting status.
  • Quality control: Inspection results and authorised hold or release decisions.

Configure, test and introduce the workflow.

  • We watch how material comes in and who signs for it. You describe the problems met at the gate. A short list of what needs recording returns to you.
  • Open purchase orders and the item list are brought in. The purchase team checks a sample for accuracy. The storekeeper enters real deliveries on a trial screen next to the paper register. Gaps in the form are found and fixed.
  • Hold rules, batch numbers and weighbridge entries are set where they apply. You approve which items need them. Storekeepers and the accounts desk practise on phones and screens. The paper register stops on an agreed date.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Receipt quantities link to the purchase order.
  • Rejected goods remain distinct from accepted stock.
  • Partial deliveries leave the correct balance due.
Milk collection centres

How the business operates.

A collection centre is a short, busy window. Suppliers queue with cans, the pan scale reads, a sample goes to the tester, and a slip is written for a person who has walked four kilometres at dawn. Seconds per supplier. Errors here are paid for later.

Supplier register and pass book

One record per supplier with village or route, animals in milk, bank details and cycle. The pass book lists every shift’s quantity, test and amount, printed or sent as a message.

Milk weighing and test entry

Enter litres or kilograms, fat and solids-not-fat at the platform, from the analyser file or by key. Shift, can count and tester are stored with each line.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Supplier register and pass book. One record per supplier holds village or route, animals in milk, bank details and payment cycle, and the pass book lists each shift’s quantity, test and amount.
  • Milk weighing and test entry. Litres or kilograms, fat and solids-not-fat are recorded at the weighing platform from an analyser file or by key, and the shift, can count and tester are stored with the line.
  • Rate chart and price slabs. The plant’s rate chart by fat and solids-not-fat is held with bonus slabs and effective dates, and every entry takes the row that applied on its day. Old shifts stay as they were.
  • Rejection and quality log. Clot, alcohol and adulteration results are recorded with the rejected cans and the reason given, and suppliers with repeated rejections appear on a review list for the manager.

Operational bottlenecks to check

The pass book and the register disagree

Each supplier holds a pass book, and the clerk keeps a register. A smudged line, a skipped shift or a sheet lost in the rain leaves two versions of the same morning, and neither can be proved. Each side trusts its own.

Rates are applied by memory

The rate chart has changed three times this season, and the clerk reads from a laminated sheet. A wrong row pays one supplier too little and another too much for months.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Supplier arrives

    The supplier is found by code or name. Animals in milk, cycle, bank details and open balance appear on the weighing screen before the can is lifted onto the scale.

  2. 2. Weighing and testing

    Quantity is recorded and a sample is drawn. Fat and solids-not-fat come from the analyser or by key, and a failed clot or alcohol test marks the can as rejected before any litre is added.

  3. 3. Rate and amount

    The chart row is picked automatically. A slip is printed or a message is sent with the quantity, fat, rate and amount, and the pass book picks up the same figures without anyone copying them.

  4. 4. Cooling

    Milk goes to the cooler. Readings are logged at set times by the person who took them, and any reading above your limit is flagged to the manager.

  5. 5. Dispatch

    Each tanker gets a seal number. The plant’s receipt figures are entered beside the load when they arrive, so a short delivery shows up as a difference to chase.

  6. 6. Payment cycle

    At cycle end, entries are totalled, feed dues and advances are deducted, and the bank list or cash payout sheet goes out with a statement for each supplier.

Industry reports to connect with

  • Litres and average fat and solids by supplier, shift and route
  • Rejected cans by supplier and reason
  • Cooler readings above limit, with time and person
  • Tanker loads against plant receipts, with differences

Questions before implementation.

When should milk collection centres consider goods receipt (grn)?

Use when purchased physical goods need quantity and acceptance checks on arrival. Purchased goods arrive at a receiving location.

What should we bring to the requirements discussion?

Bring anonymised examples of Purchase order; Delivery note; Acceptance and storage rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Record what physically arrives against a supplier order. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A goods receipt does not replace specialist inspection or approval of the supplier's invoice.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Receipt quantities link to the purchase order. Use this check when reviewing the first working version.

Talk to us

Discuss goods receipt (grn) for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements