Section 206C(1F) Gold Jewellery Cash TCS + BIS Hallmarking India

A 4,200-square-foot retail jewellery showroom in T. Nagar, Chennai closes its second Saturday of November 2026 with 187 invoices, an aggregate day-end sale of ₹3.42 crore, and a payment-mode split of ₹18.6 lakh cash across 74 invoices, ₹1.94 crore card across 89 invoices, ₹87 lakh UPI across 42 invoices, ₹31 lakh cheque/RTGS across 9 invoices, and ₹11 lakh accepted as gold-exchange trade-in against 23 invoices. The finance controller pulls the compliance working and sees five flags from the day’s internal audit: 3 wedding customers who each visited three times on the same day and paid ₹80,000 to ₹1.2 lakh in cash across their multi-visit purchases have aggregate cash of ₹2.4 lakh, ₹2.8 lakh and ₹3.1 lakh respectively across the same event (per-event limb of Section 269ST breached on all three, Section 271DA 100% penalty exposure of ₹8.3 lakh in aggregate); 1 wholesale buyer PAN has crossed ₹52.6 lakh of FY-to-date purchases and the November invoice that took him above ₹50 lakh should have triggered Section 206C(1H) TCS at 0.1% on ₹2.6 lakh (₹260 uncollected); 2 diamond-studded articles sold at ₹4.8 lakh and ₹6.3 lakh were manufactured pre-16-June-2021 and never routed through a BIS-recognised AHC for hallmarking — no HUID on the ledger, BIS Act Section 29 exposure; the day’s cash total of ₹18.6 lakh across 74 customers needs a PMLA compliance sweep to check whether any single customer PAN aggregates above the S.O.4571(E) notified cash-transaction threshold requiring CTR filing on the FIU-IND FINnet portal; and one Form 27EQ working for the October quarter has a mismatched Form 27D certificate issued to a buyer whose PAN was captured with a single-character typo. This is Section 206C(1F) gold jewellery cash TCS BIS hallmarking India at production scale — and getting the four-statute overlap (269ST + 271DA + 206C(1H) + PMLA + BIS) all right on a single day’s close is the difference between a defensible monthly return and a Joint Commissioner proceeding.

Quick reference

The Section 206C sub-clause map — what each provision actually covers

The confusion around Section 206C sub-clauses is one of the most durable classification errors in the Indian jewellery sector’s tax working papers, and it derives from the fact that four adjacent sub-clauses (1D, 1F, 1H and the related Section 194Q) were introduced in a compressed policy window between 2012 and 2020 with overlapping legislative intent (anti-money-laundering, formalisation of large-value commerce, expansion of the TDS/TCS net). A jeweller’s AP or TCS working file that treats them as interchangeable produces routine misclassification — an invoice tagged with a “206C(1F) 1%” line when the operative section is 206C(1H) at 0.1% is a nine-times overstatement of the collection obligation, and the reverse error (tagging 206C(1H) at 0.1% when the transaction is in fact a motor-vehicle purchase attracting 206C(1F) at 1%) is a ten-times understatement.

Section 206C(1D) was introduced by Finance Act 2012 to require TCS at 1% on the cash sale of bullion (above ₹2 lakh) and jewellery (originally above ₹5 lakh, subsequently discussed for harmonisation with the bullion threshold in later amendment cycles). The provision was operationally live from 1 July 2012 to 31 March 2017. Finance Act 2017 omitted the sub-clause with effect from 1 April 2017. The reason for omission was clean: Section 269ST, introduced by the same Finance Act 2017 with the same effective date, prohibited any cash acceptance above ₹2 lakh from a single person in a day, in respect of a single transaction, or in respect of one event, with a Section 271DA 100% penalty on the receiver. Once the underlying transaction was penal, retaining a TCS provision that taxed the very transaction the law prohibited was redundant. For a jeweller’s ledger today, 206C(1D) remains a historical anchor — pre-2017 assessment years that are still open, reopened assessments under Section 148, or Section 263 revisionary proceedings can still reference the omitted sub-clause — but no current-year invoice attracts 206C(1D).

