Gate Entry and Quality Inspection — Structured Goods Receipt at the Gate
Published: April 14, 2026
A vendor delivers 100 units. The stores team counts them, signs the challan, and sends it to accounts. Three weeks later, when finance processes the invoice, someone notices the GRN says 100 but the invoice says 95. Or worse — the GRN says 100, the invoice says 100, but only 90 usable units are actually in the warehouse because 10 arrived damaged and nobody recorded it. The damage is discovered months later during a stock check, and by then, nobody can prove whether the goods arrived damaged or were damaged in storage.
This gap — between what the vendor delivered and what the organisation actually received in usable condition — is where gate entry inspection fits. It is the first independent check: before goods enter the warehouse, an inspection at the gate documents exactly what arrived, in what condition, and how much is acceptable.
1. The Gap Between Delivery and Receipt
In organisations without gate entry inspection, the goods receipt note (GRN) is the first and only record of what was received. The person creating the GRN is typically in procurement or stores — someone who may have been involved in creating the purchase order. This creates a segregation-of-duties problem: the person who ordered the goods is also recording what arrived.
Gate entry adds an independent checkpoint. Security or quality inspection personnel — who have no involvement in the purchase decision — record what the vendor actually delivered, in what quantities, and in what condition. This record then flows into the GRN, providing a documented starting point that the stores team cannot unilaterally change.
2. The 3-Bucket Equation
Every gate entry line splits the delivered quantity into three buckets:
| Bucket | Meaning | What Happens Next |
|---|---|---|
| Accepted | Goods pass inspection — correct item, correct condition | Flows to GRN as received quantity |
| Rejected | Wrong item, wrong specification, or vendor defect | Returned to vendor — triggers vendor debit note |
| Damaged | Correct item but arrived in damaged condition | Received but flagged — triggers damage debit note |
The equation is enforced: Accepted + Rejected + Damaged = Total Received. The system will not save a gate entry line where the numbers do not balance. This forces complete accounting — every item is categorised, nothing slips through as vaguely "received."
For each line, the inspection team also records:
- Challan number and date — the vendor's delivery document reference
- Vehicle number — links the delivery to a specific shipment
- Supplier name — confirmed against the PO
- Rejection reason and remarks — free text explaining why items were rejected or damaged
- Informed user — who from the PO chain was notified about rejections or damage
3. Who Does Gate Entry?
Gate entry is restricted to the Security role. This is a deliberate design choice:
- Segregation of duties: The security guard or inspection officer has no relationship to the purchase order. They are not incentivised to accept substandard goods or inflate quantities.
- Physical presence: The security team is at the gate when the delivery arrives. They see the actual goods, the actual condition, and the actual quantity.
- Independence: Their assessment is not influenced by vendor relationships, delivery deadlines, or production pressure.
The security team sees a list of approved purchase orders pending delivery — so they know what to expect. When a vendor arrives, the guard matches the delivery against a specific PO, inspects the goods, and records the 3-bucket split.
The gate-entry surface is now split into two role capabilities: gate_entry (view-only — anyone in the receipt chain can see what's been inspected) and gate_entry_operate (write — only security personnel and admins record inspections and record pickups). The split lets you keep visibility wide without widening the operating surface.
4. From Gate to GRN
When gate entry is enabled, GRN creation does not start from scratch. The GRN form is pre-populated with gate entry data:
- Quantities flow forward: The accepted, rejected, and damaged quantities from gate entry become the starting values in the GRN.
- Invoice matching begins: The stores or procurement team adds the invoice number, invoice quantities, and invoice rates. The system compares these against the PO and the gate entry data — this is where three-way matching begins.
- Mismatches surface immediately: If the invoice says 100 but the gate accepted 90, the mismatch is flagged before the GRN is submitted for approval.
This creates a three-point chain: PO (what was ordered) → Gate Entry (what was delivered) → GRN (what was invoiced). Discrepancies at any point are documented and traceable.
5. Handling Rejections and Damage
Rejected and damaged quantities recorded at the gate do not disappear — they trigger downstream actions:
5.1 Bulk Rejection
When the entire delivery is rejected (wrong goods, wrong vendor, no PO match), the security team can reject all lines in a single action. Each line gets a rejection reason and an informed user. The rejection is recorded against the PO — the procurement team can see that a delivery was attempted and rejected.
5.2 Damage Documentation
Damaged goods are received (they physically enter the premises) but flagged. The damage count flows through to the GRN and from there to the vendor debit note workflow. A debit note of type DAMAGE is created, referencing the specific gate entry line, PO line, and damage quantity. The vendor receives a formal debit note — not an email complaint.
5.3 Under-Receipt
If the vendor delivers 80 units against a PO for 100, the gate entry records 80 (split into accepted/rejected/damaged). The remaining 20 are not yet delivered. For PIECEMEAL delivery mode POs, the vendor can deliver the remaining 20 in a subsequent delivery — a new gate entry is created for the second delivery. The cumulative received quantity is tracked against the ordered quantity.
5.4 Who Collected the Rejected Items?
For physical disposition — who collected the rejected items, when, and against what challan — ProcureTrail tracks this in an append-only pickup log. POST /gate-entry/lines/{id}/record-pickup captures the collector (vendor, transporter, or other), phone, challan, vehicle and remarks; POST /gate-entry/lines/{id}/scrap records a scrap event with a 10–2,000 character reason and a PO-approver-or-admin authorisation. Corrections flow through a soft-delete void rather than an edit-in-place, so the audit trail stays forensic.
6. Correction Workflow
Gate entry records are not directly editable — if security accidentally records 50 accepted when it should have been 55, they cannot simply change the number. This immutability is an important control: inspection records that can be silently edited are not inspection records.
Instead, a correction workflow exists:
- Request reset: The security team or admin submits a reset request explaining the error.
- Approval: Someone from the PO approval chain reviews and approves the reset.
- Re-inspection: Once approved, the gate entry line status returns to editable, and the corrected quantities can be recorded.
The reset request, approval, and original values are all preserved in the audit trail. An auditor can see: "Line was originally recorded as 50 accepted, reset was requested by [user] on [date] with reason [reason], approved by [approver], and re-recorded as 55 accepted."
The correction workflow is the difference between "gate entry is security theatre" and "gate entry is an actual control." If the numbers can be changed without documentation and approval, the inspection adds no governance value.
7. When to Enable Gate Entry
Gate entry is a feature toggle — disabled by default. Not every organisation needs it:
| Enable When | Skip When |
|---|---|
| Physical goods are received at a central gate or dock | Services only (use service acceptance instead) |
| Multiple vendors deliver daily and tracking is difficult | Few vendors, infrequent deliveries |
| Quality inspection at receipt is required (manufacturing, pharma, lab equipment) | Goods are inspected at the vendor's site before shipping |
| Audit requires independent verification of receipt quantities | Small team where segregation of duties is impractical |
| Vendor damage/rejection claims need documented evidence | Vendor relationships are trust-based and disputes are rare |
Organisations can start without gate entry and enable it later as their procurement volume grows or their audit requirements tighten. Enabling it does not affect historical data — it only applies to new GRNs created after the toggle is turned on.
8. Frequently Asked Questions
What is the 3-bucket equation in gate entry inspection?
The 3-bucket equation splits every delivery line into three quantities: accepted (goods that pass inspection), rejected (goods sent back to the vendor), and damaged (goods received in a damaged condition). The sum must equal the total received quantity. This forces the inspection team to account for every item — nothing is recorded as simply "received" without a quality assessment.
Why should gate entry be restricted to security personnel only?
Gate entry is an inspection checkpoint. If the same person who created the purchase order also records the gate entry, there is no segregation of duties. An independent inspection by security personnel ensures that the person recording the receipt has no interest in inflating accepted quantities or hiding damage.
How does gate entry connect to the GRN?
When gate entry is enabled, the GRN creation form is pre-populated with gate entry data. The quantities accepted, rejected, and damaged at the gate flow into the GRN as starting values. The GRN creator then adds invoice details, and the system compares these against the PO and gate entry data. Mismatches surface immediately.
What happens when a gate entry mistake needs to be corrected?
Gate entry records are not directly editable. A correction workflow exists: request a reset (with reason), get approval from someone in the PO approval chain, then re-record the corrected quantities. The original values, reset request, and approval are all preserved in the audit trail.
Is gate entry mandatory for all organisations?
No. Gate entry is a feature toggle, disabled by default. Organisations without a security checkpoint or without the need for gate-level inspection can skip it. When disabled, GRNs are created directly from approved POs. When enabled, GRN creation requires gate entry data to exist first.