Section 269SS + 269ST Jewellery Cash Sale Rs 2 Lakh + 271DA Penalty India

A national jewellery chain’s regional controller reviews the wedding-season monthly pack for October 2026 — the peak of the pre-Diwali and pre-wedding buying cycle across most metros. Consolidated wedding-basket invoicing across 411 stores runs at approximately ₹1,240 crore for the month, with an average customer-occasion basket of ₹9.2 lakh. The reconciliation surfaces four findings that require store-level correction before the November GSTR-1 filing and before the second-half Financial Intelligence Unit filing cycle. First, 22 customer baskets across 14 stores show cumulative cash receipts between ₹1.85 lakh and ₹2.6 lakh across the wedding-occasion window — the Section 269ST clause (c) aggregation clock ran over the ₹2 lakh cap, and Section 271DA penalty exposure on the offending baskets aggregates to approximately ₹51 lakh. Second, 9 customer accounts show cash advances of ₹22,000 to ₹40,000 booked against future gold-set orders — Section 269SS territory, with Section 271D 100% penalty exposure of approximately ₹2.7 lakh. Third, 4 order cancellations were refunded in cash at ₹28,000 to ₹52,000 per refund — Section 269T territory, with Section 271E 100% penalty exposure of approximately ₹1.6 lakh. Fourth, 6 above-threshold cash transactions were routed to the FIU-IND Cash Transaction Report queue but the buyer PAN and address fields are incomplete on 2 of them, blocking the next scheduled filing. This is Section 269SS 269ST jewellery cash sale 2 lakh penalty India reconciliation at production scale — and getting the four-section stack, the PMLA overlay, the BIS HUID discipline, the SAC 998892 / HSN 7113 GST split and the Section 273B evidentiary pack all right on the same monthly close is the difference between a clean audit walkthrough and a stacked ₹55 lakh-plus penalty case.

Quick reference

Section 269SS — the Rs 20,000 cash cap on wedding-order advances and gold-scheme deposits

Section 269SS of the Income-tax Act 1961 prohibits acceptance of any loan, deposit or specified sum in cash where the amount, or the aggregate amount, is ₹20,000 or more. The mode required is an account-payee cheque, an account-payee bank draft, or the electronic clearing system through a bank account. The prohibition binds the recipient — the jeweller — and the Section 271D penalty is 100% of the amount received.

The practical fact patterns in a jewellery-retail context are two. First, the wedding-order advance — a customer books a gold-set order to be finished four weeks ahead of the wedding date and pays a ₹25,000 to ₹75,000 cash advance at booking to lock the making-charges quote and reserve the gold-rate window. That advance has the character of a deposit against a specified transaction, and cash acceptance of ₹20,000 or more breaches Section 269SS. Second, the gold-scheme instalment — a customer enrolled in a recurring gold-purchase scheme pays a monthly instalment of ₹20,000 or more in cash at the counter. That instalment is an accrued deposit against the eventual purchase and, from the department’s audit perspective, sits within the Section 269SS envelope.

The Section 271D penalty is not discretionary once the contravention is proved. A ₹40,000 cash wedding-order advance attracts a ₹40,000 penalty on the retailer, in addition to the income-tax and GST consequences of the sale. The only statutory relief is the Section 273B reasonable-cause defence — which, as the case law surveyed later in this article confirms, is a narrow window and turns on genuine contemporaneous evidence.

The reconciliation configuration must reject any cash advance of ₹20,000 or more at the counter and route the customer to a banking-channel payment. Where the customer insists on cash on grounds that they do not maintain a bank account, the retailer’s counterparty risk is real — the department has consistently held that the retailer, as the recipient, is on the hook for the penalty regardless of the customer’s banking status. The customer’s absence of a bank account is not a reasonable cause for the retailer under Section 273B.

Section 269T — the Rs 20,000 cash cap on order-cancellation refunds

Section 269T is the mirror of Section 269SS on the repayment leg. No person shall repay any loan or deposit or specified advance, together with interest, of ₹20,000 or more otherwise than by an account-payee cheque, account-payee bank draft or electronic clearing system through a bank account. Section 271E imposes a penalty equal to the amount repaid on the person making the repayment.

The typical jewellery-retail fact pattern is the order-cancellation refund. A customer places a ₹1.2 lakh wedding-set order, pays a ₹40,000 cash advance at booking (which, as discussed above, itself breaches Section 269SS), and later cancels the order. If the retailer returns the ₹40,000 in cash — even acknowledging that the acceptance leg was already a Section 269SS breach — the refund is an independent Section 269T breach with its own Section 271E 100% penalty. The retailer therefore faces double exposure on a single cash-flow stack — ₹40,000 penalty under 271D on acceptance and a further ₹40,000 penalty under 271E on repayment.

