PLISFPI Incremental Sales over Base Year FY 2019-20 — Reconciliation

A leading Indian biscuits-and-cookies manufacturer — one of the 53 PLISFPI beneficiaries published by the Ministry of Food Processing Industries — files its FY 2024-25 incremental-sales claim with the Project Management Agency in July 2025. The eligible-segment sales (biscuits and cookies only, excluding dairy, bread, rusk, and cake products) total approximately ₹6,840 crore for the claim year. The FY 2019-20 base-year figure for the same eligible-segment scope is approximately ₹4,360 crore, locked under the scheme at first-claim filing in FY 2021-22 and unchanged ever since. The incremental over base is ₹2,480 crore, the category threshold is crossed, and the incentive at the scheme percentage works out — subject to the published category cap — to a claim of approximately ₹62 crore for the year. The PMA reviewer’s first question lands the next week: the company’s GSTR-3B aggregate turnover for FY 2024-25 (consolidated across the GSTIN registrations) shows ₹19,840 crore. The MCA XBRL-filed audited revenue is ₹19,920 crore. The eligible-segment claim is ₹6,840 crore. Where is the ₹13,000-crore gap between the claim and the GST turnover, and which line items in the gap are non-eligible product categories versus inter-state branch transfers versus non-GST revenue lines? The answer to that question — line by line, by SKU, by HSN, by GSTIN — is what gates the disbursement. This is PLISFPI incremental sales base year FY 2019-20 reconciliation at the operating altitude every beneficiary needs to clear before the cash moves.

Quick reference

The reconciliation in one paragraph

PLISFPI pays incentive on the year-on-year incremental sales an eligible beneficiary delivers over its own FY 2019-20 base year of the same in-scope product categories — biscuits and cookies for Britannia, dairy for GCMMF (Amul) and Parag, processed fruits for Dabur, ready-to-cook/ready-to-eat staples for Tata Consumer and Nestle, snacks for Bikaji and Haldiram, beverages for Varun Beverages. Each eligible year is tested independently against a category-wise minimum sales threshold; falling below threshold in one year disqualifies that year’s claim only, not the subsequent years. The PMA verification gate cross-checks the eligible-segment sales the beneficiary reports against the GSTR-3B aggregate turnover the entity has self-declared to GST, the audited revenue MCA receives in XBRL format, and the internal sales ledger — three independent data points that almost never reconcile on the first pass. The reconciliation discipline that ties them together is the single largest finance-and-compliance pain in PLISFPI claim management.

What PLISFPI actually looks like in India