Section 206C(1F) was introduced by Finance Act 2016 to require TCS at 1% on the sale of any motor vehicle where the sale consideration is above ₹10 lakh. The sub-clause has always covered motor vehicles and nothing else. It is popularly conflated with the jewellery-cash provision because 206C(1F) and the 206C(1D) amendment cycle both landed within a narrow window of the Finance Act 2016 debate, and both were introduced in the same anti-cash policy framing. But structurally 206C(1F) is not, and has never been, a jewellery provision. A jeweller who sees “206C(1F)” in an incoming purchase order or vendor-side TCS notice should treat it as a misdirected classification and query the counterparty rather than accept the sub-clause as applying to a jewellery invoice.

Section 206C(1H) was introduced by Finance Act 2020 with effect from 1 October 2020 as the operative wide-net TCS provision on the sale of goods. Any seller whose gross receipts in the immediately preceding FY exceeded ₹10 crore collects TCS at 0.1% on the aggregate sale value above ₹50 lakh per buyer PAN in a financial year. The provision applies to any goods — jewellery, bullion, diamonds, machinery, textiles, chemicals — and runs in parallel with the buyer-side Section 194Q TDS at the same 0.1% rate. Where the buyer is separately obligated to deduct 194Q on the transaction, 194Q takes priority as a matter of statutory design and the seller’s 206C(1H) obligation is displaced for that invoice. For a mid-sized jewellery chain with turnover above ₹10 crore, 206C(1H) is the actual current-year TCS provision — not 206C(1D) and not 206C(1F).

The related Section 194Q (buyer-side TDS at 0.1% on aggregate purchases above ₹50 lakh per seller PAN, where the buyer’s gross receipts in the preceding FY exceed ₹10 crore) completes the framework. Between 206C(1H) and 194Q, the same 0.1% rate is applied once per transaction, with the buyer-side deduction taking priority.

Section 393 Sl. 41–44 of the Income-tax Act 2025 codifies the successor payment-code cluster for the 206C TCS sub-clauses — the migration from Form 27EQ under the legacy Act to the successor return form under the 2025 Act uses these Sl. numbers as the sub-clause identifiers, mapped to specific four-digit payment codes. A jeweller’s TCS system must maintain both the legacy sub-clause reference (206C(1D) historical, 206C(1F) motor-vehicle, 206C(1H) operative) and the Section 393 Sl. reference for post-migration returns. The complete code map is at TDS Section 206C TCS reconciliation.

Section 269ST and Section 271DA — the operative cash-acceptance prohibition

Section 269ST is the single sharpest constraint on a jeweller’s daily till operation, and its three-limb structure is what catches out AP teams who read it as a simple ₹2 lakh transactional ceiling. The section prohibits any person from receiving an amount of ₹2 lakh or more:

• (a) in aggregate from a single person in a day,
• (b) in respect of a single transaction, or
• (c) in respect of transactions relating to one event or occasion.

Each limb applies independently. A single customer paying ₹1.8 lakh cash for a chain on Saturday morning and ₹1.4 lakh cash for a matching bracelet on Saturday evening does not breach limb (b) on either transaction — but the aggregate of ₹3.2 lakh from the same person on the same day breaches limb (a), and Section 271DA imposes a 100% penalty (₹3.2 lakh) on the RECEIVER (the jeweller), not the payer. A wedding buyer paying ₹80,000 cash across three separate invoices at the same jeweller across three visits over ten days for their daughter’s marriage breaches limb (c) on the event even though no single invoice crosses ₹2 lakh and no single day crosses ₹2 lakh — the “one event” limb captures the whole ₹2.4 lakh cash aggregate. The permitted modes for above-₹2-lakh receipts are account-payee cheque, account-payee bank draft, electronic clearing system through a bank account, and prescribed electronic modes (which have been expanded over successive CBDT notifications to include RuPay, BHIM UPI, RTGS, IMPS and other electronic rails).

