PLISFPI RTC/RTE and Millet Segment Claim Reconciliation

A food-processing beneficiary inside the PLISFPI 53-list closes the operational year for FY 2025-26 with consolidated revenue of approximately ₹3,800 crore in the foods division, of which the eligible Segment-1 RTC/RTE portfolio — instant noodles, frozen ready-meals, snack mixes, and a fast-growing millet noodle line — accounts for ₹1,420 crore. The brand’s FY 2019-20 base year for the same eligible-SKU set was ₹620 crore. The Segment-1 incremental sales line therefore stands at ₹800 crore, against which the year’s incentive at the scheme percentage in force for the operational year resolves to roughly ₹64 crore on the RTC/RTE base layer and an additional ₹9 crore on the millet sub-segment, for a single-year PLISFPI claim of ₹73 crore. The audit committee’s question on every quarterly review is brutally simple: how much of the ₹1,420 crore is provably eligible-SKU revenue, how much of the ₹9 crore millet line is provably above the 15 percent BOM ratio, and does the eligible-segment revenue tie to the audited Ind AS 108 segment disclosure that the statutory auditor will sign off in the same operational year. This is PLISFPI RTC RTE millet segment claim reconciliation at production scale, and it is the single most consequential finance discipline for the 53 beneficiaries through FY 2026-27.

Quick reference

The reconciliation in one paragraph

PLISFPI claims are not file-and-forget. A beneficiary must, for every operational year through FY 2026-27, segregate eligible-SKU sales from non-eligible SKUs in the GL by article number and HSN; tie the eligible-SKU revenue line to the GSTR-1 HSN-level summary for the same quarters; evidence the millet sub-segment by ingredient bill of materials, batch production records, and procurement-ledger linkage to the underlying ingredient HSN; certify the incremental sales calculation against the frozen FY 2019-20 base; and reconcile the eligible-segment revenue to the audited Ind AS 108 segment disclosure for the same period. A gap at any one of the four cross-checks — GL versus GSTR-1, BOM versus batch record, base year versus current year, claim versus Ind AS 108 — is a hard rejection at MoFPI certification or a clawback at the next verification cycle. The scheme deadline cliff of 31 March 2027 makes the FY 2025-26 and FY 2026-27 claim windows the most consequential of the six-year tenure.

What the PLISFPI claim filing actually looks like in India

PLISFPI is administered by the Ministry of Food Processing Industries — MoFPI — under a ₹10,900 crore outlay across six years, FY 2021-22 to FY 2026-27, with FY 2026-27 the final eligible operational year. The scheme has four segments: Segment-1 covers branded RTC/RTE plus three adjacent food categories (Processed Fruits and Vegetables; Marine Products; Mozzarella Cheese), Segment-2 covers innovative or organic products under the SMEs route, Segment-3 covers branded Indian product marketing outside India, and Segment-4 is the millet-based products component that overlays on Segment-1. The 53 named beneficiaries — ITC at slot 29 in the published list, plus HUL, Britannia, Nestle India, Bikaji, Bikanervala, Haldiram Snacks, Haldiram Foods International, Balaji Wafers, Tata Consumer, Anmol Industries, Parag Milk, Amul (GCMMF), and the other branded food processors — file annual claims against incremental sales of eligible manufactured products over the FY 2019-20 base year. ITC Foods, for example, files for YiPPee instant noodles in the RTC/RTE base segment and ITC Aashirvaad millet noodles in the millet sub-segment as two distinct evidence packs with overlapping but independent ingredient BOMs.

The claim filing flows through the MoFPI portal each operational year against an audited package. The package carries the eligible-SKU revenue by quarter for the year, the FY 2019-20 base revenue for the same eligible-SKU set, the incremental sales calculation, the millet sub-segment evidence pack (per-SKU BOM, batch production records, ingredient procurement ledger), the GSTR-1 HSN cross-foot for each claim quarter, and the Ind AS 108 audited segment disclosure that maps eligible-SKU revenue into a reportable segment in the statutory financial statements. The third-party certifier — typically the statutory auditor or an independent chartered accountant firm — signs the eligible-sales certificate, and the certified claim flows into MoFPI verification. Approved claims are released against the per-year scheme percentage matrix in force for the operational year.

The reconciliation problem sits in the gap between the brand’s internal GL — which tracks revenue by SKU but not by PLISFPI eligibility — and the four external evidence streams: the manufacturing-line BOM and batch records, the GSTR-1 HSN summary, the FY 2019-20 base-year sales register, and the audited Ind AS 108 segment disclosure. Each of those streams is owned by a different team — supply chain, GST compliance, FP&A, statutory audit — and the reconciliation has to bridge them quarterly with audit-grade traceability.

