Cold-Chain 3PL Reconciliation for Dairy and Frozen FMCG

A national dairy and frozen FMCG shipper closes the books on 30 June 2026 with a cold-chain 3PL payable of ₹2.9 crore, accrued against a rolling three-month invoice window from its two contracted 3PL operators — one national (Snowman-scale) and one regional (Coldex-scale) — covering 46 storage chambers across 11 cities and 213 active reefer lanes. Cumulative billed value across the window stands at ₹18.4 crore; SLA-recovery credits raised against temperature-deviation events add up to ₹47 lakh; spoilage claims sit at ₹1.2 crore of which ₹68 lakh is contract-recoverable and ₹52 lakh sits as brand-borne P&L. The question on the audit committee’s agenda is: how much of the ₹2.9 crore payable is clean, how much is disputed pending SLA-breach evidence review, and how much recoverable spoilage has fallen out of the claim window because the QC-reject register was never linked to the temperature-excursion log. This is cold chain 3PL reconciliation dairy frozen FMCG at production scale, and the reconciliation discipline that resolves it is what separates a controlled year-end close from a working-capital drag and PLISFPI certification exposure.

Quick reference

What cold-chain 3PL reconciliation actually is in Indian FMCG

The dairy and frozen FMCG value chain in India runs almost entirely on outsourced cold-chain 3PL. A national brand — a Mother Dairy Foods across its Delhi milk pouch network and its Safal frozen peas SKU line, or an Amul, Vadilal, Kwality Wall’s, McCain, or Lactalis operation — designs its cold-chain footprint by product category (chilled dairy vs frozen), by distribution ring (metro vs Tier-2), and by SKU velocity (high-turn milk pouches vs slower-moving frozen prepared foods). Contracted 3PL operators — Snowman Logistics, Coldex, ColdRush, ColdEx, Gubba, Congelo, and regional temperature-controlled warehouse operators — provide chilled and frozen chamber capacity, temperature-monitored inbound and outbound handling, and reefer-vehicle line-haul between mother-plant, mother-warehouse, distribution hubs, and last-mile delivery points.

The 3PL invoice cycle is monthly or fortnightly. Each cycle carries five recurring components — per-pallet-day storage at the applicable temperature-band tariff, per-consignment fixed handling on inbound receipt and outbound despatch, reefer-vehicle line-haul per km or per trip by lane, ancillary charges (cross-dock, weekend premium, urgent dispatch, temperature-log data-pull), and GST at the applicable slab. Invoices land 15 to 45 days after the billing period closes and are booked into the shipper’s accounts payable subledger against the 3PL vendor code.

In parallel, three shipper-side registers are running. The despatch ledger — driven from the SAP or ERP outbound flow — records consignment ID, ASN, GRN, product batch, and units shipped from each mother-warehouse. The temperature-log excursion register — populated from calibrated data-loggers inside chambers and reefer vehicles — records lane, chamber, timestamp, and reading, with any excursion beyond the SLA band for longer than the grace window flagged as a deviation event. The QC-reject register — populated at the distributor cold room, the modern-trade DC receipt, or the outbound quality check — records reject reason code, unit count, batch, and root-cause classification.

The reconciliation problem is that each of these four datasets — 3PL invoice, despatch ledger, temperature-log excursion register, QC-reject register — has to be matched to the others before payment can be released, before SLA credits can be claimed, and before PLISFPI incremental-sales can be certified. In practice, brands with informal reconciliation carry a chronic 8 to 22 percent gap between the accrued 3PL payable and the underlying operational evidence — some of it disputed with the 3PL, some of it recoverable spoilage that has not been claimed within the contract window, and some of it duplicate billing that has not been surfaced.

Why the reconciliation matters at year-end