Section 271DA imposes a sum equal to the amount received in contravention as penalty on the receiver. The Joint Commissioner is the imposing authority. The section provides a limited defence — “good and sufficient reasons” for the contravention — but the case-law under 271DA has been narrow, and the reputational cost of a Joint Commissioner order (which is public and cross-referenced in GST and PMLA assessments) exceeds the pure ₹-value of the penalty for most established chains.

The three operational implications for a jewellery ledger:

1. Cash cap per invoice: no single invoice can accept cash above ₹1.99 lakh from a single customer. Most large chains today operate a hard system stop at ₹1.99 lakh with a manager-override flag that logs the exception for compliance review.
2. Cash aggregation per customer per day: the till software must aggregate cash across every invoice for a customer PAN (or a customer without a PAN, using name + mobile as the aggregation key) within the same calendar day, and stop cash acceptance where the running total would cross ₹1.99 lakh.
3. Cash aggregation per event: for a wedding, birthday, festival or family occasion where the same customer or a related-party group of customers is likely to return across multiple days, the ledger must carry an event tag (typically opened at the first visit with a customer-declared event date, closed at the wedding/event date + a defined tail window) and aggregate cash across every visit within the tag window. This is the hardest limb to enforce operationally, because the customer may not disclose the event on first visit, and related-party purchases (mother, sister, groom’s family) may be booked under different customer profiles. Prudent practice is a joint-account event tag opened when any invoice value exceeds ₹2 lakh in a purchase profile keyed to a wedding date or event date.

The full walkthrough for a wedding-scale purchase is at wedding purchase GST invoice vs cash audit defensibility.

PMLA reporting-entity designation — Notification S.O.4571(E) dated 28 December 2020

Notification S.O.4571(E) dated 28 December 2020 designates persons carrying on the business of dealing in precious metals and precious stones — jewellers, bullion dealers and gem dealers — as “reporting entities” under Section 2(1)(sa)(v) of the Prevention of Money-laundering Act 2002. The designation was effective for transactions where the value of one transaction or a series of related transactions in cash was above the notified threshold (originally ₹10 lakh, subsequently subject to sectoral rules and clarifications).

The obligations of a reporting entity are substantially more onerous than the Income-tax Act obligations for the same transaction. A jeweller who accepts a ₹9 lakh cash purchase (under both the 269ST ₹2-lakh cash-ceiling — because the sale was structured as multiple invoices in separately compliant increments, or accepted in the historical pre-2017 window under 206C(1D)) may still fall under the PMLA reporting threshold and be required to file a Cash Transaction Report on the FIU-IND FINnet portal.

The core standing obligations are:

• Principal Officer appointment: designate a senior person (typically the finance controller or a dedicated compliance manager) as the Principal Officer, register the person’s identity, contact and role on the FIU-IND FINnet portal, and update the registration on any change in the Principal Officer.
• Customer identification and beneficial-ownership record: for every transaction above the notified threshold, capture the customer’s PAN, address and identity proof, and — for a corporate or partnership buyer — the beneficial-ownership details identifying the natural persons who ultimately control the buyer entity.
• Five-year record retention: retain the customer identification, transaction documents and communications for five years from the date of the transaction, in a format retrievable on request from the FIU-IND or a designated authority.
• Annual reporting-entity confirmation: file the annual confirmation of reporting-entity registration and Principal Officer identity via the FINnet portal.

The event-triggered filings are:

• Cash Transaction Report (CTR): for any cash transaction (or series of connected cash transactions in a calendar month) above the notified value from a single customer, aggregate the transactions and file the CTR within the prescribed timeline. The aggregation rule catches the customer who splits a purchase across multiple visits or multiple family-member invoices to stay under the per-transaction ceiling — the FINnet portal is expected to receive an aggregated view of the customer’s cash footprint at the jeweller.
• Suspicious Transaction Report (STR): file within seven working days of forming the suspicion where the transaction pattern is inconsistent with the customer’s known profile, identification is refused/incomplete/inconsistent, or the transaction has no apparent economic or lawful purpose. STR filing has statutory whistleblower-protection and cannot be disclosed to the customer (tipping-off prohibition).
• Non-Profit Organisation Transaction Report (NTR): applies to purchase patterns tied to charitable organisations meeting specific criteria.
• Cross-Border Wire Transfer Report (CBWTR): applies to international remittance flows; less common in the retail jewellery context but relevant for NRI-facing wholesale bullion desks.

The monthly compliance close for a PMLA-designated jeweller therefore has a dedicated tab distinct from the Income-tax and GST close — Principal Officer sign-off on the CTR/STR log, FINnet portal filing acknowledgment, and cross-verification against the daily-till cash aggregate per customer PAN.

BIS Hallmarking Regulations — HUID mandatory since 16 June 2021

The Bureau of Indian Standards mandated hallmarking of gold jewellery of 14K, 18K, 20K, 22K, 23K and 24K purity in Phase I on 16 June 2021, covering 256 districts across India. Phase II extended the mandate to 32 additional districts on 4 April 2022, and Phase III further expanded it from 1 September 2023. In a mandatory-hallmarking district, no jeweller may lawfully sell an unhallmarked gold article of the notified purity grades to a retail customer.

Every hallmarked article carries a physical laser-struck mark showing four data points:

1. BIS logo — the standard mark of the Bureau of Indian Standards.
2. Purity fineness — three-digit numeric representing parts per thousand: 375 for 9K, 585 for 14K, 750 for 18K, 833 for 20K, 916 for 22K, 958 for 23K, 999 for 24K. The 22K “916 hallmark” is the most common in the Indian market.
3. HUID (Hallmark Unique ID) — a six-digit alphanumeric code unique to that specific article, assigned by the BIS-recognised AHC that hallmarked it.
4. AHC identification mark — the code of the Assaying and Hallmarking Centre that performed the assay and struck the hallmark.

The HUID is the key artefact for both the customer and the jeweller. A customer verifies the HUID on the BIS Care mobile app by entering the six-digit code — the app returns the article’s registered weight, purity, hallmarking date, AHC name and jeweller registration number, providing a portable independent authentication that the article’s stated purity has been laboratory-verified. For the jeweller, the HUID is the article’s audit fingerprint — every SKU in the inventory ledger must carry its HUID, and the HUID is what a BIS inspector reads during a market surveillance visit to confirm compliance.

The jeweller-side operational stack:

• BIS Registration Certificate: the jeweller obtains a Registration Certificate from BIS, renewable periodically, that authorises the jeweller to sell hallmarked articles. The registration number is embedded in the HUID lookup on the BIS Care app.
• AHC routing: every article is sent to a BIS-recognised AHC for assay and hallmarking before it reaches the retail floor. The AHC issues a receipt with the article’s assay reading, purity, weight and the assigned HUID.
• AHC vendor master: a mid-sized chain typically routes through 3–8 AHCs across its geographic footprint, and the AHC vendor master must be reconciled monthly against the BIS-published list of recognised centres — if an AHC’s recognition is suspended or withdrawn, articles hallmarked at that AHC in the interim window may be treated as invalidly hallmarked.
• Older unhallmarked stock: articles manufactured or acquired before 16 June 2021 that remain in inventory in a Phase I district cannot be lawfully sold as-is. The lawful lanes are (a) return the stock to an AHC for retrospective hallmarking (the AHC melts/re-tests and issues a fresh HUID against the re-manufactured article), (b) melt down and re-manufacture with fresh hallmarking, or (c) transfer to inventory in a non-mandatory market for lawful sale in that market. A customer-disclosure “sold as unhallmarked” is not a defence in a mandatory district.
• Section 29 penalty: sale of an unhallmarked article in a mandatory district attracts imprisonment up to one year or fine up to ₹1 lakh or five times the value of the goods, whichever is higher.