The audit-defensible configuration is to refund all order-cancellation amounts through banking channels regardless of the mode in which the original advance was received. Where the original acceptance was in cash and now sits as a Section 269SS breach on the retailer’s books, the retailer should still refund via NEFT or account-payee cheque; converting the second breach to a compliant refund leaves only the acceptance-side liability and does not compound it.

Section 269ST — the master Rs 2 lakh cash-consideration cap

Section 269ST is the master cap governing cash sale-consideration receipts and is the section most jewellery-retail CFOs cite as the operational binding constraint. No person shall receive an amount of ₹2 lakh or more otherwise than by account-payee cheque, account-payee bank draft or electronic clearing system through a bank account under any of three concurrent tests:

Clause (a) — aggregate from a person in a day. All cash receipts from a single customer across all transactions within a single day, at a single store or across multiple stores of the same chain, aggregate for this test. A customer paying ₹80,000 in cash at the retailer’s Bengaluru store in the morning and ₹1.5 lakh in cash at the same chain’s Whitefield store in the evening breaches clause (a) — day total ₹2.3 lakh, above the cap.

Clause (b) — single transaction. A single invoice with cash consideration of ₹2 lakh or more breaches clause (b) even if the payment is split into three ₹70,000 cash instalments over the payment window. The instalments are three legs of one transaction, and the aggregation is at the transaction level.

Clause (c) — single event or occasion. All cash receipts from a single customer across all transactions relating to one event or occasion aggregate for this test. A wedding is one occasion. A wedding customer paying ₹90,000 in cash on visit one for the bride’s gold-set booking advance, ₹80,000 on visit two for a supplementary bangles piece, and ₹60,000 on visit three for a groom’s chain — total cash across three visits over four weeks is ₹2.3 lakh — breaches clause (c) even though no individual visit was near the cap and no individual invoice touched ₹2 lakh.

The three clauses operate independently. A single transaction can breach one, two, or all three tests. The Section 271DA penalty equals the total amount of the receipt in contravention — not the excess over ₹2 lakh, but the whole cash aggregate. A ₹3 lakh cash receipt breaches clause (b) and the penalty is ₹3 lakh, not the ₹1 lakh excess.

The clause (c) occasion-aggregation test is the trap that catches the most jewellery retailers. Counter staff naturally think of Section 269ST as a single-day or single-invoice cap and clear a ₹1.5 lakh cash receipt on the reasoning that it is under the ₹2 lakh line. The occasion-aggregation clock is invisible at the counter unless the reconciliation platform actively surfaces the running per-customer, per-occasion cash aggregate at billing time. Without that visibility, the store-level audit finds the breach at month-end and the fix is retroactive.

For the wedding-basket fact pattern, the full mechanics are covered at wedding purchase Section 269ST cash cap and PAN mandate.

Section 273B — the reasonable-cause defence and its narrow window

Section 273B provides that no penalty under Section 271D, 271E or 271DA shall be imposable if the assessee proves that there was reasonable cause for the failure. The section is the only statutory relief valve. The burden rests squarely on the assessee, the evidentiary standard is genuine, and case law across ITAT benches has been consistent in narrowing the acceptable fact patterns.

Reasonable cause accepted in reported cases has included: a customer requiring cash for a documented medical emergency (hospital admission, blood-arrangement urgency) with contemporaneous evidence; an RBI-notified or bank-notified core-banking outage covering the specific window during which the cash was received; and a bona fide misunderstanding of the counterparty identity where the retailer believed the cash was received from a person other than the ultimate contracting party. Reasonable cause has been consistently rejected where the customer preferred cash for personal-privacy or convenience reasons, where the retailer accepted cash to close a competitive sale, where the staff was untrained on the ₹2 lakh cap, and where the cash was accepted with the intention of banking it via the retailer’s own bank account (which does not cleanse the customer-to-retailer mode-of-receipt breach).

The evidentiary pack a jewellery retailer must maintain to run a Section 273B defence includes: the customer statement recorded contemporaneously; the surrounding transaction context including invoice references and store identifier; the ledger position of the customer master; the CCTV timestamp of the counter transaction; the immediate banking of the cash with the source-of-funds narrative; and the customer’s own identifiable circumstances tying the fact pattern to the accepted category. The reconciliation platform must maintain this pack per exception transaction — not as a retrospective compilation but as a running record generated at the moment the exception fires.

