More Retail FMCG Settlement Reconciliation

More Retail is, by India’s modern-trade settlement standards, the long-cycle account. Aditya Birla group’s grocery chain operates a roughly fourteen-day window from goods receipt to credit advice — twice the length of DMart’s seven-day cycle and four days longer than Reliance Smart’s. For an FMCG controller running the same biscuit, snack or staples SKU through all three chains, More’s cycle is the one that anchors the cash conversion calendar. A monthly Britannia NutriChoice invoice that hits DMart on day one will have settled there by day eight; the same invoice into RSL clears by day eleven; into More, the AR ledger does not see the bank credit until day fifteen.

The cycle is not just longer. It is operationally different. More’s distribution centre runs an explicit GRN-versus-invoice tolerance window on per-case weight that absorbs small variances at receipt rather than netting them at settlement. It runs a QC reject debit mechanism that requires photo evidence per affected case before the debit appears on the settlement file. And it issues a More-specific settlement file format that does not map line-for-line to DMart’s seven-day file or RSL’s ten-day file. More Retail FMCG settlement reconciliation lives at the intersection of those three operational realities — and it has to absorb the GST treatment of every debit line back to Section 15(2), Section 34 and (post-22 September 2025 for biscuits) the 5% GST 2.0 rate.

Quick reference

Why does More Retail run a 14-day settlement cycle?

More’s longer cycle is a function of the operational discipline it has chosen to enforce at goods receipt, not a payment-terms quirk. Two structural differences from DMart’s seven-day model explain it.

First, More applies the GRN-vs-invoice tolerance at the DC dock rather than netting weight variances at the settlement file. The DC’s GRN team checks per-case net weight against the supplier’s invoice declaration, applies a small tolerance percentage on the spot, and absorbs minor variances without raising a debit. Where the variance exceeds the tolerance, the GRN is recorded at the invoice quantity but a tolerance debit is queued for the settlement file. This per-case discipline takes longer at receipt than DMart’s net-at-settlement approach.

Second, More’s QC reject window demands photo evidence per affected case before the debit is finalised. The QC team at the DC inspects the delivered cases, photographs any rejected case at unit and batch-code level, and queues the photo evidence for the settlement file. The supplier’s QA team is given the photo file as the evidence base for the debit. This evidence-gathering layer adds days that DMart’s lighter QC posture does not.

The result is a settlement cycle that is more defensible at audit and at the supplier-dispute table — but slower than DMart’s. Suppliers selling into both accounts have to model the cycle difference into their cash conversion forecasts and into their accrual logic for the trade-promotion register.

Britannia NutriChoice into More Retail — a worked example

Illustrative — public disclosures do not reveal internal scheme amounts; the figures here are representative of the operating pattern, not actual brand data. Cross-verify against your own DMS export or trade-spend GL before action.

Assume a Britannia NutriChoice 250g pack invoiced into More Retail’s distribution centres on a monthly bulk order — a ₹1.4 crore primary-sales invoice across 28,000 cases (each case carries 24 packs). Britannia’s primary-sales invoice ledger captures the order at the PO level, lists the per-case unit price, per-case GST at 5% (HSN 1905, post-22-Sept-2025) and the invoice total. The PO ships to More’s regional DC, GRN is raised at the dock, and the T+14 settlement file lands fourteen days later.

The settlement file shows the following debit lines against the ₹1.4 crore invoice:

The mechanics underneath the table need to be unwound at the supplier’s AR ledger:

• The GRN-tolerance debit (line 3) is, in Section 15(2) terms, a buyer-side price reduction applied after supply. To reduce Britannia’s outward taxable value, the supplier raises a Section 34 credit note against the affected invoice lines, GST is reduced proportionately, and More reverses the corresponding ITC. The supplier’s GSTR-1 Table 9B captures the credit note; More’s GSTR-2B reflects the ITC reversal.
• The QC reject debit (line 4) follows the same Section 34 treatment, but with the photo-evidence file as the supplier’s QA audit base. Britannia’s QA controller reviews the photo file before signing off the credit note. Where the photo evidence does not support a debit, Britannia disputes the line — the debit stays on the settlement file but no credit note is raised and the disputed amount sits in the supplier’s ledger as a contested receivable.
• The listing fee debit (line 5) is a routine modern-trade overhead and is treated as a service consideration paid by Britannia to More — More raises a tax invoice for the listing fee, Britannia claims ITC, and the deduction is settled via netting at the settlement file rather than via a Section 34 credit note. The trade-spend GL accrues the listing fee monthly per SKU per DC.
• The BTL marketing debit (line 6) is reconciled against Britannia’s trade-promotion accrual register at the scheme level. The festive shelf-talker scheme has a scheme code, a defined eligible spend, a documented BTL claim form, and a per-account allocation. If the More debit exceeds the scheme accrual at the More account, the trade-marketing team has a reconciliation break to investigate before signing off the BTL recoverable.
• The net settlement amount (line 8) is the bank credit Britannia expects on day 15. The AR controller ties the bank receipt to the net settlement and posts the difference between the invoice value and the bank receipt to a deductions-clearing account, then dispositions the deductions individually as Section 34 credit notes, listing fee netting, BTL accrual netting and disputed-receivable balances.