The cost-accounting overlay — hallmarking charges per article, AHC vendor invoice reconciliation, and inventory-carrying cost of pre-2021 stock — is at hallmarking BIS charges cost accounting.

Worked example — a ₹4.8 lakh diamond-studded gold set purchase

The Chennai showroom in the opening paragraph processes a specific customer transaction on the same Saturday of November 2026. The customer, whose PAN and Aadhaar are captured at first visit, wants to buy a diamond-studded 22K gold set (necklace + matching earrings) for a family wedding scheduled 26 December 2026. The composition of the ₹4,80,000 invoice is: 22K gold content 42 grams at ₹6,500/gram = ₹2,73,000; diamond content 1.85 carats at ₹85,000/carat = ₹1,57,250; making charges at 15% on the metal portion = ₹40,950; net of a rounding adjustment gives ₹4,80,000 net invoice value before GST (illustrative figures — cross-verify against your own metal-rate, stone-rate, making-charge policy and GST-inclusive/exclusive convention).

Illustrative — the split, rates and compliance points are representative of the operating pattern for a Tier-1 city jewellery showroom, not actual chain data. Cross-verify against your own customer master, invoice ledger and FY-to-date aggregates before action.

Statutory grid on the invoice:

• GST: 3% on the total invoice value under HSN 7113 (gold jewellery finished) = ₹14,400, taking the customer-side gross to ₹4,94,400. The diamond-studding does NOT pull the invoice into a separate HSN — the composite article is invoiced under 7113 gold jewellery. Cross-tag at jewellery GST 3%/5%/18% mixed invoice reconciliation and bullion vs retail GST supply classification.
• Section 206C(1H): the customer’s FY-to-date aggregate at this jeweller is ₹8.4 lakh before this invoice, ₹13.24 lakh after — well below the ₹50 lakh threshold. No 206C(1H) TCS on this invoice.
• Section 206C(1F): not applicable — this is jewellery, not a motor vehicle.
• Section 206C(1D): OMITTED w.e.f. 1 April 2017. Not applicable.

Payment-split alternatives and 269ST analysis:

Alternative A — customer wants to pay ₹1.9 lakh cash + ₹3.04 lakh card: The ₹1.9 lakh cash is below the ₹2 lakh single-transaction cash ceiling under 269ST limb (b). But the shop must aggregate against the customer’s daily cash across every invoice — if the customer’s father visited the same showroom that morning under the same PAN or the same event tag and paid ₹40,000 cash for a chain, the day’s aggregate for the customer’s household reaches ₹2.3 lakh and 269ST limb (a) breaches. The event limb (c) also activates because the customer has declared the December 2026 wedding — any subsequent cash visit before or immediately after the wedding aggregates into the event.

Alternative B — customer pays ₹1.5 lakh cash + ₹3.44 lakh card: The cash leg is safely below all three limbs on this specific invoice. But the ₹1.5 lakh enters both the daily cash aggregate for the customer PAN and the event aggregate. If two future visits before the wedding each add ₹40,000 cash (rings for the family), the ₹2.3 lakh event aggregate breaches limb (c).

Alternative C — customer pays ₹4.94 lakh entirely by card/UPI: All three limbs of 269ST fall away. The invoice is fully compliant on cash-acceptance grounds. PMLA CTR filing is not triggered (no cash component). Only the 206C(1H) aggregate ledger and the BIS HUID check remain.

BIS Hallmarking on the article:

The 22K gold set carries three HUIDs (necklace, left earring, right earring — each is a distinct article), each a six-digit alphanumeric assigned by the BIS-recognised AHC that hallmarked the pieces. The invoice line item records the HUID against the SKU. The customer receives a Hallmarking Certificate from the AHC as an insert with the invoice, and the customer independently verifies each HUID on the BIS Care app before leaving the showroom (a growing customer expectation in Tier-1 cities). The physical laser marks on each article show BIS logo + 916 (22K fineness) + six-digit HUID + AHC mark.