The Ind AS 108 and Ind AS 20 overlay

The single most consequential accounting decision in PLISFPI claim reconciliation is the segment reporting design. Ind AS 108 requires operating segments to be reported on the same basis used by the chief operating decision maker for resource allocation and performance assessment — meaning the eligible-SKU portfolio (the RTC/RTE base and the millet sub-segment) must be visible to the CODM, must be reviewed as a discrete portfolio for the incentive-claim decision, and must be presented as a reportable segment in the audited financials. The audited segment revenue line for the eligible-SKU portfolio must equal — to the rupee — the eligible-sales line in the PLISFPI claim for the same period. A mismatch of even a few percent invites a certifier challenge or a MoFPI verification finding, and the brand has no defensible reconciliation if the segment reporting was constructed after the claim was filed instead of alongside it.

The incentive receipt itself is accounted under Ind AS 20 (Accounting for Government Grants). A PLISFPI receipt is a grant related to income (because it is calculated on incremental sales rather than capital expenditure) and is recognised when there is reasonable assurance that the entity will comply with the conditions attaching to the grant and that the grant will be received. In practice, brands accrue the incentive receivable at year-end on the basis of the operational-year incremental sales certified by the statutory auditor, and recognise the receivable against either an “other income” line in the P&L or as a reduction of cost of goods manufactured — the policy choice must be disclosed and applied consistently across operational years.

On the GST side, the PLISFPI receipt is a government grant and not consideration for a taxable supply. It sits outside Section 15(2) of the CGST Act — meaning it does not enter the taxable value of underlying RTC/RTE SKUs and does not require an offsetting Section 34 credit note. Brands that mis-classify the receipt as a sales reduction or as part of trade-spend accrual create a downstream reconciliation gap in the TPM accrual versus payout reconciliation flow and a GSTR-1 amendment exposure that the scheme does not require.

The 22 September 2025 GST 2.0 straddle for processed-food HSNs

CBIC Central Tax (Rate) Notifications 09 to 16/2025-CTR dated 17 September 2025, effective 22 September 2025, consolidated HSN 1905 (biscuits and bread) and several adjacent processed-food categories at the 5% slab. The GSTR-1 HSN summary for the PLISFPI claim period straddling 22 September 2025 carries a rate-effective-date split — pre-22-September lines at the legacy rate, post-22-September lines at the rationalised rate. The PLISFPI eligible-SKU register must mirror the same straddle because the GSTR-1 cross-foot is the auditor’s second confirmation of eligible-segment revenue. Brands operating in the retro credit note quarter-end discipline already maintain this split for distributor scheme reconciliation; the PLISFPI claim engine should consume the same rate-effective-date master rather than rebuild it.

A worked example: ITC Foods PLISFPI claim, FY 2025-26 operational year

A leading branded foods division — ITC Foods, beneficiary slot 29 in the MoFPI 53-list — files its FY 2025-26 PLISFPI claim for the YiPPee RTC/RTE instant-noodle portfolio and the Aashirvaad millet-noodle portfolio against the FY 2019-20 base year. The eligible-SKU register carries 47 article numbers across two HSNs (HSN 1902 for pasta and noodles, with a sub-line in HSN 1904 for the cereal-based RTE crackers under the same brand umbrella) and three manufacturing plants.

Illustrative — public disclosures do not reveal internal PLISFPI claim amounts; the figures here are representative of the operating pattern, not actual brand data. Cross-verify against the audited financial statements and the MoFPI portal acknowledgement before action.

The cross-foot to GSTR-1 for the same period returns eligible-SKU HSN summary at ₹1,422 crore — a ₹2 crore gap traced to two December 2025 export shipments invoiced under a separate export HSN entry and not picked up by the eligible-SKU SKU-to-HSN match. The reconciliation engine flags the gap, the GST team confirms the export shipments are eligible-SKU manufactured product, and the claim register is updated to include the ₹2 crore in eligible revenue. The cross-foot now ties to GSTR-1.

The cross-foot to the Ind AS 108 segment disclosure returns “Branded Packaged Foods — RTC/RTE Segment” revenue at ₹1,420 crore — a clean tie after the GSTR-1 reconciliation. The millet sub-segment is presented inside the same reportable segment with a sub-line of ₹100 crore in the segment note disclosure, and the segment auditor signs off the eligible-SKU sub-line against the manufacturing BOM register and the GSTR-1 HSN summary.

