Gate Pass Audit: Reconciling Passes with Stock Records

Published on 10/31/2026

Banner illustration for the article: Gate Pass Audit: Reconciling Passes with Stock Records

Year-end stock verification at a casting unit throws up a puzzle: the stores ledger shows 2,400 kg of foundry returns sent for recycling, the vendor's weighbridge receipts show 2,240 kg received, and the gate pass register shows 31 passes that add to 2,380 kg. Three numbers, three sources, 160 kg of scrap that exists in none of them. The auditor's question is simple: which document is lying?

A gate pass audit answers that question monthly instead of annually, when the gap is still explainable. This guide lays out a reconciliation routine that matches passes against stock records and vendor receipts, a method for investigating the gaps you find, and the fixes that stop the same gap recurring.

On this page

Three records, one truth
The monthly reconciliation routine
Investigating the gaps you find
Returnable and open passes
Presenting findings without blame
Making gaps rare
Reader Q&A
Bottom line

Three records, one truth

Every material movement out of your plant leaves three footprints. The gate pass records what was authorised to leave. The stock ledger records what stores says left inventory. The transporter's or buyer's receipt records what the other side accepts it received. In a healthy system all three agree; when they do not, at least one process is broken, and the disagreement itself is the evidence.

The audit is therefore not a hunt for thieves. It is a monthly check that three independent records tell one story. Most gaps turn out to be timing (a pass issued on the 31st, received on the 2nd), unit confusion (pieces versus kilograms), or an unrecorded return. A few are real, and those are the ones the routine exists to catch early.

Key idea: You are not auditing people, you are auditing agreement between three records. A gap found in the month it happened is a process fix; the same gap found at year end is a write-off.

The monthly reconciliation routine

Block half a day in the first week of each month for the previous month's movements. With digital passes, the data collection takes minutes; the thinking goes into the exceptions.

Step 01

Export the month's passes and group by item

Pull every pass closed in the month, grouped by material type: raw material, finished goods, scrap, tools, samples. Total quantities per group. With digital passes this is a dashboard export; with paper it is a register tally.

Step 02

Match against the stock ledger

For each group, compare the pass total with the ledger's issue entries for the same month. Flag every group where the two differ by more than your tolerance, typically one percent or one unit, whichever is larger.

Step 03

Match against counterparty receipts

For sales and scrap, compare dispatch totals against customer acknowledgements and weighbridge slips. For job work, compare what left against what the job worker booked in. Differences here are claims to raise now, not discoveries for next quarter.

Step 04

Write down every exception and its resolution

Each flagged gap gets a one-line explanation and an owner: timing difference, unit mismatch, unrecorded return, or unresolved. The written log is the audit trail; a reconciliation that lives in one person's head is not one.

Investigating the gaps you find

Before the table, one ground rule: investigate quantity gaps and count gaps differently. A weight gap of a few kilograms on scrap is usually moisture, scale drift or rounding, and chasing it costs more than it returns. A count gap of one laptop, one fixture or one die is never rounding. Set your tolerance per item class so the routine spends its hours where the money and the risk actually sit.

Work the exceptions in order of likelihood. The table below covers the four causes that explain almost every gap, and the test that confirms each one.

Gap pattern	Likely cause	Confirming test
Pass total higher than receipts	Passes closed at the gate but material short-shipped or returned at the dock	Compare gate exit photos with loading bay records
Ledger higher than passes	Material issued without a pass, often for "urgent" internal transfers	Match ledger issue timestamps against the pass register for those hours
Receipts lower by a fixed small percentage	Weighbridge or unit difference, moisture loss, or systematic short loading	Reconcile one consignment end to end with both weighbridge tickets
One department's passes gap repeatedly	Process workaround in that department, or a genuine leak	Trace three of its passes from request to receipt, in person

Reconcile from data, not from registers

VisitorFlow keeps every gate pass searchable and exportable with photos and timestamps, so the monthly reconciliation starts from a clean export instead of a stack of books.

Explore Material Gate Pass Software

Returnable and open passes

The pass population that hides the most leakage is not the closed ones, it is the open ones: returnable gate passes for tools, dies, samples and repair items that left and never came back. Every month, list all passes past their expected return date and age them.

Worked example: returnable pass ageing, month end

Open returnable passes          = 46
Past expected return date       = 12
  of which under 30 days old    = 7   (chase with the borrower)
  of which 30 to 90 days        = 3   (escalate to department head)
  of which over 90 days         = 2   (write off or recover cost)

Value of the 2 oldest: one test fixture and one
calibration instrument = Rs 1,85,000 at book value

The over-90-days bucket is where assets quietly die. A fixture out for "trial" for four months is, in practice, a transfer. The ageing list converts that drift into a monthly decision: chase, escalate or write off, but decide.

Presenting findings without starting a blame war

The fastest way to kill a reconciliation routine is to make its first report read like an accusation. Security hears "your guards let material out," stores hears "your ledger is fiction," and both stop cooperating with the data collection the audit depends on.

Frame every finding as a record disagreement, not a person failure. "Passes and receipts disagree by 60 kg on foundry returns" invites a joint look at the weighbridge slips. "Stores lost 60 kg" invites a defensive memo. The underlying facts are identical; only the cooperation you get next month differs.

Two habits keep the tone right. First, circulate the exception list to the departments before the review meeting, so nobody first sees their gap projected on a screen. Second, close the loop publicly: when a gap is explained, record the explanation in the same log, so the register shows a routine that resolves issues rather than one that only raises them.

When a gap does turn out to be a genuine leak, the written monthly log is what lets you act on evidence: dates, quantities, photos and approvals, assembled while they were fresh, not reconstructed under pressure at year end.

Making gaps rare

The audit's real output is not the gap list, it is the fixes that shrink next month's list. Three structural changes do most of the work:

Fixes that shrink the gap list

✓ One unit of measure per item across pass, ledger and invoice, agreed with stores and accounts.
✓ No ledger issue entry without a pass number attached, enforced in the stores process.
✓ Expected return dates mandatory on every returnable pass, with an automatic overdue list.
✓ Gate exit photos for every vehicle, so quantity disputes have evidence, not recollections.

Mistakes that make the audit useless

✗ Reconciling annually, when memories are gone and documents are archived off-site.
✗ Writing off every gap as "timing difference" without checking it against next month's receipts.
✗ Auditing only high-value items; scrap and consumables leak more because nobody watches them.

Reader Q&A

Who should run the gate pass audit?

Someone outside both stores and security, typically accounts or internal audit. The point of matching three records is that no single department's paperwork gets to grade itself.

What tolerance should trigger an investigation?

One percent of monthly quantity or one unit, whichever is larger, is a workable default for counted items. For high-value items, zero: every discrepancy gets a written explanation regardless of size.

How do we handle passes cancelled after issue?

Cancelled passes appear in the audit with their cancellation reason and approver. A rising count of cancellations from one issuer is itself a finding: it usually means passes are being raised before the material is ready.

Can we reconcile if passes are still on paper?

Yes, but the tally work consumes the time that should go into exceptions. The routine is identical; only the data collection changes. Most plants find the manual tally is what makes the audit slip from monthly to yearly.

What about inward material?

The same three-way match applies: supplier challan, your goods receipt, and the ledger. Inward gaps are purchase claims you are entitled to raise, and suppliers repeat short shipments only when nobody reconciles.

How long should pass records be kept?

Long enough to cover your statutory audit and any customer quality traceability commitments, commonly several years. Digital records make this cheap; the discipline that matters is keeping them searchable, not just stored.

Bottom line

This week, pick one material group, finished goods or scrap, and reconcile last month's passes against the ledger. One group, one month: you will know within hours whether you have a process gap or a clean record.

This quarter, make the half-day reconciliation a fixed monthly event with a written exception log, and start the returnable pass ageing list. The metric to watch is the count of unexplained gaps per month: when it holds at zero for a quarter, your gate, stores and ledger are telling one story.