FSSAI Licence Renewal Cost Accounting for FMCG

A national ice-cream manufacturer’s controller pulls the FY 2025-26 FSSAI compliance pack on 30 June 2026 in preparation for the statutory audit. The company holds 14 FSSAI licences across the group: one Central Licence at the Ahmedabad Head Office (covering the corporate multi-state operations), one Central Licence at the Pundhra plant (which crossed the ₹20 crore turnover threshold in FY 2023-24), one State Licence at the Bareilly plant (still under threshold), and 11 State Licences at regional cold-chain depots and secondary manufacturing sites. Three renewals fell due in the year — Pundhra Central, Bareilly State, and one Karnataka depot State Licence — and two were filed inside the 60-day window at a combined notified fee of ₹22,000 (illustrative). The third — the Karnataka depot licence — was filed 47 days after expiry because the site head changed mid-cycle and the compliance calendar reminder went to an inactive email; the ₹4,700 accrued late fee sits in the compliance overhead account with a reason code, and the delay is disclosable under CARO 2020 Clause 3(vii). This is FSSAI licence renewal cost accounting FMCG at production scale, and the reconciliation discipline that surfaces the gap is what separates a clean statutory audit from a Clause 3(vii) qualification.

Quick reference

What the FSSAI licence renewal cycle actually looks like in India

The Food Safety and Standards Authority of India — FSSAI, established under the Food Safety and Standards Act 2006 — is the regulatory authority for every food business operator in India, from a road-side vendor to a national FMCG manufacturer. The licensing framework is tiered by turnover and geographic scope. Basic Registration covers small operators with annual turnover up to ₹12 lakh — outside the FMCG manufacturing conversation. State Licence covers manufacturing units with annual turnover up to ₹20 crore per unit; the licence is issued by the state Food Safety Department and applies to a single plant address. Central Licence covers manufacturers whose annual turnover exceeds ₹20 crore per unit, or whose Head Office coordinates operations across two or more states — the licence is issued by the central FSSAI and functions as an umbrella authorisation for the corporate legal entity’s multi-state footprint plus any single plant that has crossed the threshold.

For a mid-sized FMCG manufacturer with two operating plants in different states plus a corporate Head Office, the licence footprint at minimum reads: one Central Licence at the Head Office for the corporate legal entity, plus one State Licence per plant. If a plant crosses the ₹20 crore threshold in a given FY, that plant needs its own Central Licence at the next renewal — replacing the State Licence rather than layering on top of it. The State-to-Central upgrade is a common reconciliation trap because commercial finance tracks turnover per plant per FY, while the compliance team tracks licences by expiry date and category — the two teams routinely miss the trigger unless a monthly cross-check is enforced.

All filings sit on the FoSCoS portal — the Food Safety Compliance System launched by FSSAI to consolidate licensing, inspection, and enforcement into a single digital pipeline. The renewal filing flow is: log in to FoSCoS, select the licence to renew, upload the mandatory documents (audited financials, plant layout drawings, food safety management system certificate, and — for Central Licences — the No Objection Certificate from the state pollution control board), pay the notified fee online through the integrated payment gateway, and wait for the technical officer’s verification. Inspection is triggered where the FoSCoS risk-scoring algorithm flags a licence, and the officer’s site visit can add 15 to 30 days to the cycle. Renewal is granted electronically once the officer signs off. The end-to-end cycle for a Central Licence typically runs 30 to 60 days from application filing to renewed licence in hand.

The 60-day pre-expiry filing window is not a statutory requirement — the Regulations 2011 language specifies not later than 30 days before expiry — but it is the industry practice consensus for multi-plant filers because a 30-day cushion frequently gets consumed by the technical officer’s inspection scheduling and the state pollution NOC turnaround. Multi-national FMCG brands with a dozen or more plant licences typically build a rolling 90-day compliance calendar and file each renewal at the 60-day mark, keeping the buffer against portal downtime and site-level document delays.

Why the reconciliation matters at year-end