PMLA compliance sweep at day-end:

The Chennai showroom’s PMLA compliance workflow at day-end aggregates cash across every invoice by customer PAN. This customer’s day-end cash total (under Alternative A, ₹1.9 lakh) does not by itself cross the S.O.4571(E) notified threshold on a single-day basis. But the running-month cash aggregate for the PAN is checked — if the customer has visited three times in the month and paid cash on each visit, the monthly cash aggregate may cross the CTR threshold and require filing on the FINnet portal within the prescribed timeline. The Principal Officer signs off the daily compliance summary and files any CTR on the FINnet portal by the prescribed month-end date.

Cross-audit points:

1. The ₹4,80,000 invoice sits below the 206C(1H) crossing threshold for this specific customer but the FY-to-date ledger must be updated so future invoices can trigger the 0.1% TCS at the correct crossing point.
2. The event tag opened at the customer’s first-visit declaration (December 2026 wedding) must remain open across every subsequent visit by the customer or a related-party family member using the same wedding-event key, so limb (c) of 269ST is enforced across the full wedding window.
3. The three HUIDs (necklace + two earrings) must be independently recorded — each is a separately hallmarked article and each has its own registered weight, purity and AHC assay reading on the BIS database.
4. If the customer sold old gold in exchange as part of the purchase, the gold-exchange leg attracts Section 194IA-adjacent reconciliation on the buyer-side and creates a customer-side capital-gain reporting flag; the exchange value adjusts the net cash-flow but does NOT reduce the invoice value for 269ST cash-ceiling purposes.
5. The PMLA compliance sweep captures the ₹1.9 lakh (or ₹1.5 lakh under Alternative B) cash into the customer’s monthly cash ledger for CTR aggregation regardless of the specific-transaction compliance status.

The full sub-clause map is at TDS Section 206C TCS reconciliation; confirm the specific successor payment code for the 206C(1H) collection via the Section 393 payment-code finder.

Common reconciliation breakages

• 206C(1F) tagged on a jewellery invoice — an incoming purchase order from a wholesale buyer or a vendor-side TCS notice cites “Section 206C(1F) at 1%” on a jewellery transaction, and the jeweller’s AP or TCS working file accepts the classification and collects 1% TCS. The correct provision is 206C(1H) at 0.1% (nine-times overstatement) and the excess collected TCS creates a reversal-and-refund workflow with the buyer and a Form 27EQ correction return.
• Section 269ST per-event limb missed — a wedding customer pays ₹1.6 lakh cash on visit 1, ₹1.4 lakh cash on visit 2 six days later, and ₹0.8 lakh cash on visit 3 the day before the wedding. No single visit breaches limb (b), no single day breaches limb (a), but the ₹3.8 lakh event aggregate breaches limb (c). Section 271DA 100% penalty of ₹3.8 lakh on the jeweller on assessment.
• 206C(1H) crossing invoice under-collected — a wholesale buyer’s FY aggregate crosses ₹50 lakh on a specific invoice, but the TCS module was set to fire on the invoice VALUE above ₹50 lakh (whole-invoice trigger) rather than on the INCREMENTAL amount above ₹50 lakh. The 0.1% is collected on an inflated base, over-remitting to the government and creating a buyer-side dispute on the Form 27D certificate.
• BIS HUID not captured on invoice line item — an article is sold with a physical hallmark on the piece, but the invoice line and the inventory-out record do not carry the six-digit HUID. On BIS market surveillance, the mismatch between the physical article’s HUID and the invoice’s blank HUID field is treated as an evidence gap and can escalate to a Section 29 investigation on the specific SKU.
• AHC recognition-suspended in interim window — the jeweller routed a batch of articles through an AHC that had its BIS recognition suspended for 45 days during that quarter. Articles hallmarked at the AHC in the suspension window carry HUIDs that fail the BIS Care app lookup (the app returns “AHC not recognised on hallmarking date”). Customer trust and Section 29 exposure both bite.
• PMLA CTR aggregation missed across visits — a customer visits the showroom on 8, 14 and 22 November 2026 and pays ₹3.2 lakh, ₹1.9 lakh and ₹2.8 lakh cash across the three visits under separate invoices (each below the 269ST per-transaction ceiling but the first and third breaching limb (b) on their own). The daily cash aggregate for the PAN is ₹3.2 lakh on 8 November (269ST limb (a) breach), the monthly cash aggregate is ₹7.9 lakh (PMLA CTR filing threshold typically crossed). No CTR filed on the FINnet portal. On FIU-IND audit, the Principal Officer faces enforcement proceedings.
• Form 27D certificate PAN typo — the quarterly Form 27EQ carries the correct PAN, but the Form 27D certificate issued to the buyer has a single-character typo. The buyer cannot claim the TCS credit in the Form 26AS / AIS lookup and files a rectification request; the jeweller reissues Form 27D and files a correction return, but the credit lag creates a working-capital irritation for the buyer that ripples into future purchase-price negotiations.
• Older unhallmarked stock sold “as-is with disclosure” — a jeweller in a Phase I mandatory district maintains pre-2021 unhallmarked inventory and continues to sell it with a customer disclosure “this article is not hallmarked, buyer is aware”. The disclosure is not a defence under the BIS Act — the sale is a Section 29 contravention on each transaction. The remedy is retrospective hallmarking through an AHC or melt-and-re-manufacture.