CBDT Instruction No. 3/2017 — jewellers as a priority enforcement sector

CBDT Instruction No. 3/2017 dated 21 July 2017 sets out the enforcement framework for Section 269ST and names jewellers, real-estate agents, and hospitals as priority sectors for scrutiny drives. The instruction directs assessing officers to correlate the Statement of Financial Transactions (Form 61A) filings, the GST returns, and trader-specific verification drives to identify cash-receipt patterns that indicate Section 269ST breaches.

For a jewellery retailer, the practical implication is that the enforcement risk is not theoretical. Departmental scrutiny letters citing Section 269ST have landed on jewellery-chain finance offices in every wedding-season quarter since FY 2018-19, and the CBDT instruction is the anchor citation in the show-cause notice. The retailer’s first-line defence is the reconciliation record showing that the internal control was in place at the counter, the exception was flagged at billing, and either the cash was refused (no breach) or the exception was escalated with contemporaneous documentation for the Section 273B defence.

PMLA overlay — jewellers as reporting entities under FIU-IND

The Prevention of Money-laundering Act 2002 designates certain classes of persons as reporting entities under Section 2(1)(sa). Notification S.O.4571(E) dated 28 December 2020 designated persons carrying on the activity of dealing in precious metals and precious stones as reporting entities where the cash-transaction value with a single customer meets or exceeds the notified threshold. Registered reporting entities have obligations independent of and additional to the Income-tax Section 269ST cap:

• Appointment of a Principal Officer within the retailer’s finance or compliance function
• Registration on the FINnet portal of the Financial Intelligence Unit — India (FIU-IND)
• Filing of Cash Transaction Reports (CTR) for aggregated cash transactions crossing the notified threshold
• Filing of Suspicious Transaction Reports (STR) for transactions carrying reasonable grounds of proceeds-of-crime linkage
• Maintenance of Know Your Customer records for a defined retention period
• Response to FIU-IND enquiries within prescribed turnaround

The PMLA reporting obligation runs alongside the Income-tax Section 269ST discipline — a single cash receipt above the PMLA threshold from a jewellery customer triggers a CTR filing on the PMLA side and, if it also crosses the ₹2 lakh line, a Section 271DA penalty exposure on the Income-tax side. The reconciliation configuration must surface both event flags on the same transaction record so that the CTR filing runs on schedule and the internal audit catches the 269ST breach in the same monthly close cycle.

Non-registration under PMLA where the retailer meets the threshold, non-filing of CTRs or STRs, and inadequate KYC records attract monetary penalties under the PMLA rules and, in aggravated fact patterns, prosecution — separate from the Income-tax penalty stream. The two regimes reinforce each other in enforcement even as they operate under separate statutes.

BIS Hallmarking + HUID discipline — the piece-level audit chain

The Bureau of Indian Standards Act 2016 read with the Hallmarking of Gold Jewellery and Gold Artefacts Regulations 2018 and the 2021 amendments makes gold-jewellery hallmarking compulsory across the nationally-rolled-out districts. From 1 April 2022, every hallmarked piece must carry a six-digit Hallmark Unique Identification (HUID) mark alongside the BIS logo, the purity grade (14K, 18K, 22K) and the Assaying and Hallmarking Centre code.

The reconciliation relevance of HUID discipline is that it supplies a piece-level audit chain linking the physical inventory to the invoice, the invoice to the customer master, the customer master to the settlement receipt, and the settlement receipt to the Section 269ST cash-mode test. A department auditor investigating a suspected 269ST breach starts at the invoice, checks the HUID capture per line, walks the HUID back to the AHC assay register, walks the invoice forward to the settlement reference, and matches the customer PAN captured under Rule 114B. Any break in the chain — an invoice without HUID, an HUID without an AHC assay reference, a settlement receipt without an invoice link — surfaces as a red flag and expands the audit scope.

The retailer’s reconciliation configuration must therefore capture HUID at billing per piece, tie the HUID to the AHC invoice on the manufacturing/wholesale side, and knit the piece-level chain into the invoice-level and customer-master-level audit trail. Detail on the AHC invoice side of this discipline is at BIS hallmarking charges cost accounting for jewellers.

GST interaction — HSN 7113 at 3% + SAC 998892 at 5%