Three consequences flow directly from broken FSSAI licence footprint reconciliation. First, an expired licence at any manufacturing location is a Section 31 violation of the FSS Act 2006. Every SKU dispatched from an expired-licence plant carries a labelling non-compliance risk — the FSSAI licence number on the pack refers to an expired authorisation, and the Central Consumer Protection Authority has issued show-cause notices on this exact ground. Second, unpaid late fees on lapsed renewals are undisputed statutory dues that fall inside CARO 2020 Clause 3(vii). The auditor tests the plant licence register against the compliance overhead account and lists every plant with a delay, and any material delay draws a Clause 3(vii) qualification even if the absolute rupee amount is small. Third, contract-manufactured SKUs sit outside the brand’s own FSSAI fee register but inside the brand’s compliance risk. A co-packer with an expired FSSAI licence exposes the brand’s SKUs to labelling non-compliance, and the audit trail must show that the brand’s compliance team monitors co-packer licence expiry alongside its own. For brands with a broad general trade distributor pyramid, the reputational fallout from a co-packer compliance failure travels down the channel faster than any recall notice.

How the reconciliation discipline actually runs

Building the licence footprint register

The licence footprint register is the canonical source of truth for the brand’s FSSAI compliance surface. Each row carries: legal entity, plant address, FSSAI licence number, licence type (basic / state / central), licence category (manufacturer / re-labeller / re-packer / storage), issue date, expiry date, renewal filing due date (expiry minus 60 days), current FY turnover at that unit, Central Licence upgrade flag (yes if plant turnover has crossed ₹20 crore in the current FY), notified fee at the last renewal cycle, and reason code for any late filing. The register is refreshed monthly against the FoSCoS portal export — because the portal is the only authoritative source of licence status, and the portal’s downtime history means finance-team caching drifts out of date within weeks.

Parsing the FoSCoS portal export

The FoSCoS portal supports a per-licensee export of the licence master, current status, pending applications, and inspection history. The reconciliation engine downloads the export at monthly cadence, cross-checks each licence number against the internal register, and surfaces exceptions in three buckets. Bucket one — licences on the portal not in the internal register — indicates orphaned licences, typically from a plant acquisition or a Head Office relocation where the compliance team has not migrated the record. Bucket two — licences on the internal register not on the portal — indicates surrendered or expired-without-renewal licences that should not be on the compliance overhead account any longer. Bucket three — licence numbers matching but expiry dates diverging — indicates data staleness on one side or the other and is the most common source of missed renewal windows.

Reconciling to the compliance overhead GL

The compliance overhead account carries the FSSAI licence fees paid in the period, and the reconciliation cross-foots the account to the sum of two components: renewals filed in the period at the notified fee schedule, plus late fees accrued in the period at ₹100 per day per licence past expiry. Any unreconciled gap is a control failure — typically a renewal fee paid but posted to a wrong GL account (miscellaneous expenses is the standard misposting), or a late fee accrued in the compliance calendar but not journalled by finance. The cross-foot is run before month-end books close, with the TPM accrual versus payout reconciliation discipline serving as the template for period-level GL testing.

Ind AS 38 prepaid amortisation for multi-year licences

FSSAI licences can be issued for one to five years at the applicant’s option. Multi-year licences reduce the compliance operating cost per year (fewer renewal cycles, less administrative overhead) and are the industry norm for stable plants. Under Ind AS 38 and the accounting policy standard for compliance costs, a five-year licence fee paid upfront is recognised as a prepaid expense at the time of payment and amortised on a straight-line basis over the licence period. The prepaid schedule sits in a sub-ledger under the compliance overhead account, with the FY 2025-26 amortisation charge computed at (total fee ÷ 60) × months in FY. The schedule must reconcile to the balance sheet prepaid expense line at every quarter close.

Worked example — Vadilal Industries FSSAI licence footprint FY 2025-26

Vadilal Industries, one of India’s oldest ice-cream manufacturers, operates a national footprint anchored on two manufacturing plants — the Pundhra plant in Gujarat and the Bareilly plant in Uttar Pradesh — plus a corporate Head Office in Ahmedabad and cold-chain depots across the western and northern zones. The brand’s FSSAI licence footprint at 1 April 2025 consists of one Central Licence at the Head Office (multi-state HO coverage), one Central Licence at the Pundhra plant (crossed the ₹20 crore turnover threshold in FY 2022-23), one State Licence at the Bareilly plant, and multiple State Licences covering the depot network — 14 licences in total across the group.

Illustrative — public disclosures do not reveal Vadilal’s internal FSSAI licence footprint or fee schedules; the figures here are representative of the operating pattern for a two-plant national ice-cream manufacturer with a similar depot spread, not actual brand data. Cross-verify against your own FoSCoS export and compliance overhead ledger before action.