How a reconciliation platform handles this

An audit-defensible jeweller reconciliation platform holds a customer master keyed to PAN (with a fallback name+mobile aggregation key for cash-only walk-ins), tracks payment mode at invoice-line granularity, and enforces the Section 269ST three-limb cash-ceiling check at invoice generation — per-person-per-day aggregation, per-transaction ceiling, and per-event aggregation using a wedding/event tag opened at first customer declaration. It maintains a FY-to-date sale ledger per buyer PAN with the ₹50 lakh Section 206C(1H) threshold rule and fires the 0.1% TCS trigger on the incremental amount above ₹50 lakh on the crossing invoice, then on the full value of subsequent FY invoices, with automatic priority-override where the buyer has separately deducted Section 194Q on the same transaction. It ingests the BIS Care HUID lookup for every hallmarked article at inventory-in, stores the AHC identification against the SKU with the BIS-recognition-window check, and blocks invoice generation for any 14K/18K/20K/22K/23K/24K article that lacks a valid HUID in a mandatory-hallmarking district. It runs a PMLA compliance loop with a per-customer-PAN cash-aggregate ledger against the S.O.4571(E) notified threshold, escalates to the Principal Officer for CTR-filing on the FIU-IND FINnet portal, and preserves the five-year retention with a versioned audit trail. Monthly close ties Form 281 challan deposits to the books TCS payable, generates the quarterly Form 27EQ return with per-buyer payment-code breakup, issues Form 27D to each buyer, and matches against the buyer’s Form 26AS / AIS credit acknowledgment. Full posture at TDS reconciliation software India and end-to-end at reconciliation software India.

For jewellery chains running this at scale — where a mid-sized four-showroom chain in a Tier-1 city may process 800+ invoices a day at wedding season across 500+ distinct customer PANs with the full four-way statute overlap (269ST + 206C(1H) + PMLA + BIS) live on every above-threshold invoice — the difference between manual compliance-checklist discipline and platform-enforced statute routing is the difference between a defensible quarterly Form 27EQ + monthly CTR + annual BIS Registration renewal cycle and a Joint Commissioner Section 271DA proceeding with an FIU-IND enforcement notice and a BIS Section 29 investigation running in parallel. The five FAQs below address the operational questions Indian jeweller CFOs and finance controllers ask most often when structuring the cash-acceptance stack to withstand simultaneous income-tax, PMLA and BIS scrutiny.

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