Three consequences flow directly from broken cold-chain 3PL reconciliation. First, the 3PL payable is a material line in current liabilities for dairy and frozen FMCG shippers — statutory auditors under Ind AS 37 and CARO 2020 test the balance and its ageing. If the brand cannot reconcile the payable to a per-invoice open-item register with matching despatch and chamber-day evidence, the auditor either seeks additional confirmations from the 3PL or asks for a provision against disputed lines. Second, unrecovered spoilage that was in fact SLA-breach-triggered is a genuine revenue leak — spoilage that could have been recovered from the 3PL under the contract SLA is instead sitting in the brand’s P&L as cost of goods, distorting gross margin and product-level profitability. Third, PLISFPI scheme beneficiaries in Segment 1 (RTC/RTE and Millet) and Segment 3 (Marine Products) must certify FY 2026-27 incremental sales net of unrecovered spoilage against the FY 2019-20 base year; misclassification here is one of the two most common review findings on the 53 named beneficiary list per the July 2024 DPIIT order and can lead to disallowance of scheme claims. For related PLISFPI mechanics, see the PLISFPI claim mechanics reconciliation reference article.

How the reconciliation discipline actually runs

Building the 3PL invoice register

The 3PL invoice register is the canonical source of truth for what the 3PL has billed. It is generated from the AP subledger feed cross-referenced to the contract master. Each row carries: 3PL vendor code, invoice number, invoice date, billing period, storage chamber, temperature band, consignment ID (where applicable), pallet-days billed, per-pallet-day rate, per-consignment fixed handling count, reefer lane, line-haul distance or trip count, ancillary charges, GST slab, TDS code (1023 for non-Ind/HUF, 1001 for Ind/HUF), and TDS amount. The register must also carry a contract-rate column that the reconciliation engine populates from the contract master — any invoice line where the billed rate diverges from the contract rate beyond tolerance surfaces as a billing-error candidate.

Building the despatch and chamber-occupancy register

The despatch register — sourced from the SAP or ERP outbound flow — is aggregated by consignment with ASN, GRN, product batch, units shipped, temperature-band category, source chamber, destination hub, and shipment date. The chamber-occupancy register — computed from the inbound receipt and outbound despatch timestamps at each 3PL chamber — gives the pallet-days that should have been billed for each product batch and each chamber location. Cross-matching the chamber-occupancy register to the 3PL invoice’s pallet-day column is the first substantive control — any gap represents either an under-recovery by the 3PL (shipper wins) or an over-billing (shipper disputes).

Overlaying the temperature-log excursion register

The temperature-log excursion register — populated from calibrated data-loggers per the FSSAI Schedule 4 Part V requirement — is keyed by chamber or reefer-vehicle, timestamp, and reading. The reconciliation engine applies the SLA band rule (0 to 4 C chilled, at or below minus 18 C frozen, plus the contract-specific tolerance and grace window) to identify excursion events. Each excursion event is then matched to the consignment or chamber-batch that was in the affected space at the affected time-window, producing a candidate list of temperature-deviation claims. Each candidate is reviewed by the shipper’s QC team against the QC-reject register to determine whether product quality was in fact compromised.

Matching the QC-reject register and classifying spoilage

The QC-reject register — populated at distributor cold rooms, modern-trade DC receipts, and internal quality checks — is aggregated by reject reason code, batch, unit count, and reject location. Each reject entry must carry a root-cause classification that ties back to one of: temperature-deviation SLA breach (recoverable from 3PL), mechanical or reefer-vehicle breakdown (recoverable from 3PL if the 3PL owns the vehicle), rough handling (recoverable from 3PL if attributable to handling stage), over-age batch (brand-borne — inventory age discipline failure), packaging failure (brand-borne if brand-supplied packaging), and unclassified. The reconciliation engine sums the recoverable classifications by lane and by billing period, quantifies them at the contract rate (typically landed cost times units, with salvage-value netting), and issues the SLA credit claim against the 3PL. See the breakage and damage FMCG distributor claim article for the parallel discipline at the distributor interface.

Cross-footing to the AP subledger and TDS

The closing 3PL payable at month-end must equal opening payable plus period invoice value plus period ancillary accruals minus period SLA-credit-notes issued minus period spoilage-credit-notes issued minus period TDS deposited minus period cash or bank payments. The TDS deposit under Section 393(1) Sl. 4 payment code 1023 at 2% (or 1001 at 1% for Ind/HUF payees) is reconciled to the Form 26AS credit at the 3PL PAN level; disputes are routed through the vendor payment cycle. Any unreconciled gap is a control failure that audit will pursue.

Worked example — Mother Dairy Foods Delhi milk and Safal frozen peas Q1