The GST rate structure on a gold-jewellery invoice runs on two primary lines. The gold value is invoiced under HSN 7113 (articles of jewellery and parts thereof, of precious metal) at 3% GST — 1.5% CGST plus 1.5% SGST on intra-state supply, or 3% IGST on inter-state supply. The making charges are invoiced under SAC 998892 (jewellery-making services, including gemstone-setting) at 5% GST on the labour value of the piece.

The Section 269ST cash-mode test runs on the total invoice value including both GST components. The ₹2 lakh cap is not on the pre-GST fee; it is on the gross amount received. A gold-set invoice with a ₹1.85 lakh pre-GST value carrying ₹5,550 CGST plus ₹5,550 SGST plus ₹0.19 lakh making-charges GST at 5% has a gross of approximately ₹1.9 lakh — still under the cap. A gold-set invoice with a ₹1.94 lakh pre-GST value gross-up to approximately ₹2 lakh with both GST components — right at the cap edge, and cash payment must be refused.

For a mixed-rate invoice sequence covering gold pieces (3%), stone-set pieces (0.25% or 3% on the stone side), silver pieces (3%), and ancillary or packaging items (18%) — the reconciliation stack must aggregate cash receipts across the mixed-rate legs, run the Section 269ST test on the gross customer-basket total, and generate the GSTR-1 row split for each rate. The full mixed-rate mechanics are at mixed-rate jewellery invoice reconciliation.

Section 206C interaction — what applies and what has been omitted

Three sub-sections of Section 206C are relevant context for a jewellery retailer, and only one of them is operative today on jewellery-side transactions. Section 206C(1D), introduced by the Finance Act 2016 to collect 1% TCS on cash sales of jewellery exceeding ₹5 lakh and cash sales of bullion exceeding ₹2 lakh, was omitted with effect from 1 April 2017 by the Finance Act 2017 — immediately after Section 269ST was introduced with the tighter ₹2 lakh cash-mode prohibition. The legislative logic was that Section 269ST prohibits high-value cash receipts outright, so TCS collection on such receipts became redundant.

Section 206C(1F) at 1% TCS on the sale of a motor vehicle where the consideration exceeds ₹10 lakh — the widely-cited high-value-goods TCS clause — does not apply to jewellery. Retailers should not extend the motor-vehicle framing to gold-set invoices.

Section 206C(1H) at 0.1% TCS on the sale of goods above ₹50 lakh per buyer per FY may apply to B2B jewellery sales — a bulk gifting order from a corporate buyer, a wholesale supply to a downstream retailer, or a bulk supply against a wedding-list contract from a corporate treasury account. The seller-side turnover threshold and buyer-side aggregate-consideration threshold both trigger; the retailer must capture buyer PAN at the invoice and collect TCS at 0.1% on the consideration above ₹50 lakh per FY per buyer. Where the buyer is itself a TDS-deductor under Section 194Q (Section 393(1) Sl. 8 code 1031) at 0.1% on the same transaction, the buyer’s TDS obligation prevails and the seller’s TCS obligation is suspended — the two rules are mutually exclusive per the CBDT clarification circulars. Full mechanics are at TCS reconciliation under Section 206C.

Worked example — a Rs 12-lakh wedding-season gold-set order with an audit-defensible split

A Tier-1 city bride-to-be walks into the retailer’s flagship store four weeks before her wedding date. The trousseau plan totals ₹12 lakh across a bridal gold-set (necklace, earrings, maang tikka), two supplementary bangles pieces, and a groom’s chain. The customer intends to pay through a mix of instruments. The counter manager runs the reconciliation platform’s three-clause Section 269ST test at billing.

Illustrative — the figures below are representative of the operating pattern for a mid-market Tier-1 city jewellery-retail transaction, not actual retailer data. Cross-verify against your own customer master, invoice register and settlement references before action.

Customer master onboarding:

• PAN captured under Rule 114B (invoice above ₹2 lakh threshold)
• Address proof link on file
• Occasion tag set to “Wedding — 25 November 2026” with the wedding party name
• Section 269ST occasion-aggregation clock initialised at zero

Invoice sequence — three billing dates across four weeks:

Gross basket approximately ₹11.68 lakh — the ₹32,115 gap to the ₹12 lakh headline is the second supplementary bangles pair the customer added at the final visit, which the plan comfortably absorbs.

Payment split — audit-defensible configuration:

• Cheque 1 (account-payee, drawn on customer’s SBI account) against INV-2110-A: ₹4,11,450 on 21 October
• Cheque 2 (account-payee, drawn on customer’s HDFC Bank account) against INV-2110-B + INV-2410-C combined: ₹1,55,085 on 24 October — bank collection route through customer’s own account confirmed at counter
• Card swipe on customer’s own credit card against INV-1811-D: ₹3,05,950 on 18 November, RRN captured at counter
• NEFT from customer’s SBI account against INV-1811-E: ₹2,95,400 on 18 November, UTR captured at counter
• Cash leg: ₹0

Section 269ST test result:

• Clause (a) — same-day cash aggregate per person: ₹0 on every day. Cleared.
• Clause (b) — single-transaction cash: ₹0 on every invoice. Cleared.
• Clause (c) — same-occasion cash aggregate: ₹0 across the entire wedding basket. Cleared.
• No Section 271DA exposure. No Section 273B defence required.

Section 269SS / 269T test result:

• No cash advance at booking (₹0). Cleared.
• No cash refund contemplated. Cleared.
• No Section 271D or 271E exposure.

PMLA reporting test:

• No cash transaction above the PMLA-notified threshold. No CTR filing task generated for this customer.
• Buyer PAN and identity captured for the KYC record retention.

BIS HUID capture:

• 11 HUIDs across the 5 invoices (necklace 1, earrings 2, maang tikka 1, bangles 4, chain 1, finishing pieces 2)
• All HUIDs traced back to the AHC assay reference and forward to the invoice line

GSTR-1 row split for the November filing:

• HSN 7113 at 3% (CGST 1.5% + SGST 1.5%): ₹11,07,000 taxable value, ₹33,210 tax
• SAC 998892 at 5% (CGST 2.5% + SGST 2.5%): ₹5,53,500 taxable value, ₹27,675 tax
• Filed in the respective rate rows against a single customer PAN

Alternate payment split with a small cash leg — variant scenario:

If the customer had insisted on paying INV-2410-C (₹75,960 gross) in cash — say the customer preferred to close the small supplementary invoice in cash on the same visit — the reconciliation platform’s three-clause 269ST test would run as follows.

• Clause (a) same-day aggregate: ₹75,960 on 24 October (assuming no other same-day cash from the customer). Below the ₹2 lakh cap. Cleared.
• Clause (b) single-transaction: ₹75,960 on INV-2410-C. Below the cap. Cleared.
• Clause (c) same-occasion aggregate: ₹75,960 cumulative across the wedding basket. Below the cap. Cleared.

The cash leg would pass Section 269ST, but a second cash leg on any subsequent visit would need to be projected against the same-occasion aggregate before acceptance. If the customer later brings ₹1,30,000 in cash for a supplementary earring pair, the projected same-occasion aggregate would be ₹75,960 + ₹1,30,000 = ₹2,05,960 — above the ₹2 lakh cap — and the second cash leg must be refused. The counter refuses, the customer routes the ₹1,30,000 through UPI or card, the aggregate stays clean, and the audit trail is defensible.

The variant scenario also raises the PMLA test — a ₹75,960 cash receipt is below the PMLA-notified CTR threshold (which is higher than the ₹2 lakh 269ST cap) but any pattern of repeated cash from the same customer would trigger the STR review workflow for staff assessment of proceeds-of-crime linkage. The reconciliation platform surfaces both flags concurrently at billing.

Cross-audit points on the illustrative order:

1. The customer PAN is captured on every invoice above the ₹2 lakh Rule 114B threshold; the two supplementary bangles invoices (below ₹2 lakh) do not require PAN under Rule 114B but the reconciliation platform still captures the customer-master PAN link.
2. Every HUID on every piece is captured at billing and traced to the AHC assay register — the piece-level audit chain is complete.
3. Every payment leg carries a UTR, RRN, or cheque number captured against the invoice reference — no orphan settlements.
4. The GSTR-1 filing for November aggregates the customer’s invoices into the correct HSN 7113 and SAC 998892 rows — the 3% and 5% legs are separated at the invoice level and roll up cleanly.
5. The Section 269ST occasion-aggregation clock is closed after the wedding date passes — the customer master’s occasion tag is archived and any post-wedding transaction from the same customer starts a fresh occasion clock (or falls under general per-person per-day and per-transaction tests only).

Common reconciliation breakages