The same Britannia NutriChoice SKU sold into DMart settles at T+7 with a prompt-payment discount and a thinner debit-line structure; the same SKU into RSL settles at T+10 with a heavier BTL marketing reimbursement layer. The primary-sales invoice ledger is the same source of truth; the three account-specific settlement files are three distinct reconciliation flows on top of it.

How does More’s GRN-tolerance debit interact with Section 15(2) of the CGST Act?

The GRN-tolerance debit is a post-supply price reduction unilaterally applied by the buyer at goods receipt. Under Section 15(2)(b) of the CGST Act, only invoice-recorded discounts qualify as exclusions from transaction value at the supply stage — the GRN-tolerance debit does not. Section 15(3)(b) then provides the post-supply route, requiring three conjunctive prongs: (a) the price reduction must be established by an agreement at or before the time of supply, (b) the credit note must be specifically linked to the affected invoices, and (c) the recipient (More) must reverse the corresponding ITC on the discount amount.

In practice, the GRN-tolerance mechanism is documented in the supply agreement between the brand owner and More — the tolerance percentage on per-case weight, the basis for the debit (excess-over-tolerance only) and the photo evidence requirement are written into the agreement. That clears the first prong. The supplier’s Section 34 credit note raised against the GRN-tolerance debit links each affected invoice line — that clears the second prong. And More reverses the proportional ITC at GSTR-3B — that clears the third prong. The CBIC’s published guidance on Section 15(2) and Section 34 is the audit-defence base for this treatment; see the CBIC GST portal for the underlying notifications.

Where the supplier’s controllership has not built the Section 34 credit-note flow against GRN-tolerance debits, the deduction sits inside the supplier’s outward taxable value, GST is overpaid against a reduced economic receivable, and the supplier carries an unrecovered GST cost on the deduction. The same Section 15(3)(b) discipline that governs the cluster’s trade promotion accrual vs payout reconciliation for Indian FMCG cycle applies on each modern-trade debit line.

What does the QC reject debit photo-evidence audit actually look like?

The QC reject debit is operationally the highest-friction line on More’s settlement file. The DC’s QC team inspects delivered cases, identifies rejects at unit or batch level, and photographs each rejected case with case number, batch code and observed defect. The photo file is shared with the supplier’s QA controller along with the settlement file. The supplier’s QA controller has three obligations:

First, the photo evidence has to be reconciled against the supplier’s QA batch records. The batch code on the photo file is matched against the production batch in the supplier’s QA system, the unit-level defect description is checked against the QA inspection record, and the disposition (accept the debit or dispute it) is recorded against the batch.

Second, accepted QC reject debits flow to the Section 34 credit-note workflow. The supplier raises a credit note against the original invoice, the credit note specifically links the invoice line and the affected case quantity, and the credit note reduces outward taxable value and GST. The credit note is reported in GSTR-1 Table 9B; More’s GSTR-2B reflects the ITC reversal.

Third, the QA controller flags the production batch for CAPA. Even where the QC reject is a small percentage of cases, the batch-level data is the input to corrective action — a recurring defect on the same batch across multiple modern-trade accounts is a process control signal at the plant, not just a settlement debit.

Disputed QC reject debits are the slowest line on the supplier’s AR ledger. The photo evidence either does not support the debit, or the supplier’s QA records show the cases were within spec at dispatch and the defect arose downstream. The disputed amount sits as a contested receivable until More and the supplier reach commercial agreement. A clean reconciliation cycle ages these disputed lines 0-15 / 16-30 / 31-60 / 61+ days from the settlement file date and surfaces them by supplier-side QA disposition.

How does the More settlement file ingestion work alongside DMart and RSL?

The same primary-sales invoice ledger feeds three account-specific settlement reconciliation flows. The supplier’s reconciliation discipline normalises the three account-specific file formats into a single internal debit-line taxonomy, then runs the reconciliation per debit line against the source registers.

The internal taxonomy typically carries these line types: GRN-tolerance debit (with the tolerance percentage and excess basis), QC reject debit (with evidence link), listing fee debit (per SKU per DC per period), BTL marketing debit (per scheme), prompt-payment discount (where the trade agreement provides one — DMart’s seven-day cycle has the most published discipline here), and rate-difference debit (where applicable). Each account-specific column on each settlement file is mapped into this taxonomy at ingestion, so the AR controller sees a normalised debit-line view across DMart, RSL, More, Spencer’s, Trent, Walmart Best Price and Metro Cash & Carry.

The reconciliation then runs per debit line back to the source:

• GRN-tolerance and QC reject debits reconcile against the supplier’s QA records and the Section 34 credit-note register; accepted debits become credit notes, disputed debits become contested receivables.
• Listing fee debits reconcile against More’s tax invoices for listing fees and against the trade-spend GL on the listing-fee accrual; ITC on listing fees is claimed by the brand owner.
• BTL marketing debits reconcile against the trade-promotion accrual register at the scheme level and against the per-account allocation; accrual overruns and accrual under-runs are surfaced as named scheme breaks.
• The net settlement amount on each account’s file reconciles to the bank receipt on the credit-advice date; differences are dispositioned at the deductions-clearing account.

