Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Auto components ship in returnable containers — KLT/GLT bins, trolleys, pallets, dunnage — moved under a Rule 55 delivery challan with no GST because they are not a supply, expected to cycle back empty. Across multiple OEM plants on milk-run logistics the bin-out and bin-in flows scramble, bins go missing, security deposits drift out of step with the physical float, and an unreturned bin beyond its window can become a GST deemed supply — none of which a goods-invoice reconciliation captures.
Maintain a per-bin-type circulation ledger: every outward Rule 55 challan (bin-out, with declared value and e-way bill where applicable) is tied to an inward return challan/receipt (bin-in); cumulative out minus in per bin type per counterparty is the float in custody; reconcile the float against the security-deposit ledger at the agreed per-bin value; age unreturned bins against the contractual return window and quantify the GST deemed-supply exposure (tax invoice on lost/retained bins); reconcile milk-run manifests by netting flows rather than pairing dispatch-to-return.
Bin master keyed by bin type (KLT/GLT/trolley/pallet/dunnage/special), ownership (OEM/supplier/pooled), declared per-bin value and return window; outward and inward Rule 55 challan register with e-way bill linkage; counterparty/plant dimension for multi-plant circulation; security-deposit ledger by counterparty; milk-run manifest feed; GST mapping for the deemed-supply tax invoice on non-returned bins.
A per-bin-type, per-counterparty circulation reconciliation showing cumulative bin-out vs bin-in and the float in custody, a deposit-vs-float comparison at agreed per-bin value, an ageing of unreturned bins against the return window with quantified GST deemed-supply exposure, milk-run flow netting against manifests, and an exception queue for missing bins, deposit drift, mis-routed containers across plants, and bins approaching the GST trigger window.
A fastener supplier outside Chennai runs an annual packaging audit and discovers that of 4,000 KLT bins it owns and circulates across three OEM plants, the physical count finds only 3,620 in custody and in transit. The other 380 are unaccounted — parked at the wrong plant, lost on a milk-run, or quietly absorbed into another supplier’s flow. At the declared per-bin value the float is meaningful money; worse, every bin that left on a delivery challan and never came back is sitting beyond its return window, which means it has potentially crossed from a no-GST returnable movement into a deemed supply. This is the quiet rail of returnable packaging KLT bin reconciliation auto India: it carries no sales value, books no revenue, and is precisely the kind of off-invoice flow that goes unreconciled until an audit or a GST notice forces the count.
Quick reference
| Concept | Standard / mechanism | GST treatment | Reconciliation trigger |
|---|---|---|---|
| Returnable container | KLT/GLT bin, trolley, pallet, dunnage | Not a supply at dispatch | Bin-out movement |
| Movement document | Rule 55 delivery challan (+ e-way bill) | No GST; declared value carried | Outward and inward challan pairing |
| Bin circulation | Bin-out vs bin-in per bin type | n/a | Cumulative float in custody |
| Security deposit | Deposit against bins in custody | n/a (deposit, not supply) | Deposit-vs-float drift |
| Non-return beyond window | Deemed supply on retained bins | Supplier raises tax invoice (GST due) | Bin aged past return window |
| Empties return | Milk-run manifest | n/a | Flow netting vs manifests |
Why returnable packaging is its own reconciliation rail
Most reconciliation in an auto supplier follows value — quantities, prices, invoices, payments. Returnable packaging follows assets that have no sale value attached to the movement. Components ship in standardised returnable containers — KLT (small load carriers) and larger GLT bins, steel trolleys, pallets, dunnage (the inserts and separators that protect parts), and special-purpose containers built for a specific part geometry — because at JIT volumes disposable packaging is wasteful, returnables present parts at the line in a fixed standard-pack quantity, and they stack and cycle cleanly.
These containers are owned by the OEM, by the supplier, or run in a pooled model, and they are meant to cycle back empty after the parts are consumed. Because nothing is being sold when a full bin leaves, the movement is not a supply — so it cannot ride on a tax invoice, and it does not appear in the sales reconciliation at all. It needs its own ledger, its own document, and its own audit. Reconciliation here is asset-tracking, not value-matching, and it is where suppliers routinely carry silent losses.
The Rule 55 delivery challan
Goods sent for a reason other than supply — which covers returnable containers, goods sent for job work under Section 143, and goods on approval — move on a delivery challan under Rule 55 of the CGST Rules, not a tax invoice. There is no supply, so there is no GST at dispatch. The Rule 55 challan carries the description, quantity and declared value of the containers, and an e-way bill is generated against the challan where the value crosses the threshold (returnable packaging movement is a recognised e-way bill sub-type).
The reconciliation discipline is to tie every outward Rule 55 challan (bin-out) to an inward return challan or receipt (bin-in). The outward challan establishes what left and its declared value; the inward document establishes what came back. The difference, accumulated per bin type, is the float in circulation — the bins currently in the counterparty’s custody.
The bin circulation ledger
The core artefact is a per-bin-type circulation ledger:
- Bin-out — every outward Rule 55 challan, by bin type (KLT, GLT, trolley, pallet, dunnage, special), counterparty and plant, with declared value.
- Bin-in — every inward return challan/receipt, same dimensions.
- Float in custody = cumulative bin-out − cumulative bin-in, per bin type, per counterparty.
Like the cumulative-quantity discipline in OEM delivery schedule and EDI/ASN reconciliation, bin balances are a running cumulative — a single unrecorded return permanently overstates the float and a single unrecorded dispatch understates it. The ledger has to reconcile cumulatively, not movement-by-movement, and the counterparty/plant dimension is essential because the same supplier circulates bins across several OEM plants and a bin can drift from one plant’s account to another.
Security deposit reconciliation
Where the supplier owns the bins, or in a pooled model, a security deposit is commonly held against the float of containers in the counterparty’s custody, at an agreed per-bin value. The deposit sits on the balance sheet — a liability or receivable depending on direction — and is meant to be trued up against the physical bin balance.
Reconciliation ties the deposit ledger to the float: deposit held should equal bins in circulation × agreed per-bin value. When the float grows (bins not coming back) without a matching deposit adjustment or recovery claim, the supplier is silently financing a growing shortfall. The reconciliation surfaces this drift so it is settled — deposit drawdown or recovery claim — rather than discovered at year-end.
The GST deemed-supply trigger
This is the rail’s sharpest edge. Returnable packaging escapes GST only because it is expected to return. If containers are not returned within the agreed window, the position can shift to a deemed supply: the goods that left on a delivery challan have effectively been retained by the recipient, and GST may become payable on the declared value of the unreturned containers — typically discharged by the supplier raising a tax invoice for the lost/retained bins. The exact trigger and timing turn on the contract and facts, and the prudent reconciliation position is firm: a bin aged past its return window is not merely a logistics loss, it is a potential GST event that must be quantified and either recovered from the recipient or settled. For the governing provisions see the GST Portal (Government of India).
Milk-run empties and why pairing breaks
Empties usually come back on a milk-run — one vehicle on a fixed loop dropping full bins and collecting empties across several suppliers or several OEM plants in one trip. It is efficient and it breaks the one-dispatch-one-return mapping: empties collected may not correspond bin-for-bin to the full bins dropped, bins get exchanged across plants, and the return challan can aggregate empties from multiple parts and dates. Reconciliation therefore cannot assume clean pairing — it must net bin-out against bin-in per bin type across the whole circulation, reconcile to the milk-run manifests, and locate where bins are physically parked when cumulative out and in diverge.
Worked example — 4,000 KLT bins across 3 OEM plants
A supplier owning 4,000 KLT bins, circulating across 3 OEM plants, agreed per-bin value of ₹450, contractual return window of 30 days, security deposit held by each plant against bins in custody:
- Monthly bin-out across the 3 plants: ~6,800 bin movements (full bins dispatched).
- Monthly bin-in (empties returned via milk-run): ~6,600 — a net 200-bin monthly outflow that should be transient but is accreting.
- Physical audit float: 3,620 bins located in custody/transit against 4,000 owned → 380 bins missing.
- Deemed-supply exposure on bins aged past the 30-day window: 380 × ₹450 = ₹1,71,000 declared value potentially attracting GST if treated as a deemed supply, recoverable from the plants holding them.
- Deposit reconciliation: deposit held should equal bins-in-custody × ₹450; the 380-bin gap should be matched by a deposit drawdown or a recovery claim against the specific plant, not absorbed silently.
- Milk-run netting: tracing the 380 by plant shows ~240 mis-routed to Plant B’s account on a shared milk-run loop and ~140 genuinely lost — the first is a reclassification, the second a recovery/GST event.
A per-bin-type, per-plant circulation reconciliation would have surfaced the 200-bin monthly drift within the first month instead of letting it compound to 380 by the annual audit — and would have flagged each unreturned bin against its 30-day window so the GST deemed-supply exposure was quantified as it arose, not discovered later.
Where this sits in the auto-component reconciliation stack
Returnable-packaging reconciliation runs alongside the quantity rail of OEM delivery schedule and EDI/ASN reconciliation — full bins go out with the parts, empties come back separately — and any bin-loss recovery lands in the OEM-Tier 1 settlement and debit note reconciliation ledger. The full picture is in the automotive component manufacturing reconciliation sub-pillar and the broader manufacturing reconciliation pillar. For the Rule 55 delivery-challan provisions and the treatment of goods sent for reasons other than supply, see the GST Portal (Government of India).
What automated reconciliation changes
Tracking returnable containers across multiple OEM plants on milk-run logistics by hand is where suppliers lose bins silently, let security deposits drift out of step with the physical float, and miss the GST deemed-supply trigger until an audit. Purpose-built reconciliation software India treats the bin-out/bin-in flow as a cumulative per-bin-type, per-counterparty ledger, ties Rule 55 challans to returns and to the deposit ledger, ages unreturned bins against the return window, and nets milk-run flows against manifests. TransactIG ships 24+ industry presets, including a configuration for returnable-packaging and bin-circulation reconciliation. Customer outcomes include match-rate improvement from 51% to 88%. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound goods match that runs in parallel to the packaging flow, see three-way matching software India.