The millet sub-segment evidence pack carries per-SKU BOM data for the 11 Aashirvaad millet-noodle SKUs in the eligible register. The average millet ratio across the 11 SKUs is 24 percent — well above the 15 percent operational benchmark — with the lowest at 18 percent (the multigrain noodle variant) and the highest at 38 percent (the foxtail-millet single-ingredient variant). Each SKU’s BOM is tied to actual batch production records from the Aashirvaad noodle line at the Sehore plant, and the procurement ledger ties ingredient HSN to supplier invoices for the underlying jowar, bajra, ragi, foxtail, and minor-millet purchases.

The reconciliation surfaces three findings for the FP&A controller. First, four SKUs in the YiPPee portfolio launched mid-year share a manufacturing line with a non-eligible savoury-snack co-product, and the brand cannot evidence batch separation for two months of the launch period — those two months of revenue (₹3.4 crore) are dropped from the eligible register pending a manufacturing-line audit, reducing the claim by approximately ₹0.15 crore. Second, the millet sub-segment SKU list includes one Aashirvaad multigrain variant where the BOM millet ratio is 13.5 percent — below the 15 percent operational benchmark — and the SKU is moved out of the millet sub-segment and into the RTC/RTE base layer, with no net loss to the claim because it was already eligible at the base layer. Third, the FY 2019-20 base-year register was frozen at scheme inception against 41 article numbers, and 6 of the FY 2025-26 articles are line extensions of those 41 — the reconciliation maps the line extensions to their parent articles for the base-year revenue computation so that the incremental sales calculation does not double-count.

Common reconciliation breakages

• The GL revenue feed by SKU does not carry a PLISFPI-eligibility flag, so the eligible-segment revenue has to be computed every quarter by joining the SKU master against the eligible-SKU register — a join that breaks silently when new SKUs are launched without eligibility classification.
• The bill of materials is sourced from the manufacturing execution system and the SAP PP module, but the two carry different version histories — a recipe revision in one system may not flow to the other for several days, causing the millet ratio computation to vary across runs of the same period.
• The GSTR-1 HSN summary is filed at finished-product HSN, but eligible-SKU revenue in the PLISFPI claim is filed at article-number granularity — the article-to-HSN map drifts when commercial introduces new SKUs that share an existing HSN, and the cross-foot starts breaking quarter by quarter.
• The FY 2019-20 base year was frozen at scheme inception, but line extensions, brand reorganisations, and acquisitions during the six-year tenure mean the base-year article set drifts from the operational-year article set — without explicit base-year-to-current-year article mapping, the incremental sales calculation overstates or understates.
• The Ind AS 108 segment disclosure is constructed at year-end by the statutory audit team, while the PLISFPI claim is constructed quarterly by the FP&A team — the two often disagree on which SKUs belong inside the reportable segment, and the reconciliation is forced at year-end under audit pressure instead of being maintained continuously.

How a reconciliation platform handles this

A modern reconciliation engine ingests the eligible-SKU master, the GL revenue feed by SKU and quarter, the manufacturing BOM and batch production records, the GSTR-1 HSN summary, the FY 2019-20 base-year register, and the Ind AS 108 segment mapping — each in its native format — and ties them with article-number, HSN, and period as the join keys. Variances are classified by code: GL-to-GSTR-1 gaps, BOM-to-batch-record gaps, base-year-to-current-year article-mapping gaps, and segment-disclosure-to-claim gaps each get their own taxonomy bucket. Ageing the unresolved variances by claim-period quarter surfaces stuck cells for the FP&A controller, and the closing pack — eligible-segment revenue by quarter, GSTR-1 cross-foot, millet sub-segment evidence pack with per-SKU BOM ratios, incremental-sales computation against the frozen FY 2019-20 base, and Ind AS 108 segment tie — assembles as an audit-ready evidence pack ready for the statutory auditor and the MoFPI certifier. The discipline pays back at the certification stage where a clean pack moves through verification without queries, while a defective pack triggers verification holds that can delay the incentive receipt by quarters. For brands that also run growth-over-base distributor schemes, the same engine can carry the year-over-year incremental discipline across both flows. The broader category context is covered in the food processing reconciliation pillar and the commercial anchor is FMCG reconciliation software India, with the cross-cluster bridge into reconciliation software India for finance teams running PLISFPI alongside other regulatory reconciliations.

FAQ

The five FAQs above address the operational questions PLISFPI beneficiary CFOs and FP&A controllers ask most often when implementing structured RTC/RTE and millet segment claim reconciliation through the final operational year FY 2026-27.

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