PLISFPI was notified by the Ministry of Food Processing Industries in 2021 with a ₹10,900 crore outlay over six years FY 2021-22 to FY 2026-27. The scheme operates across four sub-categories: ready-to-cook/ready-to-eat (RTC/RTE) staples, processed fruits and vegetables, marine products, and mozzarella cheese. A separate window covers innovative/organic products. MoFPI selected 53 beneficiaries — the published list includes Hindustan Unilever (HUL), ITC, Britannia (#9 in the list), Dabur, Nestle India, Tata Consumer, Varun Beverages, Bikaji Foods International, Bikanervala Foods, Haldiram Snacks, Haldiram Foods International, Balaji Wafers, Gujarat Cooperative Milk Marketing Federation (GCMMF / Amul), Anmol Industries, Parag Milk Foods, and Keventer Agro, among others. Each beneficiary gave a minimum committed investment at scheme entry and accepted an annual reporting and reconciliation obligation in return for the incentive payout.

The annual claim cycle runs roughly: financial-year close on 31 March; statutory audit and MCA XBRL filing through July to October; eligible-segment sales register frozen for the claim year; reconciliation walks to GSTR-3B and MCA XBRL completed and signed by the company secretary and statutory auditor; claim pack submitted to the Project Management Agency typically by Q3 of the following financial year; PMA verification cycle through queries and document requests; disbursement when the verification clears. A beneficiary that cannot answer the PMA’s reconciliation queries on the first cycle waits another quarter or two for the cash.

The base year FY 2019-20 sits at the heart of every annual computation. The base-year figure is fixed at first-claim filing — typically computed retrospectively in FY 2021-22 from the brand’s distributor management system, sales ledger, and GST returns for the period 1 April 2019 to 31 March 2020 — and never changes for the remainder of the scheme tenure. Beneficiaries that did not build a robust base-year register at first-claim filing often discover, years into the scheme, that their FY 2019-20 SKU-level data is missing, partial, or inconsistent with the audited revenue for that year — and the rebuild becomes a year-long forensic project under PMA pressure. The closely-related discipline of growth-over-base scheme reconciliation inside trade-spend operates on the same intellectual frame at a smaller scale.

The GST overlay — Sections 35(1), 44 (GSTR-9) and the GST 2.0 transition

PLISFPI sits on top of the GST book of account. Section 35(1) of the CGST Act requires every registered person to keep a true and correct account of production, inward and outward supplies, stock, ITC, and tax payable at every place of business. The eligible-segment sales ledger required for PLISFPI reconciliation rides on this statutory base. Section 44 read with Rule 80 requires an annual return in GSTR-9 and, above the ₹5-crore aggregate turnover threshold, a self-certified reconciliation statement in GSTR-9C. The GSTR-9 aggregate turnover figure is one of the three corroborating data points the PMA tests against the PLISFPI claim. The GSTR-9C Part II walk from audited financials to GSTR-9 turnover is the second.

CBIC Notifications 09 to 16/2025-CTR effective 22 September 2025 moved several food-processing categories — biscuits under HSN 1905, chocolates, and a set of processed foods — to the rationalised 5% slab. Aerated and sweetened beverages moved to the 40% NSAB slab. For PLISFPI incremental-sales claims for FY 2025-26 and FY 2026-27, the rate change does not affect the eligibility test (sales are measured net of GST in the scheme document), but it does affect the GSTR-3B-side reconciliation walk: the GST-inclusive vs GST-exclusive carve-out has to be done at the new rate for transactions on or after 22 September 2025. Brands that maintain a pre-22-September and post-22-September split in the eligible-segment register handle the transition cleanly; brands using a blended-rate approach will see a reconciliation gap with GSTR-3B that the PMA will query. The base-year FY 2019-20 figures are unaffected because they were computed and locked years before GST 2.0.

A worked example: Britannia biscuits-and-cookies, FY 2019-20 base to FY 2025-26

A leading Indian biscuits-and-cookies manufacturer (the persona here is Britannia, #9 on the MoFPI 53-list, illustrative figures only) walks through the six-year scheme arc on the eligible-segment carve-out — biscuits and cookies products under HSN 1905 — excluding dairy, bread, rusk, cake, and ingredient sales which fall outside the PLISFPI eligible-product list.

Illustrative — public disclosures do not reveal scheme-specific eligible-segment figures and the table below is representative of the operating pattern, not actual brand data. Cross-verify against your own DMS export, GSTR-3B archive, and MCA XBRL filings before action.

The FY 2019-20 base-year register is built once. The eligible-segment sales register is rebuilt for every claim year. The PMA tests both against GSTR-3B and MCA XBRL revenue independently.

Two operating notes ride alongside the table. First, the year-on-year incremental growth is not monotonically rising — FY 2025-26 shows a dip from FY 2024-25 because of a soft monsoon affecting rural distribution and an unfavourable raw-material price cycle. The dip does not affect eligibility because the eligible-segment sales still clear the category threshold for FY 2025-26. If the dip had pushed eligible-segment sales below the threshold, FY 2025-26’s claim alone would have been disqualified — but FY 2026-27 would have remained available subject to its own threshold test. Second, the FY 2026-27 figure is a forecast at the time of writing because the year is in progress; the final-year claim filing typically lands in Q3 of FY 2027-28 and is the largest single claim of the scheme tenure because of the cumulative incremental build.

The PMA verification cycle for the FY 2024-25 claim of ₹2,480 crore incremental — the largest year on the actual filed record — required three reconciliation walks to clear. The first walk tied eligible-segment biscuits-and-cookies sales of ₹6,840 crore to the GSTR-3B aggregate turnover of ₹19,840 crore via ineligible product mix (dairy ₹4,180 crore + bread ₹2,940 crore + rusk ₹1,360 crore + cake ₹1,620 crore + ingredient sales ₹890 crore + inter-state branch transfers ₹1,540 crore + miscellaneous ₹470 crore) totalling ₹13,000 crore of carve-outs to reconcile the GST turnover side. The second walk tied the same ₹6,840 crore to the MCA XBRL audited revenue of ₹19,920 crore through a parallel mix, with the ₹80 crore delta between GSTR-3B and MCA XBRL explained by inter-state branch transfers that show in GST but net out in audited financials. The third walk tied the eligible-segment ledger to the internal GL sales account at the SKU level — and surfaced a ₹14 crore overstatement caused by an accounting-policy timing difference on sales returns that the audit team had not yet cleared. The corrective journal brought the eligible-segment figure to ₹6,826 crore, the incremental adjusted to ₹2,466 crore, and the revised claim cleared the PMA gate on the second cycle.

How does the minimum sales threshold work year by year?

PLISFPI tests each eligible year independently against a category-wise minimum sales threshold published in the scheme guidelines. The threshold is denominated in absolute rupee terms and varies by sub-category (RTC/RTE has a different threshold from marine, mozzarella, and processed F&V). For a Tier-1 beneficiary like Britannia in the RTC/RTE sub-category, the threshold is comfortably below operating sales in every year of the scheme tenure — the beneficiary’s eligible-segment sales materially exceed the threshold by design. For a smaller beneficiary in a regional sub-category, the threshold can be the binding constraint in a soft year. The discipline a finance team must build is: every claim year has its own threshold test, the test is run on the eligible-segment sales figure (not brand-wide GST turnover), and if the test fails for a year, that year alone is non-eligible and no incentive is claimed for it. The scheme continues into the next year unaffected.

The asymmetry matters in a downturn year. A beneficiary that just misses the threshold for FY 2025-26 cannot claim that year, but the beneficiary’s FY 2026-27 claim — provided the threshold is cleared again — is computed against the FY 2019-20 base, not against the missed FY 2025-26 figure. The scheme does not penalise a missed year by resetting the base.

The eligible-segment carve-out — the single hardest reconciliation gap

The eligible-segment carve-out from brand-wide sales is the reconciliation breakage that holds up more PLISFPI claims at the PMA verification gate than any other single issue. The scheme is paid on sales of specific notified product categories — for Britannia, biscuits and cookies under HSN 1905; for Nestle India, RTC/RTE noodles and culinary products; for Varun Beverages, in-scope beverage SKUs; for GCMMF (Amul), in-scope dairy products; for Bikaji and Haldiram, snacks. The GSTR-3B aggregate turnover and the MCA XBRL revenue both cover the full corporate entity, while the PLISFPI claim must isolate only the in-scope product categories.

The standard discipline that holds up to PMA scrutiny has four components. First, an SKU-eligibility master built at scheme entry tags every SKU on the brand’s portfolio to the PLISFPI category list — eligible biscuit, eligible cookie, ineligible cake, ineligible rusk, ineligible bread, ineligible dairy, ineligible miscellaneous. Second, a monthly extract from the distributor management system (or SAP CO-PA, or the brand’s primary sales system) pulls sales by SKU, by HSN, by GSTIN, by distributor, with the eligibility flag applied at row level. Third, a reconciliation walk lines up the eligible-segment monthly total to the brand-wide GSTR-3B and MCA XBRL revenue, with every line in the carve-out (each ineligible product category) substantiated by the same SKU-eligibility master. Fourth, the company secretary and statutory auditor sign off on the eligible-segment ledger before the claim pack is submitted to the PMA. Brands that did not build the SKU master at scheme entry typically rebuild it retrospectively under PMA pressure — and often discover that the FY 2019-20 base-year SKU-level data is incomplete, forcing a forensic reconstruction from invoice archives and old DMS exports.

For brands also running TPM accrual versus payout reconciliation and modern trade settlement variance reconciliation, the SKU-eligibility master is the spine that connects PLISFPI claim management to ordinary trade-spend operations — the same SKU master that classifies a scheme as PLISFPI-eligible also drives the scheme matrix, the credit-note cycle, and the GSTR-1 amendment cycle.

Common reconciliation breakages

• The FY 2019-20 base-year register was never built at scheme entry and the SKU-level eligible-segment carve-out for the base year has to be reconstructed years later from invoice archives, frequently with gaps.
• The eligible-segment sales total does not reconcile to GSTR-3B aggregate turnover because the carve-out walk omits one or more ineligible product categories (e.g., bread and rusk left in by mistake) or because branch-transfer flows are not netted out.
• The eligible-segment sales total does not reconcile to MCA XBRL audited revenue because the XBRL tag is at the consolidated entity level while the eligible-segment ledger sits at the legal-entity level, and the consolidation eliminations are not documented.
• A claim year’s eligible-segment sales fall below the category minimum threshold but the claim is still filed — the PMA rejects the year as non-eligible and the file is re-cycled.
• The pre-22-September 2025 / post-22-September 2025 GST 2.0 transition split is not maintained, and the GSTR-3B reconciliation walk shows a delta that cannot be explained without rebuilding the post-transition months at the new HSN rate.

How a reconciliation platform handles this

A purpose-built reconciliation engine ingests the brand’s monthly SKU-level eligible-segment sales register from the distributor management system in its native format, ties it line by line against the GSTR-3B aggregate turnover and the MCA XBRL revenue tag through documented carve-out walks, classifies every variance — ineligible product mix, inter-state branch transfer, accounting-policy timing, GST rate transition — by a stable variance code, surfaces ageing buckets on unreconciled lines, and produces an audit-ready claim pack that the company secretary and statutory auditor can sign off before submission to the Project Management Agency. The same engine maintains the FY 2019-20 base-year register as a locked reference once the base is approved at first-claim filing, so every subsequent annual claim runs the incremental computation against an immutable base. For brands operating at PLISFPI scale, the discipline supports the broader FMCG reconciliation software India operating model — the platform also handles trade-spend, modern-trade settlements, distributor claims, and the GST credit-note cycle on the same data spine. A general-purpose reconciliation software India deployment with the FMCG and food-processing presets is what most Tier-1 beneficiaries run.

FAQ

The five FAQs above address the operational questions Indian PLISFPI beneficiary finance teams ask most often when filing and defending annual incremental-sales claims.

Terra Insight Reconciliation Infrastructure

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

Published 27 June 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