The controller pulls the FY 2025-26 FSSAI compliance pack on 30 June 2026 in preparation for the September 2026 statutory audit.

The reconciliation surfaces three actionable findings for the controller. First, the Bareilly plant crossed ₹22 crore in operating turnover in FY 2024-25, which puts it above the ₹20 crore Central Licence threshold — the plant needs a Central Licence upgrade at the next renewal cycle (expiry 15 September 2026, so filing due by 16 July 2026 under the 60-day rule). The compliance calendar has been updated and a ₹32,500 fee delta has been budgeted for FY 2026-27. Second, the Karnataka depot late fee (₹4,700 for 47 days past expiry) has been reason-coded to compliance calendar failure — site head change without email handover — and the fix is a compliance calendar redundancy rule requiring at least two escalation contacts per plant. Third, the co-packer network reconciliation surfaces two co-packer FSSAI licences expiring within the next 90 days (a milk-condensate co-packer in Anand, Gujarat and a wafer-cone co-packer in Nashik, Maharashtra) — both have been added to the compliance calendar for the sourcing team to confirm renewal filings with the co-packers before any further POs release. The FY 2025-26 FSSAI licence line rolls forward cleanly into the CARO 2020 Clause 3(vii) workpaper with a full audit trail on the ₹4,700 late fee.

Common reconciliation breakages

Five failure modes account for the majority of FSSAI licence reconciliation misses on Indian FMCG audit cycles.

• State-to-Central threshold miss — the compliance team continues to renew a State Licence at a plant that has crossed ₹20 crore turnover in a prior FY. The licence remains formally valid but is materially deficient because the plant’s operations exceed the State Licence scope. Auditors surface this by cross-referencing the plant turnover schedule to the licence category, and the fix is a monthly compliance-versus-finance cross-check.
• Head Office Central Licence over-scoping — the compliance team assumes the Head Office Central Licence covers the plant operations, and does not maintain a plant-level State Licence. The Head Office Central Licence covers only the corporate umbrella and the specific address at which it is issued; every distinct manufacturing address needs its own licence. This misread is especially common at brands that grew through acquisition and inherited multiple plants without a full compliance transition.
• Late-fee accrual missed — the compliance overhead account carries renewal fees paid but not the late fees accrued on lapsed renewals. Finance treats the late fee as a nominal miscellaneous expense at payment time, and the CARO 2020 Clause 3(vii) trail loses the days-late detail. The fix is a per-plant late-fee sub-ledger that ties the days-late count to the reason code.
• Co-packer licence expiry unmonitored — the brand’s compliance calendar covers its own plants but not the co-packer network, and a co-packer licence lapses without the brand knowing. Every SKU dispatched from an expired-licence co-packer plant carries a labelling risk on the brand’s own pack. The reconciliation fix is a co-packer master with FSSAI licence expiry dates fed into the same compliance calendar as the brand’s own plants, with a 90-day advance alert.
• Multi-year prepaid amortisation drift — a five-year Central Licence fee paid upfront is expensed in full to the compliance overhead account in the period of payment, missing the Ind AS 38 prepaid treatment. The P&L takes a one-time hit in year one and no charge in years two through five, distorting the compliance overhead ratio quarter-on-quarter. The audit-defensible treatment is straight-line amortisation across the 60-month licence period.

How a reconciliation platform handles this

A reconciliation platform designed for Indian FMCG compliance treats the FSSAI licence footprint as a first-class three-way reconciliation surface — FoSCoS portal export against the internal licence register against the compliance overhead GL. The platform surfaces the exception cases the finance team must action: renewals due inside 60 days, licences at plants that have crossed the Central threshold, late fees accrued past expiry, and co-packer licence expiry alerts. For brands running the surface alongside PLISFPI claim mechanics and GST 2.0 rate rationalisation, the compliance overhead ledger stays reconciled to the plant compliance register month after month, and the CARO 2020 workpaper drops out of the reconciliation pack rather than requiring a year-end scramble. Terra Insight’s platform is ISO 27001:2022 certified, hosted on AWS Mumbai, and aligned with the DPDP Act 2023 and RBI IT governance framework — the licence footprint register carries the sensitive plant and co-packer data those frameworks govern, and the reconciliation infrastructure treats it accordingly.

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