The cross-account view also surfaces operating insights: the same SKU, sold into three accounts, produces three QC reject rates, three GRN-tolerance debit profiles and three listing-fee structures. Disparate rates across accounts are either an account-specific operational signal or a supplier-side production-batch signal — both worth investigating.

How does the 22 September 2025 GST 2.0 cut-over land on a More settlement file?

The September 2025 GST 2.0 rate-rationalisation set — CBIC Notifications 09/2025 through 16/2025 – Central Tax (Rate) — moved biscuits (HSN 1905 all sub-codes), chocolates and most personal-care categories that historically attracted 18% down to the 5% slab from 22 September 2025. For a Britannia NutriChoice invoice into More after 22 September, the GST column on the primary-sales invoice carries 5% on the gross taxable value, and any Section 34 credit note raised against that invoice (for GRN-tolerance or QC reject) also carries 5%. For invoices issued on or before 21 September at 18%, any Section 34 credit note raised after the cut-over inherits the original 18% rate — Section 34 follows the rate of the underlying supply, not the rate at the date of the credit note.

The same discipline applies on the buyer side: More’s settlement file at T+14 will, for the post-22-Sept cohort, show 5% on the line-item GST column, and More’s GSTR-3B ITC reversal on the supplier’s credit note will reverse at 5%. For schemes that straddle 22 September — for example a Diwali curtain-raiser that opens 15 September — the supplier’s invoice ledger carries two rate cohorts, and the supplier’s settlement reconciliation has to cohort the More debit lines accordingly. The same date-locking discipline applies in the cluster’s GST credit note reconciliation under Section 34 treatment.

Detection — where the breaks actually surface

Five detection patterns recur in the More Retail settlement reconciliation cycle.

Per-PO GRN reconciliation scan. Run every PO through a GRN-quantity-vs-invoice-quantity check at the settlement file. Where the GRN-tolerance debit appears, recompute the excess-over-tolerance percentage from the per-case weight data and reconcile it against the supplier’s pack-weight declaration. Tolerance debits that do not reconcile to a supplier-side weight variance signal either a buyer-side measurement error or a packaging line variance worth flagging to QA.

QC reject evidence audit. Reconcile the More photo-evidence file against the supplier’s QA batch record per case. Each accepted QC reject case becomes a Section 34 credit note line; each disputed case becomes a contested receivable line. The supplier’s QA disposition rate on the More photo file is an operational metric — a rising disputed-case rate is a deteriorating signal at the More relationship.

Settlement file ingestion check. Verify that every PO on the supplier’s outbound shipment register has produced a corresponding entry on the More settlement file at T+14. Missing files are an account-level disclosure gap that needs to surface to the AR controller before the cycle closes.

Cross-account settlement-cycle view. Compare the same SKU’s debit-line profile across DMart, RSL and More. Disparate QC reject rates and GRN-tolerance debit rates surface either account-specific operational signals or production-batch issues at the supplier’s plant — both worth a CAPA review.

Section 34 credit-note tie-out. Reconcile the supplier’s Section 34 credit notes raised against More debits with More’s GSTR-2B ITC reversal. Where the credit note has been raised but More has not reversed ITC in the same period, the GSTR-1 Table 9B and GSTR-2B picture drifts — the supplier’s GST compliance controller has a follow-up to chase before quarterly reconciliation.

The CBIC’s published guidance at cbic-gst.gov.in covers the Section 15(2) valuation rule, the Section 34 credit-note mechanic and the September 2025 rate-rationalisation notifications relevant to biscuits, soaps, shampoos, toothpaste and chocolates. A clean More Retail settlement reconciliation pack surfaces, per PO: invoice value, GRN quantity vs invoice quantity, GRN-tolerance debit (with weight variance), QC reject debit (with photo-evidence link and accepted-vs-disputed disposition), listing fee debit, BTL marketing debit, gross deduction sum, net settlement amount, credit-advice date, bank-receipt tie-out, Section 34 credit notes raised, ageing report on unreconciled lines, and a cross-account view comparing More against DMart and RSL on the same SKU — handed to the AR controller for receivable posting and to the trade-marketing controller for scheme sign-off.

Continue reading the FMCG cluster

• Cluster hub: FMCG reconciliation cluster hub — TPM, modern trade, general trade DMS, quick commerce, Section 15(2) valuation and PLISFPI.
• Cornerstone: Trade promotion accrual vs payout reconciliation for Indian FMCG — accrual drift, ageing buckets, provision-vs-payout variance against the trade-spend GL.
• Cross-cluster bridge: GST credit note reconciliation under Section 34 — for the credit-note mechanic that lands on every accepted GRN-tolerance and QC reject debit.
• Money page: FMCG reconciliation software India — the commercial intent surface for FMCG buyer queries.