Skip to main content
GullySystem
Manufacturing

Goods Receipt (GRN) for PCB assembly companies

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.

Reels, trays and tubes arriving from distributors are checked against the order for part number, quantity and date code. Moisture barrier bags are inspected for damage. Short deliveries are noted against the supplier.

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.
PCB assembly companies

How the business operates.

An assembly job is won or lost on small things. A reel with the wrong resistor value. Solder paste past its jar life. A moisture-sensitive BGA left out of the bake cycle. Each one is cheap to prevent and costly once boards are reflowed, tested and packed for a customer who expects them on Friday.

Bill of materials with approved alternates

Hold the customer’s list with reference designators, approved alternate parts and quantity per board, and flag substitutions that were not approved.

Reel and component lot register

Record the supplier, lot and date code of each reel received, and link the reel to the assembly lot that used it.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and quotations. Price an assembly from bill of materials cost, stencil, feeder setup, line time, test and assumed first-pass yield, and keep every revision of the quote for the next repeat order.
  • Board BOMs and alternate parts. Hold reference designators, quantity per board, approved alternates and revision letter, and flag a substitution that the customer has not approved before the kit is pulled.
  • Component purchase and receipt. Raise orders for shortages, record reels received with supplier lot, date code and moisture class, and send sensitive parts to the bake oven before they reach a shelf.
  • Reel and lot traceability. Link each reel to the assembly lot that consumed it, so a field return leads to the exact supplier lots and date codes on that board.

Operational bottlenecks to check

Reels are not tied to the boards

A reel of 10 kilo-ohm resistors is loaded on feeder 14 with no lot number noted. When a board comes back dead from a customer, the paper trail stops at the feeder bank.

Paste and stencils are managed by feel

Solder paste has a shelf life and an open-jar life, and every stencil has a print count, yet neither is logged against the lot that used it. Squeegee wear goes unseen.

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. Enquiry and quotation

    The customer’s bill of materials is loaded and priced with component cost, stencil, line time and test. Alternates are flagged for the customer’s approval before the quote goes out.

  2. 2. Purchase and receipt

    Missing parts are ordered. Reels are received with supplier lot, date code and moisture sensitivity level, and sensitive devices go to the bake queue before they reach a shelf or a feeder.

  3. 3. Kitting

    A job kit is counted against the bill of materials, line by line, and shortages are listed by reference designator. The job is released only when the kit is complete or the customer approves it short.

  4. 4. Print, place and reflow

    The stencil, paste jar, feeder setup, placement program and reflow profile are recorded for the lot. Boards pass solder paste inspection before placement. Automated optical inspection checks them again after the oven.

  5. 5. Through-hole, test and rework

    Hand-inserted and wave-soldered parts are logged against the lot. In-circuit and functional tests record results by board serial, and failures go to the rework bench with a record of the fault.

  6. 6. Pack and deliver

    Shipping paperwork states boards built, scrapped and shipped, and names the reel lots consumed. The certificate of conformance is printed from the same lot. Nothing is retyped.

Industry reports to connect with

  • Kits short, by job and part
  • First-pass yield by board type and line
  • Reels consumed by assembly lot
  • Paste jars and stencils nearing limits

Questions before implementation.

When should pcb assembly companies 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