• Section 269ST clause (c) occasion clock invisible at counter — staff clears each cash leg as under-cap on the single-transaction and single-day tests without visibility into the running occasion aggregate; the ₹2 lakh cap is breached across multiple visits and the breach surfaces only at month-end audit with Section 271DA exposure equal to the full cumulative cash.
• Cash advance at booking treated as sale consideration rather than deposit — a ₹25,000 to ₹75,000 cash wedding-order advance is booked against a proforma invoice with the reasoning that it is a sale receipt, not a deposit; the department reclassifies as a Section 269SS specified sum and imposes Section 271D 100% penalty on the retailer.
• Order-cancellation refund in cash to close the customer file cleanly — the retailer refunds a ₹40,000 order-cancellation advance in cash on grounds of operational convenience; Section 269T breach with Section 271E 100% penalty compounds the earlier Section 269SS breach on acceptance.
• PMLA CTR filing deferred to year-end reconciliation — cash transactions above the PMLA-notified threshold are logged but the CTR filing is batched to year-end rather than filed within the prescribed turnaround; FIU-IND enforcement notice cites the delay and monetary penalty is imposed.
• HUID capture skipped on smaller pieces — the counter clerk captures HUID on the primary gold-set piece but skips the HUID on smaller supplementary pieces on grounds of speed at billing; the piece-level audit chain breaks, and any subsequent 269ST or GST audit expands scope to reconstruct the missing chain from paper records.
• Section 273B reasonable-cause evidentiary pack assembled retrospectively — the retailer accepts an above-cap cash payment on grounds of a claimed customer emergency but does not record the customer statement, the CCTV timestamp, or the source-of-funds narrative at the moment of the transaction; the 273B defence during Section 271DA proceedings collapses for want of contemporaneous evidence.
• B2B jewellery order Section 206C(1H) TCS mis-applied concurrently with buyer’s Section 194Q TDS — the wholesale retailer collects 0.1% TCS on a corporate bulk order above ₹50 lakh even though the corporate buyer is a Section 194Q deductor; the buyer refuses the TCS collection, the retailer’s books carry a phantom TCS liability, and the CBDT clarification circular is cited in the resolution.
• GST tax-rate row split incorrectly aggregates HSN 7113 with SAC 998892 in a single line — the GSTR-1 filing merges gold-value and making-charges lines into a single 3% row rather than separating them into HSN 7113 at 3% and SAC 998892 at 5%; the return technically balances but the department’s system flags the anomaly and opens a scrutiny window.

How a reconciliation platform handles this

An audit-defensible jewellery-retail reconciliation platform holds a customer master keyed to PAN or Form 60 with occasion tagging, an invoice register with per-invoice consideration and tax-rate split (HSN 7113 at 3%, SAC 998892 at 5%, HSN 7102/7103 for diamond studding at 0.25%/3%, ancillary lines at 18%) and HUID capture per piece, and a settlement register with mode, reference and invoice link. At billing, the platform runs the Section 269ST three-clause test concurrently — same-day, single-transaction and same-occasion cash aggregates projected against the ₹2 lakh cap — and refuses cash the moment any clause is projected to breach. It runs the Section 269SS ₹20,000 test on any advance receipt and the Section 269T ₹20,000 test on any refund. On cash transactions crossing the PMLA-notified threshold, it generates the CTR filing task with buyer identity fields prepopulated and routes suspicious patterns to the STR review queue. It maintains the Section 273B evidentiary pack per exception transaction — customer statement, CCTV reference, ledger context and banking-of-cash narrative — so that if a Section 271DA proceeding is initiated, the defence pack is already assembled. The controller sees a monthly reconciliation pack per store and consolidated at chain level with a clear provenance trail from customer PAN to invoice to HUID per piece to settlement reference to Section 269ST cash-mode test result to PMLA event flag — the same evidence chain the assessing officer traces during audit. Full posture at reconciliation software India and the TDS side at TDS reconciliation software India.

For national jewellery chains running this at scale — where a mid-market chain across 200-plus stores may process 60,000 to 80,000 wedding-basket transactions in a single October-to-January wedding season with cumulative gross consideration well above ₹1,500 crore — the difference between platform-enforced counter discipline and manual store-level judgment is the difference between a clean CBDT Instruction 3/2017 scrutiny walkthrough and a stacked Section 271D + 271E + 271DA penalty case that compounds into PMLA scrutiny and GST audit. The five FAQs below address the operational questions Indian jewellery-retail CFOs and finance controllers ask most often when structuring the counter-to-reconciliation stack to withstand simultaneous Income-tax, PMLA, GST and BIS scrutiny in the same close cycle. Related audit-defensible scenarios are catalogued at jewellery reconciliation — 18 audit-defensible scenarios.

Terra Insight Editorial Team Reconciliation Infrastructure

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

Published 9 September 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