Mother Dairy Foods runs one of the country’s largest cold-chain footprints — chilled Delhi milk pouches through the National Capital Region and Safal frozen peas plus other frozen SKUs through a wider distribution ring. Cold-chain 3PL is split across a national operator (Snowman-scale) and a regional operator (Coldex-scale), covering 46 storage chambers across 11 cities and 213 active reefer lanes. For the quarter ending 30 June 2026, the shipper’s cold-chain reconciliation pack pulls together the following consolidated view.

Illustrative — public disclosures do not reveal internal 3PL contracts or spoilage figures; the numbers here are representative of the operating pattern, not actual brand data. Cross-verify against your own contract, AP subledger, and QC-reject register before action.

The closing ₹2.9 crore payable decomposes as follows across the two operators: ₹1.7 crore against the national 3PL (of which ₹1.4 crore is within 30-day payment cycle and ₹0.3 crore is disputed on billing-rate mismatch and pending SLA-credit netting) and ₹1.2 crore against the regional 3PL (of which ₹0.9 crore is within cycle and ₹0.3 crore is disputed on pallet-day count mismatch). The reconciliation surfaces four actionable findings.

First, 14 temperature-deviation events across the quarter — 9 in reefer-vehicle line-haul from the Kundli mother-warehouse to the Faridabad hub, 5 in the Ghaziabad chamber — were flagged by the data-loggers but 3 were not raised as SLA claims within the 24-hour notification window and lapsed. The recoverable value of the lapsed 3 events (approximately ₹6.2 lakh) sits as brand-borne spoilage that could have been recovered had the notification discipline been in place.

Second, 27 QC-reject register entries at distributor cold rooms for the Safal frozen peas SKU across the quarter were classified initially as brand-borne but on re-classification tie back to a specific reefer-vehicle mechanical breakdown event that the 3PL had acknowledged. Approximately ₹9 lakh reclassifies from brand-borne to 3PL-recoverable, and a Section 34 credit note is issued against the relevant invoice line.

Third, the billing-rate mismatch on the national 3PL — approximately ₹8 lakh across 21 invoice lines — traces to an April 2026 rate revision where the 3PL’s billing system was not synchronised with the contract amendment. The 3PL accepts the correction and issues a revision credit.

Fourth, the TDS deposit of ₹0.37 crore under code 1023 at 2% reconciles cleanly at the national 3PL’s PAN in Form 26AS, but at the regional 3PL the credit is missing for the March 2026 challan — investigation traces the gap to a TAN mis-mapping on the challan filing, which is corrected via a challan-correction request.

The FSSAI Schedule 4 Part V overlay — cold-chain infrastructure compliance

The FSSAI Food Safety and Standards (Licensing and Registration of Food Businesses) Regulations 2011 Schedule 4 Part V prescribes cold-chain infrastructure requirements that gate every dairy and frozen FMCG shipper’s 3PL selection and every SLA temperature band in the contract. The regulation covers: temperature bands for chilled and frozen storage, continuous temperature monitoring by calibrated data-loggers, reefer-vehicle validation and calibration, record retention for the temperature log for the mandated period, and root-cause investigation of every deviation event.

The direct reconciliation implication is that the temperature-log excursion register — the shipper-side data feed that drives temperature-deviation claim discovery — must be maintained in a form that meets the audit and regulatory retention window. Brands that rely on the 3PL to store the temperature log without an independent shipper-side copy lose the ability to raise claims outside the 3PL’s notification window and lose the ability to defend the cold-chain audit trail during an FSSAI inspection or a modern-trade quality audit.

Section 393(1) Sl. 4 TDS — code 1023 at 2% for the typical 3PL

Section 393(1) Sl. 4 of the Income-tax Act 2025 — the successor to legacy Section 194C — governs TDS on contractual payments to residents. Cold-chain 3PL services are contractual payments falling squarely inside this slab. The rate is 2% under payment code 1023 for non-Individual, non-HUF residents (the vast majority of contracted 3PL operators are private limited companies, LLPs, or partnership firms), and 1% under payment code 1001 for Individual or HUF residents (rarer at national scale but seen in regional last-mile reefer operators).

