Skip to main content
GullySystem
Manufacturing

Goods Receipt (GRN) for API manufacturers

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.

Starting materials arrive with the supplier’s certificate of analysis and wait in quarantine until sampled. The receipt records drum count and container condition. Quarantined stock cannot be issued.

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.
API manufacturers

How the business operates.

An API plant makes a molecule in stages. Starting materials become intermediates, intermediates become crude product, and crude product is purified, dried, milled and packed. At every stage a sample is tested, and a stage that fails its specification can send material back for rework, reprocessing or rejection, each of which must be written down. Every step leaves a record.

Route and stage master

Hold each product’s synthesis route as stages with inputs, solvents, equipment and in-process test points.

Batch manufacturing records

Record charges, temperatures, hold times, yields and sample draws for each stage, with a reviewer’s sign-off.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Starting materials and suppliers. Receive materials with supplier lot, quarantine status and sampling records, and keep approved supplier lists.
  • Route and stage master. Define each synthesis route as stages with inputs, solvents, equipment and test points, with revisions under change control.
  • Batch manufacturing records. Record charges, parameters, hold times, yields and sample draws for each stage and each reviewer’s sign-off.
  • Intermediate lot genealogy. Link final lots to their intermediates and starting materials, including reprocessed and recovered material.

Operational bottlenecks to check

Intermediates lose their lineage

A final lot is built from three intermediate lots, and a reprocessed lot is blended in. The chain from final lot back to starting material is rebuilt from folders each time a customer asks.

Deviations sit in a separate file

A deviation raised during drying is tracked in a register that is not tied to the batch. Release goes ahead without anyone checking if it is closed. The gap is found later.

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. Starting material receipt

    Materials arrive against a purchase order, are sampled and are held until released by quality staff.

  2. 2. Stage charge and reaction

    Charges, temperatures, pressures and hold times are logged against the stage and the reactor used.

  3. 3. Isolation and drying

    Filtration, centrifuging and drying are recorded with yields and samples drawn.

  4. 4. Test and review

    Results are posted against the specification. The batch record is reviewed with its deviations before the next stage or release.

  5. 5. Mill, blend and pack

    The final powder is milled, blended and packed in sealed drums, each with a recorded seal number.

  6. 6. Release and dispatch

    The lot is released, a certificate is produced and the load is shipped with the retest date visible.

Industry reports to connect with

  • Batches by stage and product
  • Yield by stage across campaigns
  • Open deviations by age and stage
  • Intermediate lots and the final lots they fed

Questions before implementation.

When should api manufacturers 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