The deduction is on the invoice value net of GST. The threshold applies per contract on aggregate payments in the financial year. Cross-verification runs in Form 26AS at the 3PL PAN level, and TDS credit disputes are one of the recurring reconciliation surfaces alongside SLA and spoilage credits. Brands that fail to correctly classify 3PL payees — for example when a partnership firm converts to LLP mid-contract without the vendor master reflecting the change — invite Section 201 default assessments for short-deduction if the wrong code was used. The vendor master must therefore carry a legal-form field and a PAN-verified TDS code, and the reconciliation engine must re-verify the classification each financial year against the 3PL’s updated incorporation status. For the parallel discipline on distributor commission, see the distributor commission Section 194H TDS reference.

Detection discipline — the controls that catch leakage early

Five controls separate brands that close the quarter cleanly on cold-chain 3PL from brands that carry a working-capital drag and PLISFPI exposure.

First, the SLA notification discipline. Every temperature-log excursion beyond the SLA band for longer than the contracted grace window must be raised to the 3PL within the notification window (typically 24 hours). The reconciliation engine runs a daily scan of the temperature-log excursion register against the SLA notifications-sent log and flags any excursion older than the notification window that has not been raised — surfacing lapse-risk before the contract window closes and the claim is forfeited.

Second, the QC-reject root-cause classification integrity check. Every QC-reject register entry must carry a root-cause classification (SLA breach, mechanical breakdown, rough handling, over-age batch, packaging failure, unclassified). The reconciliation engine flags any reject entry left unclassified beyond a defined ageing window — surfacing recoverable spoilage that would otherwise stay in the brand’s P&L. See the return-to-vendor RTV damage credit-note article for the parallel classification discipline at the reverse-logistics interface.

Third, the billing-rate contract check. Every 3PL invoice line’s billed rate is compared to the contract master’s rate for that chamber, temperature band, or lane. Any deviation beyond tolerance is flagged for query with the 3PL before payment release.

Fourth, the pallet-day chamber-occupancy check. The pallet-days billed on each invoice are compared to the chamber-occupancy register computed from shipper-side inbound and outbound timestamps. Discrepancies beyond tolerance are queried — some resolve as legitimate 3PL corrections (missed inbound scan), others as billing errors on the 3PL’s side.

Fifth, the cross-foot to the AP subledger and Form 26AS at month-end close. The closing 3PL payable in the reconciliation pack must reconcile to the AP subledger. The TDS deposited under code 1023 or 1001 must reconcile to Form 26AS at the 3PL PAN. Any gap above tolerance is a control failure routed to the controller before books close.

Cross-cluster bridges and where to read next

For FMCG brands running scheme accruals against secondary sales that pass through the cold-chain 3PL network, the TPM accrual vs payout reconciliation discipline is the upstream companion — cold-chain spoilage affects the secondary-sales base that the scheme accrual is booked against. For brands operating in modern trade and quick-commerce with frozen and chilled SKUs, the quick-commerce FMCG settlement reconciliation article covers the ECO TCS Section 52 overlay that sits alongside the 3PL cost reconciliation. For PLISFPI Segment 1 and 3 beneficiaries whose incremental-sales certification depends on net-of-spoilage figures, the PLISFPI incremental sales base year reference is essential. The FMCG reconciliation software India money page anchors the broader category.

How a reconciliation platform handles this

A dedicated reconciliation platform ingests the 3PL invoice register, the SAP or ERP despatch ledger, the chamber-occupancy register, the temperature-log excursion register, and the QC-reject register through configured feeds, applies the contract-master rate rules, the FSSAI temperature-band rules, and the Section 393(1) Sl. 4 TDS classification, and produces a per-billing-period cold-chain 3PL reconciliation pack with clean lines, disputed lines, SLA-credit accruals, spoilage split by recoverable versus brand-borne, and TDS reconciliation to Form 26AS. Customer benefit is faster close, cleaner audit trail, higher recovery of contract-eligible spoilage claims, and defensible PLISFPI net-eligible-sales certification — with the reconciliation engine surfacing operational exceptions the AP team can act on rather than absorb into next-cycle payables.

The five FAQs below address the operational questions Indian dairy and frozen FMCG controllers ask most often when implementing structured cold-chain 3PL reconciliation.

Